Forum Discussion
opnspaces
Aug 06, 2019Navigator III
I'm not an expert on this stuff, but I am curious as I find computer issues kind of fun. In thinking about what you found, it seems like dot 2 router allowed a pass through from dot 1 to the PC's behind dot2 which to me is a bit concerning. The first question I would ask would be is dot 2 running the latest firmware?
I know you didn't give makes and models of equipment, and really it's probably not all that important. But is dot 2 a standard consumer grade router like a linksys or Dlink running the standard firmware or DDWRT? Or are you running something more configurable like an Edgerouter or Mikrotik?
If running consumer grade I'm assuming you are plugging the LAN port of dot 1 into the WAN port of dot 2. If not running through the WAN port how are you preventing DHCP from getting to the dot 2 computers? If wired dot 1 LAN to dot 2 LAN then potentially the only thing keeping dot 1 from serving DHCP is the luck of the draw as the computers boot up.
Here's a test that takes a bit to setup but might be interesting.
Use 1 or more PC's on dot 2
configure static IP's to the dot 1 network like maybe
computer 1
Ip: 192.168.1.157
Subnet: 255.255.255.0
Gateway: 102.168.1.1
computer 2
Ip: 192.168.1.158
Subnet: 255.255.255.0
Gateway: 102.168.1.1
computer 3
Ip: 192.168.1.159
Subnet: 255.255.255.0
Gateway: 102.168.1.1
All three should lose internet connectivity.
now on each PC run a continuous ping to dot 1
ping -t 192.168.1.1
Reboot dot 2. Once dot 2 is up and running stop the pings (CTRL C). Scroll up on the PC screens and see if at any time during the reboot of dot 2 do any of the computers get a successful reply on the ping to dot 1?
I see what RLS7201 is suggesting and I'm trying to wrap my head around if it's a problem or not as I have the same basic setup at my house of a router in the garage with an IP on my local LAN. But like I was asking about above; My garage router is using the WAN port so that shouldn't be a problem, but it's DHCP range is .3 not .2 for anything downstream.
I know you didn't give makes and models of equipment, and really it's probably not all that important. But is dot 2 a standard consumer grade router like a linksys or Dlink running the standard firmware or DDWRT? Or are you running something more configurable like an Edgerouter or Mikrotik?
If running consumer grade I'm assuming you are plugging the LAN port of dot 1 into the WAN port of dot 2. If not running through the WAN port how are you preventing DHCP from getting to the dot 2 computers? If wired dot 1 LAN to dot 2 LAN then potentially the only thing keeping dot 1 from serving DHCP is the luck of the draw as the computers boot up.
Here's a test that takes a bit to setup but might be interesting.
Use 1 or more PC's on dot 2
configure static IP's to the dot 1 network like maybe
computer 1
Ip: 192.168.1.157
Subnet: 255.255.255.0
Gateway: 102.168.1.1
computer 2
Ip: 192.168.1.158
Subnet: 255.255.255.0
Gateway: 102.168.1.1
computer 3
Ip: 192.168.1.159
Subnet: 255.255.255.0
Gateway: 102.168.1.1
All three should lose internet connectivity.
now on each PC run a continuous ping to dot 1
ping -t 192.168.1.1
Reboot dot 2. Once dot 2 is up and running stop the pings (CTRL C). Scroll up on the PC screens and see if at any time during the reboot of dot 2 do any of the computers get a successful reply on the ping to dot 1?
I see what RLS7201 is suggesting and I'm trying to wrap my head around if it's a problem or not as I have the same basic setup at my house of a router in the garage with an IP on my local LAN. But like I was asking about above; My garage router is using the WAN port so that shouldn't be a problem, but it's DHCP range is .3 not .2 for anything downstream.
About RV Must Haves
Have a product you cannot live without? Share it with the community!8,805 PostsLatest Activity: Aug 02, 2025