Problem with NM 1.0.12 with some Realtek drivers

[Larry Finger]

A number of users are reporting that systems that use NM 1.0.12 are unable to 
connect to USB devices running the Realtek out-of-kernel drivers. It appears 
that 
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=1.0.12&id=a3c0166a2064c41408d1e08defee3a7e4a0ce3f7 
is the commit causing the problem. If that information is correct, then devices 
with mode equal to NM_802_11_MODE_UNKNOWN are ignored.


Could someone please tell me the value of NM_802_11_MODE_UNKNOWN?

Thanks,

Larry

--
If I was stranded on an island and the only way to get off
the island was to make a pretty UI, I’d die there.

Linus Torvalds
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: WiFi interface disappeared

[Larry Finger]

On 09/14/2015 06:12 PM, Jim wrote:

Dan

On FC21, the dmesg | grep rtl returns nothing.

In contrast, I booted Ubuntu and ran the same commands, which clearly show an
8192 (see below).  Now how do I restore that device?

Thanks,
Jim

(From Ubuntu)
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM
Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset
Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family
USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High
Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI
Express Root Port 1 (rev b4)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI
Express Root Port 2 (rev b4)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI
Express Root Port 3 (rev b4)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI
Express Root Port 4 (rev b4)
00:1c.7 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI
Express Root Port 8 (rev b4)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family
USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller
(rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6
port SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus
Controller (rev 04)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411
PCI Express Gigabit Ethernet Controller (rev 06)
03:00.0 System peripheral: Ricoh Co Ltd MMC/SD Host Controller (rev 07)
08:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE
802.11b/g/n WiFi Adapter (rev 01)
Bus 002 Device 003: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1)
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 5986:03b3 Acer, Inc
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Module  Size  Used by
ctr13049  2
ccm17773  2
rfcomm 69160  8
bnep   19624  2
snd_hda_codec_hdmi 46368  1
snd_hda_codec_conexant57486 1
uvcvideo   80885 0
videobuf2_vmalloc  13216  1 uvcvideo
videobuf2_memops   13362  1 videobuf2_vmalloc
videobuf2_core 40664  1 uvcvideo
videodev  134688  2 uvcvideo,videobuf2_core
snd_hda_intel  56531  3
snd_hda_codec 193017  3
snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_intel
snd_hwdep  13602  1 snd_hda_codec
arc4   12608  2
intel_rapl 18773  0
x86_pkg_temp_thermal14205  0
intel_powerclamp   14705  0
coretemp   13435  0
snd_pcm   102099  3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
kvm_intel 143187  0
kvm   455843  1 kvm_intel
snd_page_alloc 18710  2 snd_pcm,snd_hda_intel
crct10dif_pclmul   14289  0
snd_seq_midi   13324  0
crc32_pclmul   13113  0
snd_seq_midi_event 14899  1 snd_seq_midi
ghash_clmulni_intel13216  0
cryptd 20359  1 ghash_clmulni_intel
joydev 17381  0
snd_rawmidi30144  1 snd_seq_midi
btusb  32412  0
serio_raw  13462  0
bluetooth 391136  22 bnep,btusb,rfcomm
snd_seq61560  2 snd_seq_midi_event,snd_seq_midi
thinkpad_acpi  81013  1
nvram  14411  1 thinkpad_acpi
rtl8192ce  53550  0
rtl_pci26690  1 rtl8192ce
rtlwifi63475  2 rtl_pci,rtl8192ce
rtl8192c_common53172  1 rtl8192ce
snd_seq_device 14497  3 snd_seq,snd_rawmidi,snd_seq_midi
mac80211  630728  3 rtl_pci,rtlwifi,rtl8192ce
snd_timer  29482  2 snd_pcm,snd_seq
snd69322  18
snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_seq_device,snd_seq_midi

cfg80211  484040  2 mac80211,rtlwifi
i915  788212  3
mac_hid13205  0
video  19476  1 i915
drm_kms_helper 55071  1 i915
drm   303102  4 i915,drm_kms_helper
mei_me 18627  0
lpc_ich21080  0
mei82276  1 mei_me
i2c_algo_bit   13413  1 i915
shpchp 37032  0
soundcore  12680  1 snd
pa

Re: network management settings fails for opensuse 13.1

[Larry Finger]

On 12/09/2013 11:12 AM, Dan Williams wrote:

On Mon, 2013-12-09 at 16:27 +0100, Nathan Manzi wrote:

I am new user of opensuse and i need a help on how to set up my wifi. I
have  delete my windows operating systemand then i have installed opensuse
13.1 on it. Installation went well but when it comes for the settings of
network manager. I have tried to use  yast for the settings but it says
that my network is controlled by network manager and i tried to set up but
i still have the problem interfaces is unavailable and i couldn't fix it.
My laptop is hp pavillion and it is intel centrino 2 inside. I really don't
know how to fix it.  I have run this command
*hwinfo -- short --wlan  *
I have found that i have  *Network: wlp2s0   Intel PRO/Wireless
5100 AGN [Shiloh] Network connection *
when running *uname -r  *i  got this   *3.11.6.4-desktop*

But i do not see my interfaces such as eth0 or eth1 which seems to be weird
for me .  When running *ifconfig -a*
i got these interfaces *enp3s0* , *lo *and* wlp2s0 *
  so i would like to have a help to fix this issues
Thanks for helping me .


Your network interfaces are not eth0 and eth1, but instead are enp3s0
(ethernet, pci bus 3, slot 0) and wlp2s0 (wireless, pci bus 2, slot 0).
The 'udev' program determines these names for you.  There are various
ways to get udev to use more "normal" device names, but those involve
editing configuration and are best asked on the udev  mailing lists
instead of NetworkManager's.

So back to NetworkManager; do you see any kind of network control applet
in your desktop?  It's usually in the top-right or bottom-right corners
on a toolbar, or in a status area along stuff like the volume control.
If you click that network control applet, what do you see?


Nathan,

Dan Williams is extremely knowledgeable about NetworkManager, but I don't think 
he is an openSUSE user. Another place to get help, and a place where openSUSE 
users are found, is at http://forums.opensuse.org/forum.php. You should create 
an account there, and post your question on the wireless forum.


I would give you some more help here, but I would need to know what desktop you 
are using (KDE, Gnome, ??). That makes a difference on how you set the NM 
parameters. The fact that you get a wireless device named wlp2s0 means that you 
are close.


Larry


___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: networkmanager can not enable wireless scanning

[Larry Finger]

On 09/27/2013 02:31 AM, LovelyLich wrote:

Hi Larry,

From your information , and I have googled this bug

