[SLE] it's weird: My ndiswrapper can be loaded but ping does not work

Patrix Bumi

30 Jul 2006 30 Jul '06

11:17

Hi friends, I use OpenSuSE 10.1 , LinkSys WMP54G PCI (Wireless-G PCI Adapter) and LinkSys Wireless-G ADSL Gateway (IP: 192.168.1.1). Because I can't find the Linux device driver for my WMP54G, I use ndiswrapper. My ndiswrapper has been installed successfully. and I did : 1. copied the its windows device driver into "/root" ( Rt61.INF , rt61.cat , rt61.sys ) 2. ndiswrapper -i /root/Rt61.INF 3. ndiswrapper -l driver present, hardware present 4. modprobe ndiswrapper 5. and finally configure the wlan0 with yast2 (network device) as follows: - I chosed "wireless" as device type - Configuration name "0" it results wlan0 - Hardware configuration name: static-0 - Module name : ndiswrapper - IRQ : I left it blank - Operating mode : managed - network name (SSID) : linksys - Encryption : Open / disabled - IP : 192.168.1.140 / 255.255.255.0 - gateway : 192.168.1.1 My KNetwork-Manager says that my Linksys WMP54G PCI is connected to 'linksys' and active. but if I do: "ping 192.168.1.1" than I get negative result. And of course I can not go to internet with my WLAN Adapter Card. the SuSEfirewall2 is stopped. It's weird for me. Please help me. Tell me where my mistake. Thank you very much. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

Show replies by date

Ken Schneider

30 Jul 30 Jul

11:39

New subject: [SLE] it's weird: My ndiswrapper can be loaded but ping does not work

On Sun, 2006-07-30 at 18:17 +0700, Patrix Bumi wrote:

...

Hi friends,

I use OpenSuSE 10.1 , LinkSys WMP54G PCI (Wireless-G PCI Adapter) and LinkSys Wireless-G ADSL Gateway (IP: 192.168.1.1).

Because I can't find the Linux device driver for my WMP54G, I use ndiswrapper.

My ndiswrapper has been installed successfully. and I did : 1. copied the its windows device driver into "/root" ( Rt61.INF , rt61.cat , rt61.sys ) 2. ndiswrapper -i /root/Rt61.INF 3. ndiswrapper -l driver present, hardware present 4. modprobe ndiswrapper 5. and finally configure the wlan0 with yast2 (network device) as follows: - I chosed "wireless" as device type - Configuration name "0" it results wlan0 - Hardware configuration name: static-0 - Module name : ndiswrapper - IRQ : I left it blank - Operating mode : managed - network name (SSID) : linksys - Encryption : Open / disabled - IP : 192.168.1.140 / 255.255.255.0 - gateway : 192.168.1.1

My KNetwork-Manager says that my Linksys WMP54G PCI is connected to 'linksys' and active. but if I do: "ping 192.168.1.1" than I get negative result. And of course I can not go to internet with my WLAN Adapter Card.

the SuSEfirewall2 is stopped.

It's weird for me.

Please help me. Tell me where my mistake.

Thank you very much.

What is the result of route -n? Perhaps the default route is not being set. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

Patrix Bumi

13:15

Liebe Schneider, Thank you very much for your answer. Here is what happens on my SuSE10.1 ----- suse5:~ # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0 suse5:~ # ------ My internal LAN has 192.168.1.0 as the network number. the ADSL GateWay (router+modem) is the 192.168.1.1 Please tell me, how should the default route should be. How should I configure the default route? Thank you very much. Ken Schneider wrote:

...

On Sun, 2006-07-30 at 18:17 +0700, Patrix Bumi wrote:

...
Hi friends,

I use OpenSuSE 10.1 , LinkSys WMP54G PCI (Wireless-G PCI Adapter) and LinkSys Wireless-G ADSL Gateway (IP: 192.168.1.1).

Because I can't find the Linux device driver for my WMP54G, I use ndiswrapper.

My ndiswrapper has been installed successfully. and I did : 1. copied the its windows device driver into "/root" ( Rt61.INF , rt61.cat , rt61.sys ) 2. ndiswrapper -i /root/Rt61.INF 3. ndiswrapper -l driver present, hardware present 4. modprobe ndiswrapper 5. and finally configure the wlan0 with yast2 (network device) as follows: - I chosed "wireless" as device type - Configuration name "0" it results wlan0 - Hardware configuration name: static-0 - Module name : ndiswrapper - IRQ : I left it blank - Operating mode : managed - network name (SSID) : linksys - Encryption : Open / disabled - IP : 192.168.1.140 / 255.255.255.0 - gateway : 192.168.1.1

My KNetwork-Manager says that my Linksys WMP54G PCI is connected to 'linksys' and active. but if I do: "ping 192.168.1.1" than I get negative result. And of course I can not go to internet with my WLAN Adapter Card.

the SuSEfirewall2 is stopped.

It's weird for me.

Please help me. Tell me where my mistake.

Thank you very much.

What is the result of route -n? Perhaps the default route is not being set.

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

Jerry Feldman

14:50

On Sun, 30 Jul 2006 20:15:55 +0700 Patrix Bumi wrote:

...

Kernel IP routing table

Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0

...

------ My internal LAN has 192.168.1.0 as the network number. the ADSL GateWay (router+modem) is the 192.168.1.1

Please tell me, how should the default route should be. How should I configure the default route? The default route is correct. You should be able to communicate through the router.

Are you using encryption? If so, make sure your keys are correct. I found a wierd issue where key #1 was deleted on a friend's router and it shifted to key#2. At this point, show the output of 'iwconfig wlan0' Normally, I also sometimes specify the essid in cases where I may be in contact with multiple connections. -- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

