asked on
Specify next hop on a DD-wrt router
I’m trying to setup a second subnet that will have internet access and be accessible from the outside via RDP.
I have the following:
Cable modem >>>>>> Linksys E1500 >>>>>>>>>>>>>>>>>>>>>>> WAN port of WRT-54G
DD-WRT (Sp2) DD-wrt (V24-SP1)
192.168.1.1 192.168.2.1
If I leave the WRT-54G set to Gateway mode I can get to the internet but nothing from outside (RDP) can get in. I changed the mode to router on the WRT and set it to a fixed IP:
WAN IP 192.168.1.2
Subnet 255.255.255.0
Gateway 192.168.1.1
DNS 192.168.1.1
Dropped the firewall on both routers. What I don’t understand is how to specify the next hop for the WRT-54G. I can’t get on the net in router mode only Gateway mode. I can’t ping 192.168.1.1 from 192.168.2.144 (just some workstation).
In the E1500 I have created a route that looks like:
Destination LAN Net 192.168.2.0
Subnet mask 255.255.255.0
Gateway 192.168.1.2
I’ve tried to follow the instructions in http://www.dd-wrt.com/wiki/index.php/Linking_Subnets_with_Static_Routes but just can’t get communication with the WRT-54G in router mode.
So the question: How do I tell 192.168.2.1 to use 192.168.1.1 as its next hop?
I have the following:
Cable modem >>>>>> Linksys E1500 >>>>>>>>>>>>>>>>>>>>>>> WAN port of WRT-54G
DD-WRT (Sp2) DD-wrt (V24-SP1)
192.168.1.1 192.168.2.1
If I leave the WRT-54G set to Gateway mode I can get to the internet but nothing from outside (RDP) can get in. I changed the mode to router on the WRT and set it to a fixed IP:
WAN IP 192.168.1.2
Subnet 255.255.255.0
Gateway 192.168.1.1
DNS 192.168.1.1
Dropped the firewall on both routers. What I don’t understand is how to specify the next hop for the WRT-54G. I can’t get on the net in router mode only Gateway mode. I can’t ping 192.168.1.1 from 192.168.2.144 (just some workstation).
In the E1500 I have created a route that looks like:
Destination LAN Net 192.168.2.0
Subnet mask 255.255.255.0
Gateway 192.168.1.2
I’ve tried to follow the instructions in http://www.dd-wrt.com/wiki/index.php/Linking_Subnets_with_Static_Routes but just can’t get communication with the WRT-54G in router mode.
So the question: How do I tell 192.168.2.1 to use 192.168.1.1 as its next hop?
Network ArchitectureRoutersTCP/IP
Last Comment
ccampbell15
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
I'm a little confused. Router2 is set to router not Gateway which I thought dropped NAT?
I can't ping anything on the router 1 LAN from the router 2 LAN.
No way to unblock the WAN->LAN will be blocked by default?
That implies that the 192.168.2 subnet is completed isolated.
I can't ping anything on the router 1 LAN from the router 2 LAN.
No way to unblock the WAN->LAN will be blocked by default?
That implies that the 192.168.2 subnet is completed isolated.
As long as you have double NAT in those low end routers, no.
The only exception is dmz setting but that applies to only a single IP behind each router.
Base on your drawing, computers in your LAN2 side takes IP address 192.168.2.x with default gateway 192.168.2.1
The default gateway for router2 on the Router2 itself is 192.168.1.1.
In this case, packets going from LAN2 to LAN1 will be NATed and if you were to capture the packets, you will see that by the time the packets leaves router2, its source IP has been changed to 192.168.1.2.
The only exception is dmz setting but that applies to only a single IP behind each router.
Base on your drawing, computers in your LAN2 side takes IP address 192.168.2.x with default gateway 192.168.2.1
The default gateway for router2 on the Router2 itself is 192.168.1.1.
In this case, packets going from LAN2 to LAN1 will be NATed and if you were to capture the packets, you will see that by the time the packets leaves router2, its source IP has been changed to 192.168.1.2.
ASKER
Not sure what 8 hours of sleep did but when I set it up again exactly as stated I can ping both ways and get to the Vlan from the outside with RDP.
routing.docx