Re: Personal experiences (so far) with .7
On 8/14/07, Steev Klimaszewski [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gentoo experiences (which, really, we need to update our backend... I will be working on this soon, I swear) Using r2682, wireless doesn't work at all, the devices show up, however things are greyed out. So it does see the devices. If I pop out a wireless card (I have about 8-10 cards here that I can test the various drivers out) I get the following filling up my log (even if I re-insert the card) Aug 14 15:10:57 sigma NetworkManager: nm_device_get_state: assertion `NM_IS_DEVICE (device)' failed Wired works like a champ though, so that is good, I am just puzzled by why the wireless is greyed out. Even if I don't have a wire plugged in when I start NM, only wireless, it sees the devices, but then nothing. Attempting to create a wireless network or connect to other wireless network also seems to do nothing. Wireless drivers/chipsets tested against: at76c503a (usb) rtl8180 (pcmcia) atheros (0.9.3.2) bcm43xx (in-kernel 2.6.22.3(or .4 whatever is latest) orinoco-sn (http://www.projectiwear.org/~plasmahh/orinoco.html) p54 (usb - in-kernel mac80211) bcm43xx (in-kernel mac80211 as well) ndiswrapper 1.48_rc1 (this is actually a Marvell 88w8335 [Libertas] card, however, pcmcia so not covered by inkernel libertas :( ) mini-pci orinoco card, as well as a mini-pci atheros card - inkernel for the mini-pci orinoco and 0.9.3.1 for the mini-pci atheros card. Any hints? You do have wpa_supplicant = 0.5.7 running as root with -u switch passed to enable dbus interface? Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Ad-hoc channel setting bug
On 8/15/07, Ohad Lutzky [EMAIL PROTECTED] wrote: Here's a bug I've reported under Ubuntu (I can't find a bugzilla in which to report it upstream): https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/112009 - I'm trying to use NetworkManager to create an ad-hoc network with my ipw2200. The following manual method works: sudo iwconfig eth1 essid mynetwork channel 11 mode ad-hoc (That is, the laptop next to me will then see the network) However, when trying to do that with NetworkManager's create wireless network, the laptop next to me will not see the network. Checking iwconfig shows that the essid and mode were set properly - but unfortunately, one can't tell using iwconfig whether a channel was set. However, running sudo iwconfig eth1 channel 11 aftwards fixes the problem. NM should do this automatically.- This bug still seems to be there... is any progress being made? Is there any upstream bugzilla I can report this to? -- Man is the only animal that laughs and weeps, for he is the only animal that is struck with the difference between what things are and what they ought to be. - William Hazlitt Ohad Lutzky ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list You can file NetworkManager upstream bugs here: http://bugzilla.gnome.org/browse.cgi?product=NetworkManager ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Ad-hoc channel setting bug
Here's a bug I've reported under Ubuntu (I can't find a bugzilla in which to report it upstream): https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/112009 - I'm trying to use NetworkManager to create an ad-hoc network with my ipw2200. The following manual method works: sudo iwconfig eth1 essid mynetwork channel 11 mode ad-hoc (That is, the laptop next to me will then see the network) However, when trying to do that with NetworkManager's create wireless network, the laptop next to me will not see the network. Checking iwconfig shows that the essid and mode were set properly - but unfortunately, one can't tell using iwconfig whether a channel was set. However, running sudo iwconfig eth1 channel 11 aftwards fixes the problem. NM should do this automatically. - This bug still seems to be there... is any progress being made? Is there any upstream bugzilla I can report this to? -- Man is the only animal that laughs and weeps, for he is the only animal that is struck with the difference between what things are and what they ought to be. - William Hazlitt Ohad Lutzky ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Newbie question: advice in adding a new feature to network manager...
Hi: I'm new to NetworkManager and have an interest in coding up a new feature into it. I think it would be great to have the ability to partition out adhoc networks from infrastructure networks in the available wireless network list. That way, if it happens to be the case that there is a lurking adhoc network called say foo and an infrastructure network called foo, the user can differentiate between the two and choose which one they want to associate with. Additionally, with that kind of segmentation, it would be nice to ONLY see adhoc networks or infrastructure networks in the list (as a configurable option). For a managed network environment, users may only be interested in seeing one kind of network at a given time. So, any advice on how I can quickly ramp up into the design aspects of NetworkManager? Any advice on where I would likely begin to experiment with changes? Thanks! Doug ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
