![]() |
VOOZH | about |
Please make sure your Internet browser is javascript enabled. Also, check your keyboard 'CapsLock' is not 'ON'. If the problem still exists, please send email to ipv6@he.net along with your account password.
Please log into your account and click 'Update Info' which is located at the top left hand corner, in the 'Account Menu' box. There should be an option for changing the account email, next to the email address.
Please log into your account and click 'Update Info' which is located at the top left hand corner, in the 'Account Menu' box. There should be an option for changing the password.
Please visit http://ipv6.he.net/certification/forgot_password.php and enter your account email address. You will receive an email containing a link to set a new account password, along with your account username.
Please visit http://ipv6.he.net/certification/forgot_password.php and enter your account email address. You will receive an email containing a link to set a new account password.
Once you have enabled two-factor authentication, you need those credentials or one of the backup codes on your account information page to get into your account. If you do not have the recovery information saved somewhere, there is no way back into the account without it.
Under the Account Information page, there's an option to remove your account. Do note that removing your account removes all services associated with it, including any ac tive DNS zones.
Unfortunately, we don't allow the domain name to be changed once submitted. However, You can reset your certification level back to the 'Explorer' level. Simply log into your account and visit http://ipv6.he.net/certification/reset_explorer.php. Please remember that once you set back your certification level, you must retake all the certification tests.
You can reset your certification level back to the 'Explorer' level. Simply log into your account and visit http://ipv6.he.net/certification/reset_explorer.php. Please remember that once you set back your certification level, you must retake all the certification tests
Yes, we have video tutorials available for each certification test and a certification forum. You may also send email to
An IPv4 endpoint address is the IPv4 address for the system you're planning on anchoring the tunnel on. If you're using the same system to configured the tunnel as you want to anchor it on, the IPv4 endpoint address would be the one displayed on the tunnel creation page.
Yes, you can still create a tunnel even if you are using a dynamic IPv4 endpoint address. If your IPv4 endpoint address changes, you can either login to the tunnelbroker.net page and update your IPv4 endpoint address or use https://ipv4.tunnelbroker.net/nic/update which is designed to be used to update your IPv4 endpoint address.
In order to create a 6in4 tunnel, your IPv4 endpoint must be reachable. Please go over your firewall settings and make sure external ICMP requests are allowed.
In most cases, this configuration will not work. If the router is smart enough to recognize 6in4 traffic, it may. If it supports a full forwarding DMZ, it might. If it support forwarding traffic by protocol (not port!), it might.
Such a configuration has all the above complications of NAT, in addition to no ability to adjust the CGNAT router. It's highly unlikely to work as CGNAT relies on TCP and UDP ports within normal IPv4 traffic for forwarding to the proper end-user, and CGNAT implementation usually do not have any knowledge of how to forward 6in4 traffic.
If possible, get a new router that supports (allows and forwards) IP protocol 41. Alternately, you can either put the host in a DMZ and secure it as best as you can, or bypass your router to set up a tunnel.
This is normal for any configured 6in4 tunnel. As the protocol has no underlying keep-alive or heartbeat mechanism, 'up' simply means your computer has an IPv4 route which may reach the remote side. It doesn't indicate if the remote side is reachable, configured, up, or the tunnel is functional.
Because a tunnel is effectively throwing packets at the other side, without any signalling process for the tunnel mechanism itself, there's often not much to do aside from ensuring everything on your side you control will permit IP protocol 41 traffic in and out to the system you're anchoring the tunnel on. If you have a traceroute available on the system you're trying to anchor the tunnel on, and it support an option to specific the protocol the IPv4 trace packets are marked with, a trace to the tunnel server's IPv4 address with the protocol set to 41 can sometimes provide additional information.
We don't delegate reverse DNS for the tunnel's Point-To-Point(PTP) /64. We delegate only to the routed /64 or /48s. Please make sure you are using the routed prefix(es), and not the PTP /64 in your rDNS entries.
This is not possible. IPs are assigned to the specific tunnel server. The routing table growth from permitting IP portability between tunnel servers would not be feasible.
Due to a high and persistent amount of abuse, we've had to filter IRC access by default. If you need IRC access, complete the Sage level of the free IPv6 certification and then please send an email to ipv6@he.net explaining your situation. Approvals will be handled on a case-by-case basis and will usually require completion of the Sage level of the IPv6 certification.
Due to a high and persistent amount of abuse, we had to filter SMTP (tcp/25) connections by default. If you're not providing email service yourself, you should be able to use port 587 instead to your provider's email server. If you are providing email services over your tunnel and need port 25 opened, please send an email to ipv6@he.net explaining your situation. We will normally require completion of the Sage level of the IPv6 certification prior to removing this filter. NOTE: this filtering does not affect the SMTP-related tests on the IPv6 certification program.
IP addresses carry no inherent location data. Administrative databases such as WHOIS can provide some location context. However, most geolocation providers appear to use their own proprietary heuristics to attempt to determine an IP's location. Often these do not use WHOIS, or other location data available in public records. As such, the ability to correct these is often limited.