Skip to main content
added 20 characters in body
Source Link
Giacomo1968
  • 56.1k
  • 23
  • 167
  • 214

By far the simplest solution is to move your modem or your LAN to a different subnet.

Eg: Modem 192.168.1.1 Router 192.168.2.1

  • Modem: 192.168.1.1
  • Router: 192.168.2.1

Then it wont have the modem as part of the DHCP pool and will treat it as a remote network  (all remote networks go via the same port withe a "router“router on a stick"stick”).

ItsIt’s not uncommon for modems to change over to 192.168.100.1192.168.100.1 or similar when bridging for this very reason.

By far the simplest solution is to move your modem or your LAN to a different subnet.

Eg: Modem 192.168.1.1 Router 192.168.2.1

Then it wont have the modem as part of the DHCP pool and will treat it as a remote network(all remote networks go via the same port withe a "router on a stick").

Its not uncommon for modems to change over to 192.168.100.1 or similar when bridging for this very reason.

By far the simplest solution is to move your modem or your LAN to a different subnet.

Eg:

  • Modem: 192.168.1.1
  • Router: 192.168.2.1

Then it wont have the modem as part of the DHCP pool and will treat it as a remote network  (all remote networks go via the same port withe a “router on a stick”).

It’s not uncommon for modems to change over to 192.168.100.1 or similar when bridging for this very reason.

Source Link
Linef4ult
  • 4k
  • 18
  • 21

By far the simplest solution is to move your modem or your LAN to a different subnet.

Eg: Modem 192.168.1.1 Router 192.168.2.1

Then it wont have the modem as part of the DHCP pool and will treat it as a remote network(all remote networks go via the same port withe a "router on a stick").

Its not uncommon for modems to change over to 192.168.100.1 or similar when bridging for this very reason.