ipv4.tunnelbroker.net client ip update problem

[Oryx]

Greetings,

I noticed I lost IPv6 today through the HE.net tunnel broker service, found that my IPv4 IP rotated but noticed that my pfSense router did not update the IP with HE.net. I logged into my tunnel broker account and tried to update it by way of the https mechanism and it is no longer updating.

https://<he.net tunnel broker login><authentication key>@ipv4.tunnelbroker.net/nic/update?hostname=<tunnel id>

Not sure when it stopped working but it has worked for years now without a problem. If I visit the URL manually, it takes about 10 seconds and this is what is returned:

"good 127.0.0.1"

Kind of odd, I would expect to see my public IPv4 IP address here, not the link local IP but who knows. Anyone else having trouble with the dynamic client IP change?

Oryx

UPDATE 1

I tried changing my IP manually to fix it temporarily and received an error saying that my address is not responding to ICMP pings. I have a rule explicitly allowing ICMP from 66.220.2.74 and this has not been changed in years so I believe my ISP is blocking ICMP. I'll assume this is the root cause.

UPDATE 2

That was it! They unblocked ICMP and I was able to update my IPv4 address on the tunnel broker. For the record, "good 127.0.0.1" is a bad result, it should read your IPv4 address. Maybe it should say bad instead of good? :)

[kcochran]

That was it! They unblocked ICMP and I was able to update my IPv4 address on the tunnel broker. For the record, "good 127.0.0.1" is a bad result, it should read your IPv4 address. Maybe it should say bad instead of good? :)

From https://help.dyn.com/remote-access-api/return-codes/, which we base our replies on:

good 127.0.0.1    

This answer indicates good update only when 127.0.0.1 address is requested by update. In all other cases it warns user that request was ignored because of agent that does not follow our specifications.

[abdulhamid]

Greetings

Hello I have problem access he.net from my IPv6 tunnel, but others Ipv6 its okay, here my IP address :

[root@jarwo ~]# ifconfig sit1
sit1      Link encap:IPv6-in-IPv4
          inet6 addr: 2001:470:35:540::2/64 Scope:Global
          inet6 addr: fe80::7661:97ae/128 Scope:Link
          UP POINTOPOINT RUNNING NOARP  MTU:1480  Metric:1
          RX packets:11773 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10385 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:8181350 (7.8 MiB)  TX bytes:1161264 (1.1 MiB)

[root@jarwo ~]# ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 00:08:A1:69:11:0F
          inet addr:118.97.151.174  Bcast:118.97.151.255  Mask:255.255.255.0
          inet6 addr: fe80::208:a1ff:fe69:110f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:184199 errors:3 dropped:3 overruns:3 frame:0
          TX packets:169111 errors:0 dropped:0 overruns:11 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:112880148 (107.6 MiB)  TX bytes:69807180 (66.5 MiB)
          Interrupt:21 Base address:0x4000

[root@jarwo ~]# ping6 he.net
PING he.net(he.net) 56 data bytes
^C
--- he.net ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1319ms

[root@jarwo ~]# ping6 youtube.com
PING youtube.com(sc-in-x88.1e100.net) 56 data bytes
64 bytes from sc-in-x88.1e100.net: icmp_seq=1 ttl=58 time=67.3 ms
64 bytes from sc-in-x88.1e100.net: icmp_seq=2 ttl=58 time=67.3 ms
^C
--- youtube.com ping statistics ---
4 packets transmitted, 2 received, 50% packet loss, time 3004ms
rtt min/avg/max/mdev = 67.323/67.339/67.356/0.260 ms

[root@jarwo ~]# traceroute6 he.net
traceroute to he.net (2001:470:0:76::2), 30 hops max, 80 byte packets
1  2001:470:36:540::1 (2001:470:36:540::1)  3000.742 ms !H  3000.745 ms !H  3000.745 ms !H
[root@jarwo ~]# traceroute6 yahoo.com
traceroute to yahoo.com (2001:4998:58:c02::a9), 30 hops max, 80 byte packets
1  abdulhamid-4.tunnel.tserv25.sin1.ipv6.he.net (2001:470:35:540::1)  70.284 ms  72.835 ms  70.220 ms
2  ge2-13.core1.sin1.he.net (2001:470:0:17c::1)  80.237 ms  80.479 ms  80.561 ms
3  10ge6-1.core1.hkg1.he.net (2001:470:0:29f::1)  105.574 ms  116.476 ms  105.058 ms
4  10ge5-1.core1.sel1.he.net (2001:470:0:334::2)  139.972 ms  141.292 ms  139.983 ms
5  2001:7fa:8::10 (2001:7fa:8::10)  157.909 ms  165.474 ms  163.958 ms
6  2406:2000:f008:4::1 (2406:2000:f008:4::1)  165.865 ms  158.656 ms  158.485 ms
7  so-0-1-0.pat2.swp.yahoo.com (2001:4998:f007:202::)  266.479 ms  264.897 ms  264.769 ms
8  ae-5.pat2.gqb.yahoo.com (2001:4998:f007:200::1)  285.521 ms  285.523 ms  272.047 ms
9  ae-7.pat1.dnx.yahoo.com (2001:4998:f00f:201::1)  281.281 ms  280.817 ms  279.728 ms
10  ae-3.pat1.che.yahoo.com (2001:4998:f00d:2::)  301.725 ms ae-9.pat1.che.yahoo.com (2001:4998:f00d:4::)  307.074 ms ae-3.pat1.che.yahoo.com (2001:4998:f00d:2::)  303.538 ms
11  v6.ae8.pat1.bfz.yahoo.com (2001:4998:f00d:7::1)  327.143 ms v6.ae8.pat2.bfz.yahoo.com (2001:4998:f00d:8::1)  322.619 ms v6.ae9.pat2.bfz.yahoo.com (2001:4998:f00d:206::1)  324.702 ms
12  2001:4998:f01c:d::1 (2001:4998:f01c:d::1)  366.290 ms 2001:4998:f01b:203::1 (2001:4998:f01b:203::1)  317.392 ms  320.271 ms
13  2001:4998:f01c:8::1 (2001:4998:f01c:8::1)  320.186 ms 2001:4998:f01c:a::1 (2001:4998:f01c:a::1)  332.865 ms 2001:4998:58:fe1e::1 (2001:4998:58:fe1e::1)  324.326 ms
14  2001:4998:58:fe1a::1 (2001:4998:58:fe1a::1)  324.458 ms 2001:4998:58:fa00::3 (2001:4998:58:fa00::3)  323.060 ms 2001:4998:124:fe04::1 (2001:4998:124:fe04::1)  317.226 ms
15  2001:4998:58:d606::1 (2001:4998:58:d606::1)  323.408 ms 2001:4998:58:fa00::11 (2001:4998:58:fa00::11)  322.559 ms 2001:4998:58:d206::1 (2001:4998:58:d206::1)  323.677 ms
16  * 2001:4998:58:d406::1 (2001:4998:58:d406::1)  322.637 ms ir1.fp.vip.bf1.yahoo.com (2001:4998:58:c02::a9)  325.237 ms

Thanks for your support