Perhaps we should look at this another way. Is the DHCP server actually enabled in the RT firmware? It should be by default, but it is worth checking ("Setup->Lan configuration->Configure").
Also, try logging in to the router (via telnet, and have a poke around to see what is going on). The RT firmware has a lot of tools that you can use to peek around (e.g., "top", "traceroute", ifconfig, etc).
Help with wireless
- thechief
- RouterTech Team
- Posts: 12067
- Joined: Wed Feb 01, 2006 10:22 pm
- Location: England, the Centre of Africa
- Contact:
The Chief: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
No support via PM. Ask all questions on the open forum.
ok, I'm not sure what I'm looking for tho.
DHCP is enabled. But I don't think that's the route of the problem, when I gave it a static IP, it still weren't happy."network not availible" or something if I remember correctly.
/proc/net/wireless has no values under the headers.
Loads exist in ifconfig including wlan0.
in /proc/wlan/privacy/wepkeys:
key value: 0x%hX 0x%hX 0x%hX 0x%hX 0x%hX 0x%hX 0x%hX 0x%hX 0x%hX 0x%hX 0x%hX 0x%hX 0x%hX
Although I expect that's for security or something.
Apart from that, I'd need pointers what I'm looking for.
DHCP is enabled. But I don't think that's the route of the problem, when I gave it a static IP, it still weren't happy."network not availible" or something if I remember correctly.
/proc/net/wireless has no values under the headers.
Loads exist in ifconfig including wlan0.
in /proc/wlan/privacy/wepkeys:
key value: 0x%hX 0x%hX 0x%hX 0x%hX 0x%hX 0x%hX 0x%hX 0x%hX 0x%hX 0x%hX 0x%hX 0x%hX 0x%hX
Although I expect that's for security or something.
Apart from that, I'd need pointers what I'm looking for.
- thechief
- RouterTech Team
- Posts: 12067
- Joined: Wed Feb 01, 2006 10:22 pm
- Location: England, the Centre of Africa
- Contact:
We are scratching like chooks here (basically doing the work of a debugger). With these Linux-based firmwares, anything could be the problem (we've already seen the problems caused by IPv6 on client PCs).
What's the output of these commands:
What's the output of these commands:
Code: Select all
cat /proc/modules
cat /proc/interrupts
cat /var/tmp/udhcpd.conf
The Chief: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
No support via PM. Ask all questions on the open forum.
tiap 708536 1thechief wrote:Code: Select all
cat /proc/modules
tiatm 140584 1
avalanche_usb 63296 1
7: 8250514 R4000 timer/counter [MIPS interrupt]thechief wrote:Code: Select all
cat /proc/interrupts
8: 0 unified secondary [hw0 (Avalanche Primary)]
15: 252 serial [hw0 (Avalanche Primary)]
23: 64144 + SAR [hw0 (Avalanche Primary)]
29: 457672 vlynq0 [hw0 (Avalanche Primary)]
32: 1 + USB [hw0 (Avalanche Primary)]
41: 19682 + Cpmac Driver [hw0 (Avalanche Primary)]
47: 156 + DSL [hw0 (Avalanche Primary)]
80: 457670 TNETW1130 [hw0 (Low Vlynq)]
start 192.168.1.2thechief wrote:Code: Select all
cat /var/tmp/udhcpd.conf
end 192.168.1.254
inflease_time 604800
interface br0
opt router 192.168.1.1
opt dns 192.168.1.1
opt subnet 255.255.255.0
opt lease 3600
conflict_time 3600
lease_file /var/tmp/landhcps0.leases
If nothing springs to mind, then don't worry.
Disableling IPv6 is causing problems occasionally on startup, and MSN isn't working (another problem somewhere, dns related somehow I expect).
So I'll send it back and get a new one. D-Link, Belkin or Netgear I expect. Had enough hassels with this one. Thank you for your help.
- thechief
- RouterTech Team
- Posts: 12067
- Joined: Wed Feb 01, 2006 10:22 pm
- Location: England, the Centre of Africa
- Contact:
All the settings are correct, and so it should all be working. It is all weird. If you will buy another router, I would advise to avoid the AR7* chipset platform. Their firmwares are virtually all based on the same kernel and TI web interface. I would be surprised if you didn't have problems with the others also. You may well want to try another chipset.
The Chief: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
No support via PM. Ask all questions on the open forum.