Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - frgomes

Pages: [1]
1
Questions & Answers / Re: how to auto update tunnel
« on: January 12, 2018, 01:59:47 PM »
Hello sonboHol,

In my case, I have two scenarios:

1. My router updates ipv4.tunnelbroker.net, informing the public IPv4 endpoint.
This public IPv4 endpoint changes only rarely, only when I restart the modem provided by the ISP or when the ISP performs some sort of network maintenance.

2. My workstations in my LAN update FreeDNS (http://dns.he.net) informing their IPv6 addresses.
These IPv6 addresses are served via DHCP by my router, in general.


Notice that "updating" in (1) and (2) involve different methods.

1. When the router updates its endpoint against ipv4.tunnelbroker.net, it employs an URL like this:
           https://[USERNAME]:[PASSWORD]@[DOMAIN]/nic/update?hostname=[PARAMENC]
where:
    USERNAME=frgomes
    PASSWORD=cannottellyou
    DOMAIN=ipv4.tunnelbroker.net
    PARAMENC=123456 (or whatever it is my tunnel ID)


2. When my workstations update their IPv6 addresses against FreeDNS, they employ ddclient which was installed like below:

Code: [Select]
# apt-get install ddclient -y

# cat <<EOD > /etc/ddclient.conf
daemon=300
syslog=yes
debug=yes
verbose=yes
force=no
#mail=root
#mail-failure=root
pid=/var/run/ddclient.pid
#----
protocol=dyndns2
use=if, if=eth0, usev6=if, ssl=yes
server=dyn.dns.he.net
login=terra.rgomes.info
password=generated-key
terra.rgomes.info
EOD

The generated-key is provided by FreeDNS, when you define an A record or AAAA record for DDNS purposes.

I hope it helps.

2
Hello cholzhauer,

When I've tried to create the tunnel, I've informed the IP address obtained via http://checkip.dyndns.org. In this case, the IP address was 188.28.150.82.
A far as I understand 66.220.2.74 (which belongs to HE) is trying to ping 188.28.150.82 (which belongs to the mobile network operator), without success.

I've configured the APN settings in my mobile phone so that it theoretically requests a public (and exclusive) IPv4 address.
Even supposing that the mobile network operator really allocated a public and exclusive IPv4 for me, I do not have any control of such process and I cannot guarantee that the IP address responds to ICMP.

Thanks

3
Hello,

I'm trying to configure my laptop to publish its IPv6 address to dyn.dns.he.net.

When I'm at home it simply works because my router has a IPv6 tunnel already configured and ddclient simply publishes the IPv6 address.
When I'm in Brazil it works because I connect via mobile tethering and the mobile network operator in Brazil supports IPv6.
However, the vast majority of mobile network operators in the UK do not support IPv6 as yet :-( and, in this case, I suppose I should establish a tunnel for my laptop via mobile tethering.

A bit off topic, but I suppose I should have an exclusive IPv4 endpoint allocated to me by the mobile network operator.
More info here: http://www.proroute.co.uk/support/apn-settings/
Quote: "If you are going to use DYNDNS then by using the following APN setting Three mobile should allocate you with a Public IP Address."

Well, supposing that the mobile network operator allocated a public IPv4 endpoint for me, I've headed to tunnelbroker.net and tried to create a new tunnel.
Then I've got the message: "IP is not ICMP pingable. Please make sure ICMP is not blocked. If you are blocking ICMP, please allow 66.220.2.74 through your firewall."

Any idea if and how this difficulty could be circumvented?

Note: I'm not really sure if the mobile network operator really allocated an IPv4 to me.
I've tried http://checkip.dyndns.org/ many times after rebooting the phone many times but I don't have any evidence that IPv4 endpoint(s) I get were allocated exclusively to me.

Thanks a lot,

Pages: [1]