Gateway Connection problem

Software SW help
1

Hello,

had seen by pure coincidence that the connection to the gateway did not work with ipv4 (in Foris)
All other points worked and the DNS and DNSSEC test also worked.
What could be the error here?
I had already restarted the modem

The console says so:

/$ check_connection
Pinging 100.101.0.1 ... FAILED
IPv4 Gateway: FAILED
Pinging 217.31.205.50 ... OK
Pinging 198.41.0.4 ... OK
Pinging 199.7.83.42 ... OK
Pinging 8.8.8.8... OK
IPv4: OK
Pinging fe80::201:5cff:feb4:bde4%eth0... OK
IPv6 Gateway: OK
Pinging 2001:1488:0:3:2... OK
Pinging 2001:500:3::42... OK
Pinging 2001:500:2d::d ... OK
Pinging 2606:2800:220:6d:26bf:1447:1097:aa7 ... OK
IPv6: OK
Resolving api.turris.cz... OK
Resolving www.nic.cz ... OK
Resolving c.root-servers.net... OK
DNS: OK
Resolving www.rhybar.cz ... OK
DNSSEC: OK

And that’s the status in Luci:

IPv4 upstream
Protocol: DHCP Client
Address: 100.101.4.83
network mask: 255.255.192.0
gateway: 100.101.0.1
DNS 1: 62.117.5.126
DNS 2: 217,68,162,126
Expired: 24h 13m 11s
Connected: 20h 30m 58s

Best regards

2

That is a known shortfall [1] of the script and will not fix [2]

[1] https://gitlab.labs.nic.cz/turris/foris-controller/foris-controller/issues/74
[2] https://gitlab.labs.nic.cz/turris/turris-os-packages/merge_requests/131

3

Okay, that sounds plausible but what makes me wonder why did it work until a few days ago and not anymore? Did the ISP prevent this for security reasons when NAT is active? My ipv4 connection is NAT I know that.

4

what happens when you ping the ISP gateway? Maybe the ISP implemented a firewall rule that drops ICMPv4 type 0.

5

This is going into a “timeout.”
You’re probably right about that.