Check_connection issue

Software SW help
1

I’ve realized that turris claims that there is connection issue and DNS does not work (using forris checks).

Running check_connection sched some light on it:
# check_connection
Pinging 94.241.xxx.xxx … FAILED
IPv4 Gateway: FAILED
IPv4: FAILED
IPv6 Gateway: FAILED
IPv6: FAILED
DNS: FAILED
DNSSEC: FAILED

Yes, ping to the default gateway did not work. Hard to say why ISP block ICMP on default GW but it causes all subsequent tests reports a failure.
If I fake IP4 GW test in a copy of check_postgres:

RES_IP4_G=true
RES_IP4=false
RES_IP6_G=false
RES_IP6=false
RES_DNS=false
RES_DNSSEC=false

Then subsequent tests are performed and can report their results:

Pinging 94.241.112.1 ... FAILED
IPv4 Gateway: OK
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
IPv6 Gateway: FAILED
IPv6: FAILED
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

Despite I’ll treat the default GW not responding for ping as an issue, would it be possible to modify check_connection not to give up all subsequent tests?

2

do you have enabled/active “Allow-ping” ,“Allow-IGMP” rule(s) in (luci>firewall>traffic rules)?

3

Yes, it is enabled:

obrazek
obrazek997×84 6.27 KB

If I switch ISP, than gw ping works, without any changes, the sad thing is, that new ISP blocks it, I have no clue wh, except it might be a side effect of having public IP, before they configured the public address it worked. But the ky point here is, that I thought it might make sense to continue with tests even if GW ping does not work as expected (and I have a homework in the meantime to communicate with my ISP).

1 Like