Hey. Hey,

I have an interesting problem with my Vodafone router and modem. Specifically - TP-Link AX73 router and Vodafone Station modem. The modem is in bridge mode, the public IP is set up on the router. The modem itself has a management IP of 192.168.100.1.

I don't understand the reason, but I'm having trouble getting to this IP. Traceroute to this IP is without problem (both directly from the router's diagnostic page and from the computer behind it). However, the ping is not responding, and the HTTP/S requests are also timeouting.

If I turn off the modem (unplug it) and turn it back on, everything works for a while, about one minute. Then the connection starts refusing again and access doesn't work (internet yes, but modem administration no).

It doesn't matter if the SPI Firewall is on or off, it doesn't matter if I create the route manually (192.168.100.0/24 over the WAN) or not at all (all unknown ranges go automatically over the WAN). But it is interesting that as soon as I create a route, it pings with the modem and access to it starts working (again, for a minute or so) and stops again. As soon as I delete the route, the situation repeats. 

It's like something in the background is actively blocking access to this range through the WAN interface (something like BCP38?).

Has anyone encountered this condition? DOCSIS (3.1) from Vodafone CZ.

C:\Users\Petr>ping 192.168.100.1 -t

Pinging 192.168.100.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
--> route to 192.168.100.0 subnet created ...
Reply from 192.168.0.1: Destination net unreachable.
Reply from 192.168.0.1: Destination net unreachable.
Request timed out.
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=30ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=28ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63

... and again ...
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

--> route deleted ...
Reply from 192.168.0.1: Destination net unreachable.
Reply from 192.168.0.1: Destination net unreachable.
Request timed out.
Request timed out.
Reply from 192.168.100.1: bytes=32 time=10ms TTL=63
Reply from 192.168.100.1: bytes=32 time=14ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=7ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63

... and again (no response) ...
Request timed out.
Request timed out.
... (10x)
Request timed out.
Request timed out.

... and all of a sudden, the approach is back on...
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.100.1: bytes=32 time=1999ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
... (50x)
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Request timed out.
... (20x)
Request timed out.
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=20ms TTL=63
... (50x)
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Request timed out.
... (20x)
Request timed out.

Ping statistics for 192.168.100.1:
    Packets: Sent = 440, Received = 199, Lost = 241 (54% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1999ms, Average = 12ms
Control-C
^C