How many SSIDs can be listed?
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? 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). ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Multi-active devices
On Mon, Mar 10, 2008 at 10:08 AM, Dan Williams <[EMAIL PROTECTED]> wrote: > active device support to NM SVN trunk this weekend; each device is now > independent and can be active/inactive irrespective of any other device. ya! :-) ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Some questions -- more radio misshaps
I am going to have to check my bios settings again. Almost like they changed Robert Moskowitz wrote: > Dan Williams wrote: > >> On Mon, 2008-03-10 at 08:19 -0400, Robert Moskowitz wrote: >> >> >>> Hello, I am new here. Running 0.6.4 in Centos 5.1 on an HP nc2400 >>> notebook with the Intel ipw3945 dkms code from rpmforge. >>> >>> I just switched my operation over the this nc2400 from my old nc4010 >>> which had an Atheros card using the madwifi dkms code from rpmforge and >>> I did everything via wpa_supplicant.conf (and the wpa_cli program!). >>> >>> So with this install, I could not get the wpa_supplicant working. Seems >>> like it only supports the ipw2200 card? And I found NetworkManager; >>> good job! So far :) >>> >>> >> As Ryan pointed out, NM will work with any card that properly supports >> wireless extensions. For RHEL5 (because the kernel is slightly older) >> that means ipw3945 (_not_ iwl3945), iwl4965 (as a tech preview only), >> airo, orinoco/hostap, atmel, ipw2100, ipw2200, ipw2915, zd1201, and >> bcm43xx. >> >> >> >>> I am plowing through the archives to find answers, but this is slow! No >>> way that I can find to download them and import them into Thunderbird >>> for better searching. So here goes: >>> >>> >>> The nc2400 expects the OS to manage the card. There are no buttons to >>> turn the radio on and off like on my old nc4010. Here I am on a plane >>> with the radio on. Now I work with Boeing people (and work on 802.11 >>> standards), so I have some inside knowledge of 802.11 and airplanes in >>> flight, but that is not the point. The radio is eating power! I need >>> that battery life! How can I turn off the radio. I tried iwconfig >>> eth1 power on (to turn on power management), but the card is still >>> happily scanning for APs, I think. >>> >>> >> If you uncheck "Wireless Enabled" after right-clicking the applet, this >> should down the interface, which if the driver is correctly written >> (some are not), should turn off the wireless power to the card. If your >> card doesn't turn off the TX power when you run 'iwconfig eth1 down' >> then it's a driver bug. >> >> > No such command as iwconfig eth1 down. You mean ifconfig eth1 down? > > I just went trough a 'farrowing' time with this. Everything wireless > stopped. So I tried this. > This time when things stopped working I looked first before typing. Radio went off. I had unplugged the notebook and closed the unit. But I have done that earlier today. I plugged back in and while I was doing lsmod and dmesg commands, the radio came back on. More likely not related, just with power it 'woke up'? ARGH. > I could not get the wireless back up. Rebooted a number of times. No > wireless at all! > > Then the LED came on and things started working after I did a dmesg > command, which makes no sense that that turned the radio on. Could just > have been a heat glitch. But in all this I learned that iwconfig eth1 > down is not a valid command :) > > One of the joys of a meeting like the IETF is there are lots of APs > visable with lots of clients around and all sorts of nonsense to make > wireless go bump in the middle of a lookup. IEEE 802.11 meetings are > just as bad! Interop has been worst (all those vendors running their > own wireless demo network). If you want to test out your code, go to a > big conference or trade show! > > > >> >> >>> I seem to recall a way with lmsensor to turn the LEDs on and off, but I >>> think that only tied the LEDs into the reality of the operation of the >>> card, not impacting the card at all. >>> >>> This notebook also has builtin ethernet. But shortly I will be at the >>> IETF conference in Philly, and I want to run Firestarter with its NATing >>> functions so I can plug another computer into the notebook to give it >>> access through my one wireless connection. How can I get NetworkManager >>> to leave the wired alone so Firestarter can manage it and run services >>> like DHCP? >>> >>> >> Add the line "NM_CONTROLLED=no" to >> your /etc/sysconfig/network-scripts/ifcfg-eth0 (or whatever interface >> name your wired card is) and NetworkManager will ignore it. NM will >> still manage the default route then when wireless is enabled and active. >> >> >> >>> My home network runs WPA-PSK (yeah, I know the risks, I wrote the attack >>> paper, but my Radius server is currently down). I frequently run into >>> the situation where NetworkManager is not succeeding in authenticating >>> to the AP. I have no sniffing data; I would like to see some packets, >>> but Wireshark does not show interface eth1 (the wireless one). I end up >>> having to reboot to get wireless working, or switch to wired. >>> >>> >> You probably have to switch the ipw3945 into monitor mode; if you google >> around you can probably find out how, but I think it includes insertin
Re: Some questions
Dan Williams wrote: > On Mon, 2008-03-10 at 08:19 -0400, Robert Moskowitz wrote: > >> Hello, I am new here. Running 0.6.4 in Centos 5.1 on an HP nc2400 >> notebook with the Intel ipw3945 dkms code from rpmforge. >> >> I just switched my operation over the this nc2400 from my old nc4010 >> which had an Atheros card using the madwifi dkms code from rpmforge and >> I did everything via wpa_supplicant.conf (and the wpa_cli program!). >> >> So with this install, I could not get the wpa_supplicant working. Seems >> like it only supports the ipw2200 card? And I found NetworkManager; >> good job! So far :) >> > > As Ryan pointed out, NM will work with any card that properly supports > wireless extensions. For RHEL5 (because the kernel is slightly older) > that means ipw3945 (_not_ iwl3945), iwl4965 (as a tech preview only), > airo, orinoco/hostap, atmel, ipw2100, ipw2200, ipw2915, zd1201, and > bcm43xx. > > >> I am plowing through the archives to find answers, but this is slow! No >> way that I can find to download them and import them into Thunderbird >> for better searching. So here goes: >> >> >> The nc2400 expects the OS to manage the card. There are no buttons to >> turn the radio on and off like on my old nc4010. Here I am on a plane >> with the radio on. Now I work with Boeing people (and work on 802.11 >> standards), so I have some inside knowledge of 802.11 and airplanes in >> flight, but that is not the point. The radio is eating power! I need >> that battery life! How can I turn off the radio. I tried iwconfig >> eth1 power on (to turn on power management), but the card is still >> happily scanning for APs, I think. >> > > If you uncheck "Wireless Enabled" after right-clicking the applet, this > should down the interface, which if the driver is correctly written > (some are not), should turn off the wireless power to the card. If your > card doesn't turn off the TX power when you run 'iwconfig eth1 down' > then it's a driver bug. > No such command as iwconfig eth1 down. You mean ifconfig eth1 down? I just went trough a 'farrowing' time with this. Everything wireless stopped. So I tried this. I could not get the wireless back up. Rebooted a number of times. No wireless at all! Then the LED came on and things started working after I did a dmesg command, which makes no sense that that turned the radio on. Could just have been a heat glitch. But in all this I learned that iwconfig eth1 down is not a valid command :) One of the joys of a meeting like the IETF is there are lots of APs visable with lots of clients around and all sorts of nonsense to make wireless go bump in the middle of a lookup. IEEE 802.11 meetings are just as bad! Interop has been worst (all those vendors running their own wireless demo network). If you want to test out your code, go to a big conference or trade show! > >> I seem to recall a way with lmsensor to turn the LEDs on and off, but I >> think that only tied the LEDs into the reality of the operation of the >> card, not impacting the card at all. >> >> This notebook also has builtin ethernet. But shortly I will be at the >> IETF conference in Philly, and I want to run Firestarter with its NATing >> functions so I can plug another computer into the notebook to give it >> access through my one wireless connection. How can I get NetworkManager >> to leave the wired alone so Firestarter can manage it and run services >> like DHCP? >> > > Add the line "NM_CONTROLLED=no" to > your /etc/sysconfig/network-scripts/ifcfg-eth0 (or whatever interface > name your wired card is) and NetworkManager will ignore it. NM will > still manage the default route then when wireless is enabled and active. > > >> My home network runs WPA-PSK (yeah, I know the risks, I wrote the attack >> paper, but my Radius server is currently down). I frequently run into >> the situation where NetworkManager is not succeeding in authenticating >> to the AP. I have no sniffing data; I would like to see some packets, >> but Wireshark does not show interface eth1 (the wireless one). I end up >> having to reboot to get wireless working, or switch to wired. >> > > You probably have to switch the ipw3945 into monitor mode; if you google > around you can probably find out how, but I think it includes inserting > the ipw3945 module with the "rtap_iface=1" argument, then 'ifconfig > rtap0 up' and then using wireshark. > > >> Now I notice that my AP is on channel 1, and I am picking up "Oakland >> Wireless" also on channel 1. This should NOT be causing the problem (I >> hope), but I add the data point. Actually I would like the option to >> tell NetworkManager to ignore "Oakland Wireless" when I am at home, just >> not when I am over at the local park, come springtime. When I used >> wpa_supplicant.conf, I could comment out various configs (or uncomment >> them) and reload the conf file at least. Ah the pains
Re: Some questions -- wpa_supplicant
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robert Moskowitz wrote: > > Ryan Novosielski wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Please keep replies on-list for everyone's benefit. >> > oops. Just did a reply, am use that on most lists this replys to the > list, not to the original sender... > > For this list, I have to do a reply to all, the edit the to/cc headers > (using Thunderbird 1.5) There is a "Reply-To-List" extension out there that I mean to see if I can dig up. It only works on Thunderbird 1.x -- the new one that is easy to find only works on patched 2.x and the yet-unreleased 3.x. I'll let you know if I find it. (sorry to go off-topic) >> Robert Moskowitz wrote: >> >>> Ryan Novosielski wrote: >>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You might want to write a more specific subject next time, for everyone's benefit. Everyone who writes to the list has "some questions." Robert Moskowitz wrote: > Hello, I am new here. Running 0.6.4 in Centos 5.1 on an HP nc2400 > notebook with the Intel ipw3945 dkms code from rpmforge. > > I just switched my operation over the this nc2400 from my old nc4010 > which had an Atheros card using the madwifi dkms code from rpmforge > and I did everything via wpa_supplicant.conf (and the wpa_cli program!). > > So with this install, I could not get the wpa_supplicant working. > Seems like it only supports the ipw2200 card? And I found > NetworkManager; good job! So far :) > > Incorrect. It probably best supports that card, but as far as I know, all Intel cards are supported. Really any card that has a driver supporting Wireless Extensions. >>> Well I tried running: >>> >>> /usr/sbin/wpa_supplicant wpa_supplicant -B -D ipw3945 -i eth1 -c >>> /etc/wpa_supplicant/wpa_supplicant.conf >>> >>> And I get Unsupported driver 'ipw3945' >>> >>> So I read the man wpa_supplicant and find that I should say -D ipw and >>> that only ipw2200 is supported. But I tried anyway: >>> >>> /usr/sbin/wpa_supplicant wpa_supplicant -B -D ipw -i eth1 -c >>> /etc/wpa_supplicant/wpa_supplicant.conf >>> >>> And still got unsupported device. >>> >> No, you want wext for basically all modern cards, not ipw. Those other >> drivers are really legacy holdovers, and hopefully will go away. >> > OH. I missed this one. Well actually I recall that how I finally even > got NetworkManager working was to edit /etc/sysconfig/wpa_supplicant to > have: > > wpa_supplicant:DRIVERS="-Dwext" > > I did not 'get' this previously! In fact, I'm pretty sure that NetworkManager ONLY supports cards that conform to -Dwext -- wpa_supplicant can also use all the others. - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$&| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH1ckEmb+gadEcsb4RAjsTAJ94rkBndV9RcFYFTpOVTOzxnR9+LwCeM2pw zHlbaE03pA1kA/ng61OSHEE= =FFax -END PGP SIGNATURE- begin:vcard fn:Ryan Novosielski n:Novosielski;Ryan org:UMDNJ;IST/AST adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103 email;internet:[EMAIL PROTECTED] title:Systems Programmer II tel;work:(973) 972-0922 tel;fax:(973) 972-7412 tel;pager:(866) 20-UMDNJ x-mozilla-html:FALSE version:2.1 end:vcard ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Some questions -- WPA-PSK failure
The Holy ettlz wrote: > Hmmm... > > >> My home network runs WPA-PSK (yeah, I know the risks, I wrote the attack >> paper, but my Radius server is currently down). I frequently run into >> the situation where NetworkManager is not succeeding in authenticating >> to the AP. I have no sniffing data; I would like to see some packets, >> but Wireshark does not show interface eth1 (the wireless one). I end up >> having to reboot to get wireless working, or switch to wired. >> > > Does it authenticate OK when you take down the interface and restart > NetworkManager? (I ask because I have a similar problem with one WAP > that'll only authenticate once, *guaranteed*, but then never again; yet > with another WAP backending to the same RADIUS server, it'll > re-authenticate with no problems whenever I ask. See RH Bugzilla > #434821.) I will have to wait until friday to test this (provided it fails then!), but for what it is worth, I could connect to the unsecured "Oakland Wireless" AP near my home, but not my WPA-PSK AP that was under my desk. I did not try taking the interface down. Should have. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Some questions -- turnoff radio
Ryan Novosielski wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Dan Williams wrote: > > >> If you uncheck "Wireless Enabled" after right-clicking the applet, this >> should down the interface, which if the driver is correctly written >> (some are not), should turn off the wireless power to the card. Well it did not. The LED lights were happily flashing away, seemingly indicating something going out the card (like active scanning). >> If your >> card doesn't turn off the TX power when you run 'iwconfig eth1 down' >> then it's a driver bug. >> I will try this next. I only did an iwconfig eth1 power on to turn on power management. Obviously the wrong piece of magic. > > Mine used to do work this way and does no longer. I also use ipw3945, so > I figured this was worth mentioning. It is somewhat disappointing, > because it used to be my way of making sure there was no radio noise. > Now if I really want to do that, it's the killswitch only. Kill is not an option. The whole point is to use the computer without any power draw by the wireless radio! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Some questions -- wpa_supplicant
Ryan Novosielski wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Please keep replies on-list for everyone's benefit. > oops. Just did a reply, am use that on most lists this replys to the list, not to the original sender... For this list, I have to do a reply to all, the edit the to/cc headers (using Thunderbird 1.5) > Robert Moskowitz wrote: > >> Ryan Novosielski wrote: >> >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> You might want to write a more specific subject next time, for >>> everyone's benefit. Everyone who writes to the list has "some questions." >>> >>> Robert Moskowitz wrote: >>> >>> Hello, I am new here. Running 0.6.4 in Centos 5.1 on an HP nc2400 notebook with the Intel ipw3945 dkms code from rpmforge. I just switched my operation over the this nc2400 from my old nc4010 which had an Atheros card using the madwifi dkms code from rpmforge and I did everything via wpa_supplicant.conf (and the wpa_cli program!). So with this install, I could not get the wpa_supplicant working. Seems like it only supports the ipw2200 card? And I found NetworkManager; good job! So far :) >>> Incorrect. It probably best supports that card, but as far as I know, >>> all Intel cards are supported. Really any card that has a driver >>> supporting Wireless Extensions. >>> >>> >> Well I tried running: >> >> /usr/sbin/wpa_supplicant wpa_supplicant -B -D ipw3945 -i eth1 -c >> /etc/wpa_supplicant/wpa_supplicant.conf >> >> And I get Unsupported driver 'ipw3945' >> >> So I read the man wpa_supplicant and find that I should say -D ipw and >> that only ipw2200 is supported. But I tried anyway: >> >> /usr/sbin/wpa_supplicant wpa_supplicant -B -D ipw -i eth1 -c >> /etc/wpa_supplicant/wpa_supplicant.conf >> >> And still got unsupported device. >> > > No, you want wext for basically all modern cards, not ipw. Those other > drivers are really legacy holdovers, and hopefully will go away. > OH. I missed this one. Well actually I recall that how I finally even got NetworkManager working was to edit /etc/sysconfig/wpa_supplicant to have: wpa_supplicant:DRIVERS="-Dwext" I did not 'get' this previously! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
[Fwd: Re: Some questions -- turnoff radio]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Back on the list - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$&| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH1cKomb+gadEcsb4RApPuAKCztFpW1koGls/1QKp7mCDdUG62NgCfYdGI OQTe/nbkNzNt78cUffRASyU= =w4tq -END PGP SIGNATURE- --- Begin Message --- Ryan Novosielski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Williams wrote: If you uncheck "Wireless Enabled" after right-clicking the applet, this should down the interface, which if the driver is correctly written (some are not), should turn off the wireless power to the card. Well it did not. The LED lights were happily flashing away, seemingly indicating something going out the card (like active scanning). If your card doesn't turn off the TX power when you run 'iwconfig eth1 down' then it's a driver bug. I will try this next. I only did an iwconfig eth1 power on to turn on power management. Obviously the wrong piece of magic. Mine used to do work this way and does no longer. I also use ipw3945, so I figured this was worth mentioning. It is somewhat disappointing, because it used to be my way of making sure there was no radio noise. Now if I really want to do that, it's the killswitch only. Kill is not an option. The whole point is to use the computer without any power draw by the wireless radio! --- End Message --- begin:vcard fn:Ryan Novosielski n:Novosielski;Ryan org:UMDNJ;IST/AST adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103 email;internet:[EMAIL PROTECTED] title:Systems Programmer II tel;work:(973) 972-0922 tel;fax:(973) 972-7412 tel;pager:(866) 20-UMDNJ x-mozilla-html:FALSE version:2.1 end:vcard ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Some questions -- wpa_supplicant
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please keep replies on-list for everyone's benefit. Robert Moskowitz wrote: > > > Ryan Novosielski wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> You might want to write a more specific subject next time, for >> everyone's benefit. Everyone who writes to the list has "some questions." >> >> Robert Moskowitz wrote: >> >>> Hello, I am new here. Running 0.6.4 in Centos 5.1 on an HP nc2400 >>> notebook with the Intel ipw3945 dkms code from rpmforge. >>> >>> I just switched my operation over the this nc2400 from my old nc4010 >>> which had an Atheros card using the madwifi dkms code from rpmforge >>> and I did everything via wpa_supplicant.conf (and the wpa_cli program!). >>> >>> So with this install, I could not get the wpa_supplicant working. >>> Seems like it only supports the ipw2200 card? And I found >>> NetworkManager; good job! So far :) >>> >> >> Incorrect. It probably best supports that card, but as far as I know, >> all Intel cards are supported. Really any card that has a driver >> supporting Wireless Extensions. >> > Well I tried running: > > /usr/sbin/wpa_supplicant wpa_supplicant -B -D ipw3945 -i eth1 -c > /etc/wpa_supplicant/wpa_supplicant.conf > > And I get Unsupported driver 'ipw3945' > > So I read the man wpa_supplicant and find that I should say -D ipw and > that only ipw2200 is supported. But I tried anyway: > > /usr/sbin/wpa_supplicant wpa_supplicant -B -D ipw -i eth1 -c > /etc/wpa_supplicant/wpa_supplicant.conf > > And still got unsupported device. No, you want wext for basically all modern cards, not ipw. Those other drivers are really legacy holdovers, and hopefully will go away. > I added an alias to modprobe.conf and that did not help. > > This is all on Centos 5.1 - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$&| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH1cJrmb+gadEcsb4RAki2AJ9rnsnO/zfueysiWjtE2mk+Wpaf8wCgxULz fqAUTYiyl4Qk3dOQ8xZIDxQ= =4VTI -END PGP SIGNATURE- begin:vcard fn:Ryan Novosielski n:Novosielski;Ryan org:UMDNJ;IST/AST adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103 email;internet:[EMAIL PROTECTED] title:Systems Programmer II tel;work:(973) 972-0922 tel;fax:(973) 972-7412 tel;pager:(866) 20-UMDNJ x-mozilla-html:FALSE version:2.1 end:vcard ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] support for domain-search, request for comments/testing
On Thu, 2008-03-06 at 14:59 -0500, Dan Williams wrote: > On Thu, 2008-03-06 at 19:15 +0100, Michael Biebl wrote: > > Michael Biebl wrote: > > > Hi everyone, > > > > > > a few days ago I received a contribution in form of a patch [1], which > > > adds domain-search support to NetworkManager (0.6). > > > I'll be quoting the relevant part here: > > > > > [..] > > > > > > one, which supports this domain-search option. I currently don't have > > > access to a dhcp3-server with support for domain-search, so I can't test > > > it myself. Thus this request for testing. > > > I'd also like to know, if this patch has a chance of making into 0.6.6, > > > and if not, if you plan to release a 0.6.6.1 or 0.6.7 and what you think > > > of the patch in general. > > > > Any comments or feedback? > > I think in general it's the right thing to do, I have to go back and > look over the patch more closely (need to fix some of the coding style > too). > > It's too late for 0.6.6 (going to cut that today and the change is too > high-risk) but we could do a 0.6.6.1 if you like. Fixes committed to stable and trunk, thanks. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: gsm support for nokia 6680
Hi! > > I tried this with my Nokia 6021 but it didn't help. Actually ATDT > > works ok with Nokia 6021 when trying with wvdial. I think you > > might want to check with wvdial, too, is it really so that your > > 6680 does not support ATDT? > > > > https://bugzilla.redhat.com/show_bug.cgi?id=296851 > > Do you use username and password ? Because one critical thing I > forgot to tell in my email was that I had to set noauth in gconf for > it to work Username/password are defined in my wvdial.conf but they're not used (they can be anything, ppp/peers/wvdial has option noauth). The problem I see with NM is however hit before entering to that phase as the serial commands fail randomly. Details can be found from the bottom of the above bug report. Fo reference, the working wvdial.conf is below. [Dialer Defaults] Baud = 230400 Init1 = ATZ E0 Init2 = AT+CPIN? Init3 = AT+CREG? Init4 = AT+COPS? Dial Command = ATDT [Dialer gprs] Modem = /dev/ttyACM0 Phone = *99# Username = A Password = B Thanks! Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Some questions
Hmmm... > My home network runs WPA-PSK (yeah, I know the risks, I wrote the attack > paper, but my Radius server is currently down). I frequently run into > the situation where NetworkManager is not succeeding in authenticating > to the AP. I have no sniffing data; I would like to see some packets, > but Wireshark does not show interface eth1 (the wireless one). I end up > having to reboot to get wireless working, or switch to wired. Does it authenticate OK when you take down the interface and restart NetworkManager? (I ask because I have a similar problem with one WAP that'll only authenticate once, *guaranteed*, but then never again; yet with another WAP backending to the same RADIUS server, it'll re-authenticate with no problems whenever I ask. See RH Bugzilla #434821.) James -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Some questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Williams wrote: > If you uncheck "Wireless Enabled" after right-clicking the applet, this > should down the interface, which if the driver is correctly written > (some are not), should turn off the wireless power to the card. If your > card doesn't turn off the TX power when you run 'iwconfig eth1 down' > then it's a driver bug. Mine used to do work this way and does no longer. I also use ipw3945, so I figured this was worth mentioning. It is somewhat disappointing, because it used to be my way of making sure there was no radio noise. Now if I really want to do that, it's the killswitch only. - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$&| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH1VtSmb+gadEcsb4RAlPbAJ0SM1T21+evMYvTQ10fJQHy708frQCff55Z JJyavWU4eC3GlMS7YApRho8= =0AO0 -END PGP SIGNATURE- begin:vcard fn:Ryan Novosielski n:Novosielski;Ryan org:UMDNJ;IST/AST adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103 email;internet:[EMAIL PROTECTED] title:Systems Programmer II tel;work:(973) 972-0922 tel;fax:(973) 972-7412 tel;pager:(866) 20-UMDNJ x-mozilla-html:FALSE version:2.1 end:vcard ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Some questions
On Mon, 2008-03-10 at 08:19 -0400, Robert Moskowitz wrote: > Hello, I am new here. Running 0.6.4 in Centos 5.1 on an HP nc2400 > notebook with the Intel ipw3945 dkms code from rpmforge. > > I just switched my operation over the this nc2400 from my old nc4010 > which had an Atheros card using the madwifi dkms code from rpmforge and > I did everything via wpa_supplicant.conf (and the wpa_cli program!). > > So with this install, I could not get the wpa_supplicant working. Seems > like it only supports the ipw2200 card? And I found NetworkManager; > good job! So far :) As Ryan pointed out, NM will work with any card that properly supports wireless extensions. For RHEL5 (because the kernel is slightly older) that means ipw3945 (_not_ iwl3945), iwl4965 (as a tech preview only), airo, orinoco/hostap, atmel, ipw2100, ipw2200, ipw2915, zd1201, and bcm43xx. > I am plowing through the archives to find answers, but this is slow! No > way that I can find to download them and import them into Thunderbird > for better searching. So here goes: > > > The nc2400 expects the OS to manage the card. There are no buttons to > turn the radio on and off like on my old nc4010. Here I am on a plane > with the radio on. Now I work with Boeing people (and work on 802.11 > standards), so I have some inside knowledge of 802.11 and airplanes in > flight, but that is not the point. The radio is eating power! I need > that battery life! How can I turn off the radio. I tried iwconfig > eth1 power on (to turn on power management), but the card is still > happily scanning for APs, I think. If you uncheck "Wireless Enabled" after right-clicking the applet, this should down the interface, which if the driver is correctly written (some are not), should turn off the wireless power to the card. If your card doesn't turn off the TX power when you run 'iwconfig eth1 down' then it's a driver bug. > I seem to recall a way with lmsensor to turn the LEDs on and off, but I > think that only tied the LEDs into the reality of the operation of the > card, not impacting the card at all. > > This notebook also has builtin ethernet. But shortly I will be at the > IETF conference in Philly, and I want to run Firestarter with its NATing > functions so I can plug another computer into the notebook to give it > access through my one wireless connection. How can I get NetworkManager > to leave the wired alone so Firestarter can manage it and run services > like DHCP? Add the line "NM_CONTROLLED=no" to your /etc/sysconfig/network-scripts/ifcfg-eth0 (or whatever interface name your wired card is) and NetworkManager will ignore it. NM will still manage the default route then when wireless is enabled and active. > My home network runs WPA-PSK (yeah, I know the risks, I wrote the attack > paper, but my Radius server is currently down). I frequently run into > the situation where NetworkManager is not succeeding in authenticating > to the AP. I have no sniffing data; I would like to see some packets, > but Wireshark does not show interface eth1 (the wireless one). I end up > having to reboot to get wireless working, or switch to wired. You probably have to switch the ipw3945 into monitor mode; if you google around you can probably find out how, but I think it includes inserting the ipw3945 module with the "rtap_iface=1" argument, then 'ifconfig rtap0 up' and then using wireshark. > Now I notice that my AP is on channel 1, and I am picking up "Oakland > Wireless" also on channel 1. This should NOT be causing the problem (I > hope), but I add the data point. Actually I would like the option to > tell NetworkManager to ignore "Oakland Wireless" when I am at home, just > not when I am over at the local park, come springtime. When I used > wpa_supplicant.conf, I could comment out various configs (or uncomment > them) and reload the conf file at least. Ah the pains of a real nice > integrated gui! NetworkManager will attempt to connect to the network you last used (via a timestamp of the last successful connection). Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: does current svn version networkmanager support WPA (PEAP-MSCHAPV2)?
On Sun, 2008-03-09 at 01:59 -0600, Forrest Sheng Bao wrote: > Ok, now I have understand. I just need to install wpa_supplicant and > do the configuration in NetworkManager. Then NetworkManager will call > wpa_supplicant to access the Wi-Fi. > > So I did it and it could connect to the Wi-Fi. I tried to surf the > Internet and it worked. I was so excited. > > But there is a problem, I always got disconnected after the connection > was established. And NetworkManager didn't try to reconnect > automatically. And I found the only way I can reconnect was to click > "Connect to other wireless network" and input the authenticating > information again. It didn't work if I just select the network name I > wanted. I am not sure why. I also found that on the network list, > NetworkManager sometimes didn't display a WPA-enabled network as > security enabled, without a shield icon. Odd; when you see the wireless network in the menu without the shield for security-enabled, can you run: /usr/bin/nm-tool sudo /sbin/iwlist wlan0 scan (assuming that wlan0 is your wireless device, and that your user can sudo). I'm trying to get an idea here of what NM thinks it knows, versus what the driver thinks it knows. You may wish to email me the output directly since the output of both of these may expose details of your machine you'd rather keep private. Thanks Dan > On Thu, Mar 6, 2008 at 10:36 AM, Dan Williams <[EMAIL PROTECTED]> wrote: > On Thu, 2008-03-06 at 10:40 -0500, Ryan Novosielski wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > > wpa_supplicant does not require any configuration on Ubuntu > though to > > work with NetworkManager. The whole thing "just works." I > realize that > > it doesn't work for you, but there should be no tweaking > required, just > > entering the correct settings. You might see about running > > wpa_supplicant SEPARATELY to see if you can connect with it. > If you can, > > that would be more information to use to debug > NetworkManager. > > > > Incidentally, what sort of wireless card do you have? One > requirement is > > that the card work properly with wireless extensions (-Dwext > in > > wpa_supplicant). > > > Right; I'd suggest trying straight wpa_supplicant with -D wext > to ensure > that it's not NetworkManager first. If that reliably fails, > then > there's something wrong with the driver, hardware, or the > configuration > being used. > > Dan > > > > > -- > Forrest Sheng Bao > Ph.D. student, Dept. of Computer Science > M.Sc. student, Dept. of Electrical & Computer Engineering > Texas Tech University, USA > http://fsbao.net > 1-806-577-4592 > > Forrest is an equal opportunity Email sender. > 1. You are encouraged to use the language you prefer. Beyond English, > I can also read traditional/simplified Chinese and a bit German. > 2. I will only send you files readable to free or open source > software. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Multi-active devices
On Sat, 2008-03-08 at 18:44 -0600, Jerry Vonau wrote: > Hi All: > > What support is planned for multiple gateways? I build firewalls > that don't run X (so no runlevel 5 here), with the recent CLI support, I > might just try to use NM in the future. I setup multi-gateway (2+ ISPs) > support using my own scripts or Shorewall's built-in support. I have had > a small hand in the development of Shorewall's multi-isp support, and > the supporting of the same on Shorewall's mailing list. In past have > submitted patches to initscripts for this support (BZ171763), I have > working experence with iproute and what is needed to make this work in > real life, is there any interest in having NM support this? What sort of configuration setup do you need? I committed the multiple active device support to NM SVN trunk this weekend; each device is now independent and can be active/inactive irrespective of any other device. Do you need complicated routing setup or other interface-specific parameters? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.7 connection sharing
On Sat, 2008-03-08 at 16:48 -0500, Darren Albers wrote: > On Sat, Mar 8, 2008 at 4:18 PM, Dan Williams <[EMAIL PROTECTED]> wrote: > > Hi, > > > > After some discussion in a related thread on fedora-devel, I've thought > > through the WiFi connection sharing a bit more, and been schooled on a > > few things. > > > > Mac OS X provides a full infrastructure-mode network when sharing an > > internet connection over wireless. It also provides DHCP to clients of > > that wifi network, and uses addresses in the 10.x.x.x space. > > > > Unfortunately, given the current driver situation, NM on Linux won't be > > able to do the same thing, since few drivers support master mode well at > > this time. Therefore, NM 0.7 will: > > > > 1) as the _originator_ of a wireless network, either by sharing a > > connection or creating a new wireless network, use 802.11 Ad-Hoc and > > provide a DHCP server (see below) > > > > 2) require opt-in to get IPv4 LL on device types known to usually use > > DHCP, requiring the user to pick between Auto-IP and DHCP (ie, Auto-IP > > and DHCP will be mutually exclusive) > > > > 3) Perform DHCP by default on Ad-Hoc networks, unless the user has opted > > into Auto-IP in the connection editor > > > > 4) use dnsmasq as the DHCP server for shared connections. The ISC dhcpd > > uses 20MB of RAM when running and that's just unacceptable. dnsmasq > > also provides proxied DNS, which is a nice bonus. > > > > Dan > > > > > > ___ > > NetworkManager-list mailing list > > NetworkManager-list@gnome.org > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > > Since the network is ad-hoc I assume there won't be a way to set encryption? Ad-Hoc can use WEP (either 40 or 104-bit) on all cards, and can do WPA-PSK on cards that support WPA. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Some questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You might want to write a more specific subject next time, for everyone's benefit. Everyone who writes to the list has "some questions." Robert Moskowitz wrote: > Hello, I am new here. Running 0.6.4 in Centos 5.1 on an HP nc2400 > notebook with the Intel ipw3945 dkms code from rpmforge. > > I just switched my operation over the this nc2400 from my old nc4010 > which had an Atheros card using the madwifi dkms code from rpmforge and > I did everything via wpa_supplicant.conf (and the wpa_cli program!). > > So with this install, I could not get the wpa_supplicant working. Seems > like it only supports the ipw2200 card? And I found NetworkManager; > good job! So far :) Incorrect. It probably best supports that card, but as far as I know, all Intel cards are supported. Really any card that has a driver supporting Wireless Extensions. > I am plowing through the archives to find answers, but this is slow! No > way that I can find to download them and import them into Thunderbird > for better searching. So here goes: > > The nc2400 expects the OS to manage the card. There are no buttons to > turn the radio on and off like on my old nc4010. Here I am on a plane > with the radio on. Now I work with Boeing people (and work on 802.11 > standards), so I have some inside knowledge of 802.11 and airplanes in > flight, but that is not the point. The radio is eating power! I need > that battery life! How can I turn off the radio. I tried iwconfig > eth1 power on (to turn on power management), but the card is still > happily scanning for APs, I think. > > I seem to recall a way with lmsensor to turn the LEDs on and off, but I > think that only tied the LEDs into the reality of the operation of the > card, not impacting the card at all. > > This notebook also has builtin ethernet. But shortly I will be at the > IETF conference in Philly, and I want to run Firestarter with its NATing > functions so I can plug another computer into the notebook to give it > access through my one wireless connection. How can I get NetworkManager > to leave the wired alone so Firestarter can manage it and run services > like DHCP? Often, adding this to your distro's configuration files (like /etc/network/interfaces, etc.) will cause this to be left alone. > My home network runs WPA-PSK (yeah, I know the risks, I wrote the attack > paper, but my Radius server is currently down). I frequently run into > the situation where NetworkManager is not succeeding in authenticating > to the AP. I have no sniffing data; I would like to see some packets, > but Wireshark does not show interface eth1 (the wireless one). I end up > having to reboot to get wireless working, or switch to wired. > > Now I notice that my AP is on channel 1, and I am picking up "Oakland > Wireless" also on channel 1. This should NOT be causing the problem (I > hope), but I add the data point. Actually I would like the option to > tell NetworkManager to ignore "Oakland Wireless" when I am at home, just > not when I am over at the local park, come springtime. When I used > wpa_supplicant.conf, I could comment out various configs (or uncomment > them) and reload the conf file at least. Ah the pains of a real nice > integrated gui! > > I can't test anything at home until I get back on friday, but thought I > would mention it now while I am venting. > > Plane is decending. Will be connected in a couple hours. - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$&| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH1UECmb+gadEcsb4RAm/5AKCKKvIxMSKsEBYaZFD/bvMMcRXL/QCgwwn4 h6PgJ/j16e+2QCuZtRVKFjY= =Xr2t -END PGP SIGNATURE- begin:vcard fn:Ryan Novosielski n:Novosielski;Ryan org:UMDNJ;IST/AST adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103 email;internet:[EMAIL PROTECTED] title:Systems Programmer II tel;work:(973) 972-0922 tel;fax:(973) 972-7412 tel;pager:(866) 20-UMDNJ x-mozilla-html:FALSE version:2.1 end:vcard ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Some questions
Hello, I am new here. Running 0.6.4 in Centos 5.1 on an HP nc2400 notebook with the Intel ipw3945 dkms code from rpmforge. I just switched my operation over the this nc2400 from my old nc4010 which had an Atheros card using the madwifi dkms code from rpmforge and I did everything via wpa_supplicant.conf (and the wpa_cli program!). So with this install, I could not get the wpa_supplicant working. Seems like it only supports the ipw2200 card? And I found NetworkManager; good job! So far :) I am plowing through the archives to find answers, but this is slow! No way that I can find to download them and import them into Thunderbird for better searching. So here goes: The nc2400 expects the OS to manage the card. There are no buttons to turn the radio on and off like on my old nc4010. Here I am on a plane with the radio on. Now I work with Boeing people (and work on 802.11 standards), so I have some inside knowledge of 802.11 and airplanes in flight, but that is not the point. The radio is eating power! I need that battery life! How can I turn off the radio. I tried iwconfig eth1 power on (to turn on power management), but the card is still happily scanning for APs, I think. I seem to recall a way with lmsensor to turn the LEDs on and off, but I think that only tied the LEDs into the reality of the operation of the card, not impacting the card at all. This notebook also has builtin ethernet. But shortly I will be at the IETF conference in Philly, and I want to run Firestarter with its NATing functions so I can plug another computer into the notebook to give it access through my one wireless connection. How can I get NetworkManager to leave the wired alone so Firestarter can manage it and run services like DHCP? My home network runs WPA-PSK (yeah, I know the risks, I wrote the attack paper, but my Radius server is currently down). I frequently run into the situation where NetworkManager is not succeeding in authenticating to the AP. I have no sniffing data; I would like to see some packets, but Wireshark does not show interface eth1 (the wireless one). I end up having to reboot to get wireless working, or switch to wired. Now I notice that my AP is on channel 1, and I am picking up "Oakland Wireless" also on channel 1. This should NOT be causing the problem (I hope), but I add the data point. Actually I would like the option to tell NetworkManager to ignore "Oakland Wireless" when I am at home, just not when I am over at the local park, come springtime. When I used wpa_supplicant.conf, I could comment out various configs (or uncomment them) and reload the conf file at least. Ah the pains of a real nice integrated gui! I can't test anything at home until I get back on friday, but thought I would mention it now while I am venting. Plane is decending. Will be connected in a couple hours. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: Reporting working WLAN adapter
Is there any wiki to include this interesting data about drivers?. We could use http://live.gnome.org and include also HAL information. Regards. De: [EMAIL PROTECTED] en nombre de Hans-Joachim Klein Enviado el: dom 09/03/2008 14:51 Para: networkmanager-list@gnome.org Asunto: Reporting working WLAN adapter Hi, I want to report my WLAN adapter to work with Network Manager. It is a D-Link DWA-643 (Express card). It works with the drivers from http://snapshots.madwifi.org/ file: madwifi-ng-current.tar.gz lspci reports: Atheros Communications, Inc. AR5418 802.11abgn Wireless PCI Express Adapter -- With best regards Hans-J. Klein Public Key: http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0x1006E4DA340C1B32 Key Fingerprint: 0945 2348 CDA7 5792 52D2 824F 1006 E4DA 340C 1B32 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Reporting working WLAN adapter
Hi, I want to report my WLAN adapter to work with Network Manager. It is a D-Link DWA-643 (Express card). It works with the drivers from http://snapshots.madwifi.org/ file: madwifi-ng-current.tar.gz lspci reports: Atheros Communications, Inc. AR5418 802.11abgn Wireless PCI Express Adapter -- With best regards Hans-J. Klein Public Key: http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0x1006E4DA340C1B32 Key Fingerprint: 0945 2348 CDA7 5792 52D2 824F 1006 E4DA 340C 1B32 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: gsm support for nokia 6680
Le samedi 08 mars 2008 à 02:19 -0800, Daniel Qarras a écrit : > Hi, > > > In response to Dan blog entry about getting phone working I got > > mine on trail though it required a change from ATDT to ATD before > > the gsm number setting. > > I tried this with my Nokia 6021 but it didn't help. Actually ATDT works > ok with Nokia 6021 when trying with wvdial. I think you might want to > check with wvdial, too, is it really so that your 6680 does not support > ATDT? > > I've been trying to get connected with my 6021 but still no success, > please see (you can find a working wvdial.conf there if interested): > > https://bugzilla.redhat.com/show_bug.cgi?id=296851 > > It is a bit strange that wvdial works and NM does not and also that > gnokii works and gnome-phone-manager does not. It may be a long shot > but could there be something fishy in a component common to NM/g-p-m > not used by wvdial/gnokii? > > Cheers! Do you use username and password ? Because one critical thing I forgot to tell in my email was that I had to set noauth in gconf for it to work (gconf-editor system>networking>connections>[findout the number that match you gsm connection]>ppp then check noauth. Regards Alban ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
