wingcom Posted February 11, 2007 Report Share Posted February 11, 2007 Hello, I have multiple interfaces to connect to the internet. I've got wired and non-wired access. Wired works fine and I am now trying to connect to a Open WEP protected wireless network. To do this I have the choice between 2 interface cards: one with a native driver (hostap_cs) which is 802.11b and an ndiswrapper wrapped one (Asus onboard which is 802.11g) Now everything looks fine (input here is from the configuration with the hostap_cs down and ndiswrapper up: [root@VOYAGER wingcom]# ndiswrapper -l Installed drivers: mrv8knt driver installed, hardware present [root@VOYAGER wingcom]# ifconfig eth0 Link encap:Ethernet HWaddr 00:11:D8:B2:25:3F UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:177 eth1 Link encap:Ethernet HWaddr 00:11:D8:B2:2D:0F inet addr:10.0.1.227 Bcast:10.0.1.255 Mask:255.255.255.0 inet6 addr: fe80::211:d8ff:feb2:2d0f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:577463 errors:0 dropped:0 overruns:0 frame:517 TX packets:461840 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:627796271 (598.7 MiB) TX bytes:124948958 (119.1 MiB) Interrupt:169 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1553751 errors:0 dropped:0 overruns:0 frame:0 TX packets:1553751 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2221609601 (2.0 GiB) TX bytes:2221609601 (2.0 GiB) vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01 inet addr:192.168.94.1 Bcast:192.168.94.255 Mask:255.255.255.0 inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:1134 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vmnet8 Link encap:Ethernet HWaddr 00:50:56:C0:00:08 inet addr:192.168.210.1 Bcast:192.168.210.255 Mask:255.255.255.0 inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:1134 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) wlan2 Link encap:Ethernet HWaddr 00:11:D8:B2:34:DF inet addr:192.168.0.127 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:74 Memory:cdd90000-cdda0000 The access point is on static ip mode (DWL-2000ap+). This configuration is tested with windows 2K and works! But the above "should work too"... however: i think my routes are messed up: [root@VOYAGER wingcom]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.210.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet8 10.0.1.0 0.0.0.0 255.255.255.0 U 5 0 0 eth1 192.168.0.0 0.0.0.0 255.255.255.0 U 35 0 0 wlan2 192.168.94.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet1 169.254.0.0 0.0.0.0 255.255.0.0 U 5 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 35 0 0 wlan2 0.0.0.0 10.0.1.1 0.0.0.0 UG 5 0 0 eth1 So according to this table the network 192.168.0.0-254 should pick wlan2 but it doesn't. Prove to this: [root@VOYAGER wingcom]# traceroute 192.168.0.50 traceroute: Warning: Multiple interfaces found; using 127.0.0.1 @ lo traceroute to 192.168.0.50 (192.168.0.50), 30 hops max, 46 byte packets 1 VOYAGER (127.0.0.1) 3002.313 ms !H 3004.797 ms !H 3005.140 ms !H Anybody any idea what could be wrong? If this were windows I would reboot but i'v learned that that is just a waste of time in linux. If it doesn't work like this, it won't work on reboot too :) which is a good thing actually :)) any suggestions are welcome thanx, wingcom [moved from Software by spinynorman] Quote Link to comment Share on other sites More sharing options...
wingcom Posted February 13, 2007 Author Report Share Posted February 13, 2007 Sorry i posted this in the wrong section. Looked over this one i guess :s Anyways, its not a routing problem... I just can't connect when I got WEP encryption enabled :s I tried many different ways for configuring it, from Mandriva wizards to commandline. ifdown wlan0 iwconfig wlan0 essid "My network" iwconfig wlan0 mode managed iwconfig wlan0 enc on iwconfig wlan0 key open s:mykey ifup wlan0 Am I missing something? - I am sure about the key - The configuration is tested and works on a windows client - I can do monitor mode and find my AP. It reports a good signal strength iwlist wlan0 scan gives me a list... sometimes but not all the time :s I got alot of packets that I receive but are encrypted - RX Invalid Crypts - so thats where I saw my encryption isn't working. But I have no clue what this could be. I used to connect to the access point on Mandriva 2005 through a DWL-G122 USB Dongle. It normally has WPA encryption enabled but i changed it to WEP for testing purposes. I don't know whats going on here. I tried the hostap_cs AND the orinoco_cs drivers. None work... I also got an onboard Asus Wifi-g chip which i tried using ndiswrapper (which looks ok but I think I saw some dumps in the logs when loading it, eventhough it does not report something bad elsewhere) no success here either. Maybe its my pci-to-pcmcia bridge? Is this known to cause troubles? I read something about interrupt handling but that was only for older kernels? Quote Link to comment Share on other sites More sharing options...
wingcom Posted February 14, 2007 Author Report Share Posted February 14, 2007 Ok, its working with the ndiswrapper driver now. I just had to unload the current driver (from RPM) and load the custom-built one (for custom kernel) :blush: Now it loads fine and can connect to the network. Its transmitting and receiving packets like it should, picks the correct route and pings the router. How unfortunate that these things tend to get broken all at the same time :s Well, at least one of them is fixed... But I hate things on my computer that don't work so I should get this to work with the Senao Prism2 Card as well! I hope it has nothing to do with the udev renaming stuff. What I've also noticed is: if I set the configuration manually through iwconfig and I point it to an non-protected wireless network in the neighbourhood with essid "Default" and afterwards I kill this connection/interface then I do ifup wlan0, it doesn't change the info to the info found at /etc/sysconfig/network-scripts/ifcfg-wlan0 Is this normal behaviour? If i use ifup shouldn it adjust to the settings in this network-scipt? It just stays on "Default" Quote Link to comment Share on other sites More sharing options...
wingcom Posted February 27, 2007 Author Report Share Posted February 27, 2007 Problems were udev and wirless wizard related. check my post about hostap && udev. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.