Re: netmanager problems with ubuntu 8.04
On Mon, May 19, 2008 at 06:59:33PM -0400, Dan Williams wrote: > On Mon, 2008-05-19 at 18:28 -0400, Eric S. Johansson wrote: > > Darren Albers wrote: > > > On Mon, May 19, 2008 at 8:17 AM, Alexander Sack <[EMAIL PROTECTED]> wrote: > > >> On Mon, May 19, 2008 at 07:23:30AM -0400, Darren Albers wrote: > > >>> Check out the howto at the link I posted, you need to install > > >>> libdbus-glib-1-dev and libdbus-glib-2-dev > > >> The proper depends of nm 0.7 for hardy should already be in the PPA of > > >> the ubuntu network-manager team: > > >> > > >> https://edge.launchpad.net/~network-manager/+archive > > >> > > >> Remember to get the wpasupplicant from there as well. > > >> > > >> - Alexander > > >> > > >> > > > > > > I also should have clarified that you didn't need all the development > > > packages if you don't plan on building VPN plugins. > > > > > > I didn't realize that you had already packaged wpa_supplicant so I > > > will update my notes to use that package instead. I know that you > > > are busy, but do you have plans to start building snapshots of NM 0.7? > > > > Having tried putting all the pieces together from what people said here, > > all I > > can say is "ouch". While it is most definitely "no blame", please don't > > inflict > > these .deb on any other poor sod that happens to come along. Why? > > > > it's trivially easy, in fact almost guaranteed to end up in the condition > > where > > you have no network connectivity whatsoever. if you aren't comfortable with > > editing /etc/network/interfaces, it will be most unpleasant. > > > > DHCP requests are sent, received, and ignored. This is true for both WiFi > > and > > ethernet. > > Looks like there might be Debian-style D-Bus permission issues with the > nm-dhcp.action callout's dbus config files disallowing it from sending > NetworkManager the returned DHCP configuration. > > What's the contents of your /etc/dbus-1/system.d/nm-dhcp-client.conf > file? > what you need here appears to be this commit: http://bazaar.launchpad.net/~asac/network-manager/main.eni/revision/2764 - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
On Mon, May 19, 2008 at 08:35:40AM -0400, Darren Albers wrote: > On Mon, May 19, 2008 at 8:17 AM, Alexander Sack <[EMAIL PROTECTED]> wrote: > > On Mon, May 19, 2008 at 07:23:30AM -0400, Darren Albers wrote: > >> Check out the howto at the link I posted, you need to install > >> libdbus-glib-1-dev and libdbus-glib-2-dev > > > > The proper depends of nm 0.7 for hardy should already be in the PPA of > > the ubuntu network-manager team: > > > > https://edge.launchpad.net/~network-manager/+archive > > > > Remember to get the wpasupplicant from there as well. > > > > - Alexander > > > > > > I also should have clarified that you didn't need all the development > packages if you don't plan on building VPN plugins. > > I didn't realize that you had already packaged wpa_supplicant so I > will update my notes to use that package instead. I know that you > are busy, but do you have plans to start building snapshots of NM 0.7? > Very soon. In particular I am currently at a conference this week and have this on top of my todo once i return. - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
On Mon, May 19, 2008 at 9:23 PM, Eric S. Johansson <[EMAIL PROTECTED]> wrote: > Darren Albers wrote: > >> >> In the short-term set the two deny's at the bottom to permit. It >> will get DHCP working and maybe Dan or someone can help us figure out >> what the proper permissions are. > > that was actually part of the original instructions but for some reason my > calibrated eyeball diff failed. Now I can access my open access point and I > will try it tomorrow on a wep protected one. > > Unfortunately, adding open VPN connections don't seem to work at all. I can > make do with a CLI invocation in the host OS in the meantime. I may need to > play some games to give the guest OSs access to the same open VPN connection > but that's my problem. > > How much commentary do people want on user interface issues? I am disabled > and as a result am highly sensitive to bad user interfaces. the current > user interface failed me miserably because 1) I had to type, and 2) my > exceedingly clumsy typing caused the user interface to fail in ways that > forced me to go back to the beginning multiple times. This process cost me > a good deal of physical pain. > > you can't do much about 1 because NaturallySpeaking is barely usable under > wine. With any luck, that will change of the next year but right now, it's > not so good if you need full function speech recognition under Linux[1]. > But 2, that we can do something about. We can minimize typing and the user > interface flow can make failures a little less painful. > > > ---eric > > [1] no, don't mention Sphinx, don't mention Julius, don't mention HTK or any > other speech recognition product whose primary goal is to give graduate > students something to do and write a paper about. They don't work, have > large enough vocabularies, or sufficient language modeling not to mention > user interfaces or integration to an authoring systems/applications. Yes, I > do get very cranky on this topic. :-) > Eric, I had some issues with OpenVPN but got it working. I have some rough notes I will post once I clean up. I think the primary issue was that when I built it the first time I didn't use the right prefix and it put the configuration files in /usr/etc or something weird like that. Regarding the UI issues, I will let Dan comment in detail but in 99% of the cases you should never need to do anything beyond enter your wireless key (And with WEP select the key type) since NM will detect the network type and prompt you when you select it. The manage networks dialog shouldn't be something you need to use often. In my case I have connected to 3-4 different wireless networks and 1 Aircard without going into that UI except for my own curiosity. That doesn't mean that the interface shouldn't be cleaned up to make it more useful to those in situations like your though. Not to go off-subject but your comment regarding accessibility is interesting since I read a lot of posts that say how good that is in Gnome but I have never had anyone with personal experience comment on it. That is really too bad Thanks! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
Darren Albers wrote: > > In the short-term set the two deny's at the bottom to permit. It > will get DHCP working and maybe Dan or someone can help us figure out > what the proper permissions are. that was actually part of the original instructions but for some reason my calibrated eyeball diff failed. Now I can access my open access point and I will try it tomorrow on a wep protected one. Unfortunately, adding open VPN connections don't seem to work at all. I can make do with a CLI invocation in the host OS in the meantime. I may need to play some games to give the guest OSs access to the same open VPN connection but that's my problem. How much commentary do people want on user interface issues? I am disabled and as a result am highly sensitive to bad user interfaces. the current user interface failed me miserably because 1) I had to type, and 2) my exceedingly clumsy typing caused the user interface to fail in ways that forced me to go back to the beginning multiple times. This process cost me a good deal of physical pain. you can't do much about 1 because NaturallySpeaking is barely usable under wine. With any luck, that will change of the next year but right now, it's not so good if you need full function speech recognition under Linux[1]. But 2, that we can do something about. We can minimize typing and the user interface flow can make failures a little less painful. ---eric [1] no, don't mention Sphinx, don't mention Julius, don't mention HTK or any other speech recognition product whose primary goal is to give graduate students something to do and write a paper about. They don't work, have large enough vocabularies, or sufficient language modeling not to mention user interfaces or integration to an authoring systems/applications. Yes, I do get very cranky on this topic. :-) ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
On Mon, May 19, 2008 at 9:07 PM, Dan Williams <[EMAIL PROTECTED]> wrote: > On Mon, 2008-05-19 at 19:17 -0400, Darren Albers wrote: >> On Mon, May 19, 2008 at 7:05 PM, Eric S. Johansson <[EMAIL PROTECTED]> wrote: >> > Dan Williams wrote: >> >> Looks like there might be Debian-style D-Bus permission issues with the >> >> nm-dhcp.action callout's dbus config files disallowing it from sending >> >> NetworkManager the returned DHCP configuration. >> >> >> >> What's the contents of your /etc/dbus-1/system.d/nm-dhcp-client.conf >> >> file? >> > >> > > > "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" >> > "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";> >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > ___ >> > NetworkManager-list mailing list >> > NetworkManager-list@gnome.org >> > http://mail.gnome.org/mailman/listinfo/networkmanager-list >> > >> >> In the short-term set the two deny's at the bottom to permit. It >> will get DHCP working and maybe Dan or someone can help us figure out >> what the proper permissions are. >> >> So far I have tried allowing console and netdev to own it with no luck. > > It just needs permissions to talk to NM, and both should be running as > root... what were the permissions debian-based distros used for the old > dhclient-script when it was sending options to dhcdbd? That might give > some clue as to what to do. > > dan > > Good point I will check there... In the short-term a safer solution might be to leave the default deny and instead give the specific user ownership. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
On Mon, 2008-05-19 at 19:17 -0400, Darren Albers wrote: > On Mon, May 19, 2008 at 7:05 PM, Eric S. Johansson <[EMAIL PROTECTED]> wrote: > > Dan Williams wrote: > >> Looks like there might be Debian-style D-Bus permission issues with the > >> nm-dhcp.action callout's dbus config files disallowing it from sending > >> NetworkManager the returned DHCP configuration. > >> > >> What's the contents of your /etc/dbus-1/system.d/nm-dhcp-client.conf > >> file? > > > > > "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" > > "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";> > > > > > > > > > > > > > > > > > > > > > > ___ > > NetworkManager-list mailing list > > NetworkManager-list@gnome.org > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > > In the short-term set the two deny's at the bottom to permit. It > will get DHCP working and maybe Dan or someone can help us figure out > what the proper permissions are. > > So far I have tried allowing console and netdev to own it with no luck. It just needs permissions to talk to NM, and both should be running as root... what were the permissions debian-based distros used for the old dhclient-script when it was sending options to dhcdbd? That might give some clue as to what to do. dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
On Mon, 2008-05-19 at 19:05 -0400, Eric S. Johansson wrote: > Dan Williams wrote: > > Looks like there might be Debian-style D-Bus permission issues with the > > nm-dhcp.action callout's dbus config files disallowing it from sending > > NetworkManager the returned DHCP configuration. > > > > What's the contents of your /etc/dbus-1/system.d/nm-dhcp-client.conf > > file? > >"-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" > "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";> > > > > > > > > > > Yeah, I don't think that's good enough; see Darren's instructions on how to fix that. dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
On Mon, May 19, 2008 at 7:05 PM, Eric S. Johansson <[EMAIL PROTECTED]> wrote: > Dan Williams wrote: >> Looks like there might be Debian-style D-Bus permission issues with the >> nm-dhcp.action callout's dbus config files disallowing it from sending >> NetworkManager the returned DHCP configuration. >> >> What's the contents of your /etc/dbus-1/system.d/nm-dhcp-client.conf >> file? > > "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" > "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";> > > > > > > > > > > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > In the short-term set the two deny's at the bottom to permit. It will get DHCP working and maybe Dan or someone can help us figure out what the proper permissions are. So far I have tried allowing console and netdev to own it with no luck. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
Dan Williams wrote: > Looks like there might be Debian-style D-Bus permission issues with the > nm-dhcp.action callout's dbus config files disallowing it from sending > NetworkManager the returned DHCP configuration. > > What's the contents of your /etc/dbus-1/system.d/nm-dhcp-client.conf > file? http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";> ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
On Mon, 2008-05-19 at 18:28 -0400, Eric S. Johansson wrote: > Darren Albers wrote: > > On Mon, May 19, 2008 at 8:17 AM, Alexander Sack <[EMAIL PROTECTED]> wrote: > >> On Mon, May 19, 2008 at 07:23:30AM -0400, Darren Albers wrote: > >>> Check out the howto at the link I posted, you need to install > >>> libdbus-glib-1-dev and libdbus-glib-2-dev > >> The proper depends of nm 0.7 for hardy should already be in the PPA of > >> the ubuntu network-manager team: > >> > >> https://edge.launchpad.net/~network-manager/+archive > >> > >> Remember to get the wpasupplicant from there as well. > >> > >> - Alexander > >> > >> > > > > I also should have clarified that you didn't need all the development > > packages if you don't plan on building VPN plugins. > > > > I didn't realize that you had already packaged wpa_supplicant so I > > will update my notes to use that package instead. I know that you > > are busy, but do you have plans to start building snapshots of NM 0.7? > > Having tried putting all the pieces together from what people said here, all > I > can say is "ouch". While it is most definitely "no blame", please don't > inflict > these .deb on any other poor sod that happens to come along. Why? > > it's trivially easy, in fact almost guaranteed to end up in the condition > where > you have no network connectivity whatsoever. if you aren't comfortable with > editing /etc/network/interfaces, it will be most unpleasant. > > DHCP requests are sent, received, and ignored. This is true for both WiFi > and > ethernet. Looks like there might be Debian-style D-Bus permission issues with the nm-dhcp.action callout's dbus config files disallowing it from sending NetworkManager the returned DHCP configuration. What's the contents of your /etc/dbus-1/system.d/nm-dhcp-client.conf file? Dan > Adding a static ethernet configuration requires rebooting the machine before > it > is seen. > > The user interface for adding a static IP configuration would only be seen as > good by geek tab (temporarily able-bodied). Field selection, visual > feedback, > and ease with which you can lose what you just typed in all work against the > user. > > I've attached a cut down version of syslog. I apologize for its chaos but I > was > flailing about trying desperately to get an ethernet connection back so I > could > tell you about how unpleasant experience had been. :-) > > Let me know what you have another set of .deb for me to test and what, if > any, I > should remove. Once a test crash dummy, always a test crash dummy. (I > wonder > if I can get my library to give me an ethernet cable instead of WiFi?) > > plain text document attachment (syslog) > May 19 18:00:44 first-triad NetworkManager: (eth0): device state > change: 1 -> 2 > May 19 18:00:44 first-triad NetworkManager: (eth0): bringing up > device. > May 19 18:00:44 first-triad kernel: [ 41.356740] e1000: eth0: > e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX > May 19 18:00:44 first-triad NetworkManager: (eth0): preparing device. > May 19 18:00:44 first-triad NetworkManager: (eth0): deactivating > device. > May 19 18:00:44 first-triad kernel: [ 41.356747] e1000: eth0: > e1000_watchdog: 10/100 speed: disabling TSO > May 19 18:00:44 first-triad kernel: [ 41.356840] ADDRCONF(NETDEV_UP): eth0: > link is not ready > May 19 18:00:44 first-triad kernel: [ 41.356843] bridge-eth0: enabling the > bridge > May 19 18:00:44 first-triad kernel: [ 41.356847] bridge-eth0: up > May 19 18:00:44 first-triad kernel: [ 41.359114] ADDRCONF(NETDEV_CHANGE): > eth0: link becomes ready > May 19 18:00:44 first-triad NetworkManager: (wlan0): device state > change: 1 -> 2 > May 19 18:00:44 first-triad NetworkManager: (wlan0): bringing up > device. > May 19 18:00:44 first-triad kernel: [ 41.362583] ACPI: PCI Interrupt > :05:00.0[A] -> GSI 19 (level, low) -> IRQ 19 > May 19 18:00:44 first-triad kernel: [ 41.362706] PM: Writing back config > space on device :05:00.0 at offset 1 (was 12, writing 16) > May 19 18:00:45 first-triad vmnet-dhcpd: Configured subnet: 192.168.253.0 > May 19 18:00:45 first-triad vmnet-dhcpd: Setting vmnet-dhcp IP address: > 192.168.253.254 > May 19 18:00:45 first-triad vmnet-dhcpd: Recving on > VNet/vmnet8/192.168.253.0 > May 19 18:00:45 first-triad vmnet-dhcpd: Sending on > VNet/vmnet8/192.168.253.0 > May 19 18:00:45 first-triad kernel: [ 41.491344] /dev/vmnet: open called by > PID 5962 (vmnet-dhcpd) > May 19 18:00:45 first-triad kernel: [ 41.491367] /dev/vmnet: port on hub 8 > successfully opened > May 19 18:00:45 first-triad kernel: [ 41.497347] /dev/vmnet: open called by > PID 5982 (vmnet-natd) > May 19 18:00:45 first-triad kernel: [ 41.497367] /dev/vmnet: port on hub 8 > successfully opened > May 19 18:00:45 first-triad kernel: [ 41.512666] iwl3945: Tunable channels: > 11 802.11bg, 13 802.11a channels > May 19 18:00:45 first-tri
Re: netmanager problems with ubuntu 8.04
On Mon, May 19, 2008 at 6:28 PM, Eric S. Johansson <[EMAIL PROTECTED]> wrote: > Darren Albers wrote: >> >> On Mon, May 19, 2008 at 8:17 AM, Alexander Sack <[EMAIL PROTECTED]> wrote: >>> >>> On Mon, May 19, 2008 at 07:23:30AM -0400, Darren Albers wrote: Check out the howto at the link I posted, you need to install libdbus-glib-1-dev and libdbus-glib-2-dev >>> >>> The proper depends of nm 0.7 for hardy should already be in the PPA of >>> the ubuntu network-manager team: >>> >>> https://edge.launchpad.net/~network-manager/+archive >>> >>> Remember to get the wpasupplicant from there as well. >>> >>> - Alexander >>> >>> >> >> I also should have clarified that you didn't need all the development >> packages if you don't plan on building VPN plugins. >> >> I didn't realize that you had already packaged wpa_supplicant so I >> will update my notes to use that package instead. I know that you >> are busy, but do you have plans to start building snapshots of NM 0.7? > > Having tried putting all the pieces together from what people said here, all > I can say is "ouch". While it is most definitely "no blame", please don't > inflict these .deb on any other poor sod that happens to come along. Why? Did you edit /etc/dbus-1/system.d/nm-dhcp-client.conf as described in the Howto? The symptoms you describe seem identical to your account not having the permissions required that editing nm-dhcp-client.conf gives you. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
Darren Albers wrote: On Mon, May 19, 2008 at 8:17 AM, Alexander Sack <[EMAIL PROTECTED]> wrote: On Mon, May 19, 2008 at 07:23:30AM -0400, Darren Albers wrote: Check out the howto at the link I posted, you need to install libdbus-glib-1-dev and libdbus-glib-2-dev The proper depends of nm 0.7 for hardy should already be in the PPA of the ubuntu network-manager team: https://edge.launchpad.net/~network-manager/+archive Remember to get the wpasupplicant from there as well. - Alexander I also should have clarified that you didn't need all the development packages if you don't plan on building VPN plugins. I didn't realize that you had already packaged wpa_supplicant so I will update my notes to use that package instead. I know that you are busy, but do you have plans to start building snapshots of NM 0.7? Having tried putting all the pieces together from what people said here, all I can say is "ouch". While it is most definitely "no blame", please don't inflict these .deb on any other poor sod that happens to come along. Why? it's trivially easy, in fact almost guaranteed to end up in the condition where you have no network connectivity whatsoever. if you aren't comfortable with editing /etc/network/interfaces, it will be most unpleasant. DHCP requests are sent, received, and ignored. This is true for both WiFi and ethernet. Adding a static ethernet configuration requires rebooting the machine before it is seen. The user interface for adding a static IP configuration would only be seen as good by geek tab (temporarily able-bodied). Field selection, visual feedback, and ease with which you can lose what you just typed in all work against the user. I've attached a cut down version of syslog. I apologize for its chaos but I was flailing about trying desperately to get an ethernet connection back so I could tell you about how unpleasant experience had been. :-) Let me know what you have another set of .deb for me to test and what, if any, I should remove. Once a test crash dummy, always a test crash dummy. (I wonder if I can get my library to give me an ethernet cable instead of WiFi?) May 19 18:00:44 first-triad NetworkManager: (eth0): device state change: 1 -> 2 May 19 18:00:44 first-triad NetworkManager: (eth0): bringing up device. May 19 18:00:44 first-triad kernel: [ 41.356740] e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX May 19 18:00:44 first-triad NetworkManager: (eth0): preparing device. May 19 18:00:44 first-triad NetworkManager: (eth0): deactivating device. May 19 18:00:44 first-triad kernel: [ 41.356747] e1000: eth0: e1000_watchdog: 10/100 speed: disabling TSO May 19 18:00:44 first-triad kernel: [ 41.356840] ADDRCONF(NETDEV_UP): eth0: link is not ready May 19 18:00:44 first-triad kernel: [ 41.356843] bridge-eth0: enabling the bridge May 19 18:00:44 first-triad kernel: [ 41.356847] bridge-eth0: up May 19 18:00:44 first-triad kernel: [ 41.359114] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready May 19 18:00:44 first-triad NetworkManager: (wlan0): device state change: 1 -> 2 May 19 18:00:44 first-triad NetworkManager: (wlan0): bringing up device. May 19 18:00:44 first-triad kernel: [ 41.362583] ACPI: PCI Interrupt :05:00.0[A] -> GSI 19 (level, low) -> IRQ 19 May 19 18:00:44 first-triad kernel: [ 41.362706] PM: Writing back config space on device :05:00.0 at offset 1 (was 12, writing 16) May 19 18:00:45 first-triad vmnet-dhcpd: Configured subnet: 192.168.253.0 May 19 18:00:45 first-triad vmnet-dhcpd: Setting vmnet-dhcp IP address: 192.168.253.254 May 19 18:00:45 first-triad vmnet-dhcpd: Recving on VNet/vmnet8/192.168.253.0 May 19 18:00:45 first-triad vmnet-dhcpd: Sending on VNet/vmnet8/192.168.253.0 May 19 18:00:45 first-triad kernel: [ 41.491344] /dev/vmnet: open called by PID 5962 (vmnet-dhcpd) May 19 18:00:45 first-triad kernel: [ 41.491367] /dev/vmnet: port on hub 8 successfully opened May 19 18:00:45 first-triad kernel: [ 41.497347] /dev/vmnet: open called by PID 5982 (vmnet-natd) May 19 18:00:45 first-triad kernel: [ 41.497367] /dev/vmnet: port on hub 8 successfully opened May 19 18:00:45 first-triad kernel: [ 41.512666] iwl3945: Tunable channels: 11 802.11bg, 13 802.11a channels May 19 18:00:45 first-triad kernel: [ 41.516681] Registered led device: iwl-phy0:RX May 19 18:00:45 first-triad kernel: [ 41.516713] Registered led device: iwl-phy0:TX May 19 18:00:45 first-triad NetworkManager: (wlan0): preparing device. May 19 18:00:45 first-triad kernel: [ 41.524146] ADDRCONF(NETDEV_UP): wlan0: link is not ready May 19 18:00:45 first-triad NetworkManager: (wlan0): deactivating device. May 19 18:00:45 first-triad NetworkManager: (eth0): carrier now ON (device state 2) May 19 18:00:45 first-triad NetworkManager: (eth0): device state change: 2 -> 3 May 19 18:00:45 first-triad NetworkManager: (wlan0): devic
Re: netmanager problems with ubuntu 8.04
On Mon, May 19, 2008 at 8:17 AM, Alexander Sack <[EMAIL PROTECTED]> wrote: > On Mon, May 19, 2008 at 07:23:30AM -0400, Darren Albers wrote: >> Check out the howto at the link I posted, you need to install >> libdbus-glib-1-dev and libdbus-glib-2-dev > > The proper depends of nm 0.7 for hardy should already be in the PPA of > the ubuntu network-manager team: > > https://edge.launchpad.net/~network-manager/+archive > > Remember to get the wpasupplicant from there as well. > > - Alexander > > I also should have clarified that you didn't need all the development packages if you don't plan on building VPN plugins. I didn't realize that you had already packaged wpa_supplicant so I will update my notes to use that package instead. I know that you are busy, but do you have plans to start building snapshots of NM 0.7? Thanks! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
On Mon, May 19, 2008 at 07:23:30AM -0400, Darren Albers wrote: > Check out the howto at the link I posted, you need to install > libdbus-glib-1-dev and libdbus-glib-2-dev The proper depends of nm 0.7 for hardy should already be in the PPA of the ubuntu network-manager team: https://edge.launchpad.net/~network-manager/+archive Remember to get the wpasupplicant from there as well. - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
Check out the howto at the link I posted, you need to install libdbus-glib-1-dev and libdbus-glib-2-dev On Sun, May 18, 2008 at 11:34 PM, Eric S. Johansson <[EMAIL PROTECTED]> wrote: > Darren Albers wrote: >> >> I think those packages are somewhat old, Alexander is the Ubuntu >> Maintainer so they are certainly trustworthy but the feature set in >> those packages is significantly less than recent snapshots. I know >> that Alexander is busy and in the past he has stated that it is his >> intent is to provide packages when NM 0.7 goes final so in the >> meantime I rebuilt the packages Michael Biebl is building for Debian >> SID and so far they seem to work well. I posted the packages and a >> howto here: >> >> http://ubuntuforums.org/showthread.php?t=797059 >> >> Please do not post any bugs to Launchpad for these packages, they are >> not in any way shape or form support by Canonical. >> >> These packages were rebuilt from Michael's repo as of May 9th. > > > [EMAIL PROTECTED]:~/netmgr$ sudo dpkg -i *.drb > [sudo] password for esj: > sudo: pam_authenticate: Conversation error > [EMAIL PROTECTED]:~/netmgr$ > [EMAIL PROTECTED]:~/netmgr$ sudo dpkg -i *.deb > [sudo] password for esj: > (Reading database ... 107465 files and directories currently installed.) > Preparing to replace libdbus-glib-1-2 0.74-2 (using > libdbus-glib-1-2_0.74-4_i386.deb) ... > Unpacking replacement libdbus-glib-1-2 ... > Preparing to replace libnm-glib0 0.7~~svn20080121t191418+eni1-0ubuntu0~pre7 > (using libnm-glib0_0.7.0~svn3645-1_i386.deb) ... > Unpacking replacement libnm-glib0 ... > Selecting previously deselected package libnm-glib-dev. > Unpacking libnm-glib-dev (from libnm-glib-dev_0.7.0~svn3645-1_i386.deb) ... > Preparing to replace libnm-util0 0.7~~svn20080121t191418+eni1-0ubuntu0~pre4 > (using libnm-util0_0.7.0~svn3645-1_i386.deb) ... > Unpacking replacement libnm-util0 ... > Selecting previously deselected package libnm-util-dev. > Unpacking libnm-util-dev (from libnm-util-dev_0.7.0~svn3645-1_i386.deb) ... > Preparing to replace network-manager > 0.7~~svn20080121t191418+eni1-0ubuntu0~pre7 (using > network-manager_0.7.0~svn3645-1_i386.deb) ... > Unpacking replacement network-manager ... > Selecting previously deselected package network-manager-dev. > Unpacking network-manager-dev (from > network-manager-dev_0.7.0~svn3645-1_i386.deb) ... > Preparing to replace network-manager-gnome > 0.7~~svn20080121t194048-0ubuntu0~pre6 (using > network-manager-gnome_0.7.0~svn718-1_i386.deb) ... > Unpacking replacement network-manager-gnome ... > Setting up libdbus-glib-1-2 (0.74-4) ... > > dpkg: dependency problems prevent configuration of libnm-glib-dev: > libnm-glib-dev depends on libdbus-glib-1-dev (>= 0.60); however: > Package libdbus-glib-1-dev is not installed. > dpkg: error processing libnm-glib-dev (--install): > dependency problems - leaving unconfigured > Setting up libnm-util0 (0.7.0~svn3645-1) ... > > dpkg: dependency problems prevent configuration of libnm-util-dev: > libnm-util-dev depends on libdbus-glib-1-dev (>= 0.60); however: > Package libdbus-glib-1-dev is not installed. > dpkg: error processing libnm-util-dev (--install): > dependency problems - leaving unconfigured > dpkg: dependency problems prevent configuration of network-manager: > network-manager depends on libnl1; however: > Package libnl1 is not installed. > dpkg: error processing network-manager (--install): > dependency problems - leaving unconfigured > Setting up network-manager-dev (0.7.0~svn3645-1) ... > dpkg: dependency problems prevent configuration of network-manager-gnome: > network-manager-gnome depends on network-manager (>= 0.7); however: > Package network-manager is not configured yet. > dpkg: error processing network-manager-gnome (--install): > dependency problems - leaving unconfigured > Setting up libnm-glib0 (0.7.0~svn3645-1) ... > > Processing triggers for libc6 ... > ldconfig deferred processing now taking place > Errors were encountered while processing: > libnm-glib-dev > libnm-util-dev > network-manager > network-manager-gnome > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
Darren Albers wrote: > I think those packages are somewhat old, Alexander is the Ubuntu > Maintainer so they are certainly trustworthy but the feature set in > those packages is significantly less than recent snapshots. I know > that Alexander is busy and in the past he has stated that it is his > intent is to provide packages when NM 0.7 goes final so in the > meantime I rebuilt the packages Michael Biebl is building for Debian > SID and so far they seem to work well. I posted the packages and a > howto here: > > http://ubuntuforums.org/showthread.php?t=797059 > > Please do not post any bugs to Launchpad for these packages, they are > not in any way shape or form support by Canonical. > > These packages were rebuilt from Michael's repo as of May 9th. [EMAIL PROTECTED]:~/netmgr$ sudo dpkg -i *.drb [sudo] password for esj: sudo: pam_authenticate: Conversation error [EMAIL PROTECTED]:~/netmgr$ [EMAIL PROTECTED]:~/netmgr$ sudo dpkg -i *.deb [sudo] password for esj: (Reading database ... 107465 files and directories currently installed.) Preparing to replace libdbus-glib-1-2 0.74-2 (using libdbus-glib-1-2_0.74-4_i386.deb) ... Unpacking replacement libdbus-glib-1-2 ... Preparing to replace libnm-glib0 0.7~~svn20080121t191418+eni1-0ubuntu0~pre7 (using libnm-glib0_0.7.0~svn3645-1_i386.deb) ... Unpacking replacement libnm-glib0 ... Selecting previously deselected package libnm-glib-dev. Unpacking libnm-glib-dev (from libnm-glib-dev_0.7.0~svn3645-1_i386.deb) ... Preparing to replace libnm-util0 0.7~~svn20080121t191418+eni1-0ubuntu0~pre4 (using libnm-util0_0.7.0~svn3645-1_i386.deb) ... Unpacking replacement libnm-util0 ... Selecting previously deselected package libnm-util-dev. Unpacking libnm-util-dev (from libnm-util-dev_0.7.0~svn3645-1_i386.deb) ... Preparing to replace network-manager 0.7~~svn20080121t191418+eni1-0ubuntu0~pre7 (using network-manager_0.7.0~svn3645-1_i386.deb) ... Unpacking replacement network-manager ... Selecting previously deselected package network-manager-dev. Unpacking network-manager-dev (from network-manager-dev_0.7.0~svn3645-1_i386.deb) ... Preparing to replace network-manager-gnome 0.7~~svn20080121t194048-0ubuntu0~pre6 (using network-manager-gnome_0.7.0~svn718-1_i386.deb) ... Unpacking replacement network-manager-gnome ... Setting up libdbus-glib-1-2 (0.74-4) ... dpkg: dependency problems prevent configuration of libnm-glib-dev: libnm-glib-dev depends on libdbus-glib-1-dev (>= 0.60); however: Package libdbus-glib-1-dev is not installed. dpkg: error processing libnm-glib-dev (--install): dependency problems - leaving unconfigured Setting up libnm-util0 (0.7.0~svn3645-1) ... dpkg: dependency problems prevent configuration of libnm-util-dev: libnm-util-dev depends on libdbus-glib-1-dev (>= 0.60); however: Package libdbus-glib-1-dev is not installed. dpkg: error processing libnm-util-dev (--install): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of network-manager: network-manager depends on libnl1; however: Package libnl1 is not installed. dpkg: error processing network-manager (--install): dependency problems - leaving unconfigured Setting up network-manager-dev (0.7.0~svn3645-1) ... dpkg: dependency problems prevent configuration of network-manager-gnome: network-manager-gnome depends on network-manager (>= 0.7); however: Package network-manager is not configured yet. dpkg: error processing network-manager-gnome (--install): dependency problems - leaving unconfigured Setting up libnm-glib0 (0.7.0~svn3645-1) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place Errors were encountered while processing: libnm-glib-dev libnm-util-dev network-manager network-manager-gnome ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
On Sun, 18 May 2008, Darren Albers wrote: > I think those packages are somewhat old Ah. That might explain why while those packages loaded OK and I could see the wired and wireless networks, it couldn't connect to any of my WPA2 access points. I've given up on NM anyway- I've just taken to running wpa_supplicant and dhcpcd by hand, which works reliably. -Kenny -- Kenneth R. Crudup Sr. SW Engineer, Scott County Consulting, Los Angeles O: 3630 S. Sepulveda Blvd. #138, L.A., CA 90034-6809 (888) 454-8181 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
On Sun, May 18, 2008 at 3:36 PM, Darren Albers <[EMAIL PROTECTED]> wrote: > On Sun, May 18, 2008 at 2:29 AM, Eric S. Johansson <[EMAIL PROTECTED]> wrote: >> Kenneth Crudup wrote: >>> On Sun, 18 May 2008, Eric S. Johansson wrote: >>> ... but ends up with me trying networkmanager 0.7. must say that with backported modules, wifi works great again. I am most grateful. >>> >>> What did you do?! I've been unable to get it to work from the SVN. >>> >> >> didn't use svn. not that much of a masochist. >> >> back port modules info here >> http://linuxtechie.wordpress.com/2008/04/24/making-intel-wireless-3945abg-work-better-on-ubuntu-hardy/ >> >> network manager 0.7 info from here >> http://ubuntuforums.org/showthread.php?t=676992 >> > > I think those packages are somewhat old, Alexander is the Ubuntu > Maintainer so they are certainly trustworthy but the feature set in > those packages is significantly less than recent snapshots. I know > that Alexander is busy and in the past he has stated that it is his > intent is to provide packages when NM 0.7 goes final so in the > meantime I rebuilt the packages Michael Biebl is building for Debian > SID and so far they seem to work well. I posted the packages and a > howto here: > > http://ubuntuforums.org/showthread.php?t=797059 > > Please do not post any bugs to Launchpad for these packages, they are > not in any way shape or form support by Canonical. > > These packages were rebuilt from Michael's repo as of May 9th. > Also, all the credit for this and /none/ of the blame goes to Michael for these packages. I simply rebuilt them for Ubuntu, which may be different enough from Sid to cause issues. In my testing I haven't found any but it is possible so don't blame him (or me!) if your wireless card eats your cat. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
On Sun, May 18, 2008 at 2:29 AM, Eric S. Johansson <[EMAIL PROTECTED]> wrote: > Kenneth Crudup wrote: >> On Sun, 18 May 2008, Eric S. Johansson wrote: >> >>> ... but ends up with me trying networkmanager 0.7. must say that with >>> backported modules, wifi works great again. I am most grateful. >> >> What did you do?! I've been unable to get it to work from the SVN. >> > > didn't use svn. not that much of a masochist. > > back port modules info here > http://linuxtechie.wordpress.com/2008/04/24/making-intel-wireless-3945abg-work-better-on-ubuntu-hardy/ > > network manager 0.7 info from here > http://ubuntuforums.org/showthread.php?t=676992 > I think those packages are somewhat old, Alexander is the Ubuntu Maintainer so they are certainly trustworthy but the feature set in those packages is significantly less than recent snapshots. I know that Alexander is busy and in the past he has stated that it is his intent is to provide packages when NM 0.7 goes final so in the meantime I rebuilt the packages Michael Biebl is building for Debian SID and so far they seem to work well. I posted the packages and a howto here: http://ubuntuforums.org/showthread.php?t=797059 Please do not post any bugs to Launchpad for these packages, they are not in any way shape or form support by Canonical. These packages were rebuilt from Michael's repo as of May 9th. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
Kenneth Crudup wrote: > On Sun, 18 May 2008, Eric S. Johansson wrote: > >> ... but ends up with me trying networkmanager 0.7. must say that with >> backported modules, wifi works great again. I am most grateful. > > What did you do?! I've been unable to get it to work from the SVN. > didn't use svn. not that much of a masochist. back port modules info here http://linuxtechie.wordpress.com/2008/04/24/making-intel-wireless-3945abg-work-better-on-ubuntu-hardy/ network manager 0.7 info from here http://ubuntuforums.org/showthread.php?t=676992 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
On Sun, 18 May 2008, Eric S. Johansson wrote: > ... but ends up with me trying networkmanager 0.7. must say that with > backported modules, wifi works great again. I am most grateful. What did you do?! I've been unable to get it to work from the SVN. -Kenny -- Kenneth R. Crudup Sr. SW Engineer, Scott County Consulting, Los Angeles O: 3630 S. Sepulveda Blvd. #138, L.A., CA 90034-6809 (888) 454-8181 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
