Exclude certain APs from roaming
Hello list, I'm wondering if there is a way to exclude specific APs from roaming? In my case every time I boot my notebook nm connects to an AP in the neighbourhood which seems to be an open system with no access key configured. This behaviour I notice every time when any open AP is active. nm first tries to connect to this one an not to the last one it was connected. Isn't this a security lack? Thanks in advance, Klaus ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Proper WEP Code
On Sun, 2007-12-09 at 19:22 -0500, Dan Williams wrote: On Sun, 2007-12-09 at 15:48 -0600, Aaron Konstam wrote: On Mon, 2007-12-10 at 01:42 +1000, [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey everyone sorry to disturb you all but what is the proper way to put your wep code in hex into the nm-applet? So far i can't figure it out and it won't allow me to connect. This is my code (obviously without the stars): **:38:22:05:40:AB:**:EF:04:38:22:05:** Thanks in advance i tried googling it but i don't think i could think of the right combination of search phrase. NJ But the associated question do you really want to set the WEP encryption code in hex rather than in ASCII, which is another option. He needs to be sure he matches the setting used on the AP. It won't work if he uses the wrong type in the applet. That said, most APs don't use ASCII passphrases (it was an older lucent thing), so I'd expect it to be a hex key, most likely. Dan Dan, You may be right but all of the wireless APs distributed by ATT have ASCII WEP passwds that are annoyingly 10 rather then 13 ASCII characters. -- === Could I have a drug overdose? === 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
Re: Exclude certain APs from roaming
On Mon, 2007-12-10 at 09:57 +0100, [EMAIL PROTECTED] wrote: Hello list, I'm wondering if there is a way to exclude specific APs from roaming? In my case every time I boot my notebook nm connects to an AP in the neighbourhood which seems to be an open system with no access key configured. This behaviour I notice every time when any open AP is active. nm first tries to connect to this one an not to the last one it was connected. Isn't this a security lack? You probably chose that AP from the menu at least once before... 0.6.x: look for it in GConf under /system/networking/wireless/networks and use gconftool-2 --recursive-unset /system/networking/wireless/networks/essid to kill it. 0.7.x: look for it in GConf under /system/networking/connections/connection id/connection/ and do the same sort of thing with gconftool-2. 0.7.x will soon have a connection editor which will allow you to do this graphically and easily. Just not enough time quite yet to clean up what's there. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Overriding connections (VPN) that abuse DNS (was: Wireless DHCP overwrites DNS settings)
On Mon, 2007-12-10 at 11:44 -0500, Derek Atkins wrote: Dan Williams [EMAIL PROTECTED] writes: On Sat, 2007-12-08 at 13:36 -0800, Ross Patterson wrote: This is somewhat related. I have a poorly behaved VPN connection that sends NM empty DNS settings so that no DNS works when I'm connected to the VPN. I can't fix the VPN, so my current workaround is to copy /etc/resolv.conf before I connect to the VPN, and then write it over the /etc/resolv.conf written by NM *after* connecting to the VPN. IOW, I manually restore the original DNS configuration. This is annoying to say the least. My question is, is there a way to preseve the DNS settings on *just that* VPN connection so I don't have to do this dance every time? Not yet; but it can be fixed internally in NetworkManager pretty easily. Nobody has come up with a patch yet, and I haven't had time. Internally, the IP4 configs are essentially a stack with between 0 and 2 configs per device. The device's config is at #1, and the VPN config is at #2. Whenever the config stack changes, settings should get merged with the higher numbered items taking priority over the lower numbered ones. Right now, a config with a higher number blows away the config with the lower number entirely. I have a VPN that also gives me incomplete DNS info. The way I fixed this was by writing a wrapper around /usr/bin/nm-vpnc-service-vpnc-helper that adjusts the vpnc environment before passing it back to NM via dbus. In my case I needed to adjust the CISCO_DEF_DOMAIN variable. YMMV. I was working on this today; the interesting thing is that if the VPN hands back bogus DNS information, should NM honor the default domain that the VPN sends back, if any, and should it honor the DNS searches, if any? I'd guess no to searches, maybe yes to default domain. The DNS searches and nameservers should probably be together in that if there are no nameservers specified, NM falls back to the underlying device's nameservers and searches. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Overriding connections (VPN) that abuse DNS (was: Wireless DHCP overwrites DNS settings)
Quoting Dan Williams [EMAIL PROTECTED]: I have a VPN that also gives me incomplete DNS info. The way I fixed this was by writing a wrapper around /usr/bin/nm-vpnc-service-vpnc-helper that adjusts the vpnc environment before passing it back to NM via dbus. In my case I needed to adjust the CISCO_DEF_DOMAIN variable. YMMV. I was working on this today; the interesting thing is that if the VPN hands back bogus DNS information, should NM honor the default domain that the VPN sends back, if any, and should it honor the DNS searches, if any? I'd guess no to searches, maybe yes to default domain. The DNS searches and nameservers should probably be together in that if there are no nameservers specified, NM falls back to the underlying device's nameservers and searches. In my case the problem was with Split DNS. I needed to convince NM to configure the Split DNS to send two domains to the VPN DNS Servers and not just the single domain that the VPN returned. Dan -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Proper WEP Code
Aaron Konstam wrote: I am confused as usual. You are seeming to say that 40/128 ASCII passphrase are for APs that already have a passwphrase stored in their memory. But then things get confusing. Are you saying that a 40/128 HEX passphrase can actually change the passphrase stored in the AP? No, he's saying that behind the scenes, all passphrases are actually just exchanged as hex. So, if you type in 'A' it will send '4141414141' in the background. If you had just used the hex in the first place, it would work too. --Pat ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