report:https://bugs.launchpad.net/ubuntu/+source/linux/+bug/938630,
and I have tried `rmmod acer-wmi`, the nm's "enable wireless" button
now is not unchecked again( great !), but nm still cannot scan for
wireless ssid. sadly :(


At least there is progress. You may need to blacklist acer-wmi to keep it from 
ever loading.


Please run the commands

sudo iw dev wlan0 scan trigger
sudo iw dev wlan0 scan dump

What is the result? That will test manual scanning.

Larry


___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: networkmanager can not enable wireless scanning

[Larry Finger]

On 09/26/2013 09:38 PM, LovelyLich wrote:

2013/9/27 Dan Williams :

On Thu, 2013-09-26 at 15:09 +0800, LovelyLich wrote:

Thanks Larry for your help.
iwconfig shows a wireless device.
here is my output :


What is the "rfkill list" output if, as root, you run "rfkill unblock
wifi"?

Dan


Thanks Dan, the output is :
[root@localhost]/home/codedancer# rfkill unblock all
[root@localhost]/home/codedancer# rfkill list
0: acer-wireless: Wireless LAN
 Soft blocked: yes
 Hard blocked: no
1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
[root@localhost]/home/codedancer#


sorry i am not familiar with this aspect, so i can only do what you
tell me to do , and can not think more things.


Is your computer built by Acer? I think I remember a case where the module 
acer-wmi got loaded on a laptop built by a different manufacturer, and it caused 
exactly this kind of problem.


Larry


___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: networkmanager can not enable wireless scanning

[Larry Finger]

On 09/25/2013 09:28 PM, LovelyLich wrote:

Hi list,
When I click 'enable wireless', nm will automaticly uncheck the button
before 'enable wireless'.
Even if I try to boot with  ubuntu 13.04 livecd , it still cannot
enable wireless.
here is my laptop info from fedora:
lspci -v
03:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network
Adapter (rev 01)
 Subsystem: Lite-On Communications Inc Device 6627
 Flags: bus master, fast devsel, latency 0, IRQ 18
 Memory at f790 (64-bit, non-prefetchable) [size=512K]
 Expansion ROM at f798 [disabled] [size=64K]
 Capabilities: [40] Power Management version 2
 Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+
 Capabilities: [70] Express Endpoint, MSI 00
 Capabilities: [100] Advanced Error Reporting
 Capabilities: [140] Virtual Channel
 Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
 Kernel driver in use: ath9k

ethtool -i :
[root@localhost]/home/codedancer# ethtool -i wlp3s0
driver: ath9k
version: 3.9.5-301.fc19.x86_64
firmware-version: N/A
bus-info: :03:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
[root@localhost]/home/codedancer#

Please help me , thanks .
if you need more info, just let me know.


Two things that suppress wireless come to mind.

Does iwconfig show a wireless device? If not, you may be missing the necessary 
firmware. Check the output of dmesg to see if there are any messages regarding 
missing firmware.


Does "rfkill list" show anything blocked?

Larry


___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: how to export wpa_supplicant.conf from networkmanager

[Larry Finger]

On 06/20/2013 09:03 AM, Pavel Simerda wrote:

- Original Message -

From: "Wayne" 
To: networkmanager-list@gnome.org
Sent: Thursday, June 20, 2013 11:26:42 AM
Subject: how to export wpa_supplicant.conf from networkmanager

Hi! All,
Sorry to disturb.
I have a wili in office, the ubuntu can connect to it using networkmanger,
but my anroid phone can't.
The wpa_supplicant could be edited to enable the connection, but I don't know
how to write the configuration.

So my question is: could I export the wifi config from networkmanger to
wpa_supplicant format.
Networkmanager should know the correct config.



AFAIK you can just connect and search /run (and similar directories, depending 
on distribution) for the configuration file.


On my system, "ps ax" shows the following startup line for wpa_supplicant:

/usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f 
/var/log/wpa_supplicant.log


That indicates that the configuration file is 
/etc/wpa_supplicant/wpa_supplicant.conf. It may be different for your distro, 
but the starting line will tell you where it is.


Larry


___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Multiple WLAN Routers with same SSID

[Larry Finger]

On 09/21/2012 12:14 PM, Marius Kotsbak wrote:


On Sep 20, 2012 11:38 PM, "Petric Frank" mailto:pfr...@gmx.de>>
wrote:
 > In fact (here in Germany) german telecom delivered WLAN-routers which all 
have
 > preset the same (E)SSID. Shall i go to every household (even if i can locate
 > them) in my environment to tell them to change their SSID ?

That is bad (but it seems like Linksys routers are the same), but you should be
able to change the SSID of the AP you use.


As far as I know, all routers from a given manufacturer come from the factory 
with the same ESSID and the same router password. It certainly is true for 
Netgear and Linksys, As Marius says, you should change the ESSID, and it is very 
important to change the password. If you don't, you may find that someone else 
will lock you out of your AP/router, and you will need to learn where the reset 
button is located. The default ESSID is a clue that the password might not have 
been changed.


Larry


___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Ad hoc mode via Dbus

[Larry Finger]

On 09/18/2012 03:58 AM, ppulib...@libero.it wrote:


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


Set verbose logging on the DBus and establish the ad-hoc connection. You can 
then reverse engineer the connection from that log, or you can download the code 
for the applet and NM and see what they do.


Larry

___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: WLAN

[Larry Finger]

On 05/31/2012 05:31 AM, Daniel Ackwonu wrote:

Thank you for answering!

The Output of lspci -nn is:

daniel@linzuntu:~$ lspci -nn
00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1705]
00:01.0 VGA compatible controller [0300]: ATI Technologies Inc Device 
[1002:9647]
00:01.1 Audio device [0403]: ATI Technologies Inc Device [1002:1714]
00:02.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Device [1022:1707]
00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Device [1022:1709]
00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Device [1022:170a]
00:06.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Device [1022:170b]
00:10.0 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7812]
(rev 03)
00:10.1 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7812]
(rev 03)
00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] Device [1022:7804]
00:12.0 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7807]
(rev 11)
00:12.2 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7808]
(rev 11)
00:13.0 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7807]
(rev 11)
00:13.2 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7808]
(rev 11)
00:14.0 SMBus [0c05]: Advanced Micro Devices [AMD] Device [1022:780b] (rev 13)
00:14.1 IDE interface [0101]: Advanced Micro Devices [AMD] Device [1022:780c]
(rev 40)
00:14.2 Audio device [0403]: Advanced Micro Devices [AMD] Device [1022:780d]
(rev 01)
00:14.3 ISA bridge [0601]: Advanced Micro Devices [AMD] Device [1022:780e] (rev 
11)
00:14.4 PCI bridge [0604]: Advanced Micro Devices [AMD] Device [1022:780f] (rev 
40)
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1700] (rev
43)
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1701]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1702]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1703]
00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1704]
00:18.5 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1718]
00:18.6 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1716]
00:18.7 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1719]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Device 
[1002:6741]
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)
03:00.0 Network controller [0280]: RaLink Device [1814:5390]
04:00.0 Class [ff00]: Realtek Semiconductor Co., Ltd. Device [10ec:5209] (rev 
01)
04:00.1 SD Host controller [0805]: Realtek Semiconductor Co., Ltd. Device
[10ec:5209] (rev 01)


Two points of mailing list etiquette:

(1) ALWAYS use the "Reply All" button - NEVER drop any list or individual. If 
your mailer does not have that feature, get a new mailer. People like me do what 
we can to help, but only if our exchange of information is in the public record. 
If you want private consulting, you need to pay for it.


(2) Do not top post. By placing your reply at the bottom, everyone can read in 
natural order. With your reply at the top, one has to scroll down an up.


Your wireless device is the one described by:
> 03:00.0 Network controller [0280]: RaLink Device [1814:5390]

The appropriate driver for newer kernels is rt2800pci. As you did not provide 
any information regarding kernel or distro information, I have no idea if that 
driver is included in the configuration, or if your kernel is too old to have 
support for the 5390.


I suggest that you contact the mailing list for your distro and find out what it 
takes to support this device on their system. The latest versions of 
compat-wireless should work, but I have no idea if a precompiled version is 
available for your distro.


Larry
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: WLAN

[Larry Finger]

On 05/29/2012 04:18 AM, Daniel Ackwonu wrote:

Hello!

My name is Daniel and I am using Ubuntu on a new HP notebook. I have got the
problem that my Realtek Wlan card(RTL8111) is not recognized by my operating
system. I have tried a few things but it is still not working. If one of you
could help that would be great.
Thank you.

iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

vboxnet0 no wireless extensions.


The Realtek RTL8111 is a wired interface, not wireless. The output of the dmesg 
command should give you some indication of why the wireless device is not 
created. You are probably missing firmware.


If the above does not provide any clues, please post the output of 'lspci -nn'.

Larry

___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Funny behavior for NM and the KDE plasmoid

[Larry Finger]

I am running openSUSE 12.1 KDE using Rev 0.9.1.90-4.6.1-x86_64 ov 
NetworkManager, and version 0.9.1+0.9.0-1.6.1-x86_64 of the 
plasmoid-networkmanagement applet. For the most part, any problems that I see 
are the fault of the underlying wireless drivers; however, I do see one problem.


In general, the applet shows whatever APs that show up in a manually-triggered 
scan. There is, however, one exception. If I have the "Connect Automatically" 
box checked for one of the APs, that AP rarely shows in the possible 
connections. The one major exception is when the driver is unloaded, and then 
reloaded, when the connection is started nearly instantly. I have not tested the 
nm-applet to see if it shows the same behavior.


Are there any steps that I can take to help show where the problem happens?

Thanks,

Larry
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Fedora16 - Brain dead wireless network manager

[Larry Finger]

On 01/17/2012 08:29 AM, Robert Moskowitz wrote:

