Skip to main content
Super User

Return to Answer

Apologies for the absolutely minor edit, I accidentally downvoted and ot was the only way to remove it.
Source Link
Mokubai ♦
Mokubai ♦
  • 93.8k
  • 27
  • 215
  • 245

If you are captive, the network can do pretty much anything it wants with your connection attempts.

So if you choose to go to http://20.20.20.20http://20.20.20.20/, the gateway can respond to those requests itself with a simple http redirect to the login page.

The gateway is not obliged to forward packets to IP addresses beyond itself.

If you are captive, the network can do pretty much anything it wants with your connection attempts.

So if you choose to go to http://20.20.20.20, the gateway can respond to those requests itself with a simple http redirect to the login page.

The gateway is not obliged to forward packets to IP addresses beyond itself.

If you are captive, the network can do pretty much anything it wants with your connection attempts.

So if you choose to go to http://20.20.20.20/, the gateway can respond to those requests itself with a simple http redirect to the login page.

The gateway is not obliged to forward packets to IP addresses beyond itself.

Source Link
Paul
Paul
  • 60.3k
  • 19
  • 152
  • 171

If you are captive, the network can do pretty much anything it wants with your connection attempts.

So if you choose to go to http://20.20.20.20, the gateway can respond to those requests itself with a simple http redirect to the login page.

The gateway is not obliged to forward packets to IP addresses beyond itself.