Patrix Bumi

15:28

New subject: [SLE] it's weird: My ndiswrapper can be loaded but ping does not work

Hi, Jerry... No, on my router I setup no encryption for each connection (open). I neglect all security risk in my internal LAN for convenience. That's why I switch-off encryption also on each wLAN cards. here is the output: " suse5:~ # iwconfig wlan0 wlan0 IEEE 802.11g ESSID:off/any Mode:Auto Frequency:2.462 GHz Access Point: Not-Associated Bit Rate:54 Mb/s Tx-Power:20 dBm Sensitivity=-121 dBm RTS thr:2347 B Fragment thr:2346 B Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 suse5:~ # " Please help me. This is the first time for me for using SuSE 10.1 (usually 10) and this is the first time for me for using ndiswrapper. I bought LinkSys PCI wLAN card but till now I still can't use this wLAN card. Sigh.... I started to think about: "is it because of the patches? do I have to download the patches?". but just now I started the YOU to get the patches but it's different than the previous SuSE's version. I must input the registration code and then stucked on waiting "getting update list" without ending. again sigh.... Please help me. On Sun, 2006-07-30 at 10:50 -0400, Jerry Feldman wrote:

...

On Sun, 30 Jul 2006 20:15:55 +0700 Patrix Bumi wrote:

...
Kernel IP routing table

Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0

...
------ My internal LAN has 192.168.1.0 as the network number. the ADSL GateWay (router+modem) is the 192.168.1.1

Please tell me, how should the default route should be. How should I configure the default route? The default route is correct. You should be able to communicate through the router.

Are you using encryption? If so, make sure your keys are correct. I found a wierd issue where key #1 was deleted on a friend's router and it shifted to key#2. At this point, show the output of 'iwconfig wlan0'

Normally, I also sometimes specify the essid in cases where I may be in contact with multiple connections.

John Andersen

18:42

On Sunday 30 July 2006 03:17, Patrix Bumi wrote:

...

5. and finally configure the wlan0 with yast2 (network device) as follows: - I chosed "wireless" as device type - Configuration name "0" it results wlan0 - Hardware configuration name: static-0 - Module name : ndiswrapper - IRQ : I left it blank - Operating mode : managed - network name (SSID) : linksys - Encryption : Open / disabled - IP : 192.168.1.140 / 255.255.255.0 - gateway : 192.168.1.1

Whao, are you saying you MANUALLY set that IP rathern than letting the Linksys give you one? Because the output of your iwconfig says you are not talking at all to that router.

...

suse5:~ # iwconfig wlan0 wlan0 IEEE 802.11g ESSID:off/any Mode:Auto Frequency:2.462 GHz Access Point: Not-Associated Bit Rate:54 Mb/s Tx-Power:20 dBm Sensitivity=-121 dBm RTS thr:2347 B Fragment thr:2346 B Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Also, are you sure you even need ndswrapper for that particular nic? -- _____________________________________ John Andersen

Patrix Bumi

19:22

OK. I will use DHCP client. I don't understand with this one: " Also, are you sure you even need ndswrapper for that particular nic? " Are you meaning that my wLAN card (Linksys WMP54G) does not work although I use ndiswrapper whereas I don't have linux device driver for my wLAN card? Thank you for your respond. John Andersen wrote:

...

On Sunday 30 July 2006 03:17, Patrix Bumi wrote:

...
5. and finally configure the wlan0 with yast2 (network device) as follows: - I chosed "wireless" as device type - Configuration name "0" it results wlan0 - Hardware configuration name: static-0 - Module name : ndiswrapper - IRQ : I left it blank - Operating mode : managed - network name (SSID) : linksys - Encryption : Open / disabled - IP : 192.168.1.140 / 255.255.255.0 - gateway : 192.168.1.1

Whao, are you saying you MANUALLY set that IP rathern than letting the Linksys give you one?

Because the output of your iwconfig says you are not talking at all to that router.

...
suse5:~ # iwconfig wlan0 wlan0 IEEE 802.11g ESSID:off/any Mode:Auto Frequency:2.462 GHz Access Point: Not-Associated Bit Rate:54 Mb/s Tx-Power:20 dBm Sensitivity=-121 dBm RTS thr:2347 B Fragment thr:2346 B Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Also, are you sure you even need ndswrapper for that particular nic?

Ken Schneider

20:43

New subject: [SLE] it's weird: My ndiswrapper can be loaded but ping does not work

On Mon, 2006-07-31 at 02:22 +0700, Patrix Bumi wrote:

...

OK. I will use DHCP client.

I don't understand with this one: "

Also, are you sure you even need ndswrapper for that particular nic?

" Are you meaning that my wLAN card (Linksys WMP54G) does not work although I use ndiswrapper whereas I don't have linux device driver for my wLAN card?

Thank you for your respond.

Linksys cards do require the use of ndiswrapper, I use one as well but mine is a PCMCIA type. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

Patrix Bumi

31 Jul 31 Jul

10:34

OK, Thank you very much Ken. Ken Schneider wrote:

...

On Mon, 2006-07-31 at 02:22 +0700, Patrix Bumi wrote:

...
OK. I will use DHCP client.

I don't understand with this one: "

Also, are you sure you even need ndswrapper for that particular nic?

" Are you meaning that my wLAN card (Linksys WMP54G) does not work although I use ndiswrapper whereas I don't have linux device driver for my wLAN card?

Thank you for your respond.

Linksys cards do require the use of ndiswrapper, I use one as well but mine is a PCMCIA type.

6485

Age (days ago)

6486

Last active (days ago)

List overview

Download

8 comments

4 participants

participants (4)

Jerry Feldman
John Andersen
Ken Schneider
Patrix Bumi