Ok then everything would actually be fine now but the error bothers me, hopefully nothing worrying.
IPv4 gateway connectivity gets “Connection test failed” 
Ping the gateway? Maybe it simply doesnt respond to ping but does the routing.
I have two gateways (mwan3) one responds to ping the other does not and I also got Failed for Gateway connectivity check but its not like something that is bothering me. When you ping the gateway from CLI you could try check_connection manually from CLI to see more details
Hi, thank that you helping me…
How do I find “my” gateway? I only see a reference to a “GatewayV4” on the Luci Dashboard page. There is an IP address.
When I try to ping it via the shell, no ping comes back. Does that explain it? Is it due to the ISP?
And so far it has worked because the gateway was the upstream ISP router or? Now the Turris is connected directly to the modem.
Yes GatewayV4 is your gateway. You could check ip route command and there will be default via and there should be same IP. If it doesnt respond then nothing you can do about that. Ask your ISP if its intended if you are curious and thats it if it works then why bother. Actually I have the same exact results as you in Reforis check.
This check is well. Simple. IPv4 connectivity works DNS works so thats all you need.
The check_connection command will pick your gateway automatically
1 Like
Does internet access work for computers connected to the router?
@AreYouLoco
Very cool, thanks for the quick help in this case, then all is well, I’m not that curious 
@moeller0
Thank you very much for your help and patience in this whole issue!
It feels a bit strange at the moment, but it’s actually no different as in the past as I used a FritzBox on the Telekom DSL connection Now just a Turris directly on the fiber optic connection
Could you post the output of the following commands run on your router:
# these will take a bit
tracepath -b -4 one.one.one.one
tracepath -b -6 one.one.one.one
# these will take each over 100 seconds...
mtr -ezb4w -c 100 -o LSNBAWVJMXI one.one.one.one
mtr -ezb6w -c 100 -o LSNBAWVJMXI one.one.one.one
you might need to install these binaries first:
opkg update , opkg install mtr-json iputils-tracepath
Ok, here the output but why do you want this now? I think everything is fine now.
tracepath -b -4 1.1.1.1
1?: [LOCALHOST] pmtu 1492
1: p3e9bf549.dip0.t-ipconnect.de (62.155.245.73) 935.002ms
1: p3e9bf549.dip0.t-ipconnect.de (62.155.245.73) 32.004ms
2: f-ed13-i.F.DE.NET.DTAG.DE (217.5.118.234) 848.005ms asymm 4
3: 80.156.160.223 (80.156.160.223) 922.012ms asymm 4
4: if-ae-19-2.tcore2.fr0-frankfurt.as6453.net (80.231.65.10) 576.011ms asymm 5
5: 195.219.148.122 (195.219.148.122) 752.022ms asymm 4
6: 162.158.84.53 (162.158.84.53) 59.012ms
7: no reply
8: no reply
9: no reply
10: no reply
11: no reply
12: no reply
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
Too many hops: pmtu 1492
Resume: pmtu 1492
tracepath -b -6 1.1.1.1
tracepath: 1.1.1.1: Name does not resolve
mtr -ezb4w -c 100 -o LSNBAWVJMXI 1.1.1.1
Start: 2024-12-30T17:24:14+0100
HOST: myhost Loss% Snt Last Best Avg Wrst StDev Jttr Javg Jmax Jint
1. AS3320 p3e9bf549.dip0.t-ipconnect.de (62.155.245.73) 0.0% 100 2.2 1.7 3.0 17.5 2.8 1.1 1.1 10.6 13.3
2. AS3320 f-ed13-i.F.DE.NET.DTAG.DE (217.5.67.30) 0.0% 100 5.6 5.3 5.9 10.5 0.5 0.2 0.3 4.7 10.2
3. AS3320 80.156.160.223 (80.156.160.223) 43.0% 100 12.6 11.8 13.1 35.0 3.8 0.7 1.2 22.0 39.2
4. AS6453 if-ae-19-2.tcore2.fr0-frankfurt.as6453.net (80.231.65.10) 21.0% 100 10.8 10.6 11.3 22.9 1.9 0.1 0.9 12.1 11.1
[MPLS: Lbl 751 TC 0 S u TTL 1]
5. AS6453 195.219.148.122 (195.219.148.122) 0.0% 100 32.2 5.4 9.4 40.0 7.5 26.5 6.2 34.2 113.4
6. AS13335 162.158.84.169 (162.158.84.169) 0.0% 100 5.8 5.4 8.3 39.1 5.9 3.7 4.6 32.9 84.4
7. AS13335 one.one.one.one (1.1.1.1) 0.0% 100 4.7 4.7 5.1 5.7 0.1 0.3 0.1 0.7 2.4
mtr -ezb6w -c 100 -o LSNBAWVJMXI one.one.one.one
mtr: udp socket connect failed: Network unreachable
That will not work, fort IPv6 you need to use the symbolic name one.one.one.one instead of the IPv4 address 1.1.1.1
tracepath -b -6 one.one.one.one
1: send failed
Resume: pmtu 128000
I am not using IP6 at the moment on the turris…
Is the output as you aspected?
Good morning @moeller0
Is the output as you aspected?
Everything is fine now or?
Well, I had extected working IPv6… and the invocation with an numeric IPv4 address was not testing that. But if IPv6 is disabled on purpose this seems expected.
A question though, why did you disable IPv6?
IP6 is something I don’t understand yet. Since everything still works for me, I simply deactivated it. I haven’t understood it all yet.
It was safer for me to deactivate and I only have to concentrate on IP4, e.g. for my Pi-hole configuration and other things. Maybe I should take a closer look at this.
So what IPv6 will make easier is to make internal computers reachable from the outside, e.g. remote control your home computer from away (arguably that is better handled with a VPN though and that works reasonably well with IPv4) or offer your own minecraft server for your friends, or your kids’ friends. With OpenWrt/turrisOS* all internal IPv6 addresses are shielded from the outside by the stateful firewall, so running IPv6 will not rip holes into your home network’s security either.
Personally I am quite happy with a dual stack network with both IPv4 and IPv6, and most of the time I do not notice which of the two is actually used… I consider that to be a good thing 
as they tend to simply work.
*) @miska: does team turris have a preferred capitalisation for turris and turris OS (e.g. due to trademarks) that you would like us to use?
Thanks for your information!
I think that was my fear in the past that I would rip holes into my home network. I only have a Nextcloud that I host myself on a server and that has to be accessible from outside. So far, I have solved this in the classic way via DynDNS… I also have a VPN but I rarely use…
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.