Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Pages: 1 [2] 3 4 ... 10
 11 
 on: August 26, 2022, 04:43:51 AM 
Started by Talustus - Last post by therrmann
According to the status site, it is up again:

https://www.tunnelbroker.net/status.php

But it is still not working for me.

 12 
 on: August 26, 2022, 03:30:04 AM 
Started by Talustus - Last post by revolt112
Seems to be an bigger issue... From a technician perspective would i be interested in the reason for this downtime

 13 
 on: August 26, 2022, 12:23:13 AM 
Started by Talustus - Last post by worknd
Still down yet....

 14 
 on: August 25, 2022, 11:48:45 PM 
Started by Talustus - Last post by Talustus
Hello, just short but important question :D

is "tserv6.fra1" down?
i cant reach it and tunnel server status page says
that it is down

mfg

 15 
 on: August 22, 2022, 02:04:40 PM 
Started by ictd01 - Last post by ping
I did notice that there is no loss anymore since 22-08-2022 after 11:08:35. It looks like the problem has been resolved :-)

Wooo! :D
I didnt even notice it had stopped, i had to fall back to ipv4 on most of my gear, because it was completely useless otherwise.
Whatever it was, seems so have stopped flooding my log too, roughly 2 hours later than you (times in CET)

Aug 22 13:03:55 <kern.crit> kernel: IPFW2: IPV6 - Unknown Extension Header(16), ext_hd=0
Aug 22 13:06:36 <kern.crit> last message repeated 28 times

Im super curious about what/how/where it went wrong..
Did you get any reply with info about what had happened? ???

 16 
 on: August 22, 2022, 01:36:51 PM 
Started by ictd01 - Last post by ictd01
I did notice that there is no loss anymore since 22-08-2022 after 11:08:35. It looks like the problem has been resolved :-)

 17 
 on: August 21, 2022, 08:52:07 AM 
Started by ictd01 - Last post by ping
I run pfSense and I did notice this quite a lot:

Aug 21 14:30:32   dpinger   83013   IPV6WAN1_TUNNELV6 2001:470:1f14:71::1: duplicate echo reply received
Aug 21 14:21:53   dpinger   83013   IPV6WAN1_TUNNELV6 2001:470:1f14:71::1: duplicate echo reply received
Aug 21 13:29:50   dpinger   83013   IPV6WAN1_TUNNELV6 2001:470:1f14:71::1: duplicate echo reply received

That's suspicious.

My tunnel is configured on BSD too, but with ipfw instead of pf..it too complains quite a lot in the logs..not about dups, but about unknown protocols (because 0x11 is flipped into 0x10 in the packet):

Aug 21 16:00:38 <kern.crit> kernel: IPFW2: IPV6 - Unknown Extension Header(16), ext_hd=0
Aug 21 16:01:05 <kern.crit> kernel: IPFW2: IPV6 - Unknown Extension Header(16), ext_hd=0
Aug 21 16:02:11 <kern.crit> kernel: IPFW2: IPV6 - Unknown Extension Header(16), ext_hd=0
Aug 21 16:13:27 <kern.crit> last message repeated 12 times
Aug 21 16:24:01 <kern.crit> last message repeated 9 times

Once in a while, it hits the source ip in the packet instead, so for example 2a01:4f8:120:: becomes 2901:4f8:120::
I have never experienced a bug quite like this, its kinda interesting..and annoying :P

 18 
 on: August 21, 2022, 08:08:39 AM 
Started by ictd01 - Last post by ictd01
I have sent an email to ipv6@he.net. Hopefully we'll soon find out what's causing it.

 19 
 on: August 21, 2022, 07:51:49 AM 
Started by ictd01 - Last post by ictd01
I run pfSense and I did notice this quite a lot:

Aug 21 14:30:32   dpinger   83013   IPV6WAN1_TUNNELV6 2001:470:1f14:71::1: duplicate echo reply received
Aug 21 14:21:53   dpinger   83013   IPV6WAN1_TUNNELV6 2001:470:1f14:71::1: duplicate echo reply received
Aug 21 13:29:50   dpinger   83013   IPV6WAN1_TUNNELV6 2001:470:1f14:71::1: duplicate echo reply received

That's suspicious.

 20 
 on: August 21, 2022, 06:32:43 AM 
Started by Walter H. - Last post by Walter H.
the reason of this strange behaviour:
the new modem had bugs in its firmware, which doesn't go conform with the requirements to let packets with protocol 41 untouched;

I got a new one which indeed was an old one, that doesn't touch the packets with protocol 41

Pages: 1 [2] 3 4 ... 10