Re: NM do not see any network
On Fri, 2006-12-08 at 12:30 -0500, Darren Albers wrote: > On 12/8/06, Dan Williams <[EMAIL PROTECTED]> wrote: > > On Thu, 2006-12-07 at 21:57 -0500, Darren Albers wrote: > > > dispatch_more_events: Seems to add pre-up and post-down events to > > > dispatcher.d Wasn't this always an option? Maybe what someone asked > > > earlier about running a command before an interface is activated is > > > possible with dispatcher.d with this patch? > > > > Interesting; these events are quite a bit less interesting than it may > > seem. 'pre-up' would be time-bounded, since NM certainly doesn't call > > out to synchronous, blocking scripts when it brings up a connection, nor > > should it. So whatever script gets called here for pre-up will have to > > be pretty fast, because NM isn't going to wait for it before continuing. > > This is quite racy and therefore wrong. > > > > I'm not sure what "post-down" means; there's already the disconnected > > event from the dispatcher which executes scripts when the connection is > > terminated. > > I see what this does (whether this is smart or not is beyond me...), > the package adds a script to dispatcher that users these two new > events to call the general networking configuration items that are > required by Ubuntu. For example pre-up is used to trigger a script > that calls the standard networking scripts for Debian/Ubuntu: > The first sets some wireless options using the wireless tools and the > second starts wpa_supplicant. The postdown does the opposite and > shutsdown wpa_supplicant and then sets all the wireless configuration > options to their defaults again. > > I think this is done so that people can set some specific items in > /etc/network/interfaces such as speed, channel etc.. but as long as > they keep the interface set to use DHCP Network Manager will continue > to manage it. > > Could this be a potential problem for Network Manager if things like > the rate are set there? > > > > > > disabled_devices: This tells NM not to touch devices managed in > > > /etc/network/interfaces > > > > Right; everybody does this and that's fine; but Ubuntu seems to do it > > automatically without telling users what's going on. SUSE has a config > > option in YAST, and half the questions we get here are about this > > problem in Ubuntu, because people don't realize that touching something > > in a config tool there turns something else off in NM. > > I agree and I wonder if until the recent announcement that they really > wanted people to use NetworkManager? Their point was probably that > rewriting the gnome-network-panel to inform the users of this was too > much work to make it by release or that there was nobody who wanted to > take it on. > > > > > hostap-supplicant-driver: adds a workaround for the hostap driver > > > > What does this one do? > > If it detects any of the following kernel_drivers hostap_pci, > hostap_cs, and hostap_plx it passes hostap to wpa_supplicant. > > > > I saw in the release notes for Feisty beta (I forgot the catchy code > > > > Feisty Fawn Herd 1 :) > > > > > name they used) that NM might be the default network management > > > utility for Feisty so I think the testing period there will hopefully > > > shake out any issues with their packages and maybe (hopefully?) will > > > get some patches sent upstream. > > > > Hmm, I thought Ubuntu was still punting NM-by-default since it doesn't > > cover a bunch of use-cases like static IP. That's fine, Fedora doesn't > > turn it on by default either for that same reason. SUSE's out in front > > a bit here, which actually helps everyone out by exposing issues and > > problems. > > Here is the spec they plan on implementing: > https://blueprints.launchpad.net/distros/ubuntu/+spec/network-roaming > It seems very redundant to 0.7 which I thought would be out with Right; much of that is pretty redundant for 0.7. But a few other bits seem right on. > plenty of time for Feisty April release date... Is 0.7 still on track > for Jan? Maybe February or early March, but certainly before April. The wpa_supplicant control parts are within sight of being done, and then it's on to speccing out the new configuration interface and doing multiple active devices, which will actually _simplify_ the code and DBus interface, for a change. > On a side note I used Fedora for the first time on a Mac Mini my wife > gave me for my birthday (I really tried to like MAC OS but little > things kept annoying me about it) and I was impressed. It shows a > lot of polish and there were some things that I really liked about it > and it will probably stay since my needs on that system are a lot less > than on my laptop so I won't need to learn all the nuances of another > distro. Neat. 0.7 will get into FC7 at least, and there it will certainly be better integrated. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/l
Re: NM do not see any network
On 12/8/06, Dan Williams <[EMAIL PROTECTED]> wrote: > On Thu, 2006-12-07 at 21:57 -0500, Darren Albers wrote: > > dispatch_more_events: Seems to add pre-up and post-down events to > > dispatcher.d Wasn't this always an option? Maybe what someone asked > > earlier about running a command before an interface is activated is > > possible with dispatcher.d with this patch? > > Interesting; these events are quite a bit less interesting than it may > seem. 'pre-up' would be time-bounded, since NM certainly doesn't call > out to synchronous, blocking scripts when it brings up a connection, nor > should it. So whatever script gets called here for pre-up will have to > be pretty fast, because NM isn't going to wait for it before continuing. > This is quite racy and therefore wrong. > > I'm not sure what "post-down" means; there's already the disconnected > event from the dispatcher which executes scripts when the connection is > terminated. I see what this does (whether this is smart or not is beyond me...), the package adds a script to dispatcher that users these two new events to call the general networking configuration items that are required by Ubuntu. For example pre-up is used to trigger a script that calls the standard networking scripts for Debian/Ubuntu: The first sets some wireless options using the wireless tools and the second starts wpa_supplicant. The postdown does the opposite and shutsdown wpa_supplicant and then sets all the wireless configuration options to their defaults again. I think this is done so that people can set some specific items in /etc/network/interfaces such as speed, channel etc.. but as long as they keep the interface set to use DHCP Network Manager will continue to manage it. Could this be a potential problem for Network Manager if things like the rate are set there? > > > disabled_devices: This tells NM not to touch devices managed in > > /etc/network/interfaces > > Right; everybody does this and that's fine; but Ubuntu seems to do it > automatically without telling users what's going on. SUSE has a config > option in YAST, and half the questions we get here are about this > problem in Ubuntu, because people don't realize that touching something > in a config tool there turns something else off in NM. I agree and I wonder if until the recent announcement that they really wanted people to use NetworkManager? Their point was probably that rewriting the gnome-network-panel to inform the users of this was too much work to make it by release or that there was nobody who wanted to take it on. > > hostap-supplicant-driver: adds a workaround for the hostap driver > > What does this one do? If it detects any of the following kernel_drivers hostap_pci, hostap_cs, and hostap_plx it passes hostap to wpa_supplicant. > > I saw in the release notes for Feisty beta (I forgot the catchy code > > Feisty Fawn Herd 1 :) > > > name they used) that NM might be the default network management > > utility for Feisty so I think the testing period there will hopefully > > shake out any issues with their packages and maybe (hopefully?) will > > get some patches sent upstream. > > Hmm, I thought Ubuntu was still punting NM-by-default since it doesn't > cover a bunch of use-cases like static IP. That's fine, Fedora doesn't > turn it on by default either for that same reason. SUSE's out in front > a bit here, which actually helps everyone out by exposing issues and > problems. Here is the spec they plan on implementing: https://blueprints.launchpad.net/distros/ubuntu/+spec/network-roaming It seems very redundant to 0.7 which I thought would be out with plenty of time for Feisty April release date... Is 0.7 still on track for Jan? On a side note I used Fedora for the first time on a Mac Mini my wife gave me for my birthday (I really tried to like MAC OS but little things kept annoying me about it) and I was impressed. It shows a lot of polish and there were some things that I really liked about it and it will probably stay since my needs on that system are a lot less than on my laptop so I won't need to learn all the nuances of another distro. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM do not see any network
On Thu, 2006-12-07 at 21:57 -0500, Darren Albers wrote: > On 12/6/06, Darren Albers <[EMAIL PROTECTED]> wrote: > > I'll check out launchpad tonight and see what bugs are filed and also > > look at what patches have been applied to the package and see if I can > > correlate any of them to the recent problems people have reported. > > > > Looking over launchpad last night I see basically the same bugs > repeated over and over regarding specific wireless cards but I did not > see this specific issue. > > I also looked at the patches and there are 9 patches applied to the > base 0.6.3 tarball. I am not sure why Ubuntu is not at 0.6.4 but I > think the maintainer may not have had the time between Dapper and > Edgy. > > The patches seem relatively minor (Though I am probably not a good > judge of that ;-) ) I can post all the patches if someone would like > me to. > > Here they are in summary: > Supplicant timeout patch: Increases the timeout when trying to > associate to 60 seconds. Somewhat bogus, increasing timeouts is the wrong thing to do... > dbus_access_network: adds the user haldaemon to Networkmanager.conf Debian specific, since debian uses groups to determine capabilities. In Fedora and SUSE this functionality is provided by pam_console and the "at_console=True" tag in the NM dbus conf file. > if_fix: adds #define _LINUX_IF_H > resolvconf patch: changes the function > nm_system_should_modify_resolve_conf to return false in > src/backends/NetworkManagerDebian.c > dispatch_more_events: Seems to add pre-up and post-down events to > dispatcher.d Wasn't this always an option? Maybe what someone asked > earlier about running a command before an interface is activated is > possible with dispatcher.d with this patch? Interesting; these events are quite a bit less interesting than it may seem. 'pre-up' would be time-bounded, since NM certainly doesn't call out to synchronous, blocking scripts when it brings up a connection, nor should it. So whatever script gets called here for pre-up will have to be pretty fast, because NM isn't going to wait for it before continuing. This is quite racy and therefore wrong. I'm not sure what "post-down" means; there's already the disconnected event from the dispatcher which executes scripts when the connection is terminated. > disabled_devices: This tells NM not to touch devices managed in > /etc/network/interfaces Right; everybody does this and that's fine; but Ubuntu seems to do it automatically without telling users what's going on. SUSE has a config option in YAST, and half the questions we get here are about this problem in Ubuntu, because people don't realize that touching something in a config tool there turns something else off in NM. > rml_wpa_workarounds: Robert's "famous" wpa workarounds patch ;-) > hostap-supplicant-driver: adds a workaround for the hostap driver What does this one do? > dbus 0.9: Changes dbus_connection_disconnect to dbus_connection_close ? Yes, this is legit and should be in CVS. I think it may have already been committed to HEAD. > I saw in the release notes for Feisty beta (I forgot the catchy code Feisty Fawn Herd 1 :) > name they used) that NM might be the default network management > utility for Feisty so I think the testing period there will hopefully > shake out any issues with their packages and maybe (hopefully?) will > get some patches sent upstream. Hmm, I thought Ubuntu was still punting NM-by-default since it doesn't cover a bunch of use-cases like static IP. That's fine, Fedora doesn't turn it on by default either for that same reason. SUSE's out in front a bit here, which actually helps everyone out by exposing issues and problems. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM do not see any network
On 12/6/06, Darren Albers <[EMAIL PROTECTED]> wrote: > I'll check out launchpad tonight and see what bugs are filed and also > look at what patches have been applied to the package and see if I can > correlate any of them to the recent problems people have reported. > Looking over launchpad last night I see basically the same bugs repeated over and over regarding specific wireless cards but I did not see this specific issue. I also looked at the patches and there are 9 patches applied to the base 0.6.3 tarball. I am not sure why Ubuntu is not at 0.6.4 but I think the maintainer may not have had the time between Dapper and Edgy. The patches seem relatively minor (Though I am probably not a good judge of that ;-) ) I can post all the patches if someone would like me to. Here they are in summary: Supplicant timeout patch: Increases the timeout when trying to associate to 60 seconds. dbus_access_network: adds the user haldaemon to Networkmanager.conf if_fix: adds #define _LINUX_IF_H resolvconf patch: changes the function nm_system_should_modify_resolve_conf to return false in src/backends/NetworkManagerDebian.c dispatch_more_events: Seems to add pre-up and post-down events to dispatcher.d Wasn't this always an option? Maybe what someone asked earlier about running a command before an interface is activated is possible with dispatcher.d with this patch? disabled_devices: This tells NM not to touch devices managed in /etc/network/interfaces rml_wpa_workarounds: Robert's "famous" wpa workarounds patch ;-) hostap-supplicant-driver: adds a workaround for the hostap driver dbus 0.9: Changes dbus_connection_disconnect to dbus_connection_close ? I saw in the release notes for Feisty beta (I forgot the catchy code name they used) that NM might be the default network management utility for Feisty so I think the testing period there will hopefully shake out any issues with their packages and maybe (hopefully?) will get some patches sent upstream. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM do not see any network
On 12/6/06, Dan Williams <[EMAIL PROTECTED]> wrote: > > The Ubuntu maintainers probably need to start an Ubuntu-specific FAQ for > problems users encounter. There are enough Ubuntu-specific hacks and > oddities (probably given that it's not actually in Ubuntu itself) that > these questions keep coming up, and it takes a lot of time to answer > them. Why are there so many issues relating to Ubuntu, and not to > Fedora or SUSE? Is it just better integrated on Fedora and SUSE? > >From following this list and as an Ubuntu user I can agree that it does seem like there are more issues with Ubuntu than with other distro's. However there really aren't that many patches added and for most users it seems to be fine. I wonder if we are seeing more issues with Ubuntu because it's usage seems to be increasing or maybe something went awry with the upgrade from 6.06 to 6.10? I'll check out launchpad tonight and see what bugs are filed and also look at what patches have been applied to the package and see if I can correlate any of them to the recent problems people have reported. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM do not see any network
On Wed, 2006-12-06 at 19:16 +0100, [EMAIL PROTECTED] wrote: > Hello, > > I am on Ubuntu 6.10, my wireless card is detected, but the > NM daemon says: > > NetworkManager:starting... > NetworkManager: nm_dbus_init (): > nm_dbus_init() could not acquire the NetworkManager > service as it is already taken (ret=3). Is the daemon > already running? It appears you are already running NetworkManager, hence this instance exits. If that is not the case, there appears to be DBus security problems. The Ubuntu maintainers probably need to start an Ubuntu-specific FAQ for problems users encounter. There are enough Ubuntu-specific hacks and oddities (probably given that it's not actually in Ubuntu itself) that these questions keep coming up, and it takes a lot of time to answer them. Why are there so many issues relating to Ubuntu, and not to Fedora or SUSE? Is it just better integrated on Fedora and SUSE? Dan > NetworkManager: [1165426945.917538] main (): > nm_dbus_init() failed, exiting. Either dbus is not > running, or the NetworkManager dbus security policy was > not loaded. > NetworkManager: traceback: > NetworkManager: NetworkManager(main+0x47f) > [0x80681af] > NetworkManager: > /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) > [0xb7c3f8cc] > NetworkManager: NetworkManager [0x80530a1] > Trace/breakpoint trap (core dumped) > > > I cannot understand what happens, is someone can help me, > I would be grateful, > > Ciao, > Nicola > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM do not see any network
[once again, I responded to the wrong address - #$%^ gmail! ] On 12/6/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > NetworkManager: [1165426945.917538] main (): > nm_dbus_init() failed, exiting. Either dbus is not > running, or the NetworkManager dbus security policy was > not loaded. As Dan mentioned to Joan, there have been issues with DBUS and permissions. Try adding yourself to the "plugdev" group. It doesn't seem right, but it rings a bell, and the only group I belong to that seems possible is plugdev. In any case, if you want to be able to use any USB connected hardware, you need to be in plugdev, so there's no harm in trying it. -- derek ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM do not see any network
Hello, I am on Ubuntu 6.10, my wireless card is detected, but the NM daemon says: NetworkManager:starting... NetworkManager: nm_dbus_init (): nm_dbus_init() could not acquire the NetworkManager service as it is already taken (ret=3). Is the daemon already running? NetworkManager: [1165426945.917538] main (): nm_dbus_init() failed, exiting. Either dbus is not running, or the NetworkManager dbus security policy was not loaded. NetworkManager: traceback: NetworkManager: NetworkManager(main+0x47f) [0x80681af] NetworkManager: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7c3f8cc] NetworkManager: NetworkManager [0x80530a1] Trace/breakpoint trap (core dumped) I cannot understand what happens, is someone can help me, I would be grateful, Ciao, Nicola ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