On 01/17/2012 08:38 AM, Dan Winship wrote:

On 01/17/2012 08:14 AM, Robert Moskowitz wrote:

Oh, this is on a Lenovo x120e where I see the following in the log
messages:

Jan 16 22:16:42 lx120e kernel: [81433.007709] rtl8192c_common: Loading
firmware file rtlwifi/rtl8192cfw.bin

The driver for that chipset is apparently broken in the current kernel:
https://bugzilla.redhat.com/show_bug.cgi?id=729618

(There are links to various testing kernels with different patches in
that bug, but it's hard to tell from the comments if they fix the
problem...)


Now why does that not supprise me? I did notice one update to the driver a while
back. And I have 'real work' (spec writing!) to do to test f17...

But it does not address the removal of information from the UI nor the control
over SSID selection/control.


That Fedora bug report has nothing to do with this problem - that bug was mostly 
due to placing the firmware loading message in the wrong place.


Larry
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Please add SAE support for WiFi

[Larry Finger]

On 12/16/2011 12:29 PM, Robert Moskowitz wrote:

On 12/16/2011 01:06 PM, Larry Finger wrote:

On 12/16/2011 11:43 AM, Robert Moskowitz wrote:


I sent this message also to the Fedora test list. That is the closest list I am
on to the developers.

I am right now in the need of a new AP, so I am searching for one that I can
afford that will be able to get SAE support.


You should send your request to linux-wirel...@vger.kernel.org. That is where
most of the developers of the IEEE80211 MAC layer, the supplicant, and the
device drivers can be found.


Thanks. I sent a subscribe for the list, and a search of the archives found:

http://marc.info/?l=linux-wireless&m=130145440930760&w=2

Which seems to show SAE support in user space. So I wonder if it is in my f16
install?



When SAE support is available in Linux, you would be able to implement it in
nearly every router that runs openWRT. Only those units with very limited
memory would be excluded. As openWRT-capable APs are mostly consumer grade,
they should be affordable.


And f16 with gnome 3.2 as well


That set of patches were accepted into the wireless-testing tree on April 7, 
2011, and should be in any 3.1 or later kernel. I think you should have it in 
f16. I have no idea where to get the userspace tools.


If your wireless device supports AP mode (not all do), then you could use your 
laptop as an AP.


Larry
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Please add SAE support for WiFi

[Larry Finger]

On 12/16/2011 11:43 AM, Robert Moskowitz wrote:


I sent this message also to the Fedora test list. That is the closest list I am
on to the developers.

I am right now in the need of a new AP, so I am searching for one that I can
afford that will be able to get SAE support.


You should send your request to linux-wirel...@vger.kernel.org. That is where 
most of the developers of the IEEE80211 MAC layer, the supplicant, and the 
device drivers can be found.


When SAE support is available in Linux, you would be able to implement it in 
nearly every router that runs openWRT. Only those units with very limited memory 
would be excluded. As openWRT-capable APs are mostly consumer grade, they should 
be affordable.


Larry
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Getting device 0fe6:9700 Kontron to work with NM

[Larry Finger]

On 12/02/2011 12:51 PM, Dan Williams wrote:

On Fri, 2011-12-02 at 13:27 +0200, Perazim wrote:

Update: Turns out that this device was repacked by manufacturer without
documenting NIC chip change. The correct driver is qf9700 which is not
in the standard kernel and I found the source for on the internet and
built against my kernel. Once done and installed in modules, I can
modprobe this and device is brought up and NM recognizes it.

Now I need to figure out how to get this to happen automatically when
the device is plugged.


It's a kernel problem.  If it's the same USB ID as the old device with
the old chip, then you'll need to talk to various kernel mailing lists
(linux-usb probably, or netdev) to see how to figure this out.  The
problem is that drivers mostly use USB IDs for autoloading, and if this
device has the same USB IDs then it'll conflict with the old driver.
You can't just add the same USB ID to two different drivers, there's
more coordination that needs to happen.  Unfortunately I don't know what
the coordination is off the top of my head :(


The general fix for this kind of thing is to find some value in the device 
configuration registers that is different for the two devices, and return driver 
load failure when the wrong one is found. An example is found for PCI ID 
0x10ec:0x8192, which occurs for both RTL8192SE and RTL8192E devices. In this 
case, drivers rtl8192se and r8192e read the PCI revision. If the value is 1, 
then rtl8192xe returns the invalid device code, while r8192e returns the invalid 
code when the revision is 0x10.


For your device, you would need to find some value in the USB configuration that 
differs, and do the same kind of logic. Both drivers will be loaded, but only 
the "right" one will be active.


Larry


___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NM vs broadcom on planet Ubuntu 10.10

[Larry Finger]

On 09/01/2011 12:51 PM, Mauricio Tavares wrote:

   I have here a laptop (hp pavilion dv6700 ) with ubuntu 10.10 and
a broadcom (bcm 94312 LP-PHY) wireless card using the non-free drivers
(tried both the  b43 and the SPA(?) one). When I try to connect to a
WPA2/AES router, I can enter my password and it will be trying to
connect for about a minute and then go back to asking for the password
again. But, if I replace network-manager with wicd, I have no problem
connecting. Why would NM not like this setup?


Have you checked the dmesg output? The kernel in 10.10 may not have all the 
improvements in b43 needed to operate your BCM4312. Upgrading to the 
compat-wireless package should fix that.


___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Question about

[Larry Finger]

On 03/13/2011 11:22 AM, José Queiroz wrote:

Hi Larry,

Are you using a Dell laptop? A recent kernel change broke the WMI support to
some dell hardware. If it's your case, try blacklisting dell-laptop modules and
reseting your machine.


No, this is an HP. I am not loading any wmi modules.

One more piece of info. As I said earlier, switching from knetworkmanager to the 
plasmoid allowed it to work. I then switched back to knetworkmanager (I like it 
better), and wireless still worked.


Larry

___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Question about

[Larry Finger]

I am running openSUSE 11.4 with NetworkManager 0.8.2 and knetworkmanager 0.9. 
Usually everything works fine, but under some circumstances that are not 
understood, wireless is disabled. It is not blocked by a radio-kill switch, as 
'rfkill list' shows


0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

Similarly, I see no reason for the block in /var/log/NetworkManager. For 
completeness, 'nmcli nm' shows


RUNNING  STATE   WIFI-HARDWARE   WIFI   WWAN-HARDWARE   WWAN
running  disconnectedenabled disabled   enabled enabled

Are there any other commands that might tell me where the problem is occurring? 
Switching from knetworkmanager to the plasmoid networkmanager package clears the 
problem, but I would like to understand the problem.


Thanks,

Larry
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Network Manager reason codes

[Larry Finger]

On 03/07/2011 02:33 PM, Kai Sommer wrote:


OT:
Can someone recommend a well (Linux) functional USB WLAN stick/chip!?


Devices containing the Realtek RTL8187L or RTL8187B chips work out-of-the-box 
and do not need external firmware. My TL8187L is a Netgear WG111V2. You might 
not find any new ones, but Ebay usually has some available.


Larry
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NM disconnect after one hour with a wired network

[Larry Finger]

On 01/09/2011 05:15 AM, Charles Cultien wrote:
> Hi,
> I have a very strange problem :
> I'm connected with the wired network of my university and each time,
> after one hour, Network Manager disconnect himself and didn't reconnect
> automatically. So I have to reconnect by myself evry hour and this is
> boring !
> 
> I don't know why and how change this. A dmesg didn't show anything (on
> the moment it disconnect).
> 
> I'm using LInux Mint DEbian (so debian testing) with :
> Linux kernel 2.6.32-5-686
> GNOME 2.30.2
> Network Manager 0.8.1
> I'am am behind a proxy (automatically given by the script
> htpp://proxyconf) and so the gnome proxy is configured.
> 
> Thank you for helping and didn't hesitate asking for trying something or
> given more information.

Does the listing produced by running 'iw event -t -f' show anything at the time
of disconnect?

Larry
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Help with wireless device

[Larry Finger]

Hi,

One of the people I'm trying to help on the openSUSE Forum has a problem in that
the KDE applet always has wireless networking disabled. Once it is enabled
manually, then the wireless comes up as expected.

In /var/log/NetworkManager, the following is reported:

  Dec 31 14:54:59 linux-ioxs NetworkManager:   (wlan0): bringing up 
device.
  Dec 31 14:54:59 linux-ioxs NetworkManager:   (wlan0): deactivating
device (reason: 2).
  Dec 31 14:54:59 linux-ioxs NetworkManager:   modem-manager is now 
available
  Dec 31 14:54:59 linux-ioxs NetworkManager:   default_adapter_cb(): bluez
error getting default adapter: The name org.bluez was not provided by any
.service files
  Dec 31 14:54:59 linux-ioxs NetworkManager:   Trying to start the
supplicant...
  Dec 31 14:54:59 linux-ioxs NetworkManager:   (wlan0): supplicant manager
state:  down -> idle
  Dec 31 14:54:59 linux-ioxs nm-dispatcher.action: Script
'/etc/NetworkManager/dispatcher.d/netcontrol_services' exited with error status 
127.

Why is wlan0 deactivated with reason 2?

What should we be checking? AFAICT, everything in the Connection Manager is 
correct.

Thanks,

Larry
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: BCM4312/b43 acts weird with NetworkManager and F13

[Larry Finger]

On 08/07/2010 08:32 AM, Ville-Pekka Vainio wrote:
> I decided to test the Broadcom proprietary driver and it has the same
> problem as b43, I still need to click "Enable Wireless" before NM shows
> any wifi networks. I think that's unnecessary, the wireless could just
> be enabled by default.

As I suspected, it is not a b43 problem.
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: howto ignore rfkill switch

[Larry Finger]

On 08/06/2010 12:51 AM, Dana Goyette wrote:
> 
> My Samsung laptop's rfkill switch, on the other hand, is entirely
> software.  If I unload the samsung-laptop module with the wifi card set
> to "kill", the wifi card can at least receive.  I'm not sure about
> sending, since r8192pci mostly fails.

The staging drivers for the 8192 know nothing about the rfkill subsystem, thus
this point is moot.

Larry
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: howto ignore rfkill switch

[Larry Finger]

On 04/26/2010 11:32 AM, Jim Cromie wrote:
> On Thu, Apr 22, 2010 at 9:44 AM, Dan Williams  wrote:
>> On Wed, 2010-04-21 at 18:49 -0600, Jim Cromie wrote:
> 
>>> 1 - with only built-in wifi card, I get a blank list.
> 
>>> 2 - once I plug in the pcmcia and usb cards, theyre both unblocked,
>>> but the builtin (ipw2200) is still missing.
> 
>>> Blocking and unblocking alters the displayed state (as above)
>>> but NM-applet says that all 3 are disabled.
>>
>> Yes, for a number of reasons.  First, we can't usually figure out which
>> killswitch is for which wifi device.  It's often just not possible, plus
>> "platform" killswitches provided by your laptop BIOS aren't tied to a
>> specific wifi device.  Second, you're probably better off blacklisting
>> the internal wifi driver modules so they simply don't load in the first
>> place.  Add the names (libipw, ipw2200) to
>> to /etc/modprobe.d/blacklist.conf to do this.
>>
>> If you rmmod ipw2200, what happens?
> 
> 
> Interesting. At 1st, I failed to see this as responsive;
> how could removing a driver enable others ?
> but I tried anyway, and lo-and-behold:
> 
> with ipw2200 rmmod'd, I can now enable the pcmcia card
> (which didnt work before), after a few tries, it connected !!
> It held for several minutes, then dropped, and wont reconnect,
> but that appears to be something else
> So laptop is usable (w/o a leash) again, thanks!
> 
> so, what happened ?  Is this a teachable moment ?

This is expected behavior. My box has a PCIe card that usually contains
one of the Broadcom flavors. If I turn off the switch, that will disable
any of my USB cards unless I unload b43, which also unloads its copy of
rfkill. Even though the b43 driver is not active on the air, its
feedback through rfkill is still active.

> 1- I re-modprobed ipw2200, and NM promptly killed the
> pcmcia card's connection, and shows both wifis as disabled.

As described above, that is predictable.

> 2- rmmod again removes both cards from NM-applets
> available wifi-interfaces list, but ejecting and reinserting pcmcia
> card reconnects.
> 
> 3- doing this also increments phy#, Im now on phy3
> (this isnt surprising/noteworthy really)

Each invocation is a new instance for mac80211 and is expected. When
testing, I sometimes get to 3 digit phy#.

> 
> Im also a bit unclear on soft/hard/platform distinctions,
> perhaps others are too.
> 
> 1- my kill switch affects plugin devices, so it cant be a hardware kill 
> switch;
> hardware kills are directly connected to internal devices, and theres
> no such pcb-trace that crosses the USB plug  ( there *could* be in the
> pcmcia connector, but that too seems unlikely )
> Or do I read 'hardware' too literally ?

Once any hardware switch kills the radio, it kills it for ALL devices.
That is for safety and compliance with regulations. There is no physical
connection to the USB. The interaction is through the rfkill software.
It is a hard block because some hardware device is blocking.

> 2- the rfkill-LED is hard-wired to switch.
> I cant prove this though; since I cant toggle the switch,
> "udevadm monitor" cant see events that dont happen.

That depends on the device. On my box, b43 controls the LED. If b43 is
unloaded, the LED is always off; however, USB devices are not blocked,
even if the switch is off. Only if b43 is loaded does the switch
block/unblock.

> 3- why doesnt "rfkill list all" show the internal wifi device ?
> Is there a way for it to read and report a platform rfkill ?
> (presumably just once)

Pass on this one.

> 4- rfkill module is used by sony_laptop module,
> does this make my kill switch a 'platform kill' ?

Ditto.

Larry
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: network manager install help please

[Larry Finger]

On 03/16/2010 04:51 PM, Ken Taylor wrote:
> Hi Guys
> 
> I have a Suse distro
> 
> How do I install the network manager?
> 
> I have it downloaded, but can't work out how to install it
> 
> Any help really appreciated as my little lenovo S10e has lost it's
> ability to connect to a wifi network and Lenovo Support are clueless

If it is openSUSE 11.1 or 11.2, it is built in. For earlier releases, you would
have to build from source. What did you download?
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: "/etc/init.d/NetworkManager quit" ?

[Larry Finger]

On 02/27/2010 11:05 AM, Graham Lyon wrote:
> The point you're missing here is that network manager solves a very real
> problem with links going down after boot time and not automatically
> coming back up when they're available again (Read as: laptop users). A
> daemon was necessary to fix this and nothing like it had been done
> before. The design, therefore, is not perfect and so regressions are
> inevitable. This does not mean, however, the the init scripts were
> better - they just had 15 years or so to mature ;)
> 
> On 27 February 2010 14:47, Dominik George  > wrote:
> 
> 
> > For use on servers: because it means that you only have to learn
> one tool.
> > Also, why not? ;)
> >
> This, dear fellow user, I will not discuss publicly, as I would probably
> be banned from the list ;).
> 
> In short: NetworkManager is all in all a single pain in the a . Both
> on Desktops *and* on servers.
> 
> So why not stick to traditional runlevel control when t is known to work
> better?

If you move around and connect to multiple AP's, traditional runlevel control is
a PITA. With NM, you can create the new connection with the GUI. If it already
exists, a single click brings it up. For systems with only wired connections, I
don't use it, but if it has wireless, it is very useful.

Larry

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: realtek 8172 does not work with networkmanager and wpa on ubuntu 9.10

[Larry Finger]

On 02/11/2010 04:02 PM, vincent guffens wrote:
> Dear list,
> 
> I have recently bought a thinkpad edge 64 bits with a realtek 8192.
> 
> lspci reports
> Network controller: Realtek Semiconductor Co., Ltd. Device 8172 (rev 10)
> 
> I have installed ubuntu 9.10 amd64 but Linux does not come with the
> driver for this card. The driver is available from
> 
> http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=48&Level=5&Conn=4&ProdID=226&DownTypeID=3&GetDown=false&Downloads=true#2281
> 
> The driver compiles without problem but I can not connect to my access
> point when network manager is running. If I disable it, I can manually
> connect to the access point using the  following wpa.conf

