Member_2_6558702
asked on
No Internet Access on secondary router connected LAN-WAN
I have a Netgear R7000V2 router as my primary router. I have connected a second router flashed with Tomato which servers as my secondary router. One of the LAN ports from the secondary router is connected to the WAN port of the primary router. My configuration is as follows:
Primary (WAN port connected to Internet)
LAN IP Address 192.168.0.1
DHCP enabled serving 192.168.0.100 - 192.168.0.149
Static Route added - Destination IP 192.168.2.0 ; IP Subnet Mask 255.255.255.0 ; Gateway IP Address 192.168.0.110
Metric 2
IP Address reserved for secondary router 192.168.0.110
Secondary Router
WAN Configuration:
IP Address 192.168.0.110
Subnet Mask 255.255.255.0
Gateway 192.168.0.1
LAN Configuration
IP Address 192.168.2.1
Subnet Mask 255.255.255.0
DHCP enabled serving addresses 192.168.2.100 - 192.168.2.149
Router Mode
Firewall disabled via firewall script
# disable firewall
iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
I need both subnets communicate with each other for filesharing etc. I also need internet access for all PCs across both subnets. Currently I am able to communicate between the subnets using IP addressing but not able to use hostnames. PCs on the secondary router (192.168.2.0 subnet) are not able to access the internet. From the secondary router I'm able to ping google.com and other various websites using the built in Ping and Trace Route tool. I know I can connect the routers LAN-LAN (I had this configuration originally) but I have a unique scenario involving a VPN where this configuration wasn't working for me so I switched the this setup. I'm struggling to figure out what is preventing internet access from the second subnet. Please help!
Primary (WAN port connected to Internet)
LAN IP Address 192.168.0.1
DHCP enabled serving 192.168.0.100 - 192.168.0.149
Static Route added - Destination IP 192.168.2.0 ; IP Subnet Mask 255.255.255.0 ; Gateway IP Address 192.168.0.110
Metric 2
IP Address reserved for secondary router 192.168.0.110
Secondary Router
WAN Configuration:
IP Address 192.168.0.110
Subnet Mask 255.255.255.0
Gateway 192.168.0.1
LAN Configuration
IP Address 192.168.2.1
Subnet Mask 255.255.255.0
DHCP enabled serving addresses 192.168.2.100 - 192.168.2.149
Router Mode
Firewall disabled via firewall script
# disable firewall
iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
I need both subnets communicate with each other for filesharing etc. I also need internet access for all PCs across both subnets. Currently I am able to communicate between the subnets using IP addressing but not able to use hostnames. PCs on the secondary router (192.168.2.0 subnet) are not able to access the internet. From the secondary router I'm able to ping google.com and other various websites using the built in Ping and Trace Route tool. I know I can connect the routers LAN-LAN (I had this configuration originally) but I have a unique scenario involving a VPN where this configuration wasn't working for me so I switched the this setup. I'm struggling to figure out what is preventing internet access from the second subnet. Please help!
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Hostname-lookup in a windows environment can be tricky. All windows (and samba) boxes on a subnet will elect a 'master browser', which usually acts as a WINS server as well. This is largely a broadcast-based process, so it is contained within the subnet.
You should be able to push down WINS settings via DHCP, so you could force all machines to use a single server.
If you happen to have a Windows Server on the network, just use that and use DNS instead of WINS, it's much more robust.