#### LAN configuration
config interface lan
option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.0.110
option netmask 255.255.255.0
option gateway 192.168.0.1
option dns 8.8.8.8
#### WAN configuration
config interface wan
option ifname "eth0.1"
option proto dhcp
If you follow the instructions here you should be able to ssh to the router over the wireless network. You'll have to figure out the IP for the wireless interface first.
I think you want to disable bridging on the LAN and move the wireless to "option network wan". Back up your original files in case you need to go back!
#### LAN configuration
config interface lan
#option type bridge
option ifname "eth0.0"
option proto static
option ipaddr 192.168.0.110
option netmask 255.255.255.0
option gateway 192.168.0.1
option dns 8.8.8.8
#### WAN configuration
config interface wan
option ifname "eth0.1"
option proto static
option ipaddr 192.168.0.110
option netmask 255.255.255.0
option gateway 192.168.0.1
option dns 8.8.8.8
I just rebooted the router after applying these changes and now the router is up and running. I'll just have to give it some time see what happens.
Another interesting thing worth mentioning is the fact that when I pinged it all night from a PC, it did not get off line. I will stop the ping now and with the new network config file, I'll wait to see if it goes offline.
There is really nothing unusual about the network. The router is a Linksys WRTU54G-TM.
I had it for about 2 years now and no problems whatsoever.
I have a PS3 and a Wii on the network as well and those do not loose connectivity.
Again, as I mentioned in the previous post: The router did not loose wireless while I was pinging it all night (about 12 hours).
Don't you think that's odd?
I think when it is being solicited to respond to something or to run a service it stays online. When I didn't ping it it still ran the MPD, but it lost connection, but pinging it, it was required to respond and it didn't loose it.
What do you think?
My suspicion is that there is no (zero) activity on the wireless connection to the WL-520gU if you are not streaming music or pinging, so one side or the other is losing the DHCP lease or dropping the connection. It is not so strange, because usually you will have some kind of periodic network activity that would keep the connection alive. In my case, I never use the radio without it streaming music (I simply turn it off when not in use) so I have not encountered this issue. That said, I left the radio on overnight (with mpd stopped) and I was still able to communicate with it in the morning.
I believe the solution is to either change the DHCP lease time on your WRT54G, or modify the networking settings on the WL-520 to add a keepalive or figure out why it is not periodically renewing the DHCP lease (which I believe it should).
I agree, it should keep the DHCP lease as the Linksys's DHCP timer is at 0 (zero) - meaning 7 days.
Remember yesterday I was pinging from the Asus and lost connection. Last night until this morning I was pinging the Asus from my PC at it didn't.
Anyways, how do I add a line and where for a keep alive timer? I think it's worth a try.
# set leds to normal state
. /etc/diag.sh
set_state done
# ping forever
ping 192.168.0.1 &
}
Or create a new boot script for it, using one of the existing ones an an example (and create a link in /etc/rc.d)... I'm not sure what the "correct" way to do this is.
Another option would be to create a cron job that runs once every minute or so and executes the ping command. There is lots of info online about using cron.