Re: intel pro wireless 3945ABG + Feisty Ubuntu + F7t4
dragoran <[EMAIL PROTECTED]> writes: > If you are using fedora 7 please try with a kernel from here (will be in > rawhide soon): > http://people.redhat.com/davej/kernels/Fedora/fc7/RPMS.kernel/ Okay, I tried this kernel (3125). It's working a little better. I can't connect at all to my 802.11(a) network, but I was FINALLY able to connect to my 802.11(b/g) network. But as soon as it connected, it disconnected. The logs look like: May 3 12:07:39 pgpdev NetworkManager: Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete. May 3 12:07:39 pgpdev NetworkManager: Activation (wlan0) successful, device activated. May 3 12:07:40 pgpdev NetworkManager: SWITCH: terminating current connection 'wlan0' because it is no longer valid. May 3 12:07:40 pgpdev NetworkManager: Deactivating device wlan0. May 3 12:07:40 pgpdev dhclient: wmaster0: unknown hardware addres type 801 May 3 12:07:40 pgpdev dhclient: wmaster0: unknown hardware addres type 801 May 3 12:07:40 pgpdev dhclient: DHCPRELEASE on wlan0 to XX.XX.XX.XX port 67 May 3 12:07:41 pgpdev wpa_supplicant[3787]: CTRL-EVENT-TERMINATING - signal 15 received May 3 12:07:41 pgpdev avahi-daemon]2735]: Withdrawing address record for YY.YY.YY.YY on wlan0. May 3 12:07:41 pgpdev avahi-daemon]2735]: Leaving mDNS multicast group on interface wlan0.IPv4 with address YY.YY.YY.YY. May 3 12:07:41 pgpdev avahi-daemon]2735]: Interface wlan0.IPv4 no longer relevant for mDNS. May 3 12:07:41 pgpdev NetworkManager: nm_device_is_802_3_ethernet: assertion `dev != NULL' failed May 3 12:07:41 pgpdev NetworkManager: nm_device_is_802_11_wireless: assertion `dev != NULL' failed So... Closer, but still no dice. -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: intel pro wireless 3945ABG + Feisty Ubuntu + F7t4
Derek Atkins wrote: > Dan, > > Dan Williams <[EMAIL PROTECTED]> writes: > > >> Is this with iwlwifi or the older 3945 ieee80211-based drivers? >> >> Dan >> > > I just installed F7t4 on my new T60 and I'm seeing this problem, > too. Using the iwlwifi and NM packages from an updated F7t4 > system I cannot connect to my home (WEP-protected) 802.11 b/g > or 802.11a networks. It just wont associate. > > I haven't tried connecting directly from the ifconfig scripts > to see if that works or not. > > In my dmesg log I see tons of: > > iwlwifi: TODO: Look into long/short preamble change handling. > > I also see: > > wmaster0: Does not support passive scan, disabled > > I haven't tried open networks or WPA (although I suppose I can open up > one of my networks to test it). > > Any suggestions of things to do or test? > > If you are using fedora 7 please try with a kernel from here (will be in rawhide soon): http://people.redhat.com/davej/kernels/Fedora/fc7/RPMS.kernel/ ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
VPNC - crash
When using Cisco .pcf profiles with no user authentication, only group based, network-manager is crashing. Any way to diagnose the issues and post a bug? Don't know if it is network-manager or vpnc causing the issue. Looks like dbus is rejecting the null username: May 3 09:49:33 greg-laptop NetworkManager: ^I nm_vpn_service_stage3_connect_cb (): (VPN Service org.freedesktop.NetworkManager.vpnc): could not start the VPN 'Anderon County Schools'. dbus says: '(null)' 'Invalid VPN options.'. May 3 09:49:33 greg-laptop NetworkManager: ^IVPN Activation (Anderon County Schools) failed. May 3 09:49:33 greg-laptop NetworkManager: file nm-vpn-manager.c: line 447 (nm_vpn_manager_vpn_connection_died): assertion failed: (manager) May 3 09:50:20 greg-laptop kernel: [ 1257.516000] Cisco Systems VPN Client Version 4.8.00 (0490) kernel module loaded May 3 09:50:40 greg-laptop kernel: [ 1278.008000] cipsec0: no IPv6 routers present As you can see, the Cisco client works fine following. We have several clients we use no usernames with to log into their networks. Network manager dies completely in this instance. Thanks, Greg ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: intel pro wireless 3945ABG + Feisty Ubuntu + F7t4
Dan, Dan Williams <[EMAIL PROTECTED]> writes: > Is this with iwlwifi or the older 3945 ieee80211-based drivers? > > Dan I just installed F7t4 on my new T60 and I'm seeing this problem, too. Using the iwlwifi and NM packages from an updated F7t4 system I cannot connect to my home (WEP-protected) 802.11 b/g or 802.11a networks. It just wont associate. I haven't tried connecting directly from the ifconfig scripts to see if that works or not. In my dmesg log I see tons of: iwlwifi: TODO: Look into long/short preamble change handling. I also see: wmaster0: Does not support passive scan, disabled I haven't tried open networks or WPA (although I suppose I can open up one of my networks to test it). Any suggestions of things to do or test? -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 won't connect to an ordinary AP
Hi, Today I noticed another bug with NM 0.6.5. All I wanted to do is to connect to an ordinary WEP AP. Nothing special here, but it kept hanging at dhclient stage. I was surprised to see that setting all the stuff manually (i.e. essid & wep) and then running dhclient from command line worked just fine. With NM however, even though I could see with iwconfig that essid & wep were set correctly, it kept hanging at aforementioned dhclient stage. syslog excerpt is here: http://pastebin.ca/468927 What I also noticed is that although dhclient run manually was successful, it wouldn't set up the resolv.conf at all. Seems that dhcp server is buggy or not configures properly; could this be a reason of such NM behaviour? -- Regards, Dawid Wróbel ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Request for ergonomy feature
Am Mittwoch, den 02.05.2007, 17:39 -0400 schrieb Dan Williams: > On Wed, 2007-05-02 at 23:00 +0200, Michael Trunner wrote: > > Hi, > > > > I had a very similar idea. If I have choose a network it shouldn't > > switch to another when the my goes off. Because everyday when my own > > network is to faraway nm switch to the network of my neighbour. In this > > case nm shouldn't search for other networks. I think a checkbox "search > > for networks" would be nice. > > If you don't want to associate with your neighbors network, remove it > from GConf. You connected to it once upon a time, which is why NM is > trying now. Granted, there should be a nice way to remove cached > networks, but having a checkbox for scanning is not the solution. > Hmm okay, but I have a similar problem on my University. There is one for the complete campus (VPN) and one for special buildings with eap which I prefer. But sometimes it switch like at home. Deleting the gconf entry is okay for the problem with my neighbours. But not for my problem one the university, because when I leave the building (so there is no eap conncetion) then I'm using the campus WLAN and the gconf entry is back. Maybe some one have a good idea for this problem. Michael > Dan > > > Bye > > > > Michael > > > > Am Mittwoch, den 02.05.2007, 19:12 +0300 schrieb Joan Moreau: > > > The point is not to do it by oneself or by the pc, but one may click > > > several time on the icon to see the status of the discovery which > > > trigger a new search and that does not end , while having to click once > > > on a button let people be able to see the current list of network > > > without "risking" to trigger a new search. > > > > > > > > > Christopher Aillon wrote: > > > > Greg Oliver wrote: > > > > > > > >> On Wed, 2007-05-02 at 09:08 +0200, Soren Hansen wrote: > > > >> > > > >>> Could one of you perhaps explain to me why you want to do something > > > >>> manually that network-manager does for you automatically? I don't > > > >>> quite > > > >>> get it. > > > >>> > > > >> Honestly, so my LED does not blink repeatedly > > > >> > > > > > > > > You'll have others blinking anyway. Hard disk, etc. > > > > > > > > > > > >> - as well as go back to a > > > >> previous request to have wired/wireless active simultaneously (I know > > > >> thats coming). In that situation, that would be most pleasant. My > > > >> radio would not be scanning constantly when I do not need it and I > > > >> could > > > >> scan when I want them both on. > > > >> > > > > > > > > And if your wired ever dies out? Or if you need to move for some > > > > reason > > > > and need to unplug? Do you want NetworkManager to just sit there for > > > > you to realize what happened, then click the applet, then click perform > > > > scan, wait for a few seconds, figure out which Network, and then > > > > connect > > > > you to wireless? > > > > > > > > Personally, I'd rather my music stream keep on playing. The whole > > > > point > > > > of NetworkManager is to do the work for you. People that don't want it > > > > to do the work still have iwconfig/iwlist. > > > > > > > > ___ > > > > NetworkManager-list mailing list > > > > NetworkManager-list@gnome.org > > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > > > > > ___ > > > NetworkManager-list mailing list > > > NetworkManager-list@gnome.org > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > > > -- Wenn das eigene Wohlbefinden von der vereinigten Dummheit fast aller Anderer geprägt ist, lebt man meistens in einer Demokratie. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Ad-hoc information
On 4/30/07, Dan Williams <[EMAIL PROTECTED]> wrote: > On Mon, 2007-04-30 at 20:02 +0300, Ohad Lutzky wrote: > > On 4/30/07, Dan Williams <[EMAIL PROTECTED]> wrote: > > > On Mon, 2007-04-30 at 09:56 +0300, Ohad Lutzky wrote: > > > > On 4/29/07, Dan Williams <[EMAIL PROTECTED]> wrote: > > > > > On Sun, 2007-04-29 at 11:32 +0300, Ohad Lutzky wrote: > > > > > > Hello, > > > > > > > > > > > > I'm interested in writing a program which interfaces with > > > > > > networkmanager in order to manipulate wireless networks. The program > > > > > > is part of an academic project, which cannot be GPLd (despite my > > > > > > wanting to), therefore I cannot use libiw directly. I would like to > > > > > > know whether or not the DBus API allows me to > > > > > > > > > > > > - Create Ad-hoc networks (that is, set the ESSID, and set the mode > > > > > > to Ad-hoc) > > > > > > > > > > No, because wpa_supplicant doesn't set the channel for adhoc networks > > > > > (it has no channel/freq command) and some drivers need this to happen. > > > > > But it should work with certain drivers that use a default adhoc > > > > > channel. > > > > > > > > In that case, how (shortly, before I delve into the source code) does > > > > the "Create New Wireless Network" option of nm-applet work? One would > > > > require root privileges to do this, and as nm-applet runs > > > > unprivileged, I figured it would use the NM daemon for it. > > > > > > Yes, it works unprivileged. Many drivers will use a default adhoc > > > channel, but the ipw2100/ipw2200 at least won't work without a channel > > > explicitly being set, which requires the wpa_supplicant changes. > > > > So how does this happen, when the GUI option is selected? > > It currently does not, and is an open bug that requires changes in > wpa_supplicant. This is a problem for me then... as I'm doing this as part of an academic project, I want this fixed - I certainly want to help fix it myself, I'm a bit familiar with wpa_supplicant. Where is the open bug for this? I could not find it in bugzilla. -- Protect your digital freedom and privacy, eliminate DRM, learn more at http://www.defectivebydesign.org/what_is_drm Ohad Lutzky ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Using a different WEP key index
Hello everyone. I'm running Ubuntu 7.04, and I have an Atheros based wi-fi card hence all the ath0-ing going on below. My situation is that the wireless network I need to connect to requires me to use the second key index. Here is how I've got it running on the command line: sudo ifconfig ath0 down sudo iwconfig ath0 essid sudo iwconfig ath0 ap sudo iwconfig ath0 key [2] sudo iwconfig ath0 key [2] sudo iwconfig ath0 key open sudo iwconfig ath0 key on sudo ifconfig ath0 up sudo dhclient ath0 ping www.google.com (pings are returned) The problems with this are: - it took me 3 hours to figure out - i don't know how to connect without first knowing the mac address of the AP i'm trying to connect to - probably the biggest problem, the connection drops after about 10 seconds unless I keep it alive by pinging somewhere What I need to be able to do: - Get network manager to accept a key for index 2 and then use it As you may have gathered, I'm stuck on this part. Both the Microsoft wi-fi manager and the custom Win32 wi-fi manager supplied with the PCMCIA card have the option to use either key 1, 2, 3 or 4. Network manager doesn't, or not that I can see, and means I don't know what to do. Is this possible to do with network manager at the moment? For preference I'd really like to get it working in NM but I'll settle for a way to keep it working for a usable period of time via the terminal. Thanks for any advice. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: VPN Interface Suggestion
> I think it would make sense to add a checkbox option titled "exclusive > connection" to each of the vpn configuration dialogs, with some sort of > tooltip stating "When established, this vpn connection will disconnect all > other vpn connections." Is this really required to disallow multiple connections? Isn't it possible to run multiple OpenVPN connections and multiple IPsec connections at the same time? If a VPN service does not support multiple connections (which one does not?), it should handle that on its own and signal changes to NM. I think replacing the radio buttons in the "VPN Connections" menu by checkboxes should be considered. So each individal connection can be brought up and down, independently. This seems very intuitive to me. As I have seen so far, the DBUS API needs some changes to support multiple connections. Currently only one active connection is allowed per DBUS service. Or did I miss the point? Martin ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
