[PATCH] network-manager-applet: autogen.sh broken
Hi,
"autogen.sh" (for network-manager-applet) is still checking
for "src/applet-dbus.c" to verify if the current directory is top level.
Using the attached patch "applet.c" is used for checking as "applet-dbus.c"
was removed a while ago.
Please commit to trunk.
Thanks,
Helmut
Index: autogen.sh
===
--- autogen.sh (Revision 143)
+++ autogen.sh (Arbeitskopie)
@@ -7,7 +7,7 @@
PKG_NAME=nm-applet
(test -f $srcdir/configure.ac \
- && test -f $srcdir/src/applet-dbus.c) || {
+ && test -f $srcdir/src/applet.c) || {
echo -n "**Error**: Directory "\`$srcdir\'" does not look like the"
echo " top-level $PKG_NAME directory"
exit 1
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager doesn't work an b9rks keyboard
Am Mittwoch, den 05.09.2007, 16:08 -0500 schrieb Steev Klimaszewski:
> On Wed, 2007-09-05 at 22:29 +0200, Thomas Ilnseher wrote:
> > Hi, all.
> >
> > I have got a serious problem eith Networkmanager: Whenever I Try to
> > connect to my wireless network, it just b0rks the keyboard. That means
> > that any attempts to press any key (even ctrl+alt+backspace) are
> > ignored. The Mouse still works as expected. If I then try to reboot the
> > computer, It hangs on rebooting. In this situation, magic sysreq works,
> > but a "ctrl+alt+printscreen+b" doesn't restart the computer, but works
> > as expected.
> >
> > If I do this manually:
> >
> > # ifconfig wlan0 up
> > # wpa_supplicant -B -iwlan0 -Dwext -c/etc/.../wpa_supplicant.conf
> > # dhcpc wlan0
> >
> > then my wireless comes up, without problems. The network is Wpa
> > encrypted. (WPA2-PSK)
> >
> > Here is some system information:
> >
> > kernel 2.6.23-rc4
> > wireless driver: bcm43xx (eth1 changed to wlan0 per udev rule!)
> > gnome DE with compiz-fusion 0.5.2 an beryl 0.5.2
> >
> > x86_64 architecture
> >
> > The distro is Gentoo unstable
> >
> > Sincerly,
> >
> > Thomas
>
> what does your /etc/dhcp/dhclient.conf look like?
I don't have this file. There is only an dhclient.conf.example
> Did you check the
> output of the networkmanager ebuild? Is it the newly stabled
> 0.6.5_p200 or 0.6.5 or something from an overlay?
It is 0.6.5_p20070823
Two things I forgot to mention:
* Network manager works as expected when using an unencrypted network.
* My wpa_supplicant.conf:
network={
ssid="NETGEAR"
psk="VERY_SECRET_PASSWORD" #this is changed, if course
priority=5
}
Thou NM is from main portage, I'm also using the xeffects overlay.
>
> ___
> 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: Network Manager doesn't work an b9rks keyboard
On Wed, 2007-09-05 at 22:29 +0200, Thomas Ilnseher wrote: > Hi, all. > > I have got a serious problem eith Networkmanager: Whenever I Try to > connect to my wireless network, it just b0rks the keyboard. That means > that any attempts to press any key (even ctrl+alt+backspace) are > ignored. The Mouse still works as expected. If I then try to reboot the > computer, It hangs on rebooting. In this situation, magic sysreq works, > but a "ctrl+alt+printscreen+b" doesn't restart the computer, but works > as expected. > > If I do this manually: > > # ifconfig wlan0 up > # wpa_supplicant -B -iwlan0 -Dwext -c/etc/.../wpa_supplicant.conf > # dhcpc wlan0 > > then my wireless comes up, without problems. The network is Wpa > encrypted. (WPA2-PSK) > > Here is some system information: > > kernel 2.6.23-rc4 > wireless driver: bcm43xx (eth1 changed to wlan0 per udev rule!) > gnome DE with compiz-fusion 0.5.2 an beryl 0.5.2 > > x86_64 architecture > > The distro is Gentoo unstable > > Sincerly, > > Thomas what does your /etc/dhcp/dhclient.conf look like? Did you check the output of the networkmanager ebuild? Is it the newly stabled 0.6.5_p200 or 0.6.5 or something from an overlay? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Network Manager doesn't work an b9rks keyboard
Hi, all. I have got a serious problem eith Networkmanager: Whenever I Try to connect to my wireless network, it just b0rks the keyboard. That means that any attempts to press any key (even ctrl+alt+backspace) are ignored. The Mouse still works as expected. If I then try to reboot the computer, It hangs on rebooting. In this situation, magic sysreq works, but a "ctrl+alt+printscreen+b" doesn't restart the computer, but works as expected. If I do this manually: # ifconfig wlan0 up # wpa_supplicant -B -iwlan0 -Dwext -c/etc/.../wpa_supplicant.conf # dhcpc wlan0 then my wireless comes up, without problems. The network is Wpa encrypted. (WPA2-PSK) Here is some system information: kernel 2.6.23-rc4 wireless driver: bcm43xx (eth1 changed to wlan0 per udev rule!) gnome DE with compiz-fusion 0.5.2 an beryl 0.5.2 x86_64 architecture The distro is Gentoo unstable Sincerly, Thomas ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Static IP settings in 0.7 -- per "connection" or "interface"?
Ok, thanks a lot! > If you create multiple connections for an interface that does not have a > good means to autodetect what connection to use (ie, ethernet, serial > modem, etc), you will need to explicitly choose which connection you'd > like. You can mark one connection as "autoconnect = False", NM won't > try it by default. So I think you can have one Connection as default > when you plug in the cable, and others available as you need them. > Right, sounds good to me. Hugo On Wed, 05 Sep 2007 14:02:32 -0400, "Dan Williams" <[EMAIL PROTECTED]> said: > On Wed, 2007-09-05 at 19:01 +0200, [EMAIL PROTECTED] wrote: > > Good day all, > > > > The NetworkManagerFAQ[1] indicates that "Better support of static IP > > addresses is planned and in-progress for NetworkManager 0.7.", as does > > various emails on the mailing list archives (though it is not totally > > clear from NetworkManagerToDo[2]). > > > > I guess it will then be possible for the user to set stuff like IP > > address, Subnet mask and Gateway (is that right?) > > > > Question: Will such settings be configured per *"connection"*, so that I > > could, for example, use one static IP for one wireless access point, > > another static IP for another wireless access point, and dynamic IP for > > others? Or will the settings be configured per *"interface"* (such as > > eth0, eth1...)? > > Per connection. There's a page at live.gnome.org called > NetworkManagerConfiguration and NetworkManagerConfigurationSpecification > that you may want to look at. Note that those pages represent the > ideal, and many of those options won't quite work for a bit... > > > (I would much prefer the former..) > > > > How about wired access points? Will NetworkManager be able to > > differentiate between different wired "connections" (or "access > > points"), and store different settings for them? > > If you create multiple connections for an interface that does not have a > good means to autodetect what connection to use (ie, ethernet, serial > modem, etc), you will need to explicitly choose which connection you'd > like. You can mark one connection as "autoconnect = False", NM won't > try it by default. So I think you can have one Connection as default > when you plug in the cable, and others available as you need them. > > Whether or not in the future there's some sort of autodetection by > arping or otherwise of a known MAC address is something people have > proposed, but needs a lot more discussion (sysadmins hate it). > > Dan > > > > > As a sidenote I would like to say that I find NetworkManager to be > > totally excellent. > > > > Best regards > > > > Hugo Heden > > > > [1] > > http://live.gnome.org/DarrenAlbers/NetworkManagerFAQ#head-c8b3f6905f51eed368b9c21893edabcc82531bbc > > [2] http://live.gnome.org/NetworkManagerToDo > > > -- http://www.fastmail.fm - A no graphics, no pop-ups email service ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Static IP settings in 0.7 -- per "connection" or "interface"?
On Wed, 2007-09-05 at 19:01 +0200, [EMAIL PROTECTED] wrote: > Good day all, > > The NetworkManagerFAQ[1] indicates that "Better support of static IP > addresses is planned and in-progress for NetworkManager 0.7.", as does > various emails on the mailing list archives (though it is not totally > clear from NetworkManagerToDo[2]). > > I guess it will then be possible for the user to set stuff like IP > address, Subnet mask and Gateway (is that right?) > > Question: Will such settings be configured per *"connection"*, so that I > could, for example, use one static IP for one wireless access point, > another static IP for another wireless access point, and dynamic IP for > others? Or will the settings be configured per *"interface"* (such as > eth0, eth1...)? Per connection. There's a page at live.gnome.org called NetworkManagerConfiguration and NetworkManagerConfigurationSpecification that you may want to look at. Note that those pages represent the ideal, and many of those options won't quite work for a bit... > (I would much prefer the former..) > > How about wired access points? Will NetworkManager be able to > differentiate between different wired "connections" (or "access > points"), and store different settings for them? If you create multiple connections for an interface that does not have a good means to autodetect what connection to use (ie, ethernet, serial modem, etc), you will need to explicitly choose which connection you'd like. You can mark one connection as "autoconnect = False", NM won't try it by default. So I think you can have one Connection as default when you plug in the cable, and others available as you need them. Whether or not in the future there's some sort of autodetection by arping or otherwise of a known MAC address is something people have proposed, but needs a lot more discussion (sysadmins hate it). Dan > > As a sidenote I would like to say that I find NetworkManager to be > totally excellent. > > Best regards > > Hugo Heden > > [1] > http://live.gnome.org/DarrenAlbers/NetworkManagerFAQ#head-c8b3f6905f51eed368b9c21893edabcc82531bbc > [2] http://live.gnome.org/NetworkManagerToDo > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Static IP settings in 0.7 -- per "connection" or "interface"?
Good day all, The NetworkManagerFAQ[1] indicates that "Better support of static IP addresses is planned and in-progress for NetworkManager 0.7.", as does various emails on the mailing list archives (though it is not totally clear from NetworkManagerToDo[2]). I guess it will then be possible for the user to set stuff like IP address, Subnet mask and Gateway (is that right?) Question: Will such settings be configured per *"connection"*, so that I could, for example, use one static IP for one wireless access point, another static IP for another wireless access point, and dynamic IP for others? Or will the settings be configured per *"interface"* (such as eth0, eth1...)? (I would much prefer the former..) How about wired access points? Will NetworkManager be able to differentiate between different wired "connections" (or "access points"), and store different settings for them? As a sidenote I would like to say that I find NetworkManager to be totally excellent. Best regards Hugo Heden [1] http://live.gnome.org/DarrenAlbers/NetworkManagerFAQ#head-c8b3f6905f51eed368b9c21893edabcc82531bbc [2] http://live.gnome.org/NetworkManagerToDo -- http://www.fastmail.fm - IMAP accessible web-mail ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wpa_supplicant options
On Wed, 2007-09-05 at 08:43 -0300, Joel Goguen wrote: > It's working great everywhere, except at my university. They just > implemented a WPA2 secured network, using TTLS/PAP, and NetworkManager > appears to hang after completing "Stage 2 of 5". I say "appears" > because it functions normally, the list of wireless networks updates, > and after a few minutes it asks me for the authentication information > again and then times out. If I disable NetworkManager and bring up > wpa_supplicant and the interface manually with -Dwext then I get the > same thing. If I use -Dmadwifi, then it all works almost immediately. So if you can reproduce the issue without NetworkManager in the mix, that helps narrow down the problem. This definitely seems like a driver problem to me. If you provide the wpa_supplicant config files to the madwifi driver people, likely they will be able to help you debug why their WEXT support isn't working here. The atheros situation will hopefully get a lot better in a few kernel versions because the ar5k mac80211-based driver will be upstream. And it'll have the same WEXT problems that iwlwifi and bcm43xx and all the others do. Which means it'll likely work quite a lot better than madwifi. Dan > I added a quick check to NetworkManager for the existence of a file, > and if it exists to pass 'madwifi' to wpa_cli instead of 'wext', and > after recompiling, installing, and creating that file, NetworkManager > authenticates to this network almost immediately. It's a horrible > hack job, if I'd wanted to spend more than 5 minutes I should have > added a command-line option or read a config file... > > On 9/5/07, Simon Geard <[EMAIL PROTECTED]> wrote: > > On Tue, 2007-09-04 at 08:42 -0300, Joel Goguen wrote: > > > I'm trying to force NetworkManager to run wpa_supplicant with a > > > specific set of options (most importantly, -Dmadwifi) but it seems no > > > matter what files I edit, it always gets run with the same options. > > > > Why do you need to use -Dmadwifi? For a long time now, the madwifi > > drivers have provided sufficient support for wireless extensions that > > the default (-Dwext) ought to be fine. It's worked fine for me since at > > least last year some time... > > > > Simon. > > > > ___ > > 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: wpa_supplicant options
It's working great everywhere, except at my university. They just implemented a WPA2 secured network, using TTLS/PAP, and NetworkManager appears to hang after completing "Stage 2 of 5". I say "appears" because it functions normally, the list of wireless networks updates, and after a few minutes it asks me for the authentication information again and then times out. If I disable NetworkManager and bring up wpa_supplicant and the interface manually with -Dwext then I get the same thing. If I use -Dmadwifi, then it all works almost immediately. I added a quick check to NetworkManager for the existence of a file, and if it exists to pass 'madwifi' to wpa_cli instead of 'wext', and after recompiling, installing, and creating that file, NetworkManager authenticates to this network almost immediately. It's a horrible hack job, if I'd wanted to spend more than 5 minutes I should have added a command-line option or read a config file... On 9/5/07, Simon Geard <[EMAIL PROTECTED]> wrote: > On Tue, 2007-09-04 at 08:42 -0300, Joel Goguen wrote: > > I'm trying to force NetworkManager to run wpa_supplicant with a > > specific set of options (most importantly, -Dmadwifi) but it seems no > > matter what files I edit, it always gets run with the same options. > > Why do you need to use -Dmadwifi? For a long time now, the madwifi > drivers have provided sufficient support for wireless extensions that > the default (-Dwext) ought to be fine. It's worked fine for me since at > least last year some time... > > Simon. > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > -- Joel Goguen http://jgoguen.net/ ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wpa_supplicant options
On Tue, 2007-09-04 at 08:42 -0300, Joel Goguen wrote: > I'm trying to force NetworkManager to run wpa_supplicant with a > specific set of options (most importantly, -Dmadwifi) but it seems no > matter what files I edit, it always gets run with the same options. Why do you need to use -Dmadwifi? For a long time now, the madwifi drivers have provided sufficient support for wireless extensions that the default (-Dwext) ought to be fine. It's worked fine for me since at least last year some time... Simon. signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
