1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Shibby 109 - IPv6 Tunnel Broken

Discussion in 'Tomato Firmware' started by Cyberian75, May 18, 2013.

  1. Cyberian75

    Cyberian75 Network Guru Member

    After upgrading to 109, the IPv6 tunnel seems broken. In Overview, it does show my v6 address; however, various "IPv6 address" sites fail to detect the tunnel.

    Please advise.
     
  2. GhaladReam

    GhaladReam Network Guru Member

    Probably a no brainer - but did you clear your NVRAM after upgrading?
     
  3. Cyberian75

    Cyberian75 Network Guru Member

    No, only because I didn't need to in prior versions.


    Does it work for you, though?
     
  4. Cyberian75

    Cyberian75 Network Guru Member

    I did it just now, but it's no use. The tunnel doesn't get detected.
     
  5. JLongshanks

    JLongshanks Networkin' Nut Member

    Have you got a /48 assigned prefix?

    I found I had to put a length of 64, rather than 48, on the IPV6 set up page otherwise my clients didn't get IPV6 addresses.

    I assume this is due to radvd being removed, and dnsmasq being used to advertise IPV6 prefixes.
     
    Cyberian75 likes this.
  6. darkknight93

    darkknight93 Networkin' Nut Member

    hm. Shibby changed the ipv6 daemon on the router from radvd to dnsmasq - so the old Setting stored in nvram i think won't work in 109

    Which IPv6 Tunnel Provider do you use? Hurrican Electric's tunnelbroker? In my case, everything works fine... :S
     
  7. Cyberian75

    Cyberian75 Network Guru Member

    That worked! Thanks! :)

    Please report this to Shibby.
     
  8. Daky

    Daky Network Guru Member

    Any1 running Windows 8 and HE tunnel on shibby's firmware?

    Can you ping\trace IPs ? (Windows 8 only)

    Thanks
     
  9. JLongshanks

    JLongshanks Networkin' Nut Member

    @Daky - I'm running windows 8 (pro 64-bit), shibby's 109 build and I have a HE tunnel. IPV6, and IPV4, ping and tracert both work for me. See below for example.

    C:\Windows\system32>ping -6 2620:0:ccc::2

    Pinging 2620:0:ccc::2 with 32 bytes of data:
    Reply from 2620:0:ccc::2: time=345ms
    Reply from 2620:0:ccc::2: time=367ms
    Reply from 2620:0:ccc::2: time=339ms
    Reply from 2620:0:ccc::2: time=330ms

    Ping statistics for 2620:0:ccc::2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 330ms, Maximum = 367ms, Average = 345ms
     
  10. shibby20

    shibby20 Network Guru Member

    RT-N66U+v109and notebook with Win8pro

     
  11. Daky

    Daky Network Guru Member

    For some reason i am having issues, firewall (service) is fully disabled in Windows 8.

    C:\Windows\system32>ping -6 google.com

    Pinging google.com [2607:f8b0:4009:804::1002] with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

    Ping statistics for 2607:f8b0:4009:804::1002:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    :/
     
  12. xorglub

    xorglub Addicted to LI Member

    There is a bug with dnsmasq when the subnet is not a /64.
    For now just shrink it to /64 and you will be fine.
     
  13. Cyberian75

    Cyberian75 Network Guru Member

    Daky: Try disabling / enabling your connection within Windows.
     
  14. Daky

    Daky Network Guru Member

    Believe it or not ( i dont know how ) , but, Kaspersky Antivirus 2013 was blocking ping\traceroute.

    After uninstalling it, there was no problem, wondering what option was doing this :\

    Tanks all
     
  15. Cyberian75

    Cyberian75 Network Guru Member

    Probably the firewall... it happened to me before with Kaspersky Internet Suite.
     
  16. Daky

    Daky Network Guru Member

    Actually, this is Kaspersky Antivirus only, i tried 2 times now (just to make sure) and it was Kaspersky blocking it. :\\ i will have to contact them probably.

    Thanks
     
  17. Kevin Darbyshire-Bryant

    Kevin Darbyshire-Bryant Networkin' Nut Member

    Bug is a slight matter of perspective. Bear in mind that SLAAC in the Ethernet world is only supposed to work with a /64 - now if 2^64 doesn't give you enough local addresses I'd say there's something wrong with you :) Do you really need 2^72 or 2^80 local host addresses?

    Similarly the DHCPv6 handling code basically only deals with 64 host bits (it fits nicely into a long long int apparently) so whilst the DHCPv6 side could be coded to deal with /56, /48 or smaller it's a hell of a lot of code changes to suddenly break beyond the 64 bit barrier (variables, memory space, code space for >64 bit address comparisons etc) - and in my head I'm asking for what real gain?

    There's an interesting comment I've just discovered in the Tomato code. "ipv6_prefix_length //The bit length of the prefix. Used by dhcp6c. For radvd, /64 is always assumed."
     
  18. JLongshanks

    JLongshanks Networkin' Nut Member

    In my case getting a /48 block from HE stopped Google Play giving me the prices of everything in dollars because it believed I was in the USA when I used the /64 block which came with my tunnel. :)
     
  19. xorglub

    xorglub Addicted to LI Member

    I 100% agree even a /64 is completely overkill for any situation I can think of.
    The issue that I see is a usability one. The average person just goes and copies and paste the different values in the appropriate boxes in the router configuration pages, that his ISP/tunnel provider told him to use.
    If you have a /56 or /48 subnet, and you fill in those values and it doesn't work, something is wrong.
     
  20. Kevin Darbyshire-Bryant

    Kevin Darbyshire-Bryant Networkin' Nut Member

    Hmm, make something idiot proof and they'll build a better idiot :) I'll look at forcing a /64 into the dnsmasq config so even if your real prefix is a /48 then by default, as you say, at least you'll get something. After all, that's all that tomato did with radvd in the background anyway.
     
    philess likes this.

Share This Page