I've asked on IRC about this and tried all the suggestions there to no avail.
The IPv6 tunnel shows no gateway and no packets received, I have tried turning the firewall off and still the issue persists.
I have tried both account and update passwords, I cannot get he.net's IPv6 to work and was told to use it over SiXxs AICCU. Any ideas what's causing this to fail?
I have a HE tunnel, which works perfectly, and there is no info about gateway in LuCI; just test the interface from the command line ("ping6 www.google.com" is probably the simplest test), and see if it works.
I should've added that I am unable to ping any IPv6 address/hostname as there is no gateway - No route to host. I will post results of some more diagnostics when I am back home.
Distribution of IPv6 to my LAN actually works fine, but communication fails due to lack of a default gateway, and yes, 'Use Default Gateway' is selected.
One guess for you:
You may have a too long interface name, which breaks firewall loading (or something in routing settings or such).
Combined to the automatic prefix "6in4-" that makes it "6in4-henet_IPv6" as seen in your route table. That is really close to the allowed max length of an interface name. You might test with a shorter interface name.
In any case, as the he.net ipv6 tunnels work ok for others (including me), this is likely just about your network & firewall config.
If a shorter interface name does not make things work to you, please post here a more complete network config. I saw at least eth0, eth1 and eth2 mentioned, which looks strange.
Shortened interface name and appended the local IP to /64 to no effect.
How can I confirm this is not a packet filter issue seeing as traffic is sent but not received?
SixXs AICCU worked on a Slackware box, how would I test if my ISP is blocking Proto 41?
I'm testing 2 ISPs, both of whom are PPPoE and haven't setup bridging yet. This issue was exactly the same even when I had LEDE dial out to the modem in bridge mode.
What modem? First time that you mention any modem...
It is quite possible that your modem filters out protocol 41 (=6in4) traffic, especially if the modem is smart and contains some routing logic.
And also first time when PPPoE is mentioned.
This whole thread is absurd as you only give minimal snippets about your network config and expect others to magically figure out advice for your specific needs. You should describe the situation better if you want help. How you are connected to the ISP etc... And show the whole /etc/config/network instead of small pieces of it.
How does the ipv4 traceroute to google look like? Does the modem show up there?
Interesting to see someone else with this issue.
I have TalkTalk fibre internet, using the BTOR ECI modem and a Linksys E3000 running LEDE 17.01. I had been using tunnelbroker.net for some time with no issues when my router ran OpenWRT BB. Since upgrading to LEDE the tunnel has suddenly stopped working. I have used the exact same configuration as before which I know did work. Anyone have any more ideas?
@jordipalet@Ringerl@calumcb Apologies, forgot to update this thread. My issue was resolved by using Huawei modem in bridged mode instead of the TP-Link. One way would be to sniff for DSL frames on the modem.
@bolvan You're confused about bridged mode. The router "dialing" via the bridged modem gets a public IP from the ISP. The issue here was likely the older bridged modem silently dropping protocol 41.
this happens to me as well, on a freshly installed 18.06.2.
I've narrowed it down to the tunnel endpoint not being updated: after I fix it manually, either by running wget or via the he.net web interface, it works fine.
I solve this by using their Dynamic DNS service to update the tunnel (this may not be an option for everyone). I also observe that just configuring a tunnel (without DDNS) if the DHCP WAN IP changes.