Router can see IPv6, LAN clients get address, but General Failure when pinging



  • Using HE tunnel broker, and I think I'm part-way there, but apparently not all the way.

    Settings are pictured here:

    http://imgur.com/a/iBtHA

    Can you see anything that's wrong with this setup? Any glaring problems or errors?



  • I don't know so much about Windows, but do you have an IPv6 default gateway at all? Please print routing table of the client computer.
    Do you use a valid prefix out of the tunnel brokers range for your LAN users?



  • It appears that the Windows box isn't seeing a default ipv6 gateway, but a linux box attached to the same system works just fine.

    C:\Users\Robert>route -6 print
    ===========================================================================
    Interface List
      7...00 15 5d 00 0a 04 ......Hyper-V Virtual Ethernet Adapter
      3...74 d0 2b 96 1a 8b ......Realtek PCIe GBE Family Controller
      5...00 1a 7d da 71 0a ......Bluetooth Device (Personal Area Network)
      1...........................Software Loopback Interface 1
    ===========================================================================
    
    IPv6 Route Table
    ===========================================================================
    Active Routes:
     If Metric Network Destination      Gateway
      1    331 ::1/128                  On-link
      3    281 2001:470:3074::17b0/128  On-link
      3    281 fe80::/64                On-link
      7    271 fe80::/64                On-link
      3    281 fe80::481c:364a:f8a5:c286/128
                                        On-link
      7    271 fe80::4c16:753:c0de:3c38/128
                                        On-link
      1    331 ff00::/8                 On-link
      3    281 ff00::/8                 On-link
      7    271 ff00::/8                 On-link
    ===========================================================================
    Persistent Routes:
      None
    
    C:\Users\Robert>ipconfig /all
    
    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : Anaerin-PC
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : localdomain
    
    Ethernet adapter vEthernet (DockerNAT):
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter
       Physical Address. . . . . . . . . : 00-15-5D-00-0A-04
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::4c16:753:c0de:3c38%7(Preferred)
       IPv4 Address. . . . . . . . . . . : 10.0.75.1(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Ethernet adapter Ethernet:
    
       Connection-specific DNS Suffix  . : localdomain
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
       Physical Address. . . . . . . . . : 74-D0-2B-96-1A-8B
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:470:3074::17b0(Preferred)
       Lease Obtained. . . . . . . . . . : February 12, 2017 11:55:08 PM
       Lease Expires . . . . . . . . . . : February 21, 2017 6:40:11 PM
       Link-local IPv6 Address . . . . . : fe80::481c:364a:f8a5:c286%3(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.0.10(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : February 12, 2017 11:35:27 PM
       Lease Expires . . . . . . . . . . : February 21, 2017 6:43:38 PM
       Default Gateway . . . . . . . . . : 192.168.0.1
       DHCP Server . . . . . . . . . . . : 192.168.0.1
       DHCPv6 IAID . . . . . . . . . . . : 41209899
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-8D-8B-DA-74-D0-2B-96-1A-8B
       DNS Servers . . . . . . . . . . . : 2001:470:3074::1
                                           192.168.0.1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Ethernet adapter Bluetooth Network Connection:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
       Physical Address. . . . . . . . . : 00-1A-7D-DA-71-0A
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    

  • LAYER 8 Global Moderator

    Your dhcpv6 is showing /48 prefix in its settings.

    That is not right.  If your using /48 from your HE, your dhcp on an interface would still hand out a /64 prefix for that interface.. The other /64's that make up your /48 would be used on other networks/vlan in your network.



  • To be honest, the handing out of IPv6 IPs seems to be working just fine, both linux and windows machines are getting valid IPv6 addresses given to them. As you can see from http://i.imgur.com/nuwPtA2.png I'm using two sections of that /48 - :1000-:2000 is for individual machines, :1-:2 is for /64 PDs (which are currently not being used). The problem appears to be Windows machines not getting a valid IPv6 route from DHCP/RA.



  • You can add the default route manually. That would at least prove that it's your only problem.

    Are you on a switch that blocks RA?



  • @Anaerin:

    As you can see from http://

    Don't you need subnet-address-number for your LAN (bits from /48 to /64). I see empty (0)?
    Try from set(3 to FFFF) if you reserved 1 & 2. Ofcourse the last 64 bits fit for DHCP for that LAN.
    (Prefix Delegation Range is not necessary for function as DHCP for your LAN).


  • Banned

    This is just absurd.

    • SLAAC requires /64, put a /64 on your LAN. Why'd you waste /48 on a single interface anyway, huh…
    • DHCPv6 doesn't work with most of mobiles (Android) and has been broken in Windows as well (at least W10).
    • Prefix delegation is completely unrelated to all of this.


  • Okay, let's start again from right at the very top.

    I have a local network, and a HE Tunnel, and I want to connect the two together. I would like to allocate a multi-ip range to each machine in the local net (Prefix Delegation, if that's the right term) for virtual machines and service hosting, but that is not particularly necessary at this point (I can just bridge the networks and have them allocate as if they were full machines on the LAN, rather than VMs on a host).

    I have available 2 ranges. An allocated /64 at 2001:470:1f17:<blah>::/64 and an allocated /48 at 2001:470:<yadda>::/48

    The HE tunnel is up and working fine on interface HeNet, with an address of 2001:470:1f17:<blah>::2 /64, talking to the gateway at 2001:470:1f17:<blah>::1

    My clients are a mixture of Windows 10, Windows 8.1, Linux and Android devices, and I would like them to autoconfigure their settings as much as is possible.</blah></blah></yadda></blah>


Log in to reply