status of nm_system_flush_arp_cache()
While converting stuff to libnl, I've noticed that nm_system_flush_arp_cache() is currently unused. Should it be removed ? regards, Benoit -- :wq ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
[PATCH] [3/3] Use libnl instead of iproute/AF_PACKET (nm_system_device_set_ip4_route)
Removes the AF_INET implementation of nm_system_device_set_ip4_route,
reimplement it with libnl.
The fifth argument is now the prefixlen, and no longer the netmask (it
was always called with 255.255.255.255)
diff -r a8b0359dcc78 src/NetworkManagerSystem.c
--- a/src/NetworkManagerSystem.cFri Apr 18 00:05:24 2008 -0400
+++ b/src/NetworkManagerSystem.cFri Apr 18 20:02:54 2008 -0400
@@ -69,16 +69,18 @@
static gboolean
nm_system_device_set_ip4_route (const char *iface,
NMIP4Config *iface_config,
-int ip4_gateway,
-int ip4_dest,
-int ip4_netmask,
+guint32 ip4_gateway,
+guint32 ip4_dest,
+int prefix,
int mss)
{
- int fd, err;
- gbooleansuccess = FALSE;
- struct rtentry rtent;
- struct sockaddr_in *p;
- struct rtentry rtent2;
+ gboolean success = FALSE;
+ struct rtnl_route * route = NULL;
+ struct rtnl_route * route2 = NULL;
+ struct nl_handle * nlh = NULL;
+ struct nl_addr* gw_addr = NULL;
+ struct nl_addr* dest_addr = NULL;
+ int err, iface_idx;
/*
* Zero is not a legal gateway and the ioctl will fail. But zero is a
@@ -97,86 +99,87 @@
return TRUE;
- fd = socket (AF_PACKET, SOCK_PACKET, htons (ETH_P_ALL));
- if (fd < 0) {
- nm_warning ("couldn't open control socket.");
- return FALSE;
+ nlh = nm_netlink_get_default_handle ();
+ g_return_val_if_fail (nlh != NULL, FALSE);
+
+ iface_idx = nm_netlink_iface_to_index (iface);
+ g_return_val_if_fail (iface_idx >= 0, FALSE);
+
+ route = rtnl_route_alloc ();
+ g_return_val_if_fail (route != NULL, FALSE);
+
+ rtnl_route_set_oif (route, iface_idx);
+
+ gw_addr = nl_addr_build (AF_INET, &ip4_gateway, sizeof (ip4_gateway));
+ if (gw_addr == NULL)
+ goto out;
+ rtnl_route_set_gateway (route, gw_addr);
+
+ dest_addr = nl_addr_build (AF_INET, &ip4_dest, sizeof (ip4_dest));
+ if (dest_addr == NULL)
+ goto out;
+ nl_addr_set_prefixlen (dest_addr, prefix);
+ rtnl_route_set_dst (route, dest_addr);
+ nl_addr_put (dest_addr);
+
+ if (mss) {
+ if (rtnl_route_set_metric (route, RTAX_ADVMSS, mss) < 0)
+ goto out;
}
- memset (&rtent, 0, sizeof (struct rtentry));
- p = (struct sockaddr_in *) &rtent.rt_dst;
- p->sin_family = AF_INET;
- p->sin_addr.s_addr = ip4_dest;
- p = (struct sockaddr_in *)
&rtent.rt_gateway;
- p->sin_family = AF_INET;
- p->sin_addr.s_addr = ip4_gateway;
- p = (struct sockaddr_in *)
&rtent.rt_genmask;
- p->sin_family = AF_INET;
- p->sin_addr.s_addr = ip4_netmask;
- rtent.rt_dev= (char *)iface;
- rtent.rt_metric = 1;
- rtent.rt_window = 0;
- rtent.rt_flags = RTF_UP | RTF_GATEWAY | (rtent.rt_window ?
RTF_WINDOW : 0);
-
- if (mss) {
- rtent.rt_flags |= RTF_MTU;
- rtent.rt_mtu = mss;
- }
-
- err = ioctl (fd, SIOCADDRT, &rtent);
+ err = rtnl_route_add (nlh, route, 0);
if (err == 0) {
/* Everything good */
success = TRUE;
goto out;
}
- if (errno != ENETUNREACH) {
+ if (err != ESRCH) {
nm_warning ("Failed to set IPv4 default route on '%s': %s",
iface,
- strerror (errno));
+ nl_geterror ());
goto out;
}
/* Gateway might be over a bridge; try adding a route to gateway first
*/
- memset (&rtent2, 0, sizeof(struct rtentry));
- p = (struct sockaddr_in *)&rtent2.rt_dst;
- p->sin_family = AF_INET;
- p = (struct sockaddr_in
*)&rtent2.rt_gateway;
- p->sin_family = AF_INET;
- p->sin_addr.s_addr = ip4_gateway;
- p = (struct sockaddr_in
*)&rtent2.rt_genmask;
- p->sin_family = AF_INET;
- p->sin_addr.s_addr = 0x;
- rtent2.rt_dev = (char *)iface;
- rtent2.rt_metric= 0;
- rtent2.rt_flags = RTF_UP | RTF_HOST;
+ route2 = rtnl_route_alloc ();
+ if (route2 == NULL)
+ goto out;
+ rtnl_route_set_oif (route2, iface_idx);
+ rtnl_route_set_dst (route2, gw_addr);
if (mss)
[PATCH] [2/3] Use libnl instead of iproute/AF_PACKET (nm_system_device_replace_default_ipv4_route)
(depends on the cleanup of the frugalware backend)
Remove nm_system_device_replace_default_ip4_route from all
backends, implement it with libnl.
diff -r 44a2c48934ef src/NetworkManagerPolicy.c
--- a/src/NetworkManagerPolicy.cWed Apr 16 00:35:47 2008 -0400
+++ b/src/NetworkManagerPolicy.cFri Apr 18 20:04:30 2008 -0400
@@ -83,12 +83,12 @@
a serial device with ppp interface, so route all the traffic to it.
*/
ip_iface = nm_device_get_ip_iface (new);
if (strcmp (ip_iface, nm_device_get_iface (new))) {
- nm_system_device_replace_default_route (ip_iface, 0, 0);
+ nm_system_device_replace_default_ip4_route (ip_iface, 0, 0);
} else {
NMIP4Config *config;
config = nm_device_get_ip4_config (new);
- nm_system_device_replace_default_route (ip_iface,
nm_ip4_config_get_gateway (config),
+ nm_system_device_replace_default_ip4_route (ip_iface,
nm_ip4_config_get_gateway (config),
nm_ip4_config_get_mss
(config));
}
}
diff -r 44a2c48934ef src/NetworkManagerSystem.c
--- a/src/NetworkManagerSystem.cWed Apr 16 00:35:47 2008 -0400
+++ b/src/NetworkManagerSystem.cFri Apr 18 20:04:30 2008 -0400
@@ -347,7 +347,7 @@
nm_system_device_flush_ip4_routes_with_iface (iface);
if (g_slist_length (routes) == 0) {
- nm_system_device_replace_default_route (iface, 0, 0);
+ nm_system_device_replace_default_ip4_route (iface, 0, 0);
} else {
GSList *iter;
@@ -500,3 +500,44 @@
rtnl_route_put (route);
}
+/*
+ * nm_system_replace_default_ip4_route
+ *
+ * Replace default IPv4 route with one via the current device
+ *
+ */
+void
+nm_system_device_replace_default_ip4_route (const char *iface, guint32 gw,
guint32 mss)
+{
+ struct rtnl_route * route;
+ struct nl_handle * nlh;
+ struct nl_addr* gw_addr;
+ int iface_idx;
+
+ nlh = nm_netlink_get_default_handle ();
+ g_return_if_fail (nlh != NULL);
+
+ route = rtnl_route_alloc();
+ g_return_if_fail (route != NULL);
+
+ iface_idx = nm_netlink_iface_to_index (iface);
+ if (iface_idx < 0)
+ goto out;
+ rtnl_route_set_oif (route, iface_idx);
+
+ if (gw > 0) {
+ if (!(gw_addr = nl_addr_build (AF_INET, &gw, sizeof (gw
+ goto out;
+ rtnl_route_set_gateway (route, gw_addr);
+ nl_addr_put (gw_addr);
+ }
+
+ if (mss > 0)
+ if (rtnl_route_set_metric (route, RTAX_ADVMSS, mss) < 0)
+ goto out;
+
+ rtnl_route_add (nlh, route, NLM_F_REPLACE);
+out:
+ rtnl_route_put (route);
+}
+
diff -r 44a2c48934ef src/NetworkManagerSystem.h
--- a/src/NetworkManagerSystem.hWed Apr 16 00:35:47 2008 -0400
+++ b/src/NetworkManagerSystem.hFri Apr 18 20:04:30 2008 -0400
@@ -38,7 +38,7 @@
void nm_system_device_flush_ip4_routes
(NMDevice *dev);
void nm_system_device_flush_ip4_routes_with_iface(const
char *iface);
-void nm_system_device_replace_default_route (const char
*iface,
+void nm_system_device_replace_default_ip4_route (const
char *iface,
guint32 gw,
guint32 mss);
diff -r 44a2c48934ef src/backends/NetworkManagerArch.c
--- a/src/backends/NetworkManagerArch.c Wed Apr 16 00:35:47 2008 -0400
+++ b/src/backends/NetworkManagerArch.c Fri Apr 18 20:04:30 2008 -0400
@@ -65,20 +65,6 @@
void nm_system_init (void)
{
nm_generic_init ();
-}
-
-/*
- * nm_system_device_replace_default_route
- *
- * Add default route to the given device
- *
- */
-void
-nm_system_device_replace_default_route (const char *iface,
-guint32 gw,
-guint32 mss)
-{
- nm_generic_device_replace_default_route (iface, gw, mss);
}
/*
diff -r 44a2c48934ef src/backends/NetworkManagerDebian.c
--- a/src/backends/NetworkManagerDebian.c Wed Apr 16 00:35:47 2008 -0400
+++ b/src/backends/NetworkManagerDebian.c Fri Apr 18 20:04:30 2008 -0400
@@ -57,20 +57,6 @@
}
/*
- * nm_system_device_replace_default_route
- *
- * Add default route to the given device
- *
- */
-void
-nm_system_device_replace_default_route (const char *iface,
-guint32 gw,
-guint32 mss)
-{
- nm_generic_device_replace_default_route (iface, gw, mss);
-}
-
-/*
* nm_system_device_flush_ip4_addresses
*
* Flush all network addresses associated with a network device
diff -r 44a2c48934ef src/backends/NetworkManagerFrugalware.c
--- a/src/backends/NetworkM
[PATCH] [1/3] Use libnl instead of iproute/AF_PACKET (nm_system_device_add_route_via_device_with_iface)
(depends on the cleanup of the frugalware backend)
Remove nm_system_device_add_ip4_route_via_device_with_iface from all
backends, implement it with libnl.
Removes validate_ip4_route since we don't call system anymore
diff -r 630520f22ebb src/NetworkManagerSystem.c
--- a/src/NetworkManagerSystem.cTue Apr 15 20:11:30 2008 -0400
+++ b/src/NetworkManagerSystem.cWed Apr 16 00:35:47 2008 -0400
@@ -52,7 +52,11 @@
#include "nm-utils.h"
#include "nm-netlink.h"
+/* Because of a bug in libnl, rtnl.h should be included before route.h */
+#include
+
#include
+#include
#include
#include
#include
@@ -284,83 +288,6 @@
return success;
}
-
-/*
- * validate_ip4_route
- *
- * Ensure that IP4 routes are in the correct format
- *
- */
-static char *validate_ip4_route (const char *route)
-{
- char * ret = NULL;
- char * temp = NULL;
- int slash_pos = -1;
- char * p = NULL;
- int len, i;
- int dot_count = 0;
- gbooleanhave_slash = FALSE;
- struct in_addr addr;
-
- g_return_val_if_fail (route != NULL, NULL);
-
- len = strlen (route);
- /* Minimum length, ie 1.1.1.1/8 */
- if (len < 9)
- return NULL;
-
- for (i = 0; i < len; i++)
- {
- /* Ensure there is only one slash */
- if (route[i] == '/')
- {
- if (have_slash)
- goto out;
-
- have_slash = TRUE;
- slash_pos = i;
- continue;
- }
-
- if (route[i] == '.')
- {
- if (dot_count >= 4)
- goto out;
-
- dot_count++;
- continue;
- }
-
- if (!isdigit (route[i]))
- goto out;
- }
-
- /* Make sure there is at least one slash and 3 dots */
- if (!have_slash || !slash_pos || (dot_count != 3))
- goto out;
-
- /* Valid IP address part */
- temp = g_strdup (route);
- temp[slash_pos] = '\0';
- memset (&addr, 0, sizeof (struct in_addr));
- if (inet_aton (temp, &addr) == 0)
- goto out;
-
- /* Ensure the network # is valid */
- p = temp + slash_pos + 1;
- i = (int) strtol (p, NULL, 10);
- if ((i < 0) || (i > 32))
- goto out;
-
- /* Success! */
- ret = g_strdup (route);
-
-out:
- g_free (temp);
- return ret;
-}
-
-
/*
* nm_system_vpn_device_set_from_ip4_config
*
@@ -424,22 +351,8 @@
} else {
GSList *iter;
- for (iter = routes; iter; iter = iter->next) {
- char *valid_ip4_route;
-
- /* Make sure the route is valid, otherwise it's a
security risk as the route
-* text is simply taken from the user, and passed
directly to system(). If
-* we did not check the route, think of:
-*
-* system("/sbin/ip route add `rm -rf /` dev eth0")
-*
-* where `rm -rf /` was the route text. As UID 0
(root), we have to be careful.
-*/
- if ((valid_ip4_route = validate_ip4_route ((char *)
iter->data))) {
-
nm_system_device_add_route_via_device_with_iface (iface, valid_ip4_route);
- g_free (valid_ip4_route);
- }
- }
+ for (iter = routes; iter; iter = iter->next)
+ nm_system_device_add_ip4_route_via_device_with_iface
(iface, (char *) iter->data);
}
out:
@@ -553,5 +466,37 @@
return success;
}
+/*
+ * nm_system_device_add_ip4_route_via_device_with_iface
+ *
+ * Add route to the given device
+ *
+ */
+void nm_system_device_add_ip4_route_via_device_with_iface (const char *iface,
const char *addr)
+{
+ struct rtnl_route * route;
+ struct nl_handle * nlh;
+ struct nl_addr* dst;
+ int iface_idx;
+ nlh = nm_netlink_get_default_handle ();
+ g_return_if_fail (nlh != NULL);
+ route = rtnl_route_alloc ();
+ g_return_if_fail (route != NULL);
+
+ iface_idx = nm_netlink_iface_to_index (iface);
+ if (iface_idx < 0)
+ goto out;
+ rtnl_route_set_oif (route, iface_idx);
+
+ if (!(dst = nl_addr_parse (addr, AF_INET)))
+ goto out;
+ rtnl_route_set_dst (route, dst);
+ nl_addr_put (dst);
+
+ rtnl_route_add (nlh, route, 0);
+out:
+ rtnl_route_put (route);
+}
+
diff -r 630520f22ebb src/NetworkManagerSystem.h
--- a/src/NetworkManagerSystem.hTue Apr 15 20:11:30 2
Re: Wireless Chips
Herbert Taylor wrote: > I just finished reading the Network manager story in the Red Hat > Magazine. It had a list of chips that work with Linux and a list that > don't. > Are these chips the kind that are in the computer or are they PCMCIA type. > I have a Dell Inspiron B130, that has a broadcom wireless card. Haven't > found a way to use it on wireless. Does anyone know of a PCMCIA card > that would work in its place? I am using Fedora 8 which works very well > on DSL. I will be doing some traveling this summer and would like to be > able to use the wireless such as in airports, etc. These wireless chips come packaged in many forms. In modern laptops, they are on a mini-PCI express card. In slightly older laptops, they are on a mini-PCI card. They also are built into PCMCIA cards. For desktops, they are built on a PCI card. In most cases, they are part of something that plugs in, but there are probably motherboards that have them soldered on. If you send the part of the output of a 'lspci -v' command that refers to the wireless card, I can tell you if your Broadcom card is supported. Unless your B130 is very recent, that device should work. Larry ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Wireless Chips
I just finished reading the Network manager story in the Red Hat Magazine. It had a list of chips that work with Linux and a list that don't. Are these chips the kind that are in the computer or are they PCMCIA type. I have a Dell Inspiron B130, that has a broadcom wireless card. Haven't found a way to use it on wireless. Does anyone know of a PCMCIA card that would work in its place? I am using Fedora 8 which works very well on DSL. I will be doing some traveling this summer and would like to be able to use the wireless such as in airports, etc. Herb Taylor ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM not detecting device when kernel module unloaded
Hi! > > otherwise it works all ok. Ie, rmmod ipw2200 && ./NetworkManager > > fails > > to detect my wireless interface but modprobe ipw2200 && > > ./NetworkManager sees the wireless device. Is this a bug or a > > feature? > > What version of NM? Current SVN trunk. > Seems like a bug. Can you grab the syslog output for around the time > that you rmmod the device? Also run 'lshal --monitor' before you > rmmod > it, hit return a bunch of times in that terminal after you do, then > modprobe it again and send that log too. > > It's a chain of udev -> hal -> NetworkManager, and we need to figure > out if HAL is sending out the device removal event. Um, please notice that I was doing rmmod/modprobe while NM was not running, so thing I was asking was whether NM should possibly init devices which have no kernel modules loaded when starting up. If I do rmmod/modprobe while NM is running then everything works like charm. Thanks. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Connection problems with wpa_supplicant already running
Hi! > > When starting up NetworkManager, wireless connection can't be > > established. I found out that I need to stop NM, stop running > > wpa_supplicant (started during boot while networking was being > started) > > and then start NM and all works well. What is weird that if I > restart > > NM then everything still works (even though w_s was running). After > > testing it seems that there are connection problems only if 1) > > wpa_supplicant is already running when starting NM and 2) > > wpa_supplicant was not started by NM (but while doing "service > network > > restart"). > > What are the contents of your /etc/sysconfig/wpa_supplicant file? > What's the command line that wpa_supplicant is started with as > reported > by 'ps aux' ? Sorry for the noise, this gotta be some local hickup, every now and this works, sometimes it fails, I can't reproduce it reliably after all. (I was using unsecured network with default F8 w_s config). Thanks. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Connection problems with wpa_supplicant already running
Hi! > > When starting up NetworkManager, wireless connection can't be > > established. I found out that I need to stop NM, stop running > > wpa_supplicant (started during boot while networking was being > started) > > and then start NM and all works well. What is weird that if I > restart > > NM then everything still works (even though w_s was running). After > > testing it seems that there are connection problems only if 1) > > wpa_supplicant is already running when starting NM and 2) > > wpa_supplicant was not started by NM (but while doing "service > network > > restart"). > > Well the simple answer is that NM executes wpa_supplicant itself and > supplies appropriate arguments so you either have the NM daemons > running > (which allows the applet to appear and be used) or you stop them and > start the wpa_supplicant daemon. > > Having all three daemons running together is a recipe for problems, > if not actually disaster. Well, now when I boot my machine network is dead due to reasons above so I'm wondering how should I fix this? It's more than a bit clumsy to kill wpa_supplicant and restart NM every time after booting the machine.. Cheers! Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Connection problems with wpa_supplicant already running
On Fri, 2008-04-18 at 08:05 -0700, Daniel Qarras wrote: > Hi, > > this is a weird failure scenario with current SVN trunk but I am able > to reproduce it every time so I'm wondering is this a local hickup or > what. I'm using Fedora 8 + latest updates + NM SVN trunk. The problem > is: > > When starting up NetworkManager, wireless connection can't be > established. I found out that I need to stop NM, stop running > wpa_supplicant (started during boot while networking was being started) > and then start NM and all works well. What is weird that if I restart > NM then everything still works (even though w_s was running). After > testing it seems that there are connection problems only if 1) > wpa_supplicant is already running when starting NM and 2) > wpa_supplicant was not started by NM (but while doing "service network > restart"). What are the contents of your /etc/sysconfig/wpa_supplicant file? What's the command line that wpa_supplicant is started with as reported by 'ps aux' ? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM not detecting device when kernel module unloaded
On Fri, 2008-04-18 at 08:11 -0700, Daniel Qarras wrote: > Hi, > > it seems that when starting NM while the kernel module for a network > device has been unloaded, the device is not initialized/detected by NM, > otherwise it works all ok. Ie, rmmod ipw2200 && ./NetworkManager fails > to detect my wireless interface but modprobe ipw2200 && > ./NetworkManager sees the wireless device. Is this a bug or a feature? What version of NM? Seems like a bug. Can you grab the syslog output for around the time that you rmmod the device? Also run 'lshal --monitor' before you rmmod it, hit return a bunch of times in that terminal after you do, then modprobe it again and send that log too. It's a chain of udev -> hal -> NetworkManager, and we need to figure out if HAL is sending out the device removal event. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM not detecting device when kernel module unloaded
Daniel Qarras wrote: > Hi, > > it seems that when starting NM while the kernel module for a network > device has been unloaded, the device is not initialized/detected by NM, > otherwise it works all ok. Ie, rmmod ipw2200 && ./NetworkManager fails > to detect my wireless interface but modprobe ipw2200 && > ./NetworkManager sees the wireless device. Is this a bug or a feature? > Why would it be a bug? It's expected that boot scripts should modprobe hardware that's present, if you deliberately unload the module then NM does not load it itself because that is the job of other sub-systems. The only reason you might unload a module is if you have USB attached wireless, if it's built in and not easily removable then the module should always be loaded. -- Brian ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Connection problems with wpa_supplicant already running
Daniel Qarras wrote: > Hi, > > this is a weird failure scenario with current SVN trunk but I am able > to reproduce it every time so I'm wondering is this a local hickup or > what. I'm using Fedora 8 + latest updates + NM SVN trunk. The problem > is: > > When starting up NetworkManager, wireless connection can't be > established. I found out that I need to stop NM, stop running > wpa_supplicant (started during boot while networking was being started) > and then start NM and all works well. What is weird that if I restart > NM then everything still works (even though w_s was running). After > testing it seems that there are connection problems only if 1) > wpa_supplicant is already running when starting NM and 2) > wpa_supplicant was not started by NM (but while doing "service network > restart"). > > This probably sounds weird but I'd like to know is there something > wrong in my system or is this a general problem? Well the simple answer is that NM executes wpa_supplicant itself and supplies appropriate arguments so you either have the NM daemons running (which allows the applet to appear and be used) or you stop them and start the wpa_supplicant daemon. Having all three daemons running together is a recipe for problems, if not actually disaster. -- Brian ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM not detecting device when kernel module unloaded
Hi, it seems that when starting NM while the kernel module for a network device has been unloaded, the device is not initialized/detected by NM, otherwise it works all ok. Ie, rmmod ipw2200 && ./NetworkManager fails to detect my wireless interface but modprobe ipw2200 && ./NetworkManager sees the wireless device. Is this a bug or a feature? Thanks. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Connection problems with wpa_supplicant already running
Hi, this is a weird failure scenario with current SVN trunk but I am able to reproduce it every time so I'm wondering is this a local hickup or what. I'm using Fedora 8 + latest updates + NM SVN trunk. The problem is: When starting up NetworkManager, wireless connection can't be established. I found out that I need to stop NM, stop running wpa_supplicant (started during boot while networking was being started) and then start NM and all works well. What is weird that if I restart NM then everything still works (even though w_s was running). After testing it seems that there are connection problems only if 1) wpa_supplicant is already running when starting NM and 2) wpa_supplicant was not started by NM (but while doing "service network restart"). This probably sounds weird but I'd like to know is there something wrong in my system or is this a general problem? Thanks. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Configure WLAN without applet?
On Fri, 2008-04-18 at 09:17 +0200, Tassilo Horn wrote: > Hi all, > > I've recently switched from traditional network setup (with > wpa_supplicant) to NetworkManager, and it seems to work pretty well. > Unfortunately, to set up encryption one's supposed to use one of these > three NM frontends: > > - Gnome NM applet > - knetworkmanager > - pyNetworkManager > > I don't want to use the first two, cause I don't use Gnome nor KDE, so > I've installed the last one and the applet sits in my XFCE tray. It > lists my local WLAN, but the functionality to set a PSK for it seems to > be broken. (Also the webpage states that it is very buggy...) What version of NetworkManager? 0.6.x or 0.7? > So is it possible to configure that WLAN without any of those applets, > maybe with some dbus calls? Yes, either with shell scripts + dbus-send, or with python and dbus. > If not, are there other frontends (preferably cli) beside the three > above? Not too many, unfortunately. Tambet started a python-based CLI front-end that he hasn't published yet *hint hint*. It's pretty easy to control NM via Python though. You first need a service that provides connections (ie, configured networks and settings) to NetworkManager which is either the user applet or the system settings daemon. Once you have that service running, and have told it about the connections you'd like to use, you can pretty easily tell NM which one to use via dbus-send or python and dbus. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: trunk: pppoe supposed to be working?
On Thu, 2008-04-17 at 20:45 +0200, Björn Martensen wrote: > Hi, > > I'd just like to know if current svn versions of NM 0.7 are supposed to > have working pppoe support. (libnm: 3571, nm: 3572, nm-applet: 685) > I entered the username and the password, left the service blank, as i > have no idea what is supposed to go in there and it works with rp-pppoe > and on my router too without a service name. > > When i connect directly to the dsl modem, NM tries to connect to "Auto > Ethernet" but fails because it doesn't get an IP address assigned. When > I select the dsl connection from the applet's list, NM crashes. I can > restart it again but the wired connections are greyed out then. When I > unplug the ethernet cable and plug it back in, NM tries to connect to > "Auto Ethernet" again, fails to get an IP address, and so on.. You'll want to turn off the "Connect automatically" for the Auto Ethernet connection, and turn on "Connect automatically" for the PPPoE connection. Obviously you can't determine which connection is appropriate for ethernet since there's no SSID or anything. The crash is probably the missing PPP setting that znscnchen reported yesterday. I'm going to fix that one today by requiring a PPP setting for PPPoE, and will add the required PPP page to the connection editor. > NM also crashes when I enter something into the service entry field. Sounds like a bug, will look at that. > I'd just like to know if this is the current state, or if I should get > any kind of IP address for direct connections, a zeroconf address for > example, or if it's "normal" currently, that I can't get an address. > And I'd also like to know if activating a dsl connection is known to > crash NM at the moment. It probably is the current state, I don't personally have PPPoE stuff to test with (my DSL modem runs in transparent bridge mode thank God) so I have to rely a bit more on bug reports from users like you. It's a big help though, so thanks :) Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Configure WLAN without applet?
Hi all, I've recently switched from traditional network setup (with wpa_supplicant) to NetworkManager, and it seems to work pretty well. Unfortunately, to set up encryption one's supposed to use one of these three NM frontends: - Gnome NM applet - knetworkmanager - pyNetworkManager I don't want to use the first two, cause I don't use Gnome nor KDE, so I've installed the last one and the applet sits in my XFCE tray. It lists my local WLAN, but the functionality to set a PSK for it seems to be broken. (Also the webpage states that it is very buggy...) So is it possible to configure that WLAN without any of those applets, maybe with some dbus calls? If not, are there other frontends (preferably cli) beside the three above? Bye, Tassilo ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
