Re: ethernet connection
Do you have 2 Ethernet devices? -derek Sent using my mobile device. Please excuse any typos. On February 12, 2020 4:37:51 PM r...@shrl.nl wrote: Is there a way to configure two wired connections. One for my home network (assigned-mac-address=permanent) and one for all other wired connections (assigned-mac-address=random) in a manner at which networkmanager autodetects if the wired connection is at my home network? -- Jaap van Wingerde e-mail: r...@shrl.nl ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Frequent network drops (NM, FC29)?
HI, I'm having an issue on my Fedora-29 laptop where my Wifi shows periodic network drops. I'm running mtr and it's working fine, but then it effectively stops transmitting packets for a few seconds, and then it starts up again. This pause coincides with the following entries in my /var/log/messages: Apr 29 10:23:25 securerf wpa_supplicant[1899]: wlp0s20f0u2: CTRL-EVENT-DISCONNECTED bssid=dc:7f:a4:67:5a:a5 reason=0 Apr 29 10:23:25 securerf wpa_supplicant[1899]: wlp0s20f0u2: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Apr 29 10:23:25 securerf wpa_supplicant[1899]: wlp0s20f0u2: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US Apr 29 10:23:33 securerf wpa_supplicant[1899]: wlp0s20f0u2: Trying to associate with dc:7f:a4:67:5a:a5 (SSID='ATT234H8Fp' freq=2462 MHz) Apr 29 10:23:33 securerf wpa_supplicant[1899]: wlp0s20f0u2: Associated with dc:7f:a4:67:5a:a5 Apr 29 10:23:33 securerf wpa_supplicant[1899]: wlp0s20f0u2: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Apr 29 10:23:33 securerf wpa_supplicant[1899]: wlp0s20f0u2: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US Apr 29 10:23:33 securerf wpa_supplicant[1899]: wlp0s20f0u2: WPA: Key negotiation completed with dc:7f:a4:67:5a:a5 [PTK=CCMP GTK=CCMP] Apr 29 10:23:33 securerf wpa_supplicant[1899]: wlp0s20f0u2: CTRL-EVENT-CONNECTED - Connection to dc:7f:a4:67:5a:a5 completed [id=0 id_str=] Apr 29 10:23:33 securerf wpa_supplicant[1899]: bgscan simple: Failed to enable signal strength monitoring Any ideas how to debug or, better yet, fix this? I have already rebooted my wifi router. I am sitting 15-20 feet away with an almost direct line-of sight, but I can literally be sitting 3 feet away and still have this issue. Other systems on my network don't appear have this kind of issue. Thanks, -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to deal with a new Wifi Adapter?
Thanks. -derek Thomas Haller writes: > On Thu, 2019-04-11 at 10:16 -0400, Derek Atkins wrote: >> Thanks, Thomas, >> >> Thomas Haller via networkmanager-list >> writes: >> >> [snip] >> >> Any chance you could give a quick explanation of what these (two?) >> sets >> of commands are doing? > > Hi, > > > UUIDS is a variable containing all the "connection.uuid"s for your Wi- > Fi profiles. > > Then, the first "for" iterates over them, and for each connection > profile it prints 5 fields (so you see what is configured in these > profiles). > > The second, itereates over the same profiles, but clears the > connection.interface-name and wifi.mac-address properties. These two > properties (among others) tie a connection profile to a certain device, > by clearing them, the profile is applicable for any device, regardless > of the interface name and MAC address. See `man nm-settings` for the > properties. And see `man nmcli` or just `nmcli help` for info about > nmcli. > > > Does this help? > > best, > Thomas > >> >> Thanks, >> >> -derek >> >> > Hi, >> > >> > I'd do: >> > >> > UUIDS="$(nmcli -g TYPE,UUID connection show | \ >> > sed -n 's/802-11-wireless://p')" >> > >> > for UUID in $UUIDS; \ >> > do \ >> > nmcli \ >> >-f connection.id,connection.uuid,802-11- >> > wireless.ssid,connection.interface-name,802-11-wireless.mac-address >> > \ >> >-mode multiline \ >> >connection show uuid "$UUID" ; \ >> > echo ; \ >> > done >> > >> > if you want to clear these values: >> > >> > for UUID in $UUIDS; \ >> > do \ >> > echo "$UUID ..." ; \ >> > nmcli connection modify uuid "$UUID" \ >> > connection.interface-name '' \ >> > wifi.mac-address '' ; \ >> > done >> > >> > >> > > In a similar vein, is there a way to tell NM to disable to >> > > embedded >> > > wifi >> > > adapter? >> > >> > put >> > >> > [device-unmanage-internal-wifi] >> > match-device=mac:aa:bb:cc:dd:ee:ff >> > managed=0 >> > >> > to /etc/NetworkManager/conf.d/99-unmanaged-internal-wifi.conf and >> > restart. >> > >> > Or even blacklist the module from loading in /etc/modprobe.d. >> > >> > >> > best, >> > Thomas >> > >> > ___ >> > networkmanager-list mailing list >> > networkmanager-list@gnome.org >> > https://mail.gnome.org/mailman/listinfo/networkmanager-list >> > > -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to deal with a new Wifi Adapter?
Thanks, Thomas, Thomas Haller via networkmanager-list writes: [snip] Any chance you could give a quick explanation of what these (two?) sets of commands are doing? Thanks, -derek > Hi, > > I'd do: > > UUIDS="$(nmcli -g TYPE,UUID connection show | \ > sed -n 's/802-11-wireless://p')" > > for UUID in $UUIDS; \ > do \ > nmcli \ >-f > connection.id,connection.uuid,802-11-wireless.ssid,connection.interface-name,802-11-wireless.mac-address > \ >-mode multiline \ >connection show uuid "$UUID" ; \ > echo ; \ > done > > if you want to clear these values: > > for UUID in $UUIDS; \ > do \ > echo "$UUID ..." ; \ > nmcli connection modify uuid "$UUID" \ > connection.interface-name '' \ > wifi.mac-address '' ; \ > done > > >> In a similar vein, is there a way to tell NM to disable to embedded >> wifi >> adapter? > > put > > [device-unmanage-internal-wifi] > match-device=mac:aa:bb:cc:dd:ee:ff > managed=0 > > to /etc/NetworkManager/conf.d/99-unmanaged-internal-wifi.conf and > restart. > > Or even blacklist the module from loading in /etc/modprobe.d. > > > best, > Thomas > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > https://mail.gnome.org/mailman/listinfo/networkmanager-list > -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
How to deal with a new Wifi Adapter?
Hi, I'm currently running Fedora 29 and my embedded wifi adapter is failing. So I bought a USB Wifi adapter, which seems to be working well.. Except for one problem: Network Manager does not know to apply all my existing wifi connection information to the new adapter. Short of going through each connection, changing it to the new adapter, then deleting the " 2" network that gets created --- is there some way to tell NM to apply all wifi networks to all wifi adapters? In a similar vein, is there a way to tell NM to disable to embedded wifi adapter? Thanks, -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: IPv6 RA route add/removal does not trigger dispatch action
Thomas Haller via networkmanager-list writes: > I think it's a missing feature. > > However, it also seems problematic, because a lot of router > advertisements are received. Running the dispatcher scripts each time, > sounds expensive. But they could be in a separate directory, and NM > would only spawn the dispatcher if there are any scripts there. Like > already done for pre-up and pre-down. I wouldn't trigger an event on every RA. That's just absurd. HOWEVER, I do feel it should trigger an event if the RA causes a local modification of state (e.g. route add/remote, etc). > best, > Thomas -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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?
Hi, Upgrading to NM 1.0.6 seems to have fixed the issue. Sorry for the noise. I suppose I should have checked to make sure I was at the current version first. -derek On Thu, October 1, 2015 3:30 pm, Derek Atkins wrote: > Hi, > > On Thu, October 1, 2015 2:51 pm, Dan Williams wrote: >> On Thu, 2015-10-01 at 13:34 -0400, Derek Atkins wrote: >>> Hi Dan, >>> >>> On Thu, October 1, 2015 12:49 pm, Dan Williams wrote: >>> >>> Apparently this still isn't working. I did the following: >>> >>> # cat /etc/sysconfig/network-scripts/ifcfg-eth0 >>> TYPE=Ethernet >>> BOOTPROTO=dhcp >>> DEFROUTE=yes >>> IPV4_FAILURE_FATAL=no >>> UUID=3a02edd8-e82d-4dca-a336-933e9177f4cd >>> DEVICE=eth0 >>> ONBOOT=yes >>> HWADDR=00:1f:7b:b2:14:42 >>> IPV6_FAILURE_FATAL=no >>> NAME=eth0 >>> # cat /etc/sysconfig/network-scripts/ifcfg-eth0:1 >>> DEVICE=eth0:1 >>> IPADDR=192.168.x.y >> >> I tested the config here and at least git master NM accepts the DHCP + >> aliases configuration. After doing 'nmcli con reload' could you do >> "nmcli con show 3a02edd8-e82d-4dca-a336-933e9177f4cd" and post the >> output for the IPv4 block? > > This is running on F22, NetworkManager-1.0.2-1.fc22.armv7hl > > I presume you mean: > ipv4.method:auto > ipv4.dns: > ipv4.dns-search: > ipv4.addresses: > ipv4.gateway: -- > ipv4.routes: > ipv4.route-metric: -1 > ipv4.ignore-auto-routes:no > ipv4.ignore-auto-dns: no > ipv4.dhcp-client-id:-- > ipv4.dhcp-send-hostname:yes > ipv4.dhcp-hostname: -- > ipv4.never-default: no > ipv4.may-fail: yes > > or do you also want: > > IP4.ADDRESS[1]: /24 > IP4.GATEWAY: > IP4.ROUTE[1]: dst = /32, nh = > , mt = 100 > IP4.DNS[1]: > IP4.DNS[2]: > IP4.DNS[3]: > IP4.DOMAIN[1]: ihtfp.org > > I just noticed there is an update available; I can try updating to 1.0.6 > to see if it solves the problem? > >> Dan > > -derek > > -- >Derek Atkins 617-623-3745 >de...@ihtfp.com www.ihtfp.com >Computer and Internet Security Consultant > > -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?
Hi, On Thu, October 1, 2015 2:51 pm, Dan Williams wrote: > On Thu, 2015-10-01 at 13:34 -0400, Derek Atkins wrote: >> Hi Dan, >> >> On Thu, October 1, 2015 12:49 pm, Dan Williams wrote: >> >> Apparently this still isn't working. I did the following: >> >> # cat /etc/sysconfig/network-scripts/ifcfg-eth0 >> TYPE=Ethernet >> BOOTPROTO=dhcp >> DEFROUTE=yes >> IPV4_FAILURE_FATAL=no >> UUID=3a02edd8-e82d-4dca-a336-933e9177f4cd >> DEVICE=eth0 >> ONBOOT=yes >> HWADDR=00:1f:7b:b2:14:42 >> IPV6_FAILURE_FATAL=no >> NAME=eth0 >> # cat /etc/sysconfig/network-scripts/ifcfg-eth0:1 >> DEVICE=eth0:1 >> IPADDR=192.168.x.y > > I tested the config here and at least git master NM accepts the DHCP + > aliases configuration. After doing 'nmcli con reload' could you do > "nmcli con show 3a02edd8-e82d-4dca-a336-933e9177f4cd" and post the > output for the IPv4 block? This is running on F22, NetworkManager-1.0.2-1.fc22.armv7hl I presume you mean: ipv4.method:auto ipv4.dns: ipv4.dns-search: ipv4.addresses: ipv4.gateway: -- ipv4.routes: ipv4.route-metric: -1 ipv4.ignore-auto-routes:no ipv4.ignore-auto-dns: no ipv4.dhcp-client-id:-- ipv4.dhcp-send-hostname:yes ipv4.dhcp-hostname: -- ipv4.never-default: no ipv4.may-fail: yes or do you also want: IP4.ADDRESS[1]: /24 IP4.GATEWAY: IP4.ROUTE[1]: dst = /32, nh = , mt = 100 IP4.DNS[1]: IP4.DNS[2]: IP4.DNS[3]: IP4.DOMAIN[1]: ihtfp.org I just noticed there is an update available; I can try updating to 1.0.6 to see if it solves the problem? > Dan -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?
Hi Dan, On Thu, October 1, 2015 12:49 pm, Dan Williams wrote: > Yes, you need a matching ifcfg file for the base interface. So you need > both ifcfg-eth0 and ifcfg-eth0:0. See the examples, eg ifcfg-aliasem0 > and ifcfg-aliasem0:1. > > The alias file should only have DEVICE and IPADDR fields; and DEVICE > must match that of the parent ifcfg file. They are intimately tied > together in the old initscripts, and the ifcfg-rh plugin remains > compatible with those. > > When NetworkManager sees the base file, it will also look for alias > files, and will add the IP address from the alias file to the main > connection's IP address list along with the label. So even with two > ifcfg files, you will only have one connection and you should see *both* > IP addresses in that one connection. When the connection is activated, > NM sends the label to the kernel, so /sbin/ip will show both addresses > on one interface, but /sbin/ifconfig will show two interfaces each with > one address, per its ignorance of the real situation. Apparently this still isn't working. I did the following: # cat /etc/sysconfig/network-scripts/ifcfg-eth0 TYPE=Ethernet BOOTPROTO=dhcp DEFROUTE=yes IPV4_FAILURE_FATAL=no UUID=3a02edd8-e82d-4dca-a336-933e9177f4cd DEVICE=eth0 ONBOOT=yes HWADDR=00:1f:7b:b2:14:42 IPV6_FAILURE_FATAL=no NAME=eth0 # cat /etc/sysconfig/network-scripts/ifcfg-eth0:1 DEVICE=eth0:1 IPADDR=192.168.x.y and after an nmcli con reload it still doesn't provide the alias address. Nor after a reboot. I'm sur I'm still missing *something* but I'm at a loss now. > Dan -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?
One more thing... On Wed, September 30, 2015 3:28 pm, Derek Atkins wrote: > Dan, > > On Wed, September 30, 2015 12:44 pm, Dan Williams wrote: >> On Wed, 2015-09-30 at 12:25 -0400, Derek Atkins wrote: >>> Dan, >>> >>> Dan Williams writes: >>> >>> I.e., just to make sure I understand correctly, in order to get what I >>> want I should just create /etc/sysconfig/network-scripts/ifcfg-eth0:0 >>> and let NM manage my alias that way? Do I need to do anything special >>> to get NM to notice it, or it will do so automagically on the next >>> restart/reboot? >> >> There are some alias examples here, FWIW: >> >> http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/settings/plugins/ifcfg-rh/tests/network-scripts >> >> And all that's really required is "nmcli con reload", you shouldn't ever >> need to restart NetworkManager to get config changes taken into account. > > I added this config file but it's not bringing up eth0:0. > > # cat /etc/sysconfig/network-scripts/ifcfg-eth0:0 > DEVICE=eth0:0 > IPADDR=192.168.x.y (yes, x.y are numbers) > BOOTPROTO=none > ONBOOT=yes > IPV6INIT=no > # > > What am I missing? Do I need the base ifcfg-eth0 file, too? (That file > was not created by anaconda). Or do I need some additional fields because > there is no ifcfg-eth0? Or do I need to tell NM to bring it up? Even after I add this file, I can't even manually "ifup" the interface! # nmcli con NAMEUUID TYPE DEVICE Wired connection 1 3a02edd8-e82d-4dca-a336-933e9177f4cd 802-3-ethernet eth0 # ifup eth0:0 Error: no device found for connection 'System eth0:0'. # nmcli con NAMEUUID TYPE DEVICE System eth0:0 81ad1dc6-9516-a6cf-73d9-600036a810a1 802-3-ethernet -- Wired connection 1 3a02edd8-e82d-4dca-a336-933e9177f4cd 802-3-ethernet eth0 # nmcli con reload # nmcli con NAMEUUID TYPE DEVICE Wired connection 1 3a02edd8-e82d-4dca-a336-933e9177f4cd 802-3-ethernet eth0 Even if I add a line NAME="System eth0:0" to the ifcfg-eth0:0 file, it still doesn't work... -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?
Dan, On Wed, September 30, 2015 12:44 pm, Dan Williams wrote: > On Wed, 2015-09-30 at 12:25 -0400, Derek Atkins wrote: >> Dan, >> >> Dan Williams writes: >> >> I.e., just to make sure I understand correctly, in order to get what I >> want I should just create /etc/sysconfig/network-scripts/ifcfg-eth0:0 >> and let NM manage my alias that way? Do I need to do anything special >> to get NM to notice it, or it will do so automagically on the next >> restart/reboot? > > There are some alias examples here, FWIW: > > http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/settings/plugins/ifcfg-rh/tests/network-scripts > > And all that's really required is "nmcli con reload", you shouldn't ever > need to restart NetworkManager to get config changes taken into account. I added this config file but it's not bringing up eth0:0. # cat /etc/sysconfig/network-scripts/ifcfg-eth0:0 DEVICE=eth0:0 IPADDR=192.168.x.y (yes, x.y are numbers) BOOTPROTO=none ONBOOT=yes IPV6INIT=no # What am I missing? Do I need the base ifcfg-eth0 file, too? (That file was not created by anaconda). Or do I need some additional fields because there is no ifcfg-eth0? Or do I need to tell NM to bring it up? > Dan -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?
Dan, Dan Williams writes: >> Could you explain more detail on how to add "label xxx" to the nmcli >> command (which you inconveniently cut out of your reply, so I've >> included it below)? I cannot find any reference to "label" in the nmcli >> documentation. >> >> nmcli con mod "Wired connection 1" +ipv4.addresses "192.168.x.y/24" > > If you really do need address labels (eg, interface aliases) then > NetworkManager has limited support for them. If you don't truly need > address labels, then I wouldn't use them. Anyway, NM supports address > labels, but only when they are set via ifcfg "alias" files. They > currently cannot be added via nmcli or set via the 'keyfile' plugin, > though that's just a case of "didn't implement yet" rather than anything > else. I.e., just to make sure I understand correctly, in order to get what I want I should just create /etc/sysconfig/network-scripts/ifcfg-eth0:0 and let NM manage my alias that way? Do I need to do anything special to get NM to notice it, or it will do so automagically on the next restart/reboot? > 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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?
Andrei, Andrei Borzenkov writes: > 29.09.2015 20:54, Dan Williams пишет: >> >>> Basically I want to automate NM doing, effectively: >>> >>>ifconfig eth0:0 192.168.x.y >> >> Don't do this with interface aliases; the kernel is perfectly capable of >> using more than one address on the same interface. Simply do: >> >> ip addr add 192.168.x.y/24 dev eth0 >> >> and magically you'll have two. >> > > > This makes addresses invisible in ifconfig output and that may confuse > legacy software (I know about at least one such case). Adding "label > xxx" will emulate legacy aliases enough to make them appear as > "normal" interface. Could you explain more detail on how to add "label xxx" to the nmcli command (which you inconveniently cut out of your reply, so I've included it below)? I cannot find any reference to "label" in the nmcli documentation. nmcli con mod "Wired connection 1" +ipv4.addresses "192.168.x.y/24" Thanks, -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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?
Hi, I've got an esoteric NM question. I've got two distinct networks that share an ethernet fabric (poor man's vlans). I have a F22 server that I want to put on both networks. It's currently configured to use DHCP for the primary network (and my DHCP server provides a static address). AFAICT there's really no way to get DHCP to provide two addresses, so I'd like to set up a secondary IP statically using nmcli (I did say this was a server, right?) Basically I want to automate NM doing, effectively: ifconfig eth0:0 192.168.x.y I know how I would do this using the old /etc/sysconfig/networking config files, but I have NO CLUE how to do with with nmcli. I've spent the last hour googling and reading about it and still haven't figured it out, yet. I suppose I could just add something to rc.local, but I'd rather do it the "right way" (and maybe learn something along the way). I know I can add a second IP to eth0 via: nmcli con mod "Wired connection 1" +ipv4.addresses "192.168.x.y/24" But I have no idea how this would interact with the primary address being obtained by DHCP. So, what nmcli magic command(s) do I need to run to do what I want? Thanks, -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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ANN: NetworkManager 0.9.10 released
Hey Dan, Congrats, and excellent work! Quick question on your 1.0 planning -- has VPN split-DNS with local caching ever made it back into NM? Back in the day it was working with named but it was dropped due to the difficulty in maintaining the named dbus interface patch. I missed that feature for a while, and was wondering if it might come back (if it hasn't already, in which case are there docs on how to configure it on Fedora)? Thanks, and again, congrats on 0.9.10. -derek Dan Williams writes: > Hi! > > Well, we finally did it. We released NetworkManager 0.9.10 with all the > awesome goodness described here: > > http://blogs.gnome.org/dcbw/2014/06/20/well-build-a-dream-house-of-net/ > > Grab the tarballs for NetworkManager and the applet/editor here: > > https://download.gnome.org/sources/NetworkManager/0.9/ > https://download.gnome.org/sources/network-manager-applet/0.9/ > (VPN plugins to come...) > > The final 0.9.10 release contains many bug fixes, most notably some > changes in veth handling, crash fixes, nmtui fixes, ifcfg-rh and keyfile > settings plugin fixes, Team fixes, translations, Bluez4 pairing fixes, > and more. A huge thanks to all of you who helped test the release > candidates! > > > > Now that we've reached the moon, why not shoot for the stars? I'm > talking about NetworkManager 1.0 later this year. To start with, we're > planning to enhance VPN capabilities to finally bring multiple > concurrent VPN/tunnels, runtime configuration API for clients, an even > leaner footprint, more robust cooperation with external tools, nmcli > interactivity fixes, connection priorities, porting away from dbus-glib > to GDBus (finally!), Bluez5 DUN support, and way more greatness. > > But best of all, *we'll be 1.0*! Nobody thought we'd get here, but 10 > years later, we're gonna finally do this. Are you ready to party? > > Dan > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > https://mail.gnome.org/mailman/listinfo/networkmanager-list > > -- 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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: where store static IP address?
Stuart Kendrick writes: > When I use NetworkManager to configure a static IP address, where does this IP > address get written to disk? It depends on the distribution. On Fedora I believe it gets stored in /etc/sysconfig/network-scripts/ifcfg- > I've tried poking through /etc/NetworkManager ... no dice > > I've tried: > grep -r a.b.c.d /etc/* > > and get no hits ... > > yet, when I reboot, NetworkManager correctly remembers the static IP address I > entered > > where does this get saved? > > --sk > > Stuart Kendrick -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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.9.9 ignores DHCP interface mtu?
On Fri, January 3, 2014 1:49 pm, Dan Williams wrote: > It appears to be a bug in the reworked IP4 config code. I've filed > https://bugzilla.gnome.org/show_bug.cgi?id=721420 to track the issue. > Until it's resolved, you could set the MTU for your device via the > device specific tab of nm-connection-editor, or directly via the > configuration files. For Fedora, you'd put "MTU=" into > the /etc/sysconfig/network-scripts/ifcfg- file corresponding to that > network connection. That *should* work; only automatic MTUs get ignored > according to my code inspection. Thanks for the quick response. I've actually decided to use this workaround (MTU=1476 in ifcfg-xxx). > Dan FYI, I've filed https://bugzilla.redhat.com/show_bug.cgi?id=1047083 for the Fedora issue, too. -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
NM 0.9.9 ignores DHCP interface mtu?
Hi all, Happy New Year! I just started playing with Fedora 20 which has NM 0.9.9 and I noticed that my F20 hosts do not honor the DHCP interface-mtu option. This was not the case with previous versions (including F19, F18, all the way back to at least F15 if not earlier) so this is clearly a new regression in F20. The only difference I can see is the change in NM version from 0.9.8 to 0.9.9. The dhclient versions are 4.2.5 on both system, so it's unlikely that's the culprit (although I could be wrong). Has anyone else seen this behavior? It's pretty easy to test. On your dhcp server (assuming you run ISC DHCPD) add something like "option interface-mtu 1476;" to part of your DHCP config and then grab a lease from that config. My F19 host will set the interface MTU to 1476, but F20 keeps it at 1500. The client is clearly requesting the option because it shows up in the lease file on the client. It's just not being processed and honored anymore. Any known fixes or workarounds? Thanks, -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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Blocking a user from activating Airplane mode
Phil, Phil Reynolds writes: > My partner sometimes uses my laptop, and on two occasions has somehow > activated Airplane mode - this of course drops the WLAN and WWAN > connections. I can't even get the WWAN to work again after this happens > without rebooting. > > I am wondering if there is a way I can stop him activating Airplane > mode - it's not something he would ever need to activate anyway. You could break their fingers! Or if that is too harsh you can yell at them to stop doing that. Or if that doesn't work you can just short-sheet their bed. ;) Seriously, you should just ask them to stop doing it. -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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
nm-applet from 0.9.8.1 not storing VPNC Group Password?
Hi, I've found that after an upgrade from Fedora 15 to 18, NetworkManager doesn't store/remember my VPNC connection Group Password. I've tried everything but deleting and recreating the VPN configuration to get it to save the password, but it wont do it. Any suggestions for what else I can do? It's annoying to have to type my password and this very long random string every time (even if I can cut-and-paste it, it's still annoying). Help? -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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
NM-Applet on F18 fails to save Vpnc Group Password
Hi, I just upgraded my system from F15 to F18 and I use the VPNC plugin to connect to my corporate VPN. My VPN configuration was working fine in F15 but didn't seem to transfer correctly to F18. In particular, even though the Edit Connections for the VPN config shows a Group Password and has it marked as "Saved", every time I try to bring up the VPN it asks me for my password *and* the group password. This is particularly the case if I bring the VPN down myself, although I believe it also happens if the VPN dies on its own after ~24 hours. Is this a known bug? Is there some way I can fix this? It's quite annoying to have to type in (or even cut-and-paste) this random value every day I want to bring up the VPN. Thanks, -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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: racoon?
Pavel Simerda writes: >> Yes, it's been seven years since IKEv2 was released. Welcome to >> IETF Time. :) > > It's been a long time since IPv6 was released :). Indeed, even longer, and look how poorly it's still supported in the wild. ;) >> However I still maintain that ipsec-tools has not been abandoned. > > Possibly. But when I was exploring the current state of IPsec userspace > implementations, its last release was more than a year old and it was > far from perfect even for IPv4 and IKEv1. Is there ever such a thing as "perfection"? :) >> >> There is still work being done on ipsec-tools, >> > >> > Yes? What news can I expect, then? >> >> You'll have to ask the current developers. I only know that there >> are still updates. > > I don't see any new release since March 2011, the mainpage links to > nonexistent websites and there's not even any information about current > development. For anyone not involved it's just as dead as any other dead > project. Hmm, I thought there was a release (0.8.1) earlier this year. Anyways, I think we've ratholed. My only point was that ipsec-tools has not been abandoned. -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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: racoon?
Pavel Simerda writes: >> From: "Derek Atkins" >> Pavel Simerda writes: >> > The Racoon software is fairly obsolete and abandoned. I admit it >> > can serve >> > your purpose but it is not really worth any new work. There is >> > Strongswan, >> > Racoon2 (a separate project) or, maybem, Openswan. AFAIK only >> > Strongswan >> > and Openswan have some support for NetworkManager. I'm curious >> > about any >> > new information you might have. >> >> It may be old but it is neither obsolete nor abandoned. > > I am sorry but I insist on the word obsolete for software that implements > obsolete IETF protocols and ignores their replacements. Fair enough on the obsolecense -- RFC 4306 was released in 2005 which does "obsolete" RFC 2409. However shortly before 4306, RFC 4109 was released which still made updates to 2409, so clearly there were coexisting efforts to create IKEv2 and update IKEv1. Yes, it's been seven years since IKEv2 was released. Welcome to IETF Time. :) However I still maintain that ipsec-tools has not been abandoned. >> There is still work being done on ipsec-tools, > > Yes? What news can I expect, then? You'll have to ask the current developers. I only know that there are still updates. -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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: racoon?
Hi, Pavel Simerda writes: > The Racoon software is fairly obsolete and abandoned. I admit it can serve > your purpose but it is not really worth any new work. There is Strongswan, > Racoon2 (a separate project) or, maybem, Openswan. AFAIK only Strongswan > and Openswan have some support for NetworkManager. I'm curious about any > new information you might have. It may be old but it is neither obsolete nor abandoned. There is still work being done on ipsec-tools, but you are right that it's generally a pretty stable platform so there are not many releases needed anymore. But it is not abandoned. > Cheers, > > Pavel -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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: F16 NetworkManager icon showing connecting when connected
On Wed, November 7, 2012 4:50 pm, Robert Moskowitz wrote: > > On 11/07/2012 11:00 AM, Derek Atkins wrote: >> Bob, >> >> On Wed, November 7, 2012 10:37 am, Robert Moskowitz wrote: >>> >>> yum --enablerepo=updates-testing update NetworkManager >>> Loaded plugins: langpacks, presto, refresh-packagekit >>> No Packages marked for Update >>> >>> Derek, where are you? Can we sit down and get this installed so I can >>> test it? (Brian, Derek is also here at the IETF meeting, and an old >>> colleague of mine). >> According to koji[0] it looks like it was just built yesterday, so it >> might not have made the mirrors yet. You could download and install >> from >> koji, or wait for the package to propagate, which might take another >> day. >> >> For what it's worth I see this myself with VPNs too, but I'm on F15 >> still >> so have no hope for a fix ;) >> >> -derek >> >> [0] http://koji.fedoraproject.org/koji/buildinfo?buildID=364798 >> > Ok. I downloaded and did a yum localinstall of: > > NetworkManager-0.9.6.4-1.fc16.x86_64.rpm > NetworkManager-glib-0.9.6.4-1.fc16.x86_64.rpm > NetworkManager-gnome-0.9.6.4-1.fc16.x86_64.rpm > NetworkManager-gtk-0.9.6.4-1.fc16.x86_64.rpm > > Do now do how do I restart NetworkManager? Is there someway other than > a reboot? For the service you can run, as root: service NetworkManager restart I'm not sure how to restart the applet. -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: F16 NetworkManager icon showing connecting when connected
Bob, On Wed, November 7, 2012 10:37 am, Robert Moskowitz wrote: > > > yum --enablerepo=updates-testing update NetworkManager > Loaded plugins: langpacks, presto, refresh-packagekit > No Packages marked for Update > > Derek, where are you? Can we sit down and get this installed so I can > test it? (Brian, Derek is also here at the IETF meeting, and an old > colleague of mine). According to koji[0] it looks like it was just built yesterday, so it might not have made the mirrors yet. You could download and install from koji, or wait for the package to propagate, which might take another day. For what it's worth I see this myself with VPNs too, but I'm on F15 still so have no hope for a fix ;) -derek [0] http://koji.fedoraproject.org/koji/buildinfo?buildID=364798 -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: F16 NetworkManager icon showing connecting when connected
On Wed, November 7, 2012 10:18 am, Robert Moskowitz wrote: > > On 11/07/2012 08:13 AM, Brian Morrison wrote: >> On Wed, 07 Nov 2012 07:43:46 -0500 >> Robert Moskowitz wrote: >> >>> Well if I get the update before next week, >> yum --enablerepo=updates-testing update Network-Manager >> >> will get the package from the testing repo and any dependencies that >> have been updated. >> > # yum --enablerepo=updates-testing update Network-Manager > Loaded plugins: langpacks, presto, refresh-packagekit > updates-testing/metalink | 2.3 kB 00:00 > updates-testing | 4.7 kB 00:00 > updates-testing/primary_db | 619 kB 00:03 > updates-testing/group_gz | 435 kB 00:01 > No Match for argument: Network-Manager > No package Network-Manager available. > No Packages marked for Update > > Now what? Try it without the dash yum --enablerepo=updates-testing update NetworkManager > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > https://mail.gnome.org/mailman/listinfo/networkmanager-list > -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Two WLANs with the same SSID but different connection names
Alexander Karlstad writes: >> So, if you have two networks with the same SSID and both use WPA/WPA2, >> then NM will select the *last used* connection. Because, for all NM >> knows (and a lot of other wifi managers too) they are the same network >> because they use the same SSID and same security type. It's pretty bad >> network planning to use the same SSID for actually different networks. > > But this is not two different networks per se. The Eduroam-network is > used all over the world at different educational institutions. The > only difference here is that I have a user account at two different > colleges, and sometimes you just get basic access when using a > username/password from a different college. That's why I want to be > able to use the two separatley. > > The workaround was disabling autoconnect for this network, but it > feels very much like a bug when I manually select which network I want > to connect to doesn't work. Even though DBUS tells me it's using the > right cridentials. > > Maybe it's possible for someone else to test this? Perhaps a better way of describing eduroam is not that there are two networks per-se, but rather you have two sets of authentication credentials that you want to use on the same network, and you want to be able to choose which set of credentials to use for any particular connection. -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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Ad hoc mode via Dbus
ppulib...@libero.it writes: > Derek, > > I know it uses DBus to communicate to NM! > The problem is I need to code code the configuration of wifi directly via > network manager over the DBus interface. I was able to configure it, but I > wasn't able to set it to ad hoc mode.This task must be automatically > performed by my application without using any GUI. Was anyone able to > successfully code this task? > Untill now I didn't find anyone who was able to do this so I think the only > way to do figure that out is to look into the source code of the network > manager.. > > The problem is that while I can And what's wrong with looking at nm-applet to see how it does it? -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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Ad hoc mode via Dbus
Hi, ppulib...@libero.it writes: > Hi Larry > > The GUI is not the problem ... > I know it must work. The problem is that my application must do this > automatically without any GUI > So if you can find out how the GUI does it... I could do the same ... codewise It uses DBUS to communicate to the NM service. -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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Cannot connect to Internet via Claro Modem (NOTE: sending log-files as attachments)
Dan Williams writes: > I've pushed a simple fix to MM05 and MM06 branches that hopefully fixes > this issue. I believe you said you're running on F14 though? If you > have the ability to rebuild an SRPM locally then I'm happy to send you > one, but I don't think I have any F14 machines left, so hopefully an > F15-based SRPM with the latest fixes works. mock -r fedora-14-i386 --rebuild foo.src.rpm > 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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Where does NM store its VPN configurations?
Dan Williams writes: > On Wed, 2011-08-10 at 12:51 -0400, Derek Atkins wrote: >> On Wed, August 10, 2011 12:33 pm, Bin Li wrote: >> > On Wed, Aug 10, 2011 at 6:29 PM, Derek Atkins wrote: >> >> Hey all, >> >> >> >> I just migrated from one laptop to another (both running Fedora 15). I >> >> completely copied my homedir over and all my wireless configuration >> >> remained but for some reason I don't see any of my previous VPN >> >> configurations on the new system. Where does NM store it, and how do I >> >> copy it over? >> > Maybe you could check /etc/NetworkManager/system-connections/ >> >> Aha, perfect. Thank you! >> >> Going from F12 -> F15 it moved with my homedir, but in F15 it somehow got >> moved from my homedir -> system-connections. I've noted this for the >> future. > > ifcfg files have no provision for VPN stuff, so yeah, we have to stuff > them into system-connections/. Sure, but previously it was stored in my personal gconf settings. Which made sense -- VPN configs were tied to me, not to the system. All my wireless configs are stored in gconf, so why move VPN configs but not wireless configs? > 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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Where does NM store its VPN configurations?
On Wed, August 10, 2011 12:33 pm, Bin Li wrote: > On Wed, Aug 10, 2011 at 6:29 PM, Derek Atkins wrote: >> Hey all, >> >> I just migrated from one laptop to another (both running Fedora 15). I >> completely copied my homedir over and all my wireless configuration >> remained but for some reason I don't see any of my previous VPN >> configurations on the new system. Where does NM store it, and how do I >> copy it over? > Maybe you could check /etc/NetworkManager/system-connections/ Aha, perfect. Thank you! Going from F12 -> F15 it moved with my homedir, but in F15 it somehow got moved from my homedir -> system-connections. I've noted this for the future. -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Where does NM store its VPN configurations?
Hey all, I just migrated from one laptop to another (both running Fedora 15). I completely copied my homedir over and all my wireless configuration remained but for some reason I don't see any of my previous VPN configurations on the new system. Where does NM store it, and how do I copy it over? -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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: DHCPv6 support in Network Manager isn't RFC compliant
On Thu, July 28, 2011 5:50 pm, Paul Wouters wrote: > On Thu, 28 Jul 2011, Stéphane Graber wrote: > >> As I'm not subscribed to this mailing-list, I'd appreciate it if you >> could Cc me on your replies. Thanks >> >> >> I've recently been spending quite a bit of time testing Network >> Manager's IPv6 support on Ubuntu as part of our ongoing effort of >> getting full IPv6 support for Oneiric. >> >> It's really looking good and Network Manager does a great job of >> handling all the possible use cases I have, except one small detail. > > [ DUID issue ] > > Actually, I found at IETF81 this week that my network manager on Fedora-14 > failed to connect to the IETF-v6only network. I've found that (historically) NM doesn't handle the IETF network well at all. In particular it has issues due to "too many APs". I've had many problems on the IETF networks in years past. I'm not in QC this week so I cannot test it this time. > Paul -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Reconnect silently
Dan Williams writes: >> I don't think you necessarily want to fail silently. It's possible that >> the password *did* change, so you want to give the user a chance to fix >> that. However I think the dialog should timeout if unattended and then >> you can assume the retry. > > We can detect changed password with WPA at least, and then not fail > silently, or at least mark the connection as "invalid" or something. > With WEP there's no way to tell though, so we might still want to pop up > the dialog there. True. With WPA we can just silently continue. I'd still like to see NM retry periodically instead of giving up after the first failure. > 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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Reconnect silently
Dan Williams writes: > On Tue, 2011-05-17 at 22:10 +0900, Misha Shnurapet wrote: >> Hi. >> >> I run torrents on my notebook. On an electricity outage NM starts asking for >> a new password, so when I'm not around and the light goes back on (powering >> up the WLAN router), it just stands stalled. Is there a way to tell NM not >> to ask for a new password ever? :) > > Not yet, but we do want to optimize this, and if you've ever connected > successfully to the network, and we know the password hasn't changed (we > can easily tell this with WPA-PSK but not as easily with other modes) > then we should just fail the connection silently and try later. Haven't > gotten around to that and nobody else has posted a patch for that > either,but it'll happen. I don't think you necessarily want to fail silently. It's possible that the password *did* change, so you want to give the user a chance to fix that. However I think the dialog should timeout if unattended and then you can assume the retry. > 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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Getting NM to re-try DHCP
Hey all, I have a strange issue. I lost power last night and one of my systems came up before my DHCP server did (which is surprising, because my DHCP server usually comes up pretty quick!) This "client" system was supposed to get itself on the network (it has an auto-logon system). However, NM didn't succeed because my DHCP server wasn't responding, yet. This is a hard-wired system (not wireless). Is there any way to get NM to periodically retry DHCP if at first it does not succeed? I realize that DHCP has its own retry mechanism, but if the whole process times out, can I set NM to retry every, say, 5 minutes? -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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Specifying an IPv6 suffix
Marc Herbert writes: > 2010/11/5 Robert Moskowitz : >> It is the principle of the thing. Yes, if I am changing my prefix I have to >> change the DNS. But if I am only changing the hardware, why am I having to >> change the DNS? > > Because IPv4 and IPv6 addresses point to network interfaces, not > hosts. Unlike DECNet addresses for instance. Sure, but in IPv4 there is no implicit tie from the hardware MAC address to the IP address; you have to arp to see who has it. Also, if you change the physical hardware (get a new MAC address) you can still get the same IP address assigned to you. So the IPv4 address is *NOT* tied to the Mac (hardware) address. I believe that Robert is asking for similar functionality in NM's support for v4. Unfortunately I'm not at the IETF this week so I cannot go ask people myself on Bob's behalf. -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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: An equivalent to dhclient.conf's "prepend domain-name-servers"?
Dan Williams writes: >> Even if NetworkManager just provided a boolean option to support a >> local caching nameserver. This could be presented in the GUI as "This >> system has a caching name server" with a check box. Default is off. >> I would like a way to configure this from the command line but I'm >> sure I could figure that out by learning a little more about dbus. > > I really, really do plan to make caching nameserver work :) PLEASE.. It used to work, many moons ago.. But I know it required special custom dbus hacks to bind to get it to work. But please... I really miss this feature. It's especially important for VPNs because right now when I turn on a VPN I get the VPN DNS servers, and if the VPN dies (like on their end) and stops transmitting packets then I lose DNS completely (at least until I manually bring down the VPN). With split-DNS/caching server it all worked great (although I did have to modify the vpn handler in order to insert domains in the search-path properly for the VPN dns servers. > 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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM + DUN on Fedora-12?
On Thu, June 24, 2010 3:04 pm, Derek Atkins wrote: > On Thu, June 24, 2010 2:06 pm, Dan Williams wrote: > >>> Could Sprint have done something to prevent PDAnet from broadcasting >>> DUN? >> >> Maybe. Does DUN setup work on Windows or a Mac if you have access to >> one? If it does, then we've got a Linux problem. If not, we have an >> Evo/PDAnet problem. > > Dont have a windows box to test on. Haven't been able to test on my > fiancée's mac. I'll see if I can. For the record, just tried with her mac and no, it doesn't see it either. Must be an Evo/PDAnet thing. -derek ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM + DUN on Fedora-12?
On Thu, June 24, 2010 2:06 pm, Dan Williams wrote: >> Could Sprint have done something to prevent PDAnet from broadcasting >> DUN? > > Maybe. Does DUN setup work on Windows or a Mac if you have access to > one? If it does, then we've got a Linux problem. If not, we have an > Evo/PDAnet problem. Dont have a windows box to test on. Haven't been able to test on my fiancée's mac. I'll see if I can. > There is the built-in wifi hotspot functionality, but you have to add > the tethering option onto your plan to make it work with 3G. Right. I'm not paying $30/mo in order to use my phone as a modem once every couple months. >> Well, I'm interesting in getting DUN (or some other tethering) working >> on >> my Evo... I'm a little upset that the Interwebs reported that USB >> tethering would work, but it doesn't.. And that PDAnet would work, but >> it >> doesn't. > > Does PDAnet have anything to say about the evo? I'd expect they are > getting a *lot* of questions if it doesn't work. I dont know. I sent them a help request yesterday and haven't heard back. >> But if I can't even get PDAnet to work... I don't know what I can do. > > Wait for HTC to release Froyo for it I guess... Or root the device and add the Wireless Tether app. ;) Which works great, by the way (not that I would ever done this to my phone, no-sir-ee) > Dan -derek ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM + DUN on Fedora-12?
Hmmm... On Wed, June 23, 2010 8:45 pm, Bastien Nocera wrote: > On Wed, 2010-06-23 at 17:39 -0700, Dan Williams wrote: > >> Googling around a bit I find people with some of the same problems. >> You're sure you've: >> >> a) paired with the computer successfully >> b) enabled BT DUN in PDAnet >> c) whatever it says here? >> http://www.junefabrics.com/android/bluetooth.php >> >> etc. Basically, if that SDP record doesn't show up, there's nothing >> that Linux or even Windows/Mac OS X can do since the device is saying >> it's not capable of DUN at all. I have PDAnet running I click on Enable Bluetooth DUN The device is saying "Bluetooth DUN service is running" Could Sprint have done something to prevent PDAnet from broadcasting DUN? > Because I still haven't added a way to get to the gnome-bluetooth > plugins after pairing, you'll need to have PDAnet enabled when pairing. > > It's on the TODO list, but could be done by anyone with a bit of GTK+ > knowledge. See: > https://bugzilla.gnome.org/show_bug.cgi?id=575414 > > Let me know off list if you're interested in working on this. Well, I'm interesting in getting DUN (or some other tethering) working on my Evo... I'm a little upset that the Interwebs reported that USB tethering would work, but it doesn't.. And that PDAnet would work, but it doesn't. But if I can't even get PDAnet to work... I don't know what I can do. > Cheers -derek ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM + DUN on Fedora-12?
Dan, On Wed, June 23, 2010 7:29 pm, Dan Williams wrote: >> I've just upgraded my FC12 laptop to the most recent packages (but not >> the testing packages). I'm hitting this kernel/USB issue. Any known >> workarounds? Any test-patches I could play with? > > Not really, but you can test stuff out manually if you want... > > 1) get your BT address I presume by "your" you mean "the phone", right? > 2) pair the device > 3) sdptool browse > 4) from the sdptool output, find the channel that DUN uses I'm not seeing it. I've attached the output below. > 5) rfcomm connect hci0 > > and it'll tell you what serial device it just made. Then you open that > up in minicom and try something like "ATI" and see what happens. > > If that all works, then the problem is likely in bluez or NM, not the > kernel. > > Dan Service RecHandle: 0x1 Service Class ID List: "PnP Information" (0x1200) Service Name: Headset Gateway Service RecHandle: 0x10001 Service Class ID List: "Headset Audio Gateway" (0x1112) "Generic Audio" (0x1203) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 1 Profile Descriptor List: "Headset" (0x1108) Version: 0x0100 Service Name: Handsfree Gateway Service RecHandle: 0x10002 Service Class ID List: "Handsfree Audio Gateway" (0x111f) "Generic Audio" (0x1203) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 2 Profile Descriptor List: "Handsfree" (0x111e) Version: 0x0105 Service Name: Object Push Service RecHandle: 0x10003 Service Class ID List: "OBEX Object Push" (0x1105) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 3 "OBEX" (0x0008) Profile Descriptor List: "OBEX Object Push" (0x1105) Version: 0x0100 Service RecHandle: 0x10004 Service Class ID List: "AV Remote Target" (0x110c) Protocol Descriptor List: "L2CAP" (0x0100) PSM: 23 "AVCTP" (0x0017) uint16: 0x100 Profile Descriptor List: "AV Remote" (0x110e) Version: 0x0100 Service Name: BRCM Advanced Audio Service RecHandle: 0x10005 Service Class ID List: "Audio Source" (0x110a) Protocol Descriptor List: "L2CAP" (0x0100) PSM: 25 "AVDTP" (0x0019) uint16: 0x102 Profile Descriptor List: "Advanced Audio" (0x110d) Version: 0x0102 Service Name: Phonebook Access PSE Service RecHandle: 0x10006 Service Class ID List: "Phonebook Access - PSE" (0x112f) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 4 "OBEX" (0x0008) Profile Descriptor List: "Phonebook Access" (0x1130) Version: 0x0100 Service RecHandle: 0x10007 Service Class ID List: UUID 128: 1103--1000-8000-00805f9b34fb Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 5 Service RecHandle: 0x10008 Service Class ID List: UUID 128: 1103--1000-8000-00805f9b34fb Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 5 Service RecHandle: 0x10009 Service Class ID List: UUID 128: 1103--1000-8000-00805f9b34fb Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 5 Service RecHandle: 0x1000a Service Class ID List: UUID 128: 1103--1000-8000-00805f9b34fb Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 5 ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM + DUN on Fedora-12?
Dan, On Tue, June 22, 2010 8:24 pm, Dan Williams wrote: > On Tue, 2010-06-22 at 18:02 -0400, Derek Atkins wrote: [snip] >> >> For one thing, the BT Net Device Setup times out detecting the phone >> details. I've got gnome-bluetooth 2.28.6 which is newer than 2.27.6 so >> that should be "new enough". For another, it seems that the NM in FC12 >> doesn't seem to support DUN (or if it does, I can't figure out how to >> connect it all up). Apparently the FC13 NM does. I backport the FC13 >> NM to FC12? Or is there something else I'm missing? > > There are various F12-updates-testing builds that do support DUN. Check > koji.fedoraproject.org for them, or 'yum --enablerepo=updates-testing' > for them. The update rate of NM/MM for F12 will be slowing down, but we > should at least get NM 0.8.1/MM 0.4 for F12 which obviously do support > DUN. Okay, I'll try to pull down the various NM updates > I've also noticed problems with BT in 2.6.32 and later kernels, but that > appears to be kernel/USB related and not necessarily due to NM. ... but how would I work around these issues? For example, why does the Bluetooth setup time out? I doubt the NM changes would fix that... So what can I do to fix it in the kernel? Is there an open bug# for it? > Dan -derek ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM + DUN on Fedora-12?
Dan Williams writes: >> For one thing, the BT Net Device Setup times out detecting the phone >> details. I've got gnome-bluetooth 2.28.6 which is newer than 2.27.6 so >> that should be "new enough". For another, it seems that the NM in FC12 >> doesn't seem to support DUN (or if it does, I can't figure out how to >> connect it all up). Apparently the FC13 NM does. I backport the FC13 >> NM to FC12? Or is there something else I'm missing? > > There are various F12-updates-testing builds that do support DUN. Check > koji.fedoraproject.org for them, or 'yum --enablerepo=updates-testing' > for them. The update rate of NM/MM for F12 will be slowing down, but we > should at least get NM 0.8.1/MM 0.4 for F12 which obviously do support > DUN. > > I've also noticed problems with BT in 2.6.32 and later kernels, but that > appears to be kernel/USB related and not necessarily due to NM. I've just upgraded my FC12 laptop to the most recent packages (but not the testing packages). I'm hitting this kernel/USB issue. Any known workarounds? Any test-patches I could play with? > 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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM + DUN on Fedora-12?
Hi, I just upgraded my phone to an Evo so I no longer get USB Tethering. Boo! However there is this nice app called PDAnet that would give me DUN via Bluetooth! YAY! However it doesn't seem to work with FC12. Boo! For one thing, the BT Net Device Setup times out detecting the phone details. I've got gnome-bluetooth 2.28.6 which is newer than 2.27.6 so that should be "new enough". For another, it seems that the NM in FC12 doesn't seem to support DUN (or if it does, I can't figure out how to connect it all up). Apparently the FC13 NM does. I backport the FC13 NM to FC12? Or is there something else I'm missing? -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 warl...@mit.eduPGP key available ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Is it possible to set MTU for a vpn connection
ritz writes: > Hello > > I do not see any option to set MTU under NMSettingVPN. All I could > find was for ethernet, and wireless. Are there any plans to add this ? The way I do this is manipulating the helper script to reset the MTU after the VPN comes up. It's a PITA. > reference: > http://live.gnome.org/NetworkManagerConfiguration > http://bugzilla.gnome.org/show_bug.cgi?id=584200 -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 warl...@mit.eduPGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: reconnect after sleeping
Dan, Dan Williams writes: > Is NM being told to go to sleep and wake up properly? If so, you'll see > these messages in the logs: > > NetworkManager: Sleeping... > NetworkManager: Waking up... > > Can you provide some logs from /var/log/messages or /var/log/daemon.log > that show the wake-up sequence? I think the problem is the lack of a wait/delay in the pm scripts.. I certainly see this issue periodically on Fedora 10. Sometimes NM doesn't wake up after a resume; I have to sometimes manually turn networking back on. It's somewhat random, though, and at this point the logs wont help me because I don't remember when I manually woke vs. automatic waking. > 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 warl...@mit.eduPGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Disable/Ignore access point
Derek Atkins writes: >> Any of them have an SSID of linksys? If you can reproduce the problem, >> then we can whip up a small tool to figure out which settings service is >> providing the 'linksys' connection. > > Not that I saw.. I do have a linksys123. > However I do NOT see the linksys in the gconf dir anymore, either. Okay, re-doing this on more sleep.. The list appears to be in LRU form, and Lo and Behold there is "Auto linksys". I just deleted it from there so hopefully it wont auto-connect again. >> Dan > > -derek -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 warl...@mit.eduPGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Disable/Ignore access point
Quoting Dan Williams : On Tue, 2009-04-28 at 12:29 -0400, Derek Atkins wrote: Quoting Dan Williams : >> Yes, I mean Network Manager itself connected to the linksys even though >> I erased it. I even stopped NM, killed nm-applet, killed gconf, deleted >> all the files, and restarted everything, and it *still* connected to >> the linksys network against my wishes. > > When you say "killed gconf", you mean 'rm -rf ~/.gconf' and then > 'killall -TERM gconfd-2' or something else? gconftool-2 --shutdown Then rm -rf ~/.gconf/.../linksys (I removed the linksys directory in the wireless networks list) >> I shouldn't have any system connections.. At least I'm pretty sure I >> never set any up. How do I check? > > If you run the connection editor, you'll see all the connections defined > on your system. And there are a bunch of "Auto ..." networks there, but not in any particular order which makes it hard to find one in particular. Any of them have an SSID of linksys? If you can reproduce the problem, then we can whip up a small tool to figure out which settings service is providing the 'linksys' connection. Not that I saw.. I do have a linksys123. However I do NOT see the linksys in the gconf dir anymore, either. 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 warl...@mit.eduPGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Disable/Ignore access point
Quoting Dan Williams : Yes, I mean Network Manager itself connected to the linksys even though I erased it. I even stopped NM, killed nm-applet, killed gconf, deleted all the files, and restarted everything, and it *still* connected to the linksys network against my wishes. When you say "killed gconf", you mean 'rm -rf ~/.gconf' and then 'killall -TERM gconfd-2' or something else? gconftool-2 --shutdown Then rm -rf ~/.gconf/.../linksys (I removed the linksys directory in the wireless networks list) I shouldn't have any system connections.. At least I'm pretty sure I never set any up. How do I check? If you run the connection editor, you'll see all the connections defined on your system. And there are a bunch of "Auto ..." networks there, but not in any particular order which makes it hard to find one in particular. 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 warl...@mit.eduPGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Disable/Ignore access point
Dan Williams writes: > On Thu, 2009-04-23 at 11:29 -0400, Derek Atkins wrote: >> Dan Williams writes: >> >> > On Mon, 2009-04-20 at 16:15 -0500, Bryan Duff wrote: >> >> My situation is that I have a number of accessible access points for >> >> me. >> >> >> >> I'll connect to the AP I want, but at some interval NetworkManager >> >> re-scans available AP's and picks an unencrypted AP (that I don't >> >> want). So I have to then, via nm-applet, reselect the AP I want to >> >> use. >> > >> > So if NM is connecting to it, you must have selected it sometime before. >> > If you won't want to connect to it, you can remove its configuration in >> > the connection editor, and NM won't connect to it automatically any >> > more. >> >> That didn't work for me.. Even after removing all remnants NM still >> wanted to connect to a local "linksys" network, no matter what I told >> it. > > When you say "NM", do you mean NetworkManager itself in the logs said it > was trying to connect, or do you mean you saw the BSSID of the linksys > ap in the results for "iwconfig" at some point? Was that linksys > connection a system connection? Yes, I mean Network Manager itself connected to the linksys even though I erased it. I even stopped NM, killed nm-applet, killed gconf, deleted all the files, and restarted everything, and it *still* connected to the linksys network against my wishes. I shouldn't have any system connections.. At least I'm pretty sure I never set any up. How do I check? > 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 warl...@mit.eduPGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Disable/Ignore access point
Dan Williams writes: > On Mon, 2009-04-20 at 16:15 -0500, Bryan Duff wrote: >> My situation is that I have a number of accessible access points for >> me. >> >> I'll connect to the AP I want, but at some interval NetworkManager >> re-scans available AP's and picks an unencrypted AP (that I don't >> want). So I have to then, via nm-applet, reselect the AP I want to >> use. > > So if NM is connecting to it, you must have selected it sometime before. > If you won't want to connect to it, you can remove its configuration in > the connection editor, and NM won't connect to it automatically any > more. That didn't work for me.. Even after removing all remnants NM still wanted to connect to a local "linksys" network, no matter what I told it. > 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 warl...@mit.eduPGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Turn off passive scanning?
Chuck, Quoting Chuck Anderson : On Tue, Mar 24, 2009 at 05:44:30PM -0400, Derek Atkins wrote: If this stack trace isn't usable enough I can try to change my console to display new lines, but I don't recall how to do that easily. Using a serial console would be challenging on my laptop as I have no serial port. netconsole may also be helpful here: http://www.novell.com/communities/node/4753/netconsole-howto-send-kernel-boot-messages-over-ethernet http://www.cyberciti.biz/tips/linux-netconsole-log-management-tutorial.html If the system is wedged so hard that I can't even use the pageup key to scroll back on the console do you really think it will be up sufficiently to send out netconsole messages? If I turn the screen into an 80x60 display instead of 80x24 then at least I can get more lines printed before the system locks up And I don't need a second machine off on the network to help me debug this. -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 warl...@mit.eduPGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Turn off passive scanning?
Dan Williams writes: >> Unfortunately the crash is very low level. Even when siting on >> the console the system locks up hard. I couldn't even page-up/page-down >> to see the full stack trace (and I didn't spend the time to leave >> my meeting, find a piece of paper, and copy it all down by hand). >> >> So... Is there some way I can turn off passive scanning in NM? > > Not really; you should be able to achieve the same result by > periodically running 'iwlist wlan0 scan' without NM running; there > clearly needs to be some fixes to the driver here... Man, is this a hard crash to capture! When it happens it occurs at such a low level that the machine hangs completely. Even the console hangs. But you're absolutely right here. I was able to reproduce the crash somewhat reliably using this script in my current environment here at the IETF: watch -n 1 iwlist wlan0 scan Of course it's hard to reliably reproduce WHEN it will occur, so I missed it a couple times. Moreover, I couldn't get the whole stack trace because it went off the top of the console and I couldn't page up to see it. > It may well not have anything to do with "passive" scanning itself, but > just scanning in general. There's passive (card just jumps to a channel > and listens for a split second, then to the next channel and listen, > etc) or active (jump to a channel, send a probe request, wait short time > for response). Honestly, I don't know. This trace is somewhat different than the last one. This one doesn't appear to have any mac80211 APIs. Hopefully this (partial) stack trace is useful, but I have no idea to whom I should send it. Note that I'll be in this environment through the end of the week so I can test fixes for three more days. If this stack trace isn't usable enough I can try to change my console to display new lines, but I don't recall how to do that easily. Using a serial console would be challenging on my laptop as I have no serial port. Let me know what you'd like me to try. -derek > Dan top of screen [] ? try_to_wake_up+0x230/0x23b [] ? signal_wake_up+0x31/0x34 [] ? complete_signal+0x10f/0x11f [] ? __slab_free+0x63/0x263 [] ? __slab_free+0x63/0x263 [] ? kmem_cache_free+0x71/0xa7 [] ? __kfree_skb+0x63/0x66 [] ? __kfree_skb+0x63/0x66 [] ? net_tx_action+0x6b/0xf3 [] ? __do_softirq+0xff/0x109 [] ? __do_softirq_0x0/0x109 [] ? do_softirq+0x77/0xdb [] ? pick_next_task+0x1d/0x34 [] ? acpi_idle_enter_bm+0x2b5/0x2cc [] ? tick_nohz_request_sched_tick+0x13a/0x14d [] ? cpu_idle+0x12d/0x134 [] ? rest_init+0x43/0x50 === Code: 03 00 00 00 7b 00 00 00 7b 00 00 00 d8 00 40 c0 ff ff ff ff cb 3e 88 c0 60 00 00 00 02 02 21 00 89 ab 6a c0 dc 3e 88 c0 7c 21 42 10 c0 c2 ef dc 3e 88 c0 4b ad 6a c0 10 c0 c2 ef 08 3f 88 c0 EIP: [] softirq_stack+0xecb/0x2 SS:ESP 0068:c0883ec0 Kernel panic - not syncing: Fatal exception in interrupt -- 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 warl...@mit.eduPGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Turn off passive scanning?
Dan et al, I seem to have found a bug in the iwl3945/mac80211 driver in the 2.6.27.19-170.2.35.fc10.i686 kernel where it dies in a page fault in skb_free(). Unfortunately I couldn't grab the full stack trace, but I saw about 5 hard crashes within an hour earlier today. I'm sitting in an extremely saturated network at the IETF, and I was attempting to perform a 'yum update'. I'm guessing it's a passive scan issue because the backtrace had a copy scan result entry. Moreover, I turned off network manager, brought wlan0 up by hand, and I haven't seen another crash. Unfortunately the crash is very low level. Even when siting on the console the system locks up hard. I couldn't even page-up/page-down to see the full stack trace (and I didn't spend the time to leave my meeting, find a piece of paper, and copy it all down by hand). So... Is there some way I can turn off passive scanning in NM? -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 warl...@mit.eduPGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: let NM know about custom connection through dbus?
Dan Williams writes: > either. There's a lot more to the NM D-Bus API than just the device > itself and whether that device is connected or not. True. However in some cases that's all that's important. For example if you want to run a VPN over your non-NM-aware device, you need to tell NM that the network is up so it can enable VPN support. Being able to tell NM "hey, there's a network here -- enable VPN" is definitely a worthwhile feature to have, and IMHO less work than "you need to make NM aware of your custom network hardware so it can manage that hardware". > 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 warl...@mit.eduPGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Bluetooth DUN and USB DUN for CDMA and GSM. Will NM 0.7.1 treat them equally?
Eric Appleman writes: > Derek Atkins wrote: >> Eric Appleman writes: >> >> >>> Right now, if I plug in my Verizon LG VX8350, NM won't even manage the >>> phone unless I configure it as a GSM modem in Mobile Broand Connection >>> Wizard. >>> >> >> I had to fix my HAL configuration to tell it that my SprintPCS >> Samsung a900m phone was a CDMA and not a GSM phone. Then it >> started working great. >> >> -derek >> >> > How did you do that? --- /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi-rpm-orig 2008-12- 19 08:11:51.0 -0500 +++ /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi 2009-01-16 17:22:45.0 -0500 @@ -66,8 +66,7 @@ -GSM-07.07 -GSM-07.05 +IS-707-A But this is for my phone.. You need to do it for yours. -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 warl...@mit.eduPGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Bluetooth DUN and USB DUN for CDMA and GSM. Will NM 0.7.1 treat them equally?
Eric Appleman writes: > Right now, if I plug in my Verizon LG VX8350, NM won't even manage the > phone unless I configure it as a GSM modem in Mobile Broand Connection > Wizard. I had to fix my HAL configuration to tell it that my SprintPCS Samsung a900m phone was a CDMA and not a GSM phone. Then it started working great. -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 warl...@mit.eduPGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile CDMA problem with my SAMSUNG phone (NM sees it as GSM?)?
Quoting Dan Williams : Now if only I could figure out why my work wifi keeps disconnecting. I see things like this in my dmesg logs: ... wlan0: authenticate with AP 00:1f:9e:ce:b3:21 wlan0: authenticated wlan0: associate with AP 00:1f:9e:ce:b3:21 wlan0: RX ReassocResp from 00:1f:9e:ce:b3:21 (capab=0x421 status=0 aid=1) wlan0: associated wlan0: deauthenticated wlan0: authenticate with AP 00:1f:9e:ce:c2:71 wlan0: authenticate with AP 00:1f:9e:ce:c2:71 wlan0: authenticate with AP 00:1f:9e:ce:c2:71 wlan0: authenticate with AP 00:1f:9e:ce:c2:71 wlan0: authentication with AP 00:1f:9e:ce:c2:71 timed out Driver or AP problem... Heavy RF environment? It could be a heavy RF environment, I don't know. It could be an AP problem, too. I just don't know. I'm using F10 with the iwl3945 driver. The SSID is a non-broadcast SSID. It seemed a bit more stable last month when I was still running F7. I kinda wish the system were a little more forgiving of transient errors. But I haven't tried just outright killing NM and seeing if it stays up when I just ifup directly. 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 warl...@mit.eduPGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile CDMA problem with my SAMSUNG phone (NM sees it as GSM?)?
Dan Williams writes: >> Here's what mine currently looks like (it looks somewhat different than >> yours): >> >> >> >> >> >> > type="strlist">GSM-07.07 >> > type="strlist">GSM-07.05 >> >> >> >> >> Should I just swap both of those "GSM-*" entries to IS-707-A? >> Or should I add an info.capabilities line and make it look like yours? > > Remove one of the "modem.command_sets" items, and change the other one > to "IS-707-A". BTW, I had a chance to test this out yesterday and it worked perfectly. Yay! And I can even start the VPN over it. Yay! Now if only I could figure out why my work wifi keeps disconnecting. I see things like this in my dmesg logs: ... wlan0: authenticate with AP 00:1f:9e:ce:b3:21 wlan0: authenticated wlan0: associate with AP 00:1f:9e:ce:b3:21 wlan0: RX ReassocResp from 00:1f:9e:ce:b3:21 (capab=0x421 status=0 aid=1) wlan0: associated wlan0: deauthenticated wlan0: authenticate with AP 00:1f:9e:ce:c2:71 wlan0: authenticate with AP 00:1f:9e:ce:c2:71 wlan0: authenticate with AP 00:1f:9e:ce:c2:71 wlan0: authenticate with AP 00:1f:9e:ce:c2:71 wlan0: authentication with AP 00:1f:9e:ce:c2:71 timed out ... > 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 warl...@mit.eduPGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile CDMA problem with my SAMSUNG phone (NM sees it as GSM?)?
Dan, Quoting Dan Williams : Looks like Samsung used the same VID/PID for the Samsung SGH-A707 (AT&T Sync). Or maybe the USB device is actually in the cable and both these phones use the same cable. For the time being, until we push auto-probing into udev, you can edit /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi and change the section for the Sync to be: modem type="strlist">IS-707-A The magic bit is removing the "GSM" lines and adding the "IS-707-A" line. Here's what mine currently looks like (it looks somewhat different than yours): GSM-07.07 GSM-07.05 Should I just swap both of those "GSM-*" entries to IS-707-A? Or should I add an info.capabilities line and make it look like yours? Thanks! 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 warl...@mit.eduPGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Mobile CDMA problem with my SAMSUNG phone (NM sees it as GSM?)?
Hi Dan (et al), I just upgraded to F10 and I'm trying to get NM to talk to my mobile phone again. I have a CDMA (SprintPCS) phone, but when I plug it in NM seems to think it's a GSM phone and there's no way I can tell it otherwise. When I plug my phone in I see: Jan 16 09:19:29 pgpdev kernel: usb 4-1: New USB device found, idVendor=04e8, idP roduct=6601 Jan 16 09:19:29 pgpdev kernel: usb 4-1: New USB device strings: Mfr=1, Product=2 , SerialNumber=0 Jan 16 09:19:29 pgpdev kernel: usb 4-1: Product: SAMSUNG CDMA Technologies Jan 16 09:19:29 pgpdev kernel: usb 4-1: Manufacturer: SAMSUNG Electronics Co.,Lt d. And NM logs: Jan 16 09:19:29 pgpdev NetworkManager: ttyACM0: driver is 'cdc_acm'. Jan 16 09:19:29 pgpdev NetworkManager: Found new Modem device 'ttyACM0'. Jan 16 09:19:29 pgpdev NetworkManager: (ttyACM0): exported as /org/freed esktop/Hal/devices/usb_device_4e8_6601_noserial_if0_serial_unknown_0 Jan 16 09:19:33 pgpdev NetworkManager: (ttyACM0): device state change: 1 -> 2 Jan 16 09:19:33 pgpdev NetworkManager: (ttyACM0): deactivating device (r eason: 2). Jan 16 09:19:33 pgpdev NetworkManager: nm_system_device_flush_ip4_routes_with_if ace: assertion `iface_idx >= 0' failed Jan 16 09:19:33 pgpdev NetworkManager: nm_system_device_flush_ip4_addresses_with _iface: assertion `iface_idx >= 0' failed Jan 16 09:19:33 pgpdev NetworkManager: (ttyACM0): device state change: 2 -> 3 So what changes do I need to make to get NM to see my phone as a CDMA phone instead of a GSM phone? -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 warl...@mit.eduPGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: What about modems (winmodems/serial)?
Dan Williams <[EMAIL PROTECTED]> writes: >> Unfortunately that's not sufficient because then you cannot turn >> on a VPN through NM because NM is unaware that you're online. >> Unless there's some trick to tell nm-applet "hey, I'm online. >> Enable VPNs so I can turn one on" that I am unaware of, this is >> a MAJOR regression from 0.6.6? > > 0.6 didn't know that Dialup was active either (because it just called > out to shellscripts!), and thus you couldn't do VPN through a dialup > connection in 0.6 either. That was one of the biggest complaints > against 0.6, and we fixed that for mobile broadband cards in 0.7, > because the most complaints *by far* came from mobile brandband users. > Something like 25:1 for wanting real mobile broadband over dialup. Hmm.. I have my PCS Phone configured as a dialup device in NM. I haven't used it in a while, but I thought that when I clicked on Dialup Connections -> Connect to PCS via Modem that it would allow me to use VPN. But I could be misremembering. You didn't reply to my previous message about whether my phone will work. > 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: What about modems (winmodems/serial)?
Dan Williams <[EMAIL PROTECTED]> writes: > On Fri, 2008-11-07 at 17:36 +0200, Peteris Krisjanis wrote: >> Hi people, >> >> Ubuntu has now chosen NM 0.7 as default network management point. >> However, there is regression in Ubuntu as you can't configure ppp >> devices anymore via GUI. > > Not that you could really do so before with NM; it just called out to > system scripts. So you can achieve the same functionality by going to > the network control panel and activating the connection there with NM > even being involved. The Dialup menu was simply a short-cut for that. Unfortunately that's not sufficient because then you cannot turn on a VPN through NM because NM is unaware that you're online. Unless there's some trick to tell nm-applet "hey, I'm online. Enable VPNs so I can turn one on" that I am unaware of, this is a MAJOR regression from 0.6.6? -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: NetworkManager 0.7.0-rc1 released
Quoting Dan Williams <[EMAIL PROTECTED]>: 2) I'm still using 0.6.6 (yes, I'm still on F7) and I periodically connect my cell phone via USB and have a "SprintPCS" network configuration in the "dialup configuration" menu. Will this version still support me? Yes, though you may need to reconfigure the connection in NM 0.7's connection editor, as well as adding your phone to the HAL fdi file that controls the hardware detection. That's all pretty easy though. Yep. I'm happy to set it up again; I just need to make sure it works because I can't turn on the VPN when my network isn't controlled by NM. What phone do you have, and what are the USB IDs reported by '/sbin/lsusb' ? It's a samsung A900m. lsusb reports: Bus 003 Device 003: ID 04e8:6601 Samsung Electronics Co., Ltd Z100 Mobile Phone Do you need more info than that? 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: NetworkManager 0.7.0-rc1 released
Dan, Dan Williams <[EMAIL PROTECTED]> writes: > Hi, > > I tagged and uploaded NM 0.7.0-rc1 on Sunday night. Yes, there are > still bugs, and yes, we'll fix the bad ones, and yes, some people's pet > bugs will only get fixed after the final release. I'll do an rc2 this > coming weekend, and we'll wrap up the 0.7 development cycle by November > 15th. This time for real :) > > http://ftp.gnome.org/pub/gnome/sources/NetworkManager/0.7/ > http://ftp.gnome.org/pub/gnome/sources/network-manager-applet/0.7/ Congrats! Nice job. It's been a long time coming and I know you've put a lot of effort into this. I've got two questions: 1) Is this going to get pushed into F9? 2) I'm still using 0.6.6 (yes, I'm still on F7) and I periodically connect my cell phone via USB and have a "SprintPCS" network configuration in the "dialup configuration" menu. Will this version still support me? > 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: wha is ipv4 prefix?? (why not netmask)
Miguel Angel Cañedo <[EMAIL PROTECTED]> writes: > I was pulling my hair trying to set static ipv4 settings. > Until I realized that NM 0.7 asks for PREFIX instead of NETMASK > > Now, my netmask should be 255.255.0.0 > How do I transalte that into the Prefix? /16 ? > What is that prefix thing? > > Thanks, > Miguel -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: API changes
Quoting Dan Williams <[EMAIL PROTECTED]>: >> Why not call it V4Addresses, to give space to add V6Addresses later? > > Because this is the NMIP4Config object; there will be an NMIP6Config > object for IPv6 support :) Ahh, well that would make sense, now, wouldn't it? ;) Sorry for the noise. > 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: API changes
Hey, Dan Williams <[EMAIL PROTECTED]> writes: > On Thu, 2008-05-08 at 16:59 +0300, Tambet Ingo wrote: >> Hey, >> >> There's a small DBus API breakage in the SVN. Interface >> "org.freedesktop.NetworkManager.IP4Config" does not have properties >> "Address", "Gateway", "Netmask", and "Broadcast" anymore. Instread, >> there's now an array of tuples 'Addresses' containing (uint address, >> uint netmask, uint gateway). The change was to allow multiple IP >> addresses per device. Here's the diff: > > As a side-note, this exactly matches the format for IP addresses that > the NMSettingIP4Config setting uses. > > Dan > >> - >> - IPv4 address. FIXME: what about multiple >> addresses? >> - >> - >> - Default gateway. >> - >> - >> - Network mask of this network. >> - >> - >> - Broadcast address of this network. >> + >> + Tuples of IPv4 address/netmask/gateway. The >> gateway is optional, if not given should be 0. Why not call it V4Addresses, to give space to add V6Addresses later? >> Tambet -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
Update! (was Re: More issues with NM-0.6 and non-broadcast SSID)
WooHoo! Since my last trip out to HQ I've updated my kernel and NM to: kernel-2.6.23.15-80.fc7 NetworkManager-0.6.6-1.fc7 wpa_supplicant-0.5.7-4.fc7 And when I got to the office this morning it connected to the non-broadcast SSID network right away without any help from me. Yay! I'll report back if this changes throughout the rest of the week. -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: How many SSIDs can be listed?
There's another problem. The wireless extensions have a size limit for the scan results data. The buffer size is a u16, which means you're limited to 65535 bytes. The network manager buffer increase algorithm keeps doubling the buffer size, so you get 2k, 4k, 8k, 16k, 32k, 64k.. but 64k mod 2^16 == 0! Meaning you never actually get to try a full 64k buffer. A workaround to this issue is to change the NM code to max out at 65535 instead of 65536 or "10" (which is the current limit).. This is being a MAJOR problem to a bunch of us at the IETF because we can easily hear well over 100 APs most of the time. -derek Quoting Dan Williams <[EMAIL PROTECTED]>: > On Mon, 2008-03-10 at 23:40 -0400, Robert Moskowitz wrote: >> Ver 0.6.4 in Centos 5.1 >> >> I am seeing 17 SSIDs in the current list. But I am not seeing one that >> I expected to see. And some of the listed SSIDs are 'stale'; that is >> they were visible in the part of the hotel I was in a couple minutes >> ago, but not in this part. So I guess a second question is how do you >> force a scan to produce a current SSID list? > > You don't force a scan. NetworkManager will periodically scan with a > backoff algorithm; it will start at 20 seconds and back off to 2 > minutes. APs are kept in the scan list for a maximum of 6 minutes > before being culled. > > The problem is that wireless is hard, and sometimes cards/drivers miss > beacons. Often they will not report all the APs that are known to be > around at a given time. So NetworkManager takes a composite of the last > few scans as the scan list. > > 0.6.x also combines APs with the same SSID in the UI. 0.7 splits them > out at the NetworkManager layer, while the applet combines APs that are > similar based on more than just SSID (SSID, security settings, band, > channel). > >> Perhaps the question may be how many APs can be handled and then those >> are turned into the SSID list (when more than one AP per SSID is found >> as in the case of some of these SSIDs). > > Are any of the APs hidden? > > Dan > > _______ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > -- 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
More issues with NM-0.6 and non-broadcast SSID
My chronic problem with non-broadcast SSID has hit upon an interesting workaround. I'm using Fedora 7 with the following package versions: NetworkManager-0.6.5-7.fc7 kernel-2.6.23.9-45.fc7 wpa_supplicant-0.5.7-4.fc7 I'm using the iwl3945 driver in the kernel. When I try to connect to my office network (non-broadcast, open 802.11g) it rarely connects. If I shut down NM, reset the driver, and just let it come up on it's own it connects fine. But yesterday I figured out that if I tell the driver to connect to any bssid then it will work great, and connects right away. In other words, as soon as I tell NM to try to connect (or as soon as it tries to connect all on its own!) I need to type the following command: iwconfig eth1 essid ap 00:00:00:00:00:00 And then it connects right away!! Yesterday it took me about 30 minutes of trial and error to get NM to accept the connection, but today... Voom. I typed this command when NM was trying to connect and voila, it connected! So it looks like the NM/wpa_supplicant bssid assignment isn't very happy here. I'm glad I found a workaround, but is there anything we can do to make it so I don't have to do this manually? Thanks, -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: Connecting to a hidden ESSID via LEAP now works.
"John W. Linville" <[EMAIL PROTECTED]> writes: > On Tue, Jan 15, 2008 at 03:10:34PM -0500, Dan Williams wrote: >> On Tue, 2008-01-15 at 09:40 -0500, Derek Atkins wrote: > >> > Will these NM fixes get into 0.6 for F7 as well? >> >> I've already committed them to 0.6.x stable branch, and at some point >> this month I'd like to gear up for a 0.6.6 release and push that to F7 >> too. Looks like either F7-testing kernels, or soon-to-be-release >> F7-testing kernels in the 2.6.23 range will have the scan_capa patch >> (it's already in package CVS). > > Derek knows how to find them in Koji, I'm sure... I'm much better when given the Koji links. I'm not all that good at finding them on my own. ;) > Now, how about the NM in RHEL5? :-) -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: Connecting to a hidden ESSID via LEAP now works.
Dan Williams <[EMAIL PROTECTED]> writes: > On Mon, 2008-01-14 at 14:12 -0500, Andrew Duggan wrote: >> Dan etal, Thanks, as of NetworkManager-0.7.0-0.6.8.svn3235.fc8 I can now >> connect to a hidden ESSID network via LEAP that previously just would >> not connect. Using a bcm4311 v1 b43 from kernel-2.6.23.12-99.fc8. >> Thanks again -- great job. > > Yep; thanks to Linville's quick backport and update of the scan > capability patch to Fedora kernels, this should now work better. > There's one case where NM forgets to merge the before and after networks > when you're connecting, which is fixed in SVN and coming to F8/rawhide > in the next update. There have been a few other hidden SSID problems > reported (not finding the hidden AP automatically for example) that I'm > tracking down, but the situation should be much improved for those > people who are running scan-capability-patched kernels. Will these NM fixes get into 0.6 for F7 as well? > 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: NetworkManager connects to DHCP AP but dhclient doesn't
Kamran Riaz Khan <[EMAIL PROTECTED]> writes: > Any ideas about what I'm doing wrong? Does "dmesg" have any interesting output? -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: Saving other Wireless network
Quoting Peter Davoust <[EMAIL PROTECTED]>: > Is there anyway to save the configuration you give nm-applet when you > connect to an "other" wireless network? It's great to be able to > connect, but I don't like having to enter my password and everything. Once it successfully connects it should remember those settings in gconf and attempt to connect the next time it sees that AP. > -Peter -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 <[EMAIL PROTECTED]> writes: > I understand that, but Dan Williams is also correct that not all hex > strings can be represented as ASCII stings. This makes an ASCII entered > passphrase a weaker encryption vehicle. True, but WEP itself is a weak encryption vehicle, so you shouldn't depend on it for anything except to stop a neighbor from accidentally, casually joining your network. If you want real wireless security you should use WPA. -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: 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
Dan Williams <[EMAIL PROTECTED]> writes: >> 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. That's not necessarily true. There's a difference between "WEP Password", "40/128 ASCII" and "40/128 HEX". In the former case you do need to make sure that the AP is set up for a password, and you'd better hope that the AP uses the same string-to-key as NM. But in the latter cases, you're just defining a key directly. The only difference is whether you're supplying the key in hex or via the ascii character codes. E.g., to enter a hex 'digit' of 41 you could just enter an ascii "A". This does not require any special configuration on the AP, because you could use 'A' and '4141414141' interchangably in NM. > 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: Overriding connections (VPN) that abuse DNS (was: Wireless DHCP overwrites DNS settings)
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. -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: Another dropped connection with iwl3945 and NM-0.6.5 on FC7
Dan Williams <[EMAIL PROTECTED]> writes: > On Tue, 2007-12-04 at 19:02 -0500, Derek Atkins wrote: >> Here's the dmesg output: >> >> eth1: RX deauthentication from 00:19:a9:47:56:91 (reason=1) >> eth1: deauthenticated >> eth1: authenticate with AP 00:19:a9:47:56:91 >> eth1: RX authentication from 00:19:a9:47:56:91 (alg=0 transaction=2 status=0) >> eth1: authenticated >> eth1: associate with AP 00:19:a9:47:56:91 >> eth1: RX ReassocResp from 00:19:a9:47:56:91 (capab=0x1 status=0 aid=80) >> eth1: associated >> eth1: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0 >> eth1: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0 >> eth1: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30 >> eth1: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15 >> eth1: No ProbeResp from current AP 00:19:a9:47:56:91 - assume out of range >> eth1: No STA entry for own AP 00:19:a9:47:56:91 >> eth1: No STA entry for own AP 00:19:a9:47:56:91 >> bridge-eth1: disabling the bridge >> bridge-eth1: down >> bridge-eth1: enabling the bridge >> bridge-eth1: up > > Looks like the driver decided that the AP had gone away. It probably > missed too many beacons or probe responses due to the RF heavy > environment or something? Could need a driver tweak. Maybe. It's the iwl3945. Maybe it was scanning? ;) The IETF really is a great testbed. Frustrating as a user, but a great testbed. > 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: scan list limitation -- doesn't like 127 APs?
Dan Williams <[EMAIL PROTECTED]> writes:
> Can you file a bug on gnome.org?
http://bugzilla.gnome.org/show_bug.cgi?id=501835
-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
Another dropped connection with iwl3945 and NM-0.6.5 on FC7
Here's the dmesg output: eth1: RX deauthentication from 00:19:a9:47:56:91 (reason=1) eth1: deauthenticated eth1: authenticate with AP 00:19:a9:47:56:91 eth1: RX authentication from 00:19:a9:47:56:91 (alg=0 transaction=2 status=0) eth1: authenticated eth1: associate with AP 00:19:a9:47:56:91 eth1: RX ReassocResp from 00:19:a9:47:56:91 (capab=0x1 status=0 aid=80) eth1: associated eth1: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0 eth1: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0 eth1: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30 eth1: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15 eth1: No ProbeResp from current AP 00:19:a9:47:56:91 - assume out of range eth1: No STA entry for own AP 00:19:a9:47:56:91 eth1: No STA entry for own AP 00:19:a9:47:56:91 bridge-eth1: disabling the bridge bridge-eth1: down bridge-eth1: enabling the bridge bridge-eth1: up At this point the network was down. Then I told nm-applet to re-connect: eth1: Initial auth_alg=0 eth1: authenticate with AP 00:19:a9:45:36:d1 eth1: authenticate with AP 00:19:a9:45:36:d1 eth1: RX authentication from 00:19:a9:45:36:d1 (alg=0 transaction=2 status=0) eth1: authenticated eth1: associate with AP 00:19:a9:45:36:d1 eth1: RX AssocResp from 00:19:a9:45:36:d1 (capab=0x1 status=0 aid=75) eth1: associated eth1: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0 eth1: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0 eth1: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30 eth1: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15 eth1: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0 eth1: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0 eth1: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30 eth1: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15 eth1: RX deauthentication from 00:19:a9:45:36:d1 (reason=2) eth1: deauthenticated eth1: authenticate with AP 00:19:a9:45:36:d1 eth1: RX authentication from 00:19:a9:45:36:d1 (alg=0 transaction=2 status=0) eth1: authenticated eth1: associate with AP 00:19:a9:45:36:d1 eth1: RX ReassocResp from 00:19:a9:45:36:d1 (capab=0x1 status=0 aid=77) eth1: associated And here I was connected again. -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
scan list limitation -- doesn't like 127 APs?
I just roamed and got kicked off the network. DMESG shows: eth1: No ProbeResp from current AP 00:19:a9:45:2f:a1 - assume out of range eth1: No STA entry for own AP 00:19:a9:45:2f:a1 eth1: Initial auth_alg=0 eth1: authenticate with AP 00:19:a9:45:2f:a1 eth1: Initial auth_alg=0 eth1: authenticate with AP 00:19:a9:45:2f:a1 eth1: authenticate with AP 00:19:a9:45:2f:a1 eth1: authenticate with AP 00:19:a9:45:2f:a1 eth1: authentication with AP 00:19:a9:45:2f:a1 timed out And then I noticed this in my /var/log/messages: Dec 4 18:21:49 pgpdev NetworkManager: request_and_convert_scan_results(): unknown error, or the card returned too much scan info: Argument list too long Running: iwlist eth1 scan | tail -20 shows: [snip] Cell 127 - Address: 00:19:A9:47:5B:32 ESSID:"ietf-a.1x" Mode:Master [snip] So, is there an AP Scan limit? -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: No inter-AP Roaming?
Quoting dragoran <[EMAIL PROTECTED]>: >> > that might be because the card is doing a scan at that time.. there is >> > a patch posted upstream (linux-wireless) that should fix this by >> > delaying scans while authenticate >> >> Do you have a URL to the patch? Or a URL to a Red Hat / Fedora Bug? > > http://marc.info/?l=linux-wireless&m=119668234926912&w=2 Thanks! https://bugzilla.redhat.com/show_bug.cgi?id=411191 -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: No inter-AP Roaming?
Quoting dragoran <[EMAIL PROTECTED]>: > On Dec 4, 2007 10:08 PM, Derek Atkins <[EMAIL PROTECTED]> wrote: >> Quoting Dan Williams <[EMAIL PROTECTED]>: >> >> > On Tue, 2007-12-04 at 15:31 -0500, Derek Atkins wrote: >> >> I'm sitting at the IETF, connected to the 802.11 network.. >> >> But as I wander from room to room, NM doesn't roam. It wont >> >> jump from one AP to another as I move around the conference >> >> facility. I'll get to my new room and find that I no longer >> >> have any network and then have to wait for a full connection >> >> sequence. >> >> >> >> What gives? I certainly don't have this problem if I just >> >> let the driver/hardware roam on its own. >> > >> > Well, NM doesn't control roaming at all, wpa_supplicant and the driver >> > do. Sometimes wpa_supplicant will push the BSSID down to the driver >> > when connecting (not entirely sure when that is) and if the driver >> > actually follows WEXT (which lots don't) that would cause the driver to >> > lock to that single BSSID and not switch. That bit is highly driver >> > dependent. It looks like wpa_supplicant will only do this when it has >> > previously timed out authentication with the station but tries again >> > (like it should). It then passes the BSSID down to the association code >> > which tries to lock the card to that BSSID specifically. >> >> Interesting. >> >> I'm using the iwl3945 driver. I DO see some authentication timeouts, >> which is really weird.. Sometimes to the point where it wont even >> successfully authenticate to the card at all and I have to reset. >> Very frustrating. > > that might be because the card is doing a scan at that time.. there is > a patch posted upstream (linux-wireless) that should fix this by > delaying scans while authenticate Do you have a URL to the patch? Or a URL to a Red Hat / Fedora Bug? Thanks, -- 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: No inter-AP Roaming?
Quoting Dan Williams <[EMAIL PROTECTED]>: > On Tue, 2007-12-04 at 15:31 -0500, Derek Atkins wrote: >> I'm sitting at the IETF, connected to the 802.11 network.. >> But as I wander from room to room, NM doesn't roam. It wont >> jump from one AP to another as I move around the conference >> facility. I'll get to my new room and find that I no longer >> have any network and then have to wait for a full connection >> sequence. >> >> What gives? I certainly don't have this problem if I just >> let the driver/hardware roam on its own. > > Well, NM doesn't control roaming at all, wpa_supplicant and the driver > do. Sometimes wpa_supplicant will push the BSSID down to the driver > when connecting (not entirely sure when that is) and if the driver > actually follows WEXT (which lots don't) that would cause the driver to > lock to that single BSSID and not switch. That bit is highly driver > dependent. It looks like wpa_supplicant will only do this when it has > previously timed out authentication with the station but tries again > (like it should). It then passes the BSSID down to the association code > which tries to lock the card to that BSSID specifically. Interesting. I'm using the iwl3945 driver. I DO see some authentication timeouts, which is really weird.. Sometimes to the point where it wont even successfully authenticate to the card at all and I have to reset. Very frustrating. How do I tell whether wpa_supplicant is locking me to a particular BSSID, and how do I undo that once it's done? > Dan -derek Strangely, it DID just roam as I went from my lunch meeting to my first after lunch session. But it's still annoying that it can drop the session so easily/quickly whereas non-NM will gladly re-acquire the association as I move between areas, even if I hit an area of no coverage. -- 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: nm with dnsmasq?
Quoting Dan Williams <[EMAIL PROTECTED]>: >> Too bad! It's really nice and useful! > > The functionality won't be going away (though it might hiccup a bit), > since it definitely is still useful. Just the communication > implementation between NM and named. Everyone agrees that it's nice to > have named (or something else) as a caching nameserver that can be > updated dynamically, but the D-Bus interface in named was never going > upstream and wasn't very maintainable. I think the hand-wavy new plan > is to use other tools that ship with named to update the forwarders in a > non-D-Bus-y way. I've got a bunch of ISC people (including a number of Bind developers) at my disposal this week. Anything in particular you'd like me to ask them or talk to them about? I'm personal friends with the BIND9 project manager. ;) > 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
No inter-AP Roaming?
I'm sitting at the IETF, connected to the 802.11 network.. But as I wander from room to room, NM doesn't roam. It wont jump from one AP to another as I move around the conference facility. I'll get to my new room and find that I no longer have any network and then have to wait for a full connection sequence. What gives? I certainly don't have this problem if I just let the driver/hardware roam on its own. Using NetworkManager-0.6.5-7.fc7 with gnome. Thanks, -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: nm with dnsmasq?
Dan Williams <[EMAIL PROTECTED]> writes: >> > Use bind with dbus turned on and it all just works. >> > >> > -derek >> Apparantly that is going away: >> https://www.redhat.com/archives/fedora-devel-list/2007-December/msg00146.html > > Yeah... Too bad! It's really nice and useful! > 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: ppp using NM
"Darren Albers" <[EMAIL PROTECTED]> writes: >> I've never had to do that with Sprint cards; I just use bob/smith as the >> user/pw. In my experience, you just need _something_ there, but it >> doesn't matter what it is (for Sprint at least). >> >> Dan >> > > Really? I wonder what the purpose of the username/password is then... lol For sprint I've always used web/web. It's worked for years and years. -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: nm with dnsmasq?
Neal Becker <[EMAIL PROTECTED]> writes: > Is there some way to get nm to cooperate with a local caching NS? I'm > thinking dnsmasq, since it's lightweight. The problem is that NM will > overwrite resolv.conf. What is the recommendation? Use bind with dbus turned on and it all just works. -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: NM stopped using local caching nameserver?
Quoting Dan Williams <[EMAIL PROTECTED]>: > On Tue, 2007-11-13 at 10:12 -0500, Derek Atkins wrote: >> I tracked this down some.. It appears part of the issue is a >> race condition between named and dbus. The startup sequence >> has named start first, and then dbus... but then named doesn't >> connect to dbus properly. If I RESTART named then everything >> appears to work okay. >> >> I suspect the problem here is that named doesn't retry to connect >> to dbus if it fails to connect on startup. >> >> Would this be a named bug? > > Well, probably an init ordering between named and dbus initscripts, > yeah. > > dan I tried various re-orderings and something or other seemed to fail when I changed the order. I fixed it by adding a named restart to rc.local. Annoying, but it works. Ideally, named should just try to reconnect to dbus. -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: NM stopped using local caching nameserver?
I tracked this down some.. It appears part of the issue is a race condition between named and dbus. The startup sequence has named start first, and then dbus... but then named doesn't connect to dbus properly. If I RESTART named then everything appears to work okay. I suspect the problem here is that named doesn't retry to connect to dbus if it fails to connect on startup. Would this be a named bug? -derek Derek Atkins <[EMAIL PROTECTED]> writes: > Hi, > > At some point network manager stopped using my local caching > nameserver. Using a mostly-up-to-date Fedora 7, my NM created > a resolv.conf that read: > >> # generated by NetworkManager, do not edit! >> >> search ihtfp.org >> >> >> nameserver 10.0.1.1 > > But it should be using nameserver 127.0.0.1. I know I've got named > running with -D: > > [EMAIL PROTECTED] wde]$ ps auxww | grep named > named 2121 0.0 0.4 58668 14272 ?Ssl Sep12 0:00 > /usr/sbin/named -u named -c /etc/named.caching-nameserver.conf -D -t > /var/named/chroot > > I've got the following packages installed: > > bind-chroot-9.4.1-9.P1.fc7 > bind-9.4.1-9.P1.fc7 > caching-nameserver-9.4.1-9.P1.fc7 > NetworkManager-0.6.5-7.fc7 > > How can I get NM to use named again? Do I need to remove the > bind-chroot package or somehow tell NM to connect to the > bind-chroot'ed dbus connection or something? > > Thanks > > -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 > > -- 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: iwl3945 fails to associate to open, non-broadcast network
Dan Williams <[EMAIL PROTECTED]> writes: > On Mon, 2007-10-15 at 11:24 -0400, Derek Atkins wrote: >> Running fedora 7 with kernel-2.6.22.9-91.fc7-i686, trying to >> connect to a non-broadcasting open network using iwl3945. >> I see this in dmesg: >> >> eth1: Initial auth_alg=0 >> eth1: authenticate with AP 00:0e:d7:91:94:70 >> eth1: RX authentication from 00:0e:d7:91:94:70 (alg=0 transaction=2 status=0) >> eth1: authenticated >> eth1: associate with AP 00:0e:d7:91:94:70 >> eth1: RX AssocResp from 00:0e:d7:91:94:70 (capab=0x0 status=45552 aid=0) >> eth1: AP denied association (code=45552) >> eth1: associate with AP 00:0e:d7:91:94:70 >> eth1: RX deauthentication from 00:0e:d7:91:94:70 (reason=2) >> eth1: deauthenticated >> >> what is status code 45552? google says nothing about it. >> I can try downgrading to an older kernel to test. >> This happens both with and without NM so it's probably a driver >> bug but I was hoping that the greater NM community might know. > > The 45552 sounds bogus; IEEE 802.11 association response codes are > 8-bits. Could be some internal status code. Hey, I'm just reporting what it was reporting. I have no idea what it means. I was finally able to cajole it into connecting by stopping NM, unloading my driver, reloading my driver, trying to connect manually, and then (once it connected manually and actually got scan results with visible ESSIDS) restarted NM. Then it connected right away and I've been happy. But it really does seem to dislike "hidden networks". :( > Dan -derek PS: Any idea why NM stopped using my local caching nameserver? -- 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
iwl3945 fails to associate to open, non-broadcast network
Running fedora 7 with kernel-2.6.22.9-91.fc7-i686, trying to connect to a non-broadcasting open network using iwl3945. I see this in dmesg: eth1: Initial auth_alg=0 eth1: authenticate with AP 00:0e:d7:91:94:70 eth1: RX authentication from 00:0e:d7:91:94:70 (alg=0 transaction=2 status=0) eth1: authenticated eth1: associate with AP 00:0e:d7:91:94:70 eth1: RX AssocResp from 00:0e:d7:91:94:70 (capab=0x0 status=45552 aid=0) eth1: AP denied association (code=45552) eth1: associate with AP 00:0e:d7:91:94:70 eth1: RX deauthentication from 00:0e:d7:91:94:70 (reason=2) eth1: deauthenticated what is status code 45552? google says nothing about it. I can try downgrading to an older kernel to test. This happens both with and without NM so it's probably a driver bug but I was hoping that the greater NM community might know. Thanks, -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: Request for ergonomy feature
Quoting Dan Williams <[EMAIL PROTECTED]>: > This is likely a distro or driver problem. When NM is told to go to > sleep (whcih your setup may not be doing), it will blow away _all_ > network state. That means, when NM wakes up (if told to wake up > correctly), it won't know about _any_ networks. It will rescan > immediately. If it's getting stale networks when you turn it back on, > that's clearly a sleep/wake bug, or a driver bug. Just for the record, nm-applet does not always properly clear it's state. When I suspend/move/resume the applet still "remembers" the networks it saw before the suspend. I've certainly seen this with a relatively up-to-date Fedora 7 system (which means NM-0.6.5). So maybe the applet is caching the state and not clearing out the list properly on suspend or resume? > 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
NM stopped using local caching nameserver?
Hi, At some point network manager stopped using my local caching nameserver. Using a mostly-up-to-date Fedora 7, my NM created a resolv.conf that read: > # generated by NetworkManager, do not edit! > > search ihtfp.org > > > nameserver 10.0.1.1 But it should be using nameserver 127.0.0.1. I know I've got named running with -D: [EMAIL PROTECTED] wde]$ ps auxww | grep named named 2121 0.0 0.4 58668 14272 ?Ssl Sep12 0:00 /usr/sbin/named -u named -c /etc/named.caching-nameserver.conf -D -t /var/named/chroot I've got the following packages installed: bind-chroot-9.4.1-9.P1.fc7 bind-9.4.1-9.P1.fc7 caching-nameserver-9.4.1-9.P1.fc7 NetworkManager-0.6.5-7.fc7 How can I get NM to use named again? Do I need to remove the bind-chroot package or somehow tell NM to connect to the bind-chroot'ed dbus connection or something? Thanks -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
