Jump to content

Unidentified wireless problem


cmt29
 Share

Recommended Posts

Hi. Got some issues setting up wireless networking under Mdv 2007.0

 

Hardware is all working fine and iwconfig shows good connection to access point. However it seems that my IP routing isn't working.

 

When using drakconnect to set up the network it would hang after specifying the ndiswrapper driver. Running ps -A showed that ip and ifup-eth were stalling the system. After killing these processes the set up would continue. But, I'm guessing that the ip routing has not been set up properly.

 

Any thoughts? I'm not sure if I was just being impatient, but I gave drakconnect a good 5 mins to sort itself out. It didn't.

 

Could I sort out the IP routing manually without gui?

 

Any help much appreciated---and let me know any further info you might need since I'm not sure where to look.

 

Thanks,

Chris

Edited by cmt29
Link to comment
Share on other sites

OK. Probably ought to supply a little more information. Sorry.

 

My router is a D-Link DSL-G604T, working just fine.

My wireless card is a Edimax 7128G, again working fine.

 

I am happily connected under Windows.

 

However I seem to get no connection under Linux.

 

Any thoughts?

Thanks,

Chris

 

Various files/outputs:

 

iwconfig

lo		no wireless extensions.

wlan0	 IEEE 802.11g  ESSID:"myessid"  Nickname:"myhostname"
	  Mode:Managed  Frequency:2.437 GHz  Access Point: xx:xx:xx:xx:xx:xx   
	  Bit Rate=54 Mb/s   Tx-Power:20 dBm   Sensitivity=-121 dBm  
	  RTS thr=2347 B   Fragment thr=2346 B   
	  Encryption key:xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx   Security mode:open
	  Power Management:off
	  Link Quality:100/100  Signal level:-49 dBm  Noise level:-256 dBm
	  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
	  Tx excessive retries:0  Invalid misc:0   Missed beacon:0

 

ifconfig

lo		Link encap:Local Loopback  
	  inet addr:127.0.0.1  Mask:255.0.0.0
	  UP LOOPBACK RUNNING  MTU:16436  Metric:1
	  RX packets:105 errors:0 dropped:0 overruns:0 frame:0
	  TX packets:105 errors:0 dropped:0 overruns:0 carrier:0
	  collisions:0 txqueuelen:0 
	  RX bytes:8953 (8.7 KiB)  TX bytes:8953 (8.7 KiB)

wlan0	 Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx  
	  inet addr:192.168.x.10  Bcast:192.168.x.255  Mask:255.255.255.0
	  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
	  RX packets:494 errors:0 dropped:0 overruns:0 frame:0
	  TX packets:362 errors:0 dropped:0 overruns:0 carrier:0
	  collisions:0 txqueuelen:1000 
	  RX bytes:24000 (23.4 KiB)  TX bytes:32700 (31.9 KiB)
	  Interrupt:19 Memory:dfff0000-dfff8000

 

route -n

Kernel IP routing table
Destination	 Gateway		 Genmask		 Flags Metric Ref	Use Iface
192.168.x.0	 0.0.0.0		 255.255.255.0   U	 35	 0		0 wlan0
169.254.0.0	 0.0.0.0		 255.255.0.0	 U	 35	 0		0 wlan0
0.0.0.0		 192.168.x.1	 0.0.0.0		 UG	35	 0		0 wlan0

 

iptables -nvL

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target	 prot opt in	 out	 source			   destination		 

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target	 prot opt in	 out	 source			   destination		 

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target	 prot opt in	 out	 source			   destination

 

iptables -nvL -t nat

Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target	 prot opt in	 out	 source			   destination		 

Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target	 prot opt in	 out	 source			   destination		 

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target	 prot opt in	 out	 source			   destination

 

resolve.conf

# search domain
nameserver 192.168.x.1
# $Id: resolv.conf,v 1.1 2006/06/02 23:25:57 othauvin Exp $
# Basic resolv.conf

# ppp temp entry

 

ifcfg-wlan0

DEVICE=wlan0
#BOOTPROTO=dhcp
BOOTPROTO=static
IPADDR=192.168.x.10
NETMASK=255.255.255.0
NETWORK=192.168.x.0
BROADCAST=192.168.x.255
ONBOOT=yes
METRIC=35
MII_NOT_SUPPORTED=no
USERCTL=yes
RESOLV_MODS=no
WIRELESS_MODE=Managed
WIRELESS_ESSID=myessid
WIRELESS_ENC_KEY="open xxxxxxxxxxxxxxxxxxxxxxxxxx"
IPV6INIT=no
IPV6TO4INIT=no
#DHCP_CLIENT=dhclient
NEEDHOSTNAME=no
PEERDNS=yes
PEERYP=yes
PEERNTPD=no

Link to comment
Share on other sites

Your routing looks fine.

 

First, try and ping your gateway, does it reply? Secondly, check /etc/resolv.conf to see if you have DNS entries configured in it.

 

If you're route is wrong, then edit /etc/sysconfig/network, the gateway is normally set in here, or /etc/sysconfig/network-scripts/ifcfg-wlan0 or ifcfg-eth0 depending on what you're interface is called. The gateway is set in either of these places.

 

To test internet connectivity, just do:

 

host linux.org

 

from the command prompt to see if if resolves dns correctly.

Link to comment
Share on other sites

Thanks for the reply.

 

I've had a go at pinging the gateway and there's no response. My resolv.conf is copied out above. Does it look OK?

 

The gateway is set OK in /etc/sysconfig/network.

 

What's the 169.254.0.0 address coming up with 'route -n' command?

 

Any further thoughts?

 

Chris

Link to comment
Share on other sites

What encryption are you using on your wireless? WPA or WEP? I would suggest removing the encryption and trying to get it working without it.

 

Once you know it's working without encryption, then start enabling encryption to get it working with that. Best way to troubleshoot. You can't ping your gateway so it's either a problem with encryption, or your wireless card, but with encryption enabled, you can't figure out which one is the problem.

Link to comment
Share on other sites

  • 1 month later...

Hi.

 

Have tried with no encryption and with WEP and neither work. Can't ping the gateway with or without WEP. Can't get a DHCP address even. Giving it a static address doesn't seem to work either.

 

Any other suggestions please?

 

Thanks,

Chris

Link to comment
Share on other sites

That difference between the gateway ip and the network ip is normal. Here's my routing table which is pretty vanilla:

 

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	 10	 0		0 eth0
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	10	 0		0 eth0

 

I agree that the routing table seems wrong - it has no entry for 127.0.0.0 and he has no idea what 169.254.0.0 is. All this points to a misconfiguration of the network probably caused by the botched attempt at configuration using the mcc tools.

 

Rather than trying to track down exactly what went wrong, I would suggest removing wlan0 using the mcc tools. Make sure that ifcfg-wlan0 is deleted in the process. If not, delete it by hand. Then confirm that wlan0 is no longer up by opening a console and checking with:

 

# ifconfig

 

There should be no entry for wlan0. Wlan0 should still be detected with iwconfig if the ndiswrapper is still loaded. Confirm this is the case with:

 

# iwconfig

 

If it's not there, load the ndiswrapper driver and check again with:

 

# modprobe ndiswrapper

# wlan0

 

Assuming wlan0 is detected, I would try to get it running from the command line. First, for simplicity, disable any encryption from your router. Then run:

 

# iwconfig wlan0 essid <insert your essid name>

# dhclient wlan0

 

If it doesn't hang on dhclient and report an error, this should connect you with your router using dhcp. Check that everything is OK by pinging your router and running route -n. Then see if you can get on the internet.

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...