Re: Errors running current SVN code
On Wed, 2007-01-31 at 10:07 -0500, Dan Williams wrote: We can change the internal stuff in 0.6, but we cannot change the DBus interface. No problem there - 0.6 works fine for me, since I don't care about it ignoring the odd access point, as long as it can connect to my own without crashing. See above. SSID will not and should not be part of the object path in D-Bus, nor in GConf. Ok, that re-working this sounds a little beyond the scope of this bug. For the time being, I might settle for making sure the SSID always gets encoded correctly so as not to crash D-Bus. Sure! I think the first step is to change NMAccessPoint so that the 'ssid' member is a u8[32]. I'd also like to change 'essid' to 'ssid' for NMAccessPoint too. No problem with the rename - that way any code that doesn't get changed doesn't compile, ensuring nothing accidentally gets missed. Incidentally, what's the difference between essid and orig_essid in that struct? Is it simply that essid is guaranteed to be in UTF8 and orig_essid might not be? Furthermore, I'd like to change the name of NMAccessPoint, but I'm not yet sure what to. NMBSSID is much more appropriate, but looks really ugly. I'll leave that one for now... I'd rather not be making more changes at once than absolutely required, and I hate resolving merge conflicts... Only for debugging output; since we won't be passing a printable SSID outside of NM (it will always be a 32 item byte array over D-Bus), we won't need to do this. Tools that interface with NM over D-Bus (the applet) will of course need to figure out how to convert random SSIDs to a printable string if only for a dropdown menu or entry of the SSID from a CLI. In that case, Volker's suggestion of showing dots in place of unprintable characters is probably the most appropriate. I'll go with that, if there's no objections. 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
Re: Errors running current SVN code
On Thu, 2007-02-01 at 21:44 +1300, Simon Geard wrote: Incidentally, what's the difference between essid and orig_essid in that struct? Is it simply that essid is guaranteed to be in UTF8 and orig_essid might not be? And as I think about it, is that a meaningful distinction if we're not going to pretend SSID is a string? 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
Re: [Fwd: failure of NETWORKMANAGER_)^_$_RELEASE ond FC5]
On Wed, 2007-01-31 at 17:44 -0600, Aaron Konstam wrote: In order to get LEAP authentication I installed the unstable version of NetworkManager from the CVS on Sept 4. This worked well for a whale but in November (possibly affected by a security patch installed on the system) Leap authentication was spotty. So I downloaded NETWORKMANAGER_0.6_4_Release on Dec 26. I compiles it successfully but just installed it today. It failed to work in the following sense. The nm-applet was launched automatically and I was asked for the password on the access point. Immediately thereafter the connection failed leaving the well known symbol on the upper panel of my desktop and I could not revive it of make it try again to connect. I immediately reinstalled the unstable version which worked. Now what can I do to get you the details that would allow you to debug the reason for failure. This product has always just worked out of the box on FC5 so I ma stumped. What can I do to pin point the reasons for failure? Probably send logs from /var/log/messages during a connection attempt (or, as root, stop NM, then '/usr/sbin/NetworkManager --no-daemon' and try to connect with the applet). If the logs are 75K, please either compress them or send them directly to me. Thanks! dan === Are [Linux users] lemmings collectively jumping off of the cliff of reliable, well-engineered commercial software? (By Matt Welsh) === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ 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: Errors running current SVN code
On Thu, 2007-02-01 at 21:49 +1300, Simon Geard wrote: On Thu, 2007-02-01 at 21:44 +1300, Simon Geard wrote: Incidentally, what's the difference between essid and orig_essid in that struct? Is it simply that essid is guaranteed to be in UTF8 and orig_essid might not be? And as I think about it, is that a meaningful distinction if we're not going to pretend SSID is a string? That's exactly the reason. Since we no longer care, orig_essid can go away and we'll just use ssid everywhere. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Phase2 patch v2
Hello. On Wed, 2007-01-31 at 16:10, Volker Braun wrote: Are you sure you are linking against the new libnm-util.so (and not your old one with the extra phase2 argument)? I purged all distro packages (Debian), build it with the source packages and your patch from scratch and it still don't work. :( I even wrote a wrapper around wpa_supplicant to always give me -dd output, but it seems nm not even start to communicate with the supplicant. This driving me nuts. :) I'll take a look into it next week again as I have some other stuff to do right now. BTW, your setup is dynamic WEP key + phase 2 or wpa enterprise + phase 2? Anybody else got such a setup working with the patch? I get the feeling that something is wrong with my local setup. regards Stefan Schmidt signature.asc Description: Digital signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Weird issue: hostap, prism2.5 card, wpa2, network-manager, kubuntu ubuntu 6.1
Hi, I have found an weird issue. I'm double posting (I know this is not proper nettiquette), but the issue seems to fall squarely between the 2 lists. IBM Thinkpad A30 Prism 2.5 card Kubuntu Ubuntu 6.10 (Edgy) package: hostap-utils v1:0.4.0-1 package: network-manager v0.6.3-2ubuntu6 hostap fails to create an adapter when loaded, unless i also install the network-manager-gnome (maybe just network-manager (although I never tried)). That is, if I do a fresh install of either Ubuntu or Kubuntu, then aptitude upgrade, install hostap-utils, blacklist orinoco_pci, orinoco, prism2_pci, and reboot. When the box comes up I only have eth0 and lo adapters under ifconfig. Then I install network-manager-gnome. rmmod hostap_pci, hostap, modprobe hostap, hostap_pci (or just reboot) and I get all the proper adapters and can connect to a WPA2 ap. It seems like something is missing from the hostap-utils distribution, or some other weird interaction is going on. Thanks Jay ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
A question of how connection proceeds.
I have been having trouble with an access point that is Leap authenticated. What sees form the applet display is an circular arrow continuing to precess and then finally a connection signaled by vertical bars. What is happening in the connecton process when the arrow precesses and what event causes the vertical bar to appear? I ask because the arrow precesses but the vertical bar does not appear. Sometimes the connection is made to a different access point and sometimes the whole process fails irrevocably in the sense no access point can be connected to. -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Phase2 patch v2
On Thu, 2007-02-01 at 14:44 +0100, Stefan Schmidt wrote: Hello. On Wed, 2007-01-31 at 16:10, Volker Braun wrote: Are you sure you are linking against the new libnm-util.so (and not your old one with the extra phase2 argument)? I purged all distro packages (Debian), build it with the source packages and your patch from scratch and it still don't work. :( I even wrote a wrapper around wpa_supplicant to always give me -dd output, but it seems nm not even start to communicate with the supplicant. If you edit the code in nm-device-802-11-device.c, in supplicant_exec(): - char * argv[4]; + char * argv[5]; GError *error = NULL; GPidpid = -1; int sup_stdout; argv[0] = WPA_SUPPLICANT_BIN; argv[1] = -g; argv[2] = WPA_SUPPLICANT_GLOBAL_SOCKET; - argv[3] = NULL; + argv[3] = -ddd; + argv[4] = NULL; That will then make NM log everything that wpa_supplicant prints to stdout and stderr, to the normal place that NM logs things. If you run NM as root with --no-daemon, it will go to your terminal. We really need to get your NM output here to see what the problem is. Dan This driving me nuts. :) I'll take a look into it next week again as I have some other stuff to do right now. BTW, your setup is dynamic WEP key + phase 2 or wpa enterprise + phase 2? Anybody else got such a setup working with the patch? I get the feeling that something is wrong with my local setup. regards Stefan Schmidt ___ 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
Can't get ip from dhcp when making connection to ap
Hi, I'm using fedora and ipw2200 with networkmanager. My problem is a bit strang i can't seem to get an ip networkmanager says 4 of 5 (connection timed out). but when i try to connected to an non secure ip i can get an ip. so I have narrowd the problem down to only i can't get an ip adres when connecting to a secure access point. plz help me out -- Philippe Delodder [EMAIL PROTECTED] http://www.delodder.be ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Phase2 patch v2
On Thu, 01 Feb 2007 14:44:34 +0100, Stefan Schmidt wrote: BTW, your setup is dynamic WEP key + phase 2 or wpa enterprise + phase 2? I use the former: Dynamic WEP + phase 2 PAP (identity+password+anonymous identity). And btw, the phase2-v2.patch is against branches/NETWORKMANAGER_0_6_0_RELEASE (=STABLE) Also, for anybody trying out a devel version of NetworkManager I suggest to work with a special directory like autogen.sh --prefix /home/user/nm-test then after the make install you can be sure that the new libraries are used: ldd /home/user/nm-test/bin/NetworkManager Please somebody give this a try and report back. I can write more explicit instructions if desired, just ask :-) Volker ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Can't get ip from dhcp when making connection to ap
On Thu, 2007-02-01 at 16:17 +0100, lodder wrote: Hi, I'm using fedora and ipw2200 with networkmanager. My problem is a bit strang i can't seem to get an ip networkmanager says 4 of 5 (connection timed out). but when i try to connected to an non secure ip i can get an ip. so I have narrowd the problem down to only i can't get an ip adres when connecting to a secure access point. Are you _sure_ your WEP key is correct? If the WEP key is incorrect, then you won't be able to do DHCP. Furthermore, there's no way to know if your WEP key is wrong (unlike with WPA). Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Phase2 patch v2
Hello.
On Thu, 2007-02-01 at 10:48, Dan Williams wrote:
On Thu, 2007-02-01 at 14:44 +0100, Stefan Schmidt wrote:
I even wrote a wrapper around wpa_supplicant to always give me -dd
output, but it seems nm not even start to communicate with the
supplicant.
If you edit the code in nm-device-802-11-device.c, in supplicant_exec():
- char * argv[4];
+ char * argv[5];
GError *error = NULL;
GPidpid = -1;
int sup_stdout;
argv[0] = WPA_SUPPLICANT_BIN;
argv[1] = -g;
argv[2] = WPA_SUPPLICANT_GLOBAL_SOCKET;
- argv[3] = NULL;
+ argv[3] = -ddd;
+ argv[4] = NULL;
I have already the following in src/nm-device-802-11-wireless.c:
supplicant_exec (NMDevice80211Wireless *self)
{
gbooleansuccess = FALSE;
char * argv[5];
GError *error = NULL;
GPidpid = -1;
int sup_stdout;
argv[0] = WPA_SUPPLICANT_BIN;
argv[1] = -dd;
argv[2] = -g;
argv[3] = WPA_SUPPLICANT_GLOBAL_SOCKET;
argv[4] = NULL;
No src/nm-device-802-11-device.c here.
That will then make NM log everything that wpa_supplicant prints to
stdout and stderr, to the normal place that NM logs things. If you run
NM as root with --no-daemon, it will go to your terminal.
We really need to get your NM output here to see what the problem is.
That's why I posted links to the first logs. There was no change in
the logs today.
regards
Stefan Schmidt
signature.asc
Description: Digital signature
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Phase2 patch v2
On Thu, 2007-02-01 at 17:01 +0100, Stefan Schmidt wrote:
Hello.
On Thu, 2007-02-01 at 10:48, Dan Williams wrote:
On Thu, 2007-02-01 at 14:44 +0100, Stefan Schmidt wrote:
I even wrote a wrapper around wpa_supplicant to always give me -dd
output, but it seems nm not even start to communicate with the
supplicant.
If you edit the code in nm-device-802-11-device.c, in supplicant_exec():
- char * argv[4];
+ char * argv[5];
GError *error = NULL;
GPidpid = -1;
int sup_stdout;
argv[0] = WPA_SUPPLICANT_BIN;
argv[1] = -g;
argv[2] = WPA_SUPPLICANT_GLOBAL_SOCKET;
- argv[3] = NULL;
+ argv[3] = -ddd;
+ argv[4] = NULL;
I have already the following in src/nm-device-802-11-wireless.c:
supplicant_exec (NMDevice80211Wireless *self)
{
gbooleansuccess = FALSE;
char * argv[5];
GError *error = NULL;
GPidpid = -1;
int sup_stdout;
argv[0] = WPA_SUPPLICANT_BIN;
argv[1] = -dd;
Put in another 'd' so there are 3 in all.
argv[2] = -g;
argv[3] = WPA_SUPPLICANT_GLOBAL_SOCKET;
argv[4] = NULL;
No src/nm-device-802-11-device.c here.
Typo on my part.
dan
That will then make NM log everything that wpa_supplicant prints to
stdout and stderr, to the normal place that NM logs things. If you run
NM as root with --no-daemon, it will go to your terminal.
We really need to get your NM output here to see what the problem is.
That's why I posted links to the first logs. There was no change in
the logs today.
regards
Stefan Schmidt
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
