Hi All,
First post hear... I have an old ASUS RT N66u router running the latest version of asuswrt merlin that will work on the router (meaning it's still all rather old and before anyone suggests to just get a new router - I will be investing in a NAS which can do all this but I need an interim solution in the meantime whilst I save up).
The old router is now being used as a wifi access point at the moment as my ISP gave me a new (but more basic) router but one which could handle the faster internet speeds (the PS4 updates as a result are now alot faster) which keeps my kids off my back!
However, the newer router doesn't have VPN but can redirect / port forward so I thought I would find out how I could continue to use the VPN on my old router. After some research, I've tried a few commands but they don't seem to stick on reboot or give some errors when setting up. i also need the Dynamic DNS service to continue to work so that i can continue to connect when away from home, but again need that service to work through the router's LAN port and not WAN. My need is I want to use a home based VPN rather than these online VPN subscription sites, so they are not an option to me.
So a couple of issues there but in theory is this possible?
This is where I got to:
new router gateway is 192.168.1.253
my old router IP is set to 192.168.1.254
DHCP is disabled on the old ASUS router. DHCP on the new router is set from 192.168.1.10 thru 192.168.1.250, subnet mask is 255.255.255.0
After a bit of research these were the commands I used whilst connected to the old router via telnet
so I'm making making sure the wan0 is static and is set to .254. I'm making sure the netmask is the same as the new router and I'm telling it the new router (ie gateway) has an IP ending .253. I'm then telling it that the WAN should be talking through the LAN ports (any: br0) (I did also try changing it to eth1 when I was having issue but this didn't really seem to help). I'm then telling it to save and then reboot.
At first the setup wouldn't stick i kept getting 0.0.0.0 for the IP's and i couldn't ping the outside world eg. 8.8.8.8.
So I tried to update some settings from the webUI of the router. I went to the WAN menu where there was a section called WAN IP Setting and I included the IP address (192.168.1.254) , Subnet Mask (255.255.255.0) and Default Gateway (192.168.1.253). That allowed a few more settings to stick.
So the (new) router gateway is now sticking but not my old router's IP
so I repeated the setup again (trying eth1 instead of br0).
and used these commands to check the output
this is what resulted but pinging the outside world (eg. 8.8.8.8) still wouldn't work
I then used the command
route -n
and
ip route
..to show more details which returned the following
so I think the routing table is missing the gateway / a default route so I worked out to use the below command to add a default route but it gave an error:
route: SIOCADDRT: No such process[/CODE]
I also tried this method but it gave another but different error
RTNETLINK answers: No such process[/CODE]
This is the point I got to. Pinging 8.8.8.8 still no success (from within the telnet / old router console). The key thing was to prove that via the old routers interface (via telnet) I could ping the new router (192.168.1.253) and the outside world (8.8.8.8). FYI, connecting via wifi to the old router which is then connected LAN-LAN on my laptop I could ping both the new router and the outside world.
I think there are a number of issues here but the main one being it keeps loosing the info needed in the routing table
the below seems to show progress but it keeps being lost on reboot:
returns:
It's the 0.0.0.0 → 192.168.1.253 via eth1 is what I need to keep in place I assume?
For some reason after doing the 'nvram commit' and then reboot it is lost again. I did also try 'nvram commit' followed by 'sync' and then 'reboot' but it made no difference.
So... I think I've reached the end of my limited knowledge and am also now confusing myself on what steps I do and don't need... there are signs of me getting there but the problem is it most likely needs a startup script to keep the settings plus I haven't even considered the need to setup the DDNS yet. I have zero knowledge of script writing but if you think it would resolve the issues, please could someone help (so that making sure I can connect LAN-LAN to the old router and from the old router telnet console I can ping 192.168.1.253 and 8.8.8.8 and also ensuring the DDNS (i use the ASUS one) will let me call home plus some some logging would be good to know things have changed.
Thanks in advance
RodP
First post hear... I have an old ASUS RT N66u router running the latest version of asuswrt merlin that will work on the router (meaning it's still all rather old and before anyone suggests to just get a new router - I will be investing in a NAS which can do all this but I need an interim solution in the meantime whilst I save up).
The old router is now being used as a wifi access point at the moment as my ISP gave me a new (but more basic) router but one which could handle the faster internet speeds (the PS4 updates as a result are now alot faster) which keeps my kids off my back!

However, the newer router doesn't have VPN but can redirect / port forward so I thought I would find out how I could continue to use the VPN on my old router. After some research, I've tried a few commands but they don't seem to stick on reboot or give some errors when setting up. i also need the Dynamic DNS service to continue to work so that i can continue to connect when away from home, but again need that service to work through the router's LAN port and not WAN. My need is I want to use a home based VPN rather than these online VPN subscription sites, so they are not an option to me.
So a couple of issues there but in theory is this possible?
This is where I got to:
new router gateway is 192.168.1.253
my old router IP is set to 192.168.1.254
DHCP is disabled on the old ASUS router. DHCP on the new router is set from 192.168.1.10 thru 192.168.1.250, subnet mask is 255.255.255.0
After a bit of research these were the commands I used whilst connected to the old router via telnet
Code:
nvram set wan0_proto=static
nvram set wan0_ipaddr=192.168.1.254
nvram set wan0_netmask=255.255.255.0
nvram set wan0_gateway=192.168.1.253
nvram set wan_ifname=br0
nvram commit
reboot
so I'm making making sure the wan0 is static and is set to .254. I'm making sure the netmask is the same as the new router and I'm telling it the new router (ie gateway) has an IP ending .253. I'm then telling it that the WAN should be talking through the LAN ports (any: br0) (I did also try changing it to eth1 when I was having issue but this didn't really seem to help). I'm then telling it to save and then reboot.
At first the setup wouldn't stick i kept getting 0.0.0.0 for the IP's and i couldn't ping the outside world eg. 8.8.8.8.
So I tried to update some settings from the webUI of the router. I went to the WAN menu where there was a section called WAN IP Setting and I included the IP address (192.168.1.254) , Subnet Mask (255.255.255.0) and Default Gateway (192.168.1.253). That allowed a few more settings to stick.
Code:
wan0_ipaddr=0.0.0.0
wan0_proto=static
wan0_proto_t=
wan0_gateway=0.0.0.0
wan0_gateway_x=192.168.1.253
wan_ifnames=eth0
size: 53416 bytes (12120 left)
wan_ifname=eth1
wan0_ipaddr_x=192.168.1.254
So the (new) router gateway is now sticking but not my old router's IP
so I repeated the setup again (trying eth1 instead of br0).
Code:
nvram set wan0_proto=static
nvram set wan0_ipaddr=192.168.1.254
nvram set wan0_netmask=255.255.255.0
nvram set wan0_gateway=192.168.1.253
nvram set wan_ifname=eth1
nvram commit
reboot
and used these commands to check the output
Code:
nvram get wan0_ipaddr
nvram get wan0_gateway
nvram get wan_ifname
this is what resulted but pinging the outside world (eg. 8.8.8.8) still wouldn't work
Code:
wan0_ipaddr=192.168.1.254
wan0_proto=stati
wan0_proto_t=
wan0_gateway=192.168.1.253
wan0_gateway_x=192.168.1.253
wan_ifnames=eth0
size: 53446 bytes (12090 left)
wan_ifname=eth1
wan0_ipaddr_x=192.168.1.254
I then used the command
route -n
and
ip route
..to show more details which returned the following
Code:
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 0 0 0 br0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
so I think the routing table is missing the gateway / a default route so I worked out to use the below command to add a default route but it gave an error:
Code:
route add default gw 192.168.1.253 eth1
I also tried this method but it gave another but different error
Code:
ip route add default via 192.168.1.253 dev eth1
This is the point I got to. Pinging 8.8.8.8 still no success (from within the telnet / old router console). The key thing was to prove that via the old routers interface (via telnet) I could ping the new router (192.168.1.253) and the outside world (8.8.8.8). FYI, connecting via wifi to the old router which is then connected LAN-LAN on my laptop I could ping both the new router and the outside world.
I think there are a number of issues here but the main one being it keeps loosing the info needed in the routing table
the below seems to show progress but it keeps being lost on reboot:
Code:
/tmp/home/root# ifconfig eth1 192.168.1.254 netmask 255.255.255.0 up
/tmp/home/root# route add default gw 192.168.1.253 dev eth1
/tmp/home/root# route -n
returns:
Code:
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 0 0 0 br0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 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.253 0.0.0.0 UG 0 0 0 eth1
It's the 0.0.0.0 → 192.168.1.253 via eth1 is what I need to keep in place I assume?
For some reason after doing the 'nvram commit' and then reboot it is lost again. I did also try 'nvram commit' followed by 'sync' and then 'reboot' but it made no difference.
So... I think I've reached the end of my limited knowledge and am also now confusing myself on what steps I do and don't need... there are signs of me getting there but the problem is it most likely needs a startup script to keep the settings plus I haven't even considered the need to setup the DDNS yet. I have zero knowledge of script writing but if you think it would resolve the issues, please could someone help (so that making sure I can connect LAN-LAN to the old router and from the old router telnet console I can ping 192.168.1.253 and 8.8.8.8 and also ensuring the DDNS (i use the ASUS one) will let me call home plus some some logging would be good to know things have changed.
Thanks in advance
RodP