LinHES Forums
http://forum.linhes.org/

Can't connect to my Router. Any ideas? [Now unsolved.]
http://forum.linhes.org/viewtopic.php?f=6&t=10915		 Page 1 of 1
Author:  tophee [ Sat Jul 22, 2006 12:49 am ]
Post subject:  Can't connect to my Router. Any ideas? [Now unsolved.]
Morning all,
At the moment I am a bit stuck with my wireless internet connection, or more accurately: I am I'm not getting a dhcp connection from my router when my wireless card requests one.

The card in my Mythenbox is a Netgear WG311T 108Mbps Wireless PCI Adaptor.

My router is a Netgear WGT624v3 108Mbps.

I have upgraded madwifi to the latest driver 0.9.1 and my wireless card can 'see' my router with the iwconfig command -it tells me the SSID and everything. Infact it sees several other wireless networks broadcasting around here.

But when I try and connect to it using the dhclient ath0 command it looks for my router but doesn't get and fails to get any DHCPOFFERS and Sleeps.

I've been on to Netgear and they were ultimately unhelpful as they don't know anyhting about Linux.

Very fraustrating. I'm beginning to think there is a problem with the router's wireless capability. -I tried with my Ma's Windows laptop a couple month or so back and I couldn't get it to connect to that.

Has anyone any experience of similar problems and know anything else I can try? Or is it just my router.

Any thoughts or experiences greatly recieved as I want to get this sorted as it's the last major hurdle I have. Everything else apart from DVB radio) (Cecil-hopefully next relase???) is sorted. Oh and getting support to ram to work.

Thanks for reading.
Author:  mac [ Sat Jul 22, 2006 3:31 am ]
Post subject: 
post the output related to your AP from the command:
iwlist ath0 scanning

and the output from iwconfig

maybe we will be able to see what is going on.

try a static ip address of 192.168.1.10 and set your default gw to 192.168.1.1
then see if you can ping 192.168.1.1.
Author:  tophee [ Sun Jul 23, 2006 4:21 am ]
Post subject: 
Hi mac,
Thanks for the reply. I wasn't able to look at this yesterday, but I've been tinkering for a while this morning.

I decided to start from scratch and had a degree of limited success. Unfortunately not enough success to warrent any sort of jubilance or celebration.

I managed briefly to connect to the router by dhclient after a complete unistall/reinstall of the madwifi drivers. But I couldn't do much more than get a connection to the router. I tried to ping a web address and I wan't able to ping it and get a responce.

Right before I go any further I will answer some of the questions you asked me and hopefull it will answer some of your questions too.
Oh and I've been following the madwifi newbi guide seen here: http://madwifi.org/wiki/UserDocs/FirstTimeHowTo

iwlist ath0 scanning doesn't work for me. Apparently ath0 chipset doesn't support it.

I did run wlanconfig ath0 list scan

The responce I got was this
Code:
SSID    BSSID                      CHAN  RATE  S:N   INT   EXPS
KAFKA  00:14:6c:45:e8:17     6         54M   4:0   100   EPSs   ATH


iwconfig gives me

Code:
IEEE 802.11g  ESSID "KAFKA"  Mode Managed 
Channel: 0  Access Point 00:00:00:00:00:00
BitRate: 0ks  Power: 18dBm Sensitivity: 0/13
Retry: off RTS thr: off Fragment: off
Encryption key: xxxxxx
Security mode: restricted


I did this after I set the WEP key.

Also: I tried iwlist ath0 scan before I set the WEP key.
Code:
Cell 01 - Address: 00:14:6c:45:e8:17
                    ESSID:"KAFKA"
                    Mode:Master
                    Frequency:2.437 GHz (Channel 6)
                    Quality=57/94  Signal level=-38 dBm  Noise level=-95 dBm
                    Encryption key:off
                    Bit Rate:1 Mb/s
                    Bit Rate:2 Mb/s
                    Bit Rate:5.5 Mb/s
                    Bit Rate:11 Mb/s
                    Bit Rate:18 Mb/s
                    Bit Rate:24 Mb/s
                    Bit Rate:36 Mb/s
                    Bit Rate:54 Mb/s
                    Bit Rate:6 Mb/s
                    Bit Rate:9 Mb/s
                    Bit Rate:12 Mb/s
                    Bit Rate:48 Mb/s
                    Extra:bcn_int=100


When I did dhclient ath0 the first time it went through and connected. Now after adding the WEP key I get this.

Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.

Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html

