Recent posts

Thanks, just tried that out and looks like I'm seeing packet loss right at my tunnel's endpoint and then continues from there until it hits Cloudflare's DNS server.

#23

IPv6 Basics & Questions & General Chatter / Re: selective failure pinging ...

Last post by PMch - December 17, 2024, 07:38:54 PM

Can it be a problem with the destination site (wand.daemon.contact in the example above)?

I have two tunnel endpoint IPv6 adresses (tunnel123456-pt.tunnel.etc.etc.he.net and tunnel123456.tunnel.etc.etc.he.net), and both of them show just the same 50% failures.

One of these is run entirely by HE, so it doesn't look like a flaw on my side. :(

#24

IPv6 Basics & Questions & General Chatter / selective failure pinging my t...

Last post by PMch - December 17, 2024, 11:15:11 AM

Hi,

a network failure suddenly appeared today at 01:40Z. No changes have happened.

Analysis showed that I can still reach some of my tunnels, and the behaviour is different for UDP, TCP and ICMP6 and for different targets. I found that it is also different for different sources.

For ping/ICMP6 it currently looks like this:

Code Select

                                                tun-1   tun-2   tun-3
from 2003:e7:171d:6eff::1                       FAIL    FAIL    FAIL
from 2003:e7:171d:6ee1:41d:92ff:fe01:104        ok      FAIL    FAIL
from 2003:e7:171d:6ee0:41d:92ff:fe01:105        ok      ok      ok
from 2003:e7:17ff:f22:41d:92ff:fe01:301         FAIL    ok      ok

tcpdump shows the packets depart from origin into the Internet (into DSL in this case), but no gif-encapsulated packet appears on the interface of the destination system.

I have no clue on why or where on the network they might disappear.

Pinging the two tunnel endpoints (ingress and egress) shows a different pattern again:

Code Select

ingress                                         tun-1   tun-2   tun-3
from 2003:e7:171d:6eff::1                       FAIL    ok      FAIL
from 2003:e7:171d:6ee1:41d:92ff:fe01:104        FAIL    ok      FAIL
from 2003:e7:171d:6ee0:41d:92ff:fe01:105        ok      FAIL    ok
from 2003:e7:17ff:f22:41d:92ff:fe01:301         FAIL    FAIL    FAIL

Code Select

egress                                          tun-1   tun-2   tun-3
from 2003:e7:171d:6eff::1                       FAIL    ok      FAIL
from 2003:e7:171d:6ee1:41d:92ff:fe01:104        ok      ok      FAIL
from 2003:e7:171d:6ee0:41d:92ff:fe01:105        ok      ok      ok
from 2003:e7:17ff:f22:41d:92ff:fe01:301         FAIL    FAIL    ok

Code Select

# ifconfig vtnet0
vtnet0: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=80028<VLAN_MTU,JUMBO_MTU,LINKSTATE>
        ether 06:1d:92:01:03:01
        inet 192.168.98.34 netmask 0xfffffffc broadcast 192.168.98.35
        inet6 fe80::2%vtnet0 prefixlen 64 scopeid 0x1
        inet6 2003:e7:1731:3cff::20 prefixlen 64
        inet6 2003:e7:1731:3cff::21 prefixlen 64
        inet6 2003:e7:1731:3cff::22 prefixlen 64
        inet6 2003:e7:1731:3cff::23 prefixlen 64
        inet6 2003:e7:1731:3cff::24 prefixlen 64
        inet6 2003:e7:1731:3cff::25 prefixlen 64
        inet6 2003:e7:1731:3cff::26 prefixlen 64
        inet6 2003:e7:1731:3cff::27 prefixlen 64
        inet6 2003:e7:1731:3cff::28 prefixlen 64
        inet6 2003:e7:1731:3cff::29 prefixlen 64
        media: Ethernet autoselect (10Gbase-T <full-duplex>)
        status: active
        nd6 options=1<PERFORMNUD>

# for i in 20 21 22 23 24 25 26 27 28 29; do ping -q -c 1 -S 2003:e7:1731:3cff::$i wand.daemon.contact >/dev/null 2>&1 && echo $i okay; done
21 okay
23 okay
24 okay
25 okay
26 okay
28 okay

The pattern reproduces. Over all quite precisely 50% failure rate.

However, trying google, or freebsd.org:

Code Select

# for i in 20 21 22 23 24 25 26 27 28 29; do ping -q -c 1 -S 2003:e7:1731:3cff::$i freebsd.org >/dev/null 2>&1 && echo $i okay; done
20 okay
21 okay
22 okay
23 okay
24 okay
25 okay
26 okay
27 okay
28 okay
29 okay

So, it is not a problem with the IPv6 on this originating site (or with the router or whatever here).

#25

IPv6 Basics & Questions & General Chatter / Re: Packet loss to tunnel.tser...

Last post by Pentium4User - December 15, 2024, 10:45:50 AM

Please use

Code Select

mtr <Target-IP>

to check where the problem occurs.

I had a similar problem and the issue was the connecting between my ISP and en exchange point.

#26

IPv6 Basics & Questions & General Chatter / Packet loss to tunnel.tserv21....

Last post by lobotiger - December 15, 2024, 10:42:21 AM

Hi everyone, over the past month or so I've noticed quite a bit of packet loss to the Toronto peering point. It's anywhere from 3%-15% at times and it becomes unusable. Anyone know what's going on?

#27

IPv6 Basics & Questions & General Chatter / Re: ping to 2600:: not working...

Last post by Pentium4User - December 01, 2024, 02:51:31 AM

2600:9000::/28 is the infor I got from whois.
According to the HE looking glass, it is not announced. At Telekom (AS3320), it is not in the routing table too.

amzn-noc-contact@amazon.com can be contacted, this is in the whois address.
d3e2y37tle8w9m.cloudfront.net at this time (TTL 40 sec) points to various networks in 2600:9000:223c::/48, which is in the HE routing table. I can ping that properly via AS3320.

Please try if the problem still exists.

For 2600::
Reachable from only a few AS, other big ones like 3320 don't have that in their routing table.
Contact Cogent/Sprint and ask them. I dunno about the peering/routing policies they have.

#28

IPv6 Basics & Questions & General Chatter / Re: Packet Loss on tserv1.ams1...

Last post by Pentium4User - December 01, 2024, 02:26:37 AM

Can you use

Code Select

sudo mtr 216.66.84.46 -i 0.2

#29

IPv6 Basics & Questions & General Chatter / Packet Loss on tserv1.ams1.he....

Last post by ictd01 - December 01, 2024, 02:14:47 AM

Hello,

I am currently experiencing 10–20% packet loss while connected to the tunnel server at 216.66.84.46 (tserv1.ams1.he.net). My location is in the Netherlands.

Is this an isolated issue on my end, or are there broader connectivity problems affecting this server?

Thank you for looking into this.

Best regards,

Bouke

#30

General Questions & Suggestions / Re: Support for SVCB and HTTPS...

Last post by jailbird - November 18, 2024, 09:06:35 PM

It looks like the web UI understands these records, but it won't let you add them nor edit them.

It would be awesome if it did!

Pages 1 2 3 4 5 ... 10