Secondary router can't "see" the internet.

[Rickster]

So i have 2 routers in my house connected via a Ethernet cable in the ceiling, if i log into the router it cant ping the outside world, find firmware updates or use NTP for its time.

What do i need to do to fix this?


PS: People who are connected to this AP via LAN or WiFi DO have internet access, just not the router its self.

 

[Phence]

Maybe disable NAT on router 2 or make sure the cable is connected to a LAN port? It sounds somehow weird that guests have connectivity but not the device.

Actually I don't know it sounds like something that shouldn't be possible.

 

[spydr97]

Seems like the secondary router is in bridge mode so it's basically just a link between the primary router and the devices. It's not actually holding the connection. Reason NTP isn't working is that it's done on the main router and all devices irrespective of whether they're on the main router or the second one are effectively connecting behind the primary router. It's not an AP so that functionality is lost. I'm not sure if it's possible to get it working the way you want, especially given that I have no clue about the specifics of the hardware as well as the settings used. Best way to update the firmware is to back up the profile, put it into router mode, update and then revert.
Sorry I can't be of more help

 

[Rickster]

Seems like the secondary router is in bridge mode so it's basically just a link between the primary router and the devices. It's not actually holding the connection. Reason NTP isn't working is that it's done on the main router and all devices irrespective of whether they're on the main router or the second one are effectively connecting behind the primary router. It's not an AP so that functionality is lost. I'm not sure if it's possible to get it working the way you want, especially given that I have no clue about the specifics of the hardware as well as the settings used. Best way to update the firmware is to back up the profile, put it into router mode, update and then revert.
Sorry I can't be of more help

It probably is in router mode. As this was the main router initially then i got one to replace this so all i did was factory reset it then set it up.

Its a Dlink DIR 825

 

[𝕎𝕚ℤ𝕒𝕣𝕕]

Most basic routers have a WAN side and a LAN side, and they route between these two. Often the LAN side has an integrated ethernet switch and an AP, this all acts as one network. If you connect a second router's LAN to the first one's LAN then they will produce the symptoms described.

For the second router to "see" the internet, it has to have its WAN port connected to the primary router's LAN...

You may have to manually configure the IP settings for the second router, as it may not support DHCP on the WAN port. (see page 34 of the DLink DIR825 manual)
You can get the settings by doing an IPCONFIG /ALL on any PC connected to the primary router. Just use a different IP.

 

[spydr97]

It probably is in router mode. As this was the main router initially then i got one to replace this so all i did was factory reset it then set it up.

Its a Dlink DIR 825

There is one other thing that comes to mind. Make sure the IP addresses of the two routers aren't the same. If you have a clash there it'll prevent the router from accessing anything directly. Disable DHCP on the secondary and statically assign it an open IP address on the router config as well as on the main router side.

 

[Rickster]

Most basic routers have a WAN side and a LAN side, and they route between these two. Often the LAN side has an integrated ethernet switch and an AP, this all acts as one network. If you connect a second router's LAN to the first one's LAN then they will produce the symptoms described.

For the second router to "see" the internet, it has to have its WAN port connected to the primary router's LAN...

You may have to manually configure the IP settings for the second router, as it may not support DHCP on the WAN port. (see page 34 of the DLink DIR825 manual)

Yea its in LAN to LAN, if i plug the cable into the WAN port on the secondary router it breaks everything. Clients cant connect, wifi goes bananas.

 

[Rickster]

There is one other thing that comes to mind. Make sure the IP addresses of the two routers aren't the same. If you have a clash there it'll prevent the router from accessing anything directly. Disable DHCP on the secondary and statically assign it an open IP address on the router config as well as on the main router side.

Yes, they have 2 different IP's DHCP is set to DHCP relay, if turned it off to no avail.

 

[𝕎𝕚ℤ𝕒𝕣𝕕]

Yea its in LAN to LAN, if i plug the cable into the WAN port on the secondary router it breaks everything. Clients cant connect, wifi goes bananas.

Question arrises, do you want the second router to actually ROUTE?

If not, kill the DHCP server on the second router.

Remember, the router expects to find the internet on its WAN port, so you might be forced to connect the WAN to one of the LAN ports (sounds crazy...)

Oops.. I forgot, see page 54, the local network address on the LAN side of the second router must have a different IP from the one assigned to the WAN side (depending on the firmware, this might cause the router to reject IPs with the same subnet range as being in conflict, so set the second router\s LAN IP to a different range. If the primary is on 192.168.x.x set the secondary to 10.0.x.x or some such.