Nightly (possibly) broke connection outside HE.net



  • So since around the first of January or so, I've been running the 2.1 nightly (I believe it was Jan 3rd) with a GIF tunnel with Hurricane Electric.

    Everything had been fine up until yesterday, when I updated to the newest nightly. After doing that, all my settings appeared to be fine, but now I'm not able to route outside the the network EXCEPT for that I can ping the HE.net IPv6 address assigned on the GIF interface. Anything beyond that, I get a routing failure:

    PING google.com(nuq04s06-in-x06.1e100.net) 56 data bytes
    From 2001:470:XXXX::1 icmp_seq=1 Destination unreachable: No route

    Now, the one thing I did notice that was different was that under gateways, I now have a dynamic6 gateway that is on my DMZ interface (previously had no IPv6). I'm unable to delete that new addition, but I can modify it.

    I uploaded the March 3rd nightly, but that doesn't seem to make a difference either. I'm kicking myself now for not making a full backup (no huge loss though).

    Anyone have any ideas what might be going on?

    Thanks


  • Rebel Alliance Developer Netgate

    Check Diag > Route, see if you have a default IPv6 route listed.

    Edit/Save/Apply your default IPv6 gateway under System > Routing, see if that helps.



  • It was in there, but the edit/apply fixed it.

    Not sure why I didn't think of that :| Something so bloody simple.

    Thanks Jimp!



  • I too had this problem, however I saw another post, and found clicking save on the He.net interface, fixed the issue, however on reboot it came back.

    My solution to the problem, was to change the recommended /128 subnet on both sides of the tunnel and made it a /64 as He.net specifies.
    Multiple reboots later, it's still coming up automagically and working.

    Hope this helps..



  • @Sn3ak:

    I too had this problem, however I saw another post, and found clicking save on the He.net interface, fixed the issue, however on reboot it came back.

    My solution to the problem, was to change the recommended /128 subnet on both sides of the tunnel and made it a /64 as He.net specifies.
    Multiple reboots later, it's still coming up automagically and working.

    Hope this helps..

    Mine survived a reboot, and then the update to the next nightly just fine once I "edited and saved" the gateway again, although I've always been using the /64 CIDR.

    Did you always have the issue with the route dropping? Or was it after a certain update?


Log in to reply