Thread: [Ndiswrapper-general] [UPDATE] IBM ThinkPad R40/Intel PRO/Wireless Lan 2100/Debian testing/2.6.0 ker
Status: Beta
Brought to you by:
pgiri
From: Olivier B. <Oli...@pu...> - 2004-01-02 13:34:23
|
Hello all, here is an update of my tests. Configuration: - IBM ThinkPad R40 - Centrino Intel PRO/Wireless Lan 2100 - Debian testing - kernel 2.6.0 - ndiswrapper CVS version Working OK: - good performance (about 600 KB/s in both RX and TX), - no more oops when rmmod ndiswrapper (thanks Giri and all the others working on it), =20 - setting key one time is ok. To have this working correctly, I have modified the script /etc/network/if-pre-up.d/wireless-tools to set the essid only after that the key is set (thanks Giri for the tip). So, I have remove the essid part, and moved it to the end of the script, in a separate iwconfig command. Current problem: - I have sometime no more Internet access. I'm not sure if this is related to the ndiswrapper or not, so I will explain it now. My configuration (some ASCII art): Internet | | +-------+--------+ +------------------+ | Zyxel 650 HW-I | | IBM ThinkPad R40 | | ADSL router +--- Wifi Network --+--+ ndiswrapper | | Wireless AP | | | | +-------+--------+ | +------------------+ | | | Internal network | +---------------+ | | | Dell Inspiron | | +---------------------+ +--+ hostap | | | Main Server | | | | | | DHCP server | ... +---------------+ +---+ Internal DNS server | | | VPN server/client | | | ... | | +---------------------+ ... I know the Zyxel may act as DHCP server, but I don't do this because it is not doing static DHCP server. The routing on every client except the Main Server is simple: - local traffic on the correct network interface - all the other traffic to the Main Server All the network traffic go trough the DHCP server, because the VPN are controled on it (up to 3 differents VPN). So, traffic from the R40 to the Internet go this way: R40 -> Main Server -> Zyxel -> Internet The connections between the Wifi network and the Internal network are always working OK. The connections between the Internal network and the Internet are always working OK. The connections between the Wifi network using hostap client are always working OK. The connections between the Wifi network using ndiswrapper client and the Internet has sometime troubles. To have is back working, I only have to do "ifdown wlan0; ifup wlan0". So my question: is it possible that this problem is with the ndisdriver ? Thanks in advance for your help. Olivier --=20 Olivier Bornet | fran=E7ais : http://puck.ch/f Swiss Ice Hockey Results | english : http://puck.ch/e http://puck.ch/ | deutsch : http://puck.ch/g Oli...@pu... | italiano : http://puck.ch/i Get my PGP-key at http://puck.ch/pgp or at http://wwwkeys.pgp.net |
From: Timo <ti...@ti...> - 2004-01-02 13:52:57
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Maybe a problem with vpn, dhcp and routing. ifup -> vpn up -> routed through vpn -> dhcp renew -> dhcp changes routes Timo -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iQEVAwUBP/V3rEn74FOC+06tAQK39gf/aWADdI0ALlnCG0T/Nlwj0RdpWqRDyWqK uUXzif3Z8uJvOiSu2B2TytiawJW+pKrzpP8kqGPnB3J9IKMu+EuWEmpFUVdSXq38 CUgd/bt2o365JBAO8fjjvfXTujHNdSLUwF5Xs07EN/k4xqPe1HId5wOPu+KdLGcF X6p9yR/96JB1Zl8twSEk2a48ExjKXa68FgGPIfG4L3G8ufXl0gKBo2j6tRz/dQCz ej1hr1rzpuXA8CmfUjLbLw2RRIyin/JZUX8w+llyqHF/oiFEVbJDglVPs6oC+p58 WlBgMZJ3vMuDaehFfZhlIcL02NfruxkcE6WYS8ucmRLQlTPIRDoAxQ== =lKfm -----END PGP SIGNATURE----- |
From: Olivier B. <Oli...@pu...> - 2004-01-02 14:01:36
|
Hi, > Maybe a problem with vpn, dhcp and routing. > ifup -> vpn up -> routed through vpn -> dhcp renew -> dhcp changes routes I think no, because the VPN is not used in this case. Olivier --=20 Olivier Bornet | fran=E7ais : http://puck.ch/f Swiss Ice Hockey Results | english : http://puck.ch/e http://puck.ch/ | deutsch : http://puck.ch/g Oli...@pu... | italiano : http://puck.ch/i Get my PGP-key at http://puck.ch/pgp or at http://wwwkeys.pgp.net |
From: Tomas S. <sz...@pi...> - 2004-01-02 14:18:26
|
On Jan-02 2004, Fri, 14:34 +0100 Olivier Bornet <Oli...@pu...> wrote: > The connections between the Wifi network using ndiswrapper client > and the Internet has sometime troubles. To have is back working, I > only have to do "ifdown wlan0; ifup wlan0". This ifdown/ifup of yours, is it just "ifconfig wlan0 down" / "ifconfig wlan0 up", or does it do more than that? -- Tomas Szepe <sz...@pi...> |
From: Timo <ti...@ti...> - 2004-01-02 14:26:27
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am Freitag, 2. Januar 2004 15:18 schrieb Tomas Szepe: > This ifdown/ifup of yours, is it just "ifconfig wlan0 down" / > "ifconfig wlan0 up", or does it do more than that? yes, it uses a configfile /etc/network/interfaces to set up static ip's, dhcp and iwconfig params. Timo -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iQEVAwUBP/V/h0n74FOC+06tAQJOawf+Ic/VWb3T0LilqB5nEHlbfDJyqVVZGi7i JDJ8OO1HpDZjwHC+GwN+QRJ9+Q6yWsJjZyxSKKdT2dBewdrDEBlXbjoMfXnqFcr0 g/aedz/g7Emy0S4KdqGV+p+FNM1u72LV3fxw57Pjwr48Hz9fZeOzYXfXf/7ghUtx NhunHsQVWTKHVbO8eTku0j8UjmxNxLstgmybHTIFVJImN0eggoK6DscA4yihmJGQ ottmn0Y3HQHpXirPwFUyXgicFWeks/evALtWrZdZ21kESwWSQ8KUXOLucnGt9EHQ WjWhWOYg3edJrCmDlen8eQLKFmgF5GYwd/f7+NLHm5tNseouk6vEdA== =SVw6 -----END PGP SIGNATURE----- |
From: Olivier B. <Oli...@pu...> - 2004-01-02 16:31:42
|
Hi Thomas, > This ifdown/ifup of yours, is it just "ifconfig wlan0 down" / > "ifconfig wlan0 up", or does it do more than that? It's some "standard" Debian command to up or down network interfaces. It does the ifconfig stuff, and other things defined in /etc/network/interfaces (like start dhcp, set wireless key, ...) Olivier --=20 Olivier Bornet | fran=E7ais : http://puck.ch/f Swiss Ice Hockey Results | english : http://puck.ch/e http://puck.ch/ | deutsch : http://puck.ch/g Oli...@pu... | italiano : http://puck.ch/i Get my PGP-key at http://puck.ch/pgp or at http://wwwkeys.pgp.net |
From: Tomas S. <sz...@pi...> - 2004-01-02 16:55:49
|
On Jan-02 2004, Fri, 17:31 +0100 Olivier Bornet <Oli...@pu...> wrote: > > This ifdown/ifup of yours, is it just "ifconfig wlan0 down" / > > "ifconfig wlan0 up", or does it do more than that? > > It's some "standard" Debian command to up or down network interfaces. It > does the ifconfig stuff, and other things defined in > /etc/network/interfaces (like start dhcp, set wireless key, ...) Ok. So could you trace the actual command that restores the connectivity? -- Tomas Szepe <sz...@pi...> |
From: Olivier B. <Oli...@pu...> - 2004-01-02 23:50:57
|
Hi, > > > This ifdown/ifup of yours, is it just "ifconfig wlan0 down" / > > > "ifconfig wlan0 up", or does it do more than that? > ... > Ok. So could you trace the actual command that restores the connectivity? This has actualy restored the connectivity: ifconfig wlan0 down ifconfig wlan0 up sudo route add default gw 10.44.0.3 Thanks for your help. Olivier --=20 Olivier Bornet | fran=E7ais : http://puck.ch/f Swiss Ice Hockey Results | english : http://puck.ch/e http://puck.ch/ | deutsch : http://puck.ch/g Oli...@pu... | italiano : http://puck.ch/i Get my PGP-key at http://puck.ch/pgp or at http://wwwkeys.pgp.net |
From: Timo <ti...@ti...> - 2004-01-03 00:16:37
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am Samstag, 3. Januar 2004 00:50 schrieb Olivier Bornet: > This has actualy restored the connectivity: >=20 > ifconfig wlan0 down > ifconfig wlan0 up > sudo route add default gw 10.44.0.3 Perhaps you can just include that default gateway setting in your dhcpd con= f, so that won't happen anymore. I bet you lost the connectivity to the outside just after a dhcp renew. Timo =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iQEVAwUBP/YJ3kn74FOC+06tAQJXdAgArSJh/biXjl25L0SMrPLKtG5oyEVFvO+F =46Z9NTKZQ5GqAXG/YNK+fHu2w1/V3K/YcQVmicujhCqA+FcLGjPO0Cxe6Tf5XQBI9 Gxj4onymJQO7YSDo90Bq0T1Sr3cJvmUxxhuby9kf5PaZt0UyUfUxyerCYrB6zkWq tcV6ULGlc+443k1KrOzxUw7B5J2moQB+4u2FoQj8cV8TJr1wPhogDn+Q559p+aKQ qhRn564nJQGn2gAN2jAROS8yIt8W/O9/kdX/EK8654MSJpZcPa/U6ANaqSz5AHjN Y4EkUT4d3BaiJcgoaAmMljCnYaQxJrq/sXyF0ilNCfeqXfrs0BLOQQ=3D=3D =3DwLPa =2D----END PGP SIGNATURE----- |
From: Olivier B. <Oli...@pu...> - 2004-01-03 00:53:00
|
Hello, > > This has actualy restored the connectivity: > >=20 > > ifconfig wlan0 down > > ifconfig wlan0 up > > sudo route add default gw 10.44.0.3 >=20 > Perhaps you can just include that default gateway setting in your > dhcpd conf, so that won't happen anymore. I bet you lost the > connectivity to the outside just after a dhcp renew. This is what I already have. And I don't think the problem come at the dhcp renew. The route is always here even when I have lost the connectivity. And re-add the default route is not enough: I have to make the ifconfig down and up before. I also have try to remove and re-add the route, and this is not enough. Thanks for the help. Olivier --=20 Olivier Bornet | fran=E7ais : http://puck.ch/f Swiss Ice Hockey Results | english : http://puck.ch/e http://puck.ch/ | deutsch : http://puck.ch/g Oli...@pu... | italiano : http://puck.ch/i Get my PGP-key at http://puck.ch/pgp or at http://wwwkeys.pgp.net |
From: Tomas S. <sz...@pi...> - 2004-01-03 08:17:04
|
On Jan-03 2004, Sat, 01:52 +0100 Olivier Bornet <Oli...@pu...> wrote: > > > This has actualy restored the connectivity: > > > > > > ifconfig wlan0 down > > > ifconfig wlan0 up > > > sudo route add default gw 10.44.0.3 > > > > Perhaps you can just include that default gateway setting in your > > dhcpd conf, so that won't happen anymore. I bet you lost the > > connectivity to the outside just after a dhcp renew. > > This is what I already have. And I don't think the problem come at the > dhcp renew. The route is always here even when I have lost the > connectivity. > > And re-add the default route is not enough: I have to make the ifconfig > down and up before. I also have try to remove and re-add the route, and > this is not enough. From Linux 2.1 on, the downing of the interface will kill its subnet route, so what I'd try next (when the connectivity is lost again) would be to 1) re-add the subnet route of the wireless interface _and_ the default route. 2) list the arp cache on the box ("arp -n") and try to delete all non-static entries? ("arp -d target") This will of course not solve your problem, but you'll get closer to learning where the problem stems from. -- Tomas Szepe <sz...@pi...> |
From: Olivier B. <Oli...@pu...> - 2004-01-11 23:31:03
|
Hi Tomas and others, On Sat, Jan 03, 2004 at 09:16:55AM +0100, Tomas Szepe wrote: > On Jan-03 2004, Sat, 01:52 +0100 Olivier Bornet <Oli...@pu...> = wrote: > > > > This has actualy restored the connectivity: > > > > [deleted: lot of explanation about my problems, losing Internet > > > > access] > From Linux 2.1 on, the downing of the interface will kill its subnet rout= e, > so what I'd try next (when the connectivity is lost again) would be to > [deleted: some explanation from Tomas for what to test (route and > arp)] Thanks for the proposition. But, ... Since my email to the list with the problems, the problem was no more coming. Maybe it was due to the Zyxel router and my main server. I have had other problems with the Zyxel router, and I have rebooted it. And I have rebooted also my main server for kernel update. Since this reboots, all is working great. Thanks a lot to ndiswrapper developpers and users, and keep up this good work. Good day. Olivier --=20 Olivier Bornet | fran=E7ais : http://puck.ch/f Swiss Ice Hockey Results | english : http://puck.ch/e http://puck.ch/ | deutsch : http://puck.ch/g Oli...@pu... | italiano : http://puck.ch/i Get my PGP-key at http://puck.ch/pgp or at http://wwwkeys.pgp.net |
From: Timo <ti...@ti...> - 2004-01-02 16:50:19
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Look at `route -n` when it occurs the next time. If that is different some tool changed the routing. Can you ping your main server when that occurs. Does the Dell get a connection. If a saw it right, the main server is not directly connected to the Dell. Timo -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iQEVAwUBP/WhQEn74FOC+06tAQJKNgf/Tfpw1RJS+weV3/AXLL2Nwoiw63629u8D 1FLQkK8SVJ1hv/EjTC459Dv3G/xBUb1B9qomM/vRDe53aBttuxWEUE37Ygb3dGMP v86Zw0v53Zs6CJT4cHQ3YaXSIk5g3/KtJ7860M9IckmWPLTSfuAshAow0XeHY7wY GHijbZD6jvz9JPhKSUzxrS8D8e3ewHMTMZO6DFjPgJIiFE/uA9WlDGbrMBXqjnB8 iPasEynngR49Bxstttg8EZDzgp7ACXiAk5LBjoR53PsMKyo1I07JQyeOEiYQkmov 6J8fb9ND20RPQiAs5l7O8HOwbY9pDWAzVj4VRNkIWOivbwWxm6kuvw== =edhN -----END PGP SIGNATURE----- |