Code:
wifi1: unknown hardware address type 801
sit0: unknown hardware address type 776
wifi1: unknown hardware address type 801
sit0: unknown hardware address type 776
Listening on LPF/ath0/00:14:6c:2c:82:f0
Sending on   LPF/ath0/00:14:6c:2c:82:f0
Sending on   Socket/fallback/fallback-net
DHCPDISCOVER on ath0 to 255.255.255.255 port 67
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 2
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval  10
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval  4
No DHCPOFFER recieved
Trying recorded lease 192.168.1.3
Ping 192.168.1.1 (192.168.1.1) 56(84) bytes of data


--- 192.168.1.1 ping statistics ---
1 packets transmitted 0 recieved =1 errors 100% packet loss
timeout
bound to 192.168.1.1 -- renewal in 37822 seconds.


So, not that much further. But at least some progress which is heartening.

I don't really understand how to set up a static address or where to put information into at the moment. I will look into it further, but any pointers would be good.
Author:  mac [ Sun Jul 23, 2006 6:49 am ]
Post subject: 
so it sort of works without the WEP key but not with?

when you did the ping, do you use an IP or the name? If you used a name try an IP instead.
Try 66.102.7.147.

If you get respone from the ping to the IP address, configure router to use the name servers
for provider.

to staticly IP your box and setup the default gw:

ifconfig ath0 192.168.1.3 netmask 255.255.255.0
route add default gw 192.168.1.1
Author:  tophee [ Mon Jul 24, 2006 4:39 am ]
Post subject: 
Hi mac,
Well, I set up a static route on my router. I was able to fille the appropriate boxes with the details you supplied. (Hope I got it right.)

ONthe static routes page of my router
Code:
 
Static Routes
 
Route Name                 Myth Box

Destination IP Address    192.168.1.3

IP Subnet Mask              255.255.255.0

Gateway IP Address    192.168.1.1

Metric                            2


On my myht box, I entered ifconfig ath0 192.168.1.3 netmask 255.255.255.0 no problem.

On attempting the second command route add default gw 192.168.1.1

I get this:
Code:
Usage: inet_route [-vF] del {-host ¦-net} Target [/prefix] [gw Gw] [metric M] [network]

inet_route [-vF] add {-host ¦-net} Target [/prefix] [gw Gw] [metric M] [network] [mss Mss] [window W] [irtt I] [mod] [dyn] {reinstate} [[dev] If]

inet_route [-vF] add {-host ¦-net} Target [/prefix] [gw Gw] [metric M] reject

inet_route [-FC] flush NOT supported


Hopefully I've made no errors in transcribing that output. With no nework I can't cut and paste.

Any more thoughts?
Author:  mac [ Mon Jul 24, 2006 7:14 pm ]
Post subject: 
default route is mute if you can't ping 192.168.1.1
Author:  tophee [ Tue Jul 25, 2006 5:01 am ]
Post subject: 
Ok, if it's default to mute how do I do something about it?

I've managed to set up a reserved address for my mythbox on my router. I discovered what it's MAC address was, which helped. Then went through the early steps of the Madwifi beginners guide I was following. This time everyting worked in the sense of I got no weird outputs to the command route add default gw 192.168.1.1.

when I dhclient ath0 and it found the router first time. I did get an unusual message though. During the DHCP sequence I got this message displayed:
Quote:
ip length 314 disagrees with bytes recieved 534
accepting packet with data after udp payload


When I try and ping anything the ping hangs. It tries to send it's package, but doesn't get anything back. It just sits there and I have to reboot to get it to stop.

So things are moving forward. Could the problem be that when I installed the madwifi drivers I recieved a message that this version of madwifi supports upto version 19 while my kernal only supports up to 17 and some things may be broken have anything to do with it?
Author:  mac [ Tue Jul 25, 2006 6:32 am ]
Post subject: 
does it work without WEP?
Author:  tophee [ Tue Jul 25, 2006 1:00 pm ]
Post subject: 
I'll try, though previously I managed to get as far as this without WEP and only once, which I described in an earlier post.
That time I couldn't ping anything either.
At least I'm learning something - though until I get it to work I won't be sure how much I've learnt...
Author:  tophee [ Mon Aug 21, 2006 4:56 am ]
Post subject: 
Solved, though I'm not quite sure how. A techy mate of mine had a fiddle with the router and it connected.
No idea what he did exactly, but he reduced the available addresses to 16. We entered the essid, the channel and the wep key in netconfig. (was reinstalling Myth) and it just worked.
Weird.
Page 1 of 1 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/