The Realtek vendor drivers can be a major problem. From what I see in your
wpa_supplicant log, it never got any scan data, which is why NM also failed.
What do you see when you run (as root)

iwlist scan

You should also post the dmesg output that pertains to this device.

Larry

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Problem with changing encryption for established connection

[Larry Finger]

On 10/24/2009 04:15 AM, Will Stephenson wrote:
> On Saturday 24 October 2009 00:53:16 Dan Williams wrote:
>> On Thu, 2009-10-22 at 10:45 -0500, Larry Finger wrote:
>>> I am using NetworkManager version 0.7.1 and kNM version 0.9. While
>>> testing openSUSE 11.2 RC1, I did the unusual step of changing the
>>> encryption scheme for a previously established ESSID/connection. As
>>> expected, when I clicked on the entry in the kNM applet to connect, I
>>> got the authentication/secrets pop-up. Supplying the new, correct
>>> password and authentication scheme failed. I could connect only by
>>> using the "Manage Connections" item from the applet and by editing the
>>> wireless connection item before trying to connect.
>>>
>>> Is this expected behavior?
>>
>> It might be the case that the AP's old encryption settings were still in
>> the scan list; How long was the AP powered off before it came back up
>> with the new settings?  Can you reproduce the situation and run
>> 'nm-tool' to check what NM thinks the AP's settings are and make sure
>> that NM reflects what they really are?  If not, it's likely a stale
>> entry in NM's scan cache.
>>
>> I'd expect to see the passphrase dialog if you change the passphrase on
>> the AP and not the security settings; if you switch between WEP and WPA
>> for example then you might also see that dialog, but NM might also be a
>> bit confused.
> 
> Agreed, but Larry might also have mis-entered the encryption type on first 
> creating the connection and be trying to edit it in the GetSecrets popup.  I 
> show the whole settings group's UI on GetSecrets because I haven't got round 
> to making a minimal secrets-only UI yet, and I doubt NM is equipped to handle 
> the non-secret parts of 802-11-wireless changing at that point.

I think changing the type after the connection was created would match
the situation you describe, and that is what happened. The original
connection was WPA2, then I used a wired connection to modify the
encryption in the AP. Next I tried to connect using that same
connection. A similar switch was later made to WEP, and finally to no
encryption. As I recall, the problem happened in the WPA2 => WPA
switch, but I'm not completely certain of that. Once I found that I
needed to edit the connection, I did that for the rest of the testing.

As this kind of type changing using the same ESSID is not usual
behavior, I have not filed a bug report, just this question on the ML.

Larry
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Problem with changing encryption for established connection

[Larry Finger]

I am using NetworkManager version 0.7.1 and kNM version 0.9. While
testing openSUSE 11.2 RC1, I did the unusual step of changing the
encryption scheme for a previously established ESSID/connection. As
expected, when I clicked on the entry in the kNM applet to connect, I
got the authentication/secrets pop-up. Supplying the new, correct
password and authentication scheme failed. I could connect only by
using the "Manage Connections" item from the applet and by editing the
wireless connection item before trying to connect.

Is this expected behavior?

Thanks,

Larry
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Phantom wireless device

[Larry Finger]

Rick Jones wrote:
> --On Thursday, August 20, 2009 12:20:35 -0400 John Mahoney
>  wrote:
> 
>> Ubuntu just pushed new kernels. Did you just pick one up. I got the
> message two days ago, but have not *rushed* into grabbing them. Maybe a
> regression?
> 
> I'm not using those kernels, I run a version of 2.6.29 slightly tweaked
> for the Eee. I've been running the same kernel for months so nothing's
> changed in that respect.

What do you have in /etc/udev/rules.d/70-persistent-net.rules?

What does the command iwconfig show?

I'm wondering if your rename rules are tripping over the master
device. FWI, the master0 wireless device will disappear in 2.6.32.


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: howto ignore rfkill switch

[Larry Finger]

Helen Gray wrote:
> Hi,
> 
> I have a laptop with a dodgy rfkill switch. It switches on and off
> randomly when touch the laptop panel above it. To avoid the problem,
> I've installed a PCMCIA card but network manager shut it down when the
> switch goes off.
> 
> Is there a way to ask network manager to ignore the rfkill switch?

What driver is used by the internal card? On my system, I have an
internal BCM4311 that uses b43, and I also use several USB cards for
testing. Before the latest rewrite of rfkill, I was able to switch off
the BCM4311 without affecting the USB sticks. Now I have to unload
b43, otherwise all radios are killed. Once b43 is unloaded, the
position of the rfkill switch is irrelevant.

If you do not wish to use the internal device at all, you should
blacklist that driver.

Larry
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: How to connect to a WPA network that uses 10 hexadecimal digits as password

[Larry Finger]

Jaap A. Haitsma wrote:
> 
> iwlist scan gives the following output
> 
> wlan0 Scan completed :
>   Cell 01 - Address: 00:1F:41:0F:FE:59
> ESSID:"STI WiFi"
> Mode:Master
> Channel:11
> Frequency:2.462 GHz (Channel 11)
> Quality=100/100  Signal level:-37 dBm  Noise level=-94 dBm
> Encryption key:on
> IE: WPA Version 1
> Group Cipher : TKIP
> Pairwise Ciphers (1) : TKIP
> Authentication Suites (1) : PSK
> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
>   9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
>   48 Mb/s; 54 Mb/s
> Extra:tsf=006526c04184
> Extra: Last beacon: 88ms ago
> 
> 
> Instructions of the hotel are the following
> 
> SSID: STI WiFi
> key: a531bc531d
> PC: Network Key
> MAC: WPA 10 digits
> 
> On windows it works right away when I enter a531bc531d as key.

It should work the same way with Linux with that 10 character string as the
shared key.

Has your system worked elsewhere with WPA1? In particular, is wpa_supplicant
installed on your system?

Does /var/log/NetworkManager yield any relevant info?

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: How to connect to a WPA network that uses 10 hexadecimal digits as password

[Larry Finger]

Jaap A. Haitsma wrote:
> On Wed, Apr 8, 2009 at 03:07, Aaron Konstam  wrote:
>> On Wed, 2009-04-08 at 08:06 +0200, Jaap A. Haitsma wrote:
>>> Hi,
>>>
>>> I'm in a hotel currently and the wifi uses WPA encryption and password
>>> is a 10 digit hexadecimal number. When I use this number in Windows it
>>> works fine. However if I use NetworkManager it doesn't. If I look at
>>> the password that's actually being stored by NetworkManager I a
>>> hexadecimal number that is much larger. I'm assuming that's the hash
>>> of the password I'm entering. However I think in this case it should
>>> not take the hash but use the 10 digit hexadecimal number directly.
>>>
>>> Is this possible in NetworkManager?
>>> Are my assumptions correct? (I've never seen this WPA with a 10digit
>>> hexadecimal password before)
>>>
>>> Thanks
>>>
>>> Jaap
>> Yes it is possible. Are you sure you are entering it as a hex numver not
>> aas a passphrase ot Asci string. Is the stored passwd filled with ascii
>> number representations which would make it longer.
> 
> I'm not entering the it as a hex numver, because I don't know how to
> do this. I don't see an option for that. I've just tried prefixing the
> hex password with with 0x, but that also does not work

Please post the output of 'iwlist scan'. That should indicate what style of
encryption is being used.

To answer your first question, if a 10 character phrase consisting of 0-9 and
A-F were used as the WPA "secret", it would not be special and would be
converted to a 32-digit hex key just like any other phrase.

Larry
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Problem with Script to restart NetworkManager

[Larry Finger]

Felipe Ferreira wrote:
> *Problem:*
> My script to reload NetworkManager (if internet conection is lost) fails
> because it cannot get the "GetSecrets" even if I run crontab even as root.
> 
> CRONTAB:
> #*/5 * * * * /home/felix/Scripts/testnet.sh
> 
> testnet.sh:
> #!/bin/bash
> #Script to test internet connection and restart Network Manager if it fails.
> /*ping -c 2 -w 3 google.com || /etc/init.d/NetworkManager restart*/
> 
> 
> *Error Msg:*
> Mar 24 20:55:10 SYSMENGO NetworkManager: /  get_secrets_cb():
> Couldn't get connection secrets: A security policy in place prevents
> this sender from sending this message to this recipient, see message bus
> configuration file (rejected message had interface
> "org.freedesktop.NetworkManagerSettings.Connection.Secrets" member
> "GetSecrets" error name "(unset)" destination
> "org.freedesktop.NetworkManagerUserSettings"). /
> 
> Related Bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=487722
> 
> Automatic Keyring, is that the solution? how can it be done?
> Is there another way to do this?

