RE: [Ndiswrapper-general] support for siemens gigaset usb adapter108 (atheros 5523) with ndiswrapper
Status: Beta
Brought to you by:
pgiri
|
From: ruud v. <r.v...@kp...> - 2006-01-26 11:34:45
|
I received a message frome system-administrator that my e-mail might not =
have been received by you yesterday.
So I try it again.
Gentoopower wrote:
-----Original Message-----
From: Gentoopower [mailto:gen...@ya...]
Sent: maandag 23 januari 2006 15:25
To: ruud vennink
Cc: ndi...@li...
Subject: Re: [Ndiswrapper-general] support for siemens gigaset usb
adapter108 (atheros 5523) with ndiswrapper-1,7
From the wpa_supplicant output it looks like your connection is ok, what
is output of command:
route
and can you ping your accesspoint 192.168.2.1?
Did you specify a nameserver in /etc/resolv.conf
-------------------------------------------------------------------------=
------------
OKAY !!!!!!!!!!!!!!!!!!!!!!!!!!!!!
- It works with the 16k stack fedora 4 core. The internet connection via =
the browser is established.
- The wpa_supplicant is essential. Without there is no connection withe =
te router. Security is operational.
- The signal is good. The KDE-WiFi monitor applet show an "ultimate" =
signal strength at speed of 54 Mbps and I feel that the response on =
browser requests is as least comparable with windows xp internet =
explorer.
The missing information was the resolv.conf file. It was empty. I =
presumed that it should be written by the wireless net tools. Because of =
your suggestion I remarked that the file was empty and wrote it by hand. =
For completeness the requested information by you is given here. It =
looks fine.
However it was operational for a super-user. I tried to make it =
operational for any user. There is no problem for the network-device =
tool to make wlan0 active by any user. For the wpa_supplicant program I =
did two things:
- put my name in the group wheel
- set the super-user bit for wpa_supplicant
The program wpa_supplicant starts. The internet-browser connects to the =
internet. One could say that there is no problem. Is that the correct =
way or do you know there is another way f.i. with the =
/etc/wpa_supplicant.conf file. I can't find the all-user case in the =
README file.
/etc/wpa_supplicant.conf
ctrl_interface=3D/var/run/wpa_supplicant
ctrl_interface_group=3Dwheel
network=3D{
ssid=3D"SX55154A6FA"
proto=3DWPA
key_mgmt=3DWPA-PSK
pairwise=3DTKIP
group=3DTKIP
psk=3D"My key"
}
The second trial will be to test with a SMP-kernel as soon as possible. =
My motherboard is a SMP board. I should re-compile and re-install =
ndiswrapper and wpa_supplicant. Maybe we will meet again if problems =
occur.
Thank you, and Laurent, so far for the support. A new usb adapter device =
can be added to the list of ndiswrapper working devices. I will mail =
sourceforge.net.
---------------------------------------------------------------
route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use =
Iface
192.168.2.0 * 255.255.255.0 U 0 0 0 =
wlan0
169.254.0.0 * 255.255.0.0 U 0 0 0 =
wlan0
default 192.168.2.1 0.0.0.0 UG 0 0 0 =
wlan0
ping 192.168.2.1 -c 10
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_seq=3D0 ttl=3D64 time=3D2.36 ms
64 bytes from 192.168.2.1: icmp_seq=3D1 ttl=3D64 time=3D2.18 ms
64 bytes from 192.168.2.1: icmp_seq=3D2 ttl=3D64 time=3D2.10 ms
64 bytes from 192.168.2.1: icmp_seq=3D3 ttl=3D64 time=3D2.77 ms
64 bytes from 192.168.2.1: icmp_seq=3D4 ttl=3D64 time=3D2.21 ms
64 bytes from 192.168.2.1: icmp_seq=3D5 ttl=3D64 time=3D2.13 ms
64 bytes from 192.168.2.1: icmp_seq=3D6 ttl=3D64 time=3D2.88 ms
64 bytes from 192.168.2.1: icmp_seq=3D7 ttl=3D64 time=3D2.23 ms
64 bytes from 192.168.2.1: icmp_seq=3D8 ttl=3D64 time=3D2.15 ms
64 bytes from 192.168.2.1: icmp_seq=3D9 ttl=3D64 time=3D2.71 ms
--- 192.168.2.1 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9009ms
rtt min/avg/max/mdev =3D 2.102/2.377/2.887/0.284 ms, pipe 2
/etc/resolv.conf
nameserver 192.168.2.1
nameserver 192.168.2.2
|