This bug is likely due to the changes in Dbus security associated with
CVE-2009-0578. Another discussion of it can be found at
https://bugzilla.novell.com/show_bug.cgi?id=486267.

Some systems are fixed by deleting an extraneous directory
/var/run/dbus/at_console/root. Others need changing of the "at_console" rules.
If you do not have the extra directory or deleting it doesn't help, try the
patches for /etc/dbus-1/system.d/nm-applet.conf or
/etc/dbus-1/system.d/knetmamager.conf.

Larry

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Permissions problem in Dbus/NetworkManager

[Larry Finger]

Recently openSUSE issued an update for 11.1 to correct the Dbus security
problems descriBed in CVE-2009-0578. After this was done, I could no longer
connect using wifi encryption.

The NetworkManager log shows the following:

Mar 17 16:06:01 larrylap NetworkManager:   Activation (wlan2/wireless):
access point 'lwfdjf_rad' has security, but secrets are required.
Mar 17 16:06:01 larrylap NetworkManager:   (wlan2): device state change:
5 -> 6
Mar 17 16:06:01 larrylap NetworkManager:   Activation (wlan2) Stage 2 of
5 (Device Configure) complete.
Mar 17 16:06:01 larrylap NetworkManager:   get_secrets_cb(): Couldn't get
connection secrets: A security policy in place prevents this sender from sending
this message to this recipient, see message bus configuration file (rejected
message had interface 
"org.freedesktop.NetworkManagerSettings.Connection.Secrets"
member "GetSecrets" error name "(unset)" destination
"org.freedesktop.NetworkManagerUserSettings").

The problem seemed to be random. One reporter had two x86 systems that appeared
to be identical - one worked and one did not.

After going through the usual checks to make sure the contents of
/etc/dbus-1/system.d were correct, one of the openSUSE people discovered that
/var/run/dbus/at_console contained both a directory for the unprivileged user,
and an extra empty directory for root. As soon as the directory for root was
deleted, everything worked as expected. Testing was done with the following 
command:

dbus-send --system --print-reply \
--dest=org.freedesktop.NetworkManagerUserSettings \
/org/freedesktop/NetworkManagerSettings/Connection/0 \
org.freedesktop.NetworkManagerSettings.Connection.Secrets.GetSecrets

This command returned an error when called as an unprivileged user, and the
expected result when used as root. Before the extraneous directory was deleted,
all users failed.

This problem was covered in the openSUSE Bugzilla #486267. I posted it here for
those openSUSE users that might not be perusing the bug list, and just in case
users of another distro might be affected.

Larry

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Help on wireless network connectivity

[Larry Finger]

Ravi wrote:

Hi,
 
I have installed fedora 9 on my laptop recently and I wanted to enable 
WiFi using Network manager.

Lan interface : Broadcom 802.11a/b/g WLAN
 
Please help me how can I get this done.


Please tell us more. From a terminal, issue the command '/sbin/lspci 
-nnv', find the first two lines of the output that describe your 
wireless, and post them. Note: I'm not certain that lspci is in /sbin. 
If you get a "command not found", become root and issue the command 
'lspci -nnv'.


Second, issue the command 'dmesg | grep b43' and post the results.

Larry

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Wireless requires roaming to be turned off and back on before connecting

[Larry Finger]

Dan Williams wrote:


AFAIK you can't actually run that command at all unless you're root,
since it has the potential to interrupt traffic either way.


From the man page for iwlist:

   scan[ning]
  Give  the  list  of  Access  Points and Ad-Hoc cells in range, 
and optionally a whole bunch of information about them (ESSID, Quality, 
Frequency, Mode...). The type of information returned depends on what the card 
supports.
  Triggering  scanning  is  a privileged operation (root only) and 
normal users can only read left-over scan results. By default, the way scanning 
is done (the scope of the scan) is dependant on the card and card 
settings.
  This command takes optional arguments, however most drivers will 
ignore those. The option essid is used to specify a scan on a specific ESSID so 
you will also see hidden networks with that name in addition to the 
  regular scan results.  The option last does not trigger a scan and reads 
left-over scan results.


This is the way that openSUSE works. I would not expect it to be different in 
other distros.


Larry

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Wireless requires roaming to be turned off and back on before connecting

[Larry Finger]

Paul Burne wrote:

If I open terminal and type 'iwlist wlan0 scan', I get, 'wlan0 No scan
results'.


Is this done as root, which does an active scan, or as an ordinary user, which 
does a passive scan?


Larry

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Network troubleshooting in 8.04

[Larry Finger]

mohamed abu amna wrote:
> I have a new Dell inspiron 1525 NB with vista preinstallation. I have 
> installed Ubuntu 8.04 and failed completely to connect to the wireless 
> network, where as this goes smoothly in Vista.. Opening the 
> administrator and then the network does not offer the option of wireless 
> networking.
> the network manager demands a */name/* and */bssids/* in the properties 
> window.
> Please I am new to this field, please help.
> Which name should I supply?
> What is bssids?
> Thanks in advance

What device does your wireless use? You can see that from 'lspci -nvv'. Post 
only the part that describes your wireless. In addition, check the output of 
the dmesg command to see what it has to say.

Larry
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NetworkManager should report killswitch state per device

[Larry Finger]

Fanen A. wrote:
> Is it possible that a situation may arise when both cards use the same 
> driver? :p
> 
> My two cents: its better if the kill switch for one device doesn't 
> affect another device (in the case of the mini-pci wireless, and the 
> pcmcia wireless cards). If its at all possible to allow the 'default' 
> behaviour of the switch killing both wlan, and bt, and wifi for the 
> (usually) onboard device, but sparing the addon card, this would be ok 
> for most folks IMHO.

I'm not sure what happens with other drivers, but for b43, the kill switch 
has absolutely no effect on a PCMCIA card. Only the mini-pci and mini-pcie 
cards have any hardware to switch off the radio signal. This makes sense as 
the user has no possibility of removing the interface. That said, downing the 
interface will turn off the radio no matter what interface is used.

Larry
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NetworkManager should report killswitch state per device

[Larry Finger]

Aaron Konstam wrote:
> I have to ask. How do you blacklist a driver?
>  ===
> We have phasers, I vote we blast 'em! -- Bailey, "The Corbomite
> Maneuver", stardate 1514.2
> ===

File /etc/modprobe.d/blacklist contains a list of modules that will not be 
loaded by modprobe via modalias. It should keep the driver for the wireless 
device in question from being loaded at boot time.

Larry

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NetworkManager should report killswitch state per device

[Larry Finger]

[EMAIL PROTECTED] wrote:
> On Thu, Apr 24, 2008 at 01:24:33PM -0400, Dan Williams wrote:
>> Expected behavior.  If you don't want to kill any wireless, don't flip
>> the switch.  I don't see real use-cases where you'd want to rfkill one
>> card but not others;
> 
> Here's a real use-case: on my wife's laptop, the integrated wifi is
> misfunctionning. (It sees network but can only intermitently connect to
> them. It just happened one day, I am sure it is an hardware problem on
> this four year old computer.) We bought an USB dongle to have a reliable
> wifi. It would be nice to stop the integrated card in order to save
> battery time.
> 
> That was a real case, I can imagine other cases where the integrated
> device doesn't have the good protocols (maybe it doesn't do g or n wifi
> networks), doesn't have the correct range, doesn't have the correct MAC
> address to be accepted by the router, and where one would like to use an
> external wifi card without the first one sucking power.
> 
> Well, anyway, it sure is'nt a priority...

Why not blacklist the driver for the defunct device?

Larry

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Invalid bug report previously, raises usability question.

[Larry Finger]

Stefán Freyr Stefánsson wrote:
> Hi again.
> 
> It seems that my previous bug report was invalid. I have already closed the 
> bug and added a comment explaining it.
> 
> I had missed one combination when trying to connect to the wireless network, 
> namely selecting "Open System" and "WEP Passphrase". Using that combination 
> brought up the wireless network without a hitch.
> 
> But this mess of mine raises a question of why the UI has to be this 
> complicated (I know, I know... most of you are probably thinking that it 
> isn't and you're probably right... but let's say for arguments sake that I'm 
> the typical idio... I mean user). Maybe it really is necessary, I am not 
> anywhere close to being any sort of an expert on wireless networks (as is 
> clearly evident from my screwup before).
> 
> But just bear with me here (and this may be a discussion that has already 
> come 
> up and been settled, apologies if that's the case).
> 
> 1) Why does a user have to select between HEX and ASCII? It isn't difficult 
> at 
> all to take the string that is entered, check how many characters it has and 
> whether there are any non-hex characters and tell from that what kind it is.
> 
> 2) Passphrase may be a little more difficult to "autodetect"... I'm not quite 
> sure how exactly that works anyways so I shouldn't really say anything here. 
> Is there anyone who sees a way of eliminating that choice as well? Of course, 
> one way would be to say that if it's not an ASCII or a HEX key, then it 
> probably is a passphrase, and if it looks like an ASCII or HEX key but 
> doesn't work as such, then try it as a passphrase? I don't know... just an 
> idea.
> 
> 3) Open System vs. Shared Key? I have no idea what the difference between the 
> two is!? Is there no way to autodetect this? Would a brute-force way (trying 
> one and then the other) be possible here?

The main reason for having to choose between passphrase and HEX with 
WEP is that there are at least two ways of converting between a 
passphrase and a hex key. If your computer doesn't use the same method 
as your AP, then there is no chance that you can connect to that AP 
without inputting the key - thus any software must allow that choice. 
With WPA, everyone got their act together, and one never heeds to 
input the key as the passphrase will always work.

Larry
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Wireless Chips

[Larry Finger]

Herbert Taylor wrote:
> I just finished reading the Network manager story in the Red Hat 
> Magazine.  It had a list of chips that work with Linux and a list that 
> don't.
> Are these chips the kind that are in the computer or are they PCMCIA type.
> I have a Dell Inspiron B130, that has a broadcom wireless card.  Haven't 
> found a way to use it on wireless.  Does anyone know of a PCMCIA card 
> that would work in its place?  I am using Fedora 8 which works very well 
> on DSL.  I will be doing some traveling this summer and would like to be 
> able to use the wireless such as in airports, etc.

These wireless chips come packaged in many forms. In modern laptops, 
they are on a mini-PCI express card. In slightly older laptops, they 
are on a mini-PCI card. They also are built into PCMCIA cards. For 
desktops, they are built on a PCI card. In most cases, they are part 
of something that plugs in, but there are probably motherboards that 
have them soldered on.

If you send the part of the output of a 'lspci -v' command that refers 
to the wireless card, I can tell you if your Broadcom card is 
supported. Unless your B130 is very recent, that device should work.

Larry
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NetworkManager, ASUS led

[Larry Finger]

Dan Williams wrote:
> On Tue, 22 Jan 2008, Howard Chu wrote:
> 
>> Following up on this thread
>> http://lists.kde.org/?l=kde-devel&m=120099366404038&w=2
>>
>> KDE's kwifimanager was explicitly patched to toggle the Wireless LED on/off 
>> on 
>> Asus notebooks. It seems that the function really belongs in NetworkManager 
>> instead. I patched my copy of NetworkManager 0.6.5 to add the function, the 
>> patch is attached. It's probably not the cleanest approach, but it works for 
>> me.
> 
> No, this function belongs in the kernel or in HAL.  Ideally the ASUS bits 
> that 
> keep track of rfkill need to be talking to the wireless LED too, or the bits 
> that actually kill the wireless (right now that's callouts from HAL if the 
> switch isn't hardwired to the card or handled in BIOS) need to do this.  
> NetworkManager certainly isn't going to be coding workarounds for every 
> laptop 
> vendor to toggle stuff like the wireless LED.  It really needs to be handled 
> at 
> a lower level than that.
> 
> There's an rfkill layer in the kernel that stuff can use, and there's also an 
> LED framework (though I'm not sure if that's generic or specific to only WLAN 
> cards).  If the ASUS LED is truly a software LED, then there need to be asus 
> specific callouts in HAL (or the asus ACPI module should hook into the rfkill 
> framework and toggle it from there) to handle this, not NetworkManager.

Which flavor of wireless card is in that Acer? The b43 driver uses the rfkill 
layer to handle the
wireless LED. It took a bit of fiddling to get it all to work as Michael Buesch 
(the one that added
rfkill to b43) does not have hardware with such a LED. All the requisite stuff 
made it to mainline
at 2.6.24-rc5 (or so). It works with NM or with if-up on my HP laptop.

Larry
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NM drops WPA connection

[Larry Finger]

Marcello Musso wrote:
> Hi,
> I have network-manager 0.6.5 installed on Ubuntu Gutsy. I use a Broadcom 
> 4318 wireless card with Ndiswrapper.
> Everything used to work fine, but now if I try to connect to a WPA 
> encrypted wireless network then I am disconnected after a few minutes.

What changed on your system? If you haven't changed any software and/or 
hardware since it used to
work, it is likely that the interference changed. If you control the access 
point, try channels 1,
6, or 11 to see if that helps.

> The nm-applet in the system tray still says I am connected, but I have no 
> networking whatsoever.

That is only one of the problems with using a Windows driver - you get the 
"stability" of Windows!!!
FWIW, my BCM4318 connects to a WPA-PSK TKIP network and never loses the 
connection. Oh yea, I'm
using b43 as the driver.

Larry

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: wifi conection

[Larry Finger]

Gilles Pelletier wrote:
> First, let's check if I'm on the right list.
> I have a desktop computer running Fedora 7 connected via a TEW-432BRP
> 54Mbps 802.11g Wireless Firewall Router to a SpeedStream 5200 adsl
> modem. This connection works since I am sending this email through it.
> I also have a Toshiba Satellite A-100 -VA7 unit laptop with WIFI
> switch on running Fedora 6.
> I want the laptop to talk to the desktop and share its internet
> connection, printer and upload/download files.
> The laptop doesn't seem to recognise the desktop and vice-versa.
> I must confess that I have no idea of where to go from here. I got the
> address for this mailing list from the fedoraproject wiki on wifi.

First of all, this question has only a little to do with NetworkManager.

You don't really want the F6 laptop to share the F7 Internet connection. To me 
that implies all
traffic from F6 going through F7 and vice versa. What you need to do is 
establish a wifi connection
from the F6 laptop to the TEW-4328BRP router. Once you have the connection, you 
share disks with
NFS, etc.

Have you turned 802.11g on in the router and set the ESSID and hopefully the 
encryption? Is the wifi
driver loaded in F6? Once the answers to these questions is yes, you should see 
your Access
Point/router in the NM applet and be able to connect.

Larry
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: My Laptop

[Larry Finger]

Stuart D. Gathman wrote:
> Broadcom wireless is only partially reverse engineered.  I tried the
> b43 driver in FC8 on the BCM94311MCG in my new laptop.  It worked, with
> WPA even, but I got kernel exceptions, DMA exception, and eventually the 
> system
> froze.  I would say it is not ready for prime time.  (I will be looking for
> where to helpfully report the exceptions for those trying to debug
> the thing.  I suspect donations of relevant hardware are most useful.)
> No problems with the zd1211 driver and USB key.

I'm sorry that you had troubles with the BCM94311MCG in your laptop, but I 
think most of your 
problems are fixed in driver b43 in any of the 2.6.24-rcX kernels. In any case, 
the place to report 
such problems is [EMAIL PROTECTED]

I have both rev 1 and 2 of that PCIe card for my laptop, and I have no kernel 
or DMA exceptions, the 
system never freezes, and my throughput is higher with the b43 driver than with 
Windows using the 
Broadcom driver.

Larry


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: My Laptop

[Larry Finger]

Herbert Taylor wrote:
> I wanted to see if I could get some advise on what to do concerning 
> wireless on my laptop.  I have a Dell Inspiron B130 with a Dell wireless 
> card, 1370 WLAN, mini-PC card.  It works fine on windows as does a 
> Linksys WUSB54G.
> 
> I have Ubuntu loaded right now in a dual boot, that one of my geek 
> friends worked on and am not sure if it will ever work right again.  I 
> have been unable to get get any drivers that will load or work with 
> Ubuntu and network manager at all.  I was using Fedora 6, but had 
> problems with that.  I am fairly new to Linux as you can guess.
> 
> Daniel Fetchinson (I believe) wrote that he installed Fedora 8 and 
> network manager was working just fine and he connected to his wireless 
> network.  I was thinking seriously of going back to Fedora but unable to 
> find a way to get a copy were we are staying for the winter in Florida.
> 
> Not sure if my Dell (Broadcom card I believe) will work the same way 
> with Fedora 8. Wish I knew more about this stuff.  Linux out performs 
> Windows in all ways, but right now I am stuck using windows while I am 
> down down here for 5 months. Any suggestions on what I might be able to 
> do would be greatly appreciated. If I could get this thing to work I 
> could drop windows completely.

The Dell 1370 is a BCM4318 and will work with the driver named bcm43xx in 
kernels 2.6.21 and later. 
  Kernel 2.6.24-rc5 also includes a better driver named b43.

One problem you will have with Ubuntu is that they configure their kernels 
without enabling the 
debug messages for bcm43xx, which greatly complicates getting started.

To use bcm43xx or b43, you will have to install firmware as the Broadcom 
copyright prevents 
distribution of this firmware. Consult
http://linuxwireless.org/en/users/Drivers/b43#devicefirmware for instructions 
on downloading _AND_ 
installing the correct firmware (version 3 for bcm43xx, version 4 for b43).

In any future postings regarding this issue, please include the output of the 
'uname -r' command, 
and the output of 'dmesg | grep bcm43xx' or 'dmesg | grep b43'. The flavor you 
use will be 
determined by the driver you are trying to use.

Larry

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Frequent Disconnects

[Larry Finger]

Patrick Hi wrote:
> Alrighty - this is a desktop computer, on the floor directly over the 
> router. Right now the signal strength is reported as 45%, oh, then it 
> just disconnected again. Now it's back and at 44%.
> 
> Linux patrickishere 2.6.20-16-386 #2 Thu Jun 7 20:16:13 UTC 2007 i686 
> GNU/Linux
> wpa_supplicant v0.5.5
> Netgear WG311T- Atheros XR or Super G, the box lists both.
> Using madwifi drivers.
> 
> Here are two syslogs from two different days. I would have posted all 
> of  today's syslog, but with so many reconnects disconnects it is now 
> over 9 MB in size -- Pastebin thinks I'm spamming. So I'm only going to 
> post part of it.
> 
> My passkey is 24 characters long, perhaps that is a problem.

The passkey length shouldn't be a problem. AFAIK, it always gets turned into a 
hex key of length 64. 
Check the encryption key listed in iwconfig.

Wit a signal strength of 44, it wouldn't take much interference to knock you 
off-line. It could come 
from a portable phone (not cell), a baby monitor, a microwave, or any number of 
sources. Google 
"wifi 2.4 interference" to see some ideas on what can interfere and how to 
avoid it. You might also 
try using a different channel from the 1,6,11 set.

Larry
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Potential problem in getting WPA key from KDE Wallet

[Larry Finger]

I may have found a problem in getting a WPA-PSK key from KDE Wallet. I have two 
AP's with one of
them used only for testing. Both are broadcasting their ESSID - the production 
machine has the ESSID
of 'lwfdjf'. When the test unit had an ESSID of 'lwfdjf2' and I selected it 
using the KDE kicker
applet for NetworkManager, I always got the screen requesting the WPA-PSK key, 
even though the KDE
Wallet showed that a key had been entered. That part worked as expected for the 
production AP.

When I changed the ESSID of the test AP to 'second', everything works OK. Did 
the fact that the
first 6 characters of the two ESSID's were the same confuse the querying of KDE 
Wallet?

I would be happy to do any further testing and/or provide the contents of logs, 
providing you tell
me where to find them. I'm using 0.6.4-51 of NetworkManager from the x86_64 
openSUSE 10.2
distribution. The kicker applet is version 0.1r606753-17.1.

Thanks,

Larry

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: ipw srcipts for hal

[Larry Finger]

dragoran wrote:
> 
> 
> On 6/25/07, *yelo_3* <[EMAIL PROTECTED] > wrote:
> 
> 
> ok
> 
> anyway sorry but why did they implement a hardware kill that cannot
> be "revoked" using software? I don't find the use case of this
> 
> 
> dunno but thats how the cards where designed...

My notebook has a slide switch for rfkill/radio disable. No software can move 
that switch with the 
hardware available.

Larry
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: permanently blacklisting an AP; rate setting on bcm43xx

[Larry Finger]

John Steele Scott wrote:
> Hi,
> 
> Is it possible to permanently blacklist an access point by its MAC
> address? I've tried removing the address in gconf-editor, but this didn't
> do what I wanted.
> 
> The situation is that I have two APs in a WDS setup. One of the APs (a
> Billion 7402VGP) does not work properly with the bcm43xx in my iBook. The
> other AP (a Belkin) works fine. So I want NetworkManager to only associate
> with the Belkin, and never with the Billion.
> 
> Another question. On the same iBook, when NetworkManager associates with
> an AP, the bit rate is 11Mbits. If I want it faster (e.g. 54Mbits), I have
> to set it manually with iwconfig. Is this a known
> bug? Is there a simple way to specific a command to run every time NM
> associates, so I could have this happen automatically?
> 
> I am using NM 0.6.4 from Ubuntu Feisty.

It is a feature, not a bug. Until very recently, none of the bcm43xx drivers 
could go very fast and 
11 Mbs was set to enable the driver to authenticate with some reliability.

What kernel version is in Feisty? Incidentally, it is rare for a bcm43xx driver 
to work reliably at 
54 Mbs. As the bcm43xx-softmac maintainer, I have access to the latest 
modifications. My BCM4311 
works best at 36 Mbs, but the throughput falls off a lot at 48 Mbs, and it 
fails at 54 Mbs. I have 
heard rumors of cards working at 54 Mbs, but no concrete data. If you can run 
an Iperf test with a 
local server, I would be interested in the numbers.

With 2.6.22-rc3, the default is set to 24 Mbs, which has the best throughput 
for most versions of 
the bcm43xx. The bcm43xx-softmac driver does not do any rate manipulation, and 
it stays where you 
set it.

Larry
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Hello

[Larry Finger]

Benjamin Kreuter wrote:
> Hi All --
> 
> My name is Benjamin Kreuter, and I'm going to be contributing a bit to 
> NetworkManager this summer, and possibly after that.  I just thought I would 
> announce myself to the list.
> 
> Also, I am having trouble connecting to anoncvs.gnome.org -- is this server 
> still in use?  If not, which repository should I be using (and why does the 
> website still say to get files from there)?

The source code control now uses svn. The URL is 
svn://websvn.kde.org/home/kde/trunk/extragear/network/knetworkmanager.

I don't know why the website is out of date.

Larry
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: nm-applet do not show my wireless

[Larry Finger]

Alejandro Adam wrote:
> Dan
> 
> Thanks for the quick answer. Here I'm trying to answer your questions. I
> couldn't find anything wrong with the wireless configuration (it works,
> in fact). But the applet still does not see it. 
> 
> The applet is the stable deb package
> 
> valhalla:/home/alejandro# nm-applet --version
> Gnome nm-applet 0.6.4
> 
> The kernel version is 2.6.18-4-686. It is the latest stable deb package
> also. I didn't compile it by myself. For the module, at the bottom I
> pasted a portion of /var/log/syslog in case is useful.

I'm not sure that 2.6.18 reports wireless statistics anywhere near correctly. I 
do know that the 
performance is greatly improved in 2.6.21. You should download and build a 
later version, or get my 
standalone package from 
ftp://lwfinger.dynalias.org/patches/bcm43xx-softmac-sa.tar.bz2.

Your firmware is OK - it is the latest version that can be used with bcm43xx.

Larry

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list