| 
 
IPV6 setup problems on OpenSuse 
  Shadow Hawkins on Friday, 08 April 2016 18:26:23
I think I have setup IPV6 correctly but I have problems getting anywhere.
My config
 > /sbin/ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:50:56:29:EF:20
          inet addr:192.168.1.29  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: 2a01:348:1f9::29/48 Scope:Global
          inet6 addr: fe80::250:56ff:fe29:ef20/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:283025 errors:0 dropped:0 overruns:0 frame:0
          TX packets:45383 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:93868259 (89.5 Mb)  TX bytes:4374104 (4.1 Mb)
          Interrupt:19 Base address:0x2000
eth0:Sock Link encap:Ethernet  HWaddr 00:50:56:29:EF:20
          inet addr:192.168.1.129  Bcast:0.0.0.0  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:19 Base address:0x2000
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:2945 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2945 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:696736 (680.4 Kb)  TX bytes:696736 (680.4 Kb)
 ip -6 route show 2a01:348:1f9::/48 dev eth0  proto kernel  metric 256  pref medium
fe80::/64 dev eth0  proto kernel  metric 256  pref medium
default via 2a01:348:1f9::2 dev eth0  metric 1024  pref medium
ping6 ::1 PING ::1(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.024 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.089 ms
64 bytes from ::1: icmp_seq=3 ttl=64 time=0.064 ms
^C
--- ::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.024/0.059/0.089/0.026 ms
But
ping6  -I eth0 fe80::250:56ff:fe29:ef20 connect: Cannot assign requested address
ping6 -I eth0 2a01:348:1f9::29 ping6: Warning: source address might be selected on device other than eth0.
PING 2a01:348:1f9::29(2a01:348:1f9::29) from ::1 eth0: 56 data bytes
From ::1 icmp_seq=1 Destination unreachable: Address unreachable
From ::1 icmp_seq=2 Destination unreachable: Address unreachable
From ::1 icmp_seq=3 Destination unreachable: Address unreachable
^C
--- 2a01:348:1f9::29 ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5017ms
Any idea what the cause might be ?
Thank you
Markus
IPV6 setup problems on OpenSuse 
inet6 addr: 2a01:348:1f9::29/48 Scope:Global 
You assigned a complete /48 to eth0? Please only use /64s on a link.
Also in that prefix you really only have a /64 and it should be out of 2a01:348:81f9::/64
Note the 8 in there. See your user home and the FAQ for the differences between the prefix used for your tunnel and the one defaulted routed to the end of it.
eth0:Sock Link encap:Ethernet  HWaddr 00:50:56:29:EF:20 
What is that for a strange interface?
Also, no more interfaces? As you really need a tunnel to get out of your network.
PS: ifconfig & netstat are "old", please start using ip addr show ip link show and ip route show
IPV6 setup problems on OpenSuse 
  Shadow Hawkins on Sunday, 10 April 2016 17:10:57
Jeroen Massar wrote:
 >           inet6 addr: 2a01:348:1f9::29/48 Scope:Global
You assigned a complete /48 to eth0? Please only use /64s on a link.
Also in that prefix you really only have a /64 and it should be out of 2a01:348:81f9::/64
Note the 8 in there. See your user home and the FAQ for the differences between the prefix used for your tunnel and the one defaulted routed to the end of it.
 
I do have a registers subnet. See route
> eth0:Sock Link encap:Ethernet  HWaddr 00:50:56:29:EF:20
What is that for a strange interface?
 
Apologies I did not say I run it as a guest in VMware player on Windows 10
Also, no more interfaces? As you really need a tunnel to get out of your network.
 
 I don't require multiple interfaces as it is a routed subnet behind my tunnel endpoint with default route to 2a01:348:1f9::2
PS: ifconfig & netstat are "old", please start using  
ip addr show
# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether 00:50:56:29:ef:20 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.29/24 scope global eth0
       valid_lft forever preferred_lft forever
    inet 192.168.1.129/24 scope global secondary eth0:SocksAlias
       valid_lft forever preferred_lft forever
    inet6 2a01:348:1f9::29/48 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::250:56ff:fe29:ef20/64 scope link
       valid_lft forever preferred_lft forever
ip link show
# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether 00:50:56:29:ef:20 brd ff:ff:ff:ff:ff:ff
and  
ip route show
# ip route show
default via 192.168.1.254 dev eth0
192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
# ip -6 route show
2a01:348:1f9::/48 dev eth0  proto kernel  metric 256  pref medium
fe80::/64 dev eth0  proto kernel  metric 256  pref medium
default via 2a01:348:1f9::2 dev eth0  metric 1024  pref medium
  I think I found the problem (although not the real cause).  When I disable duplicate address detection with net.ipv6.conf.eth0.accept_dad = 0
it all works
  When I run wireshark on the any interface I saw the following:
Neighbor Solicitation from the Linux guest MAC
No.     Time           Source                Destination           Protocol Length Info
     12 20.935319      ::                    ff02::1:ff29:ef20     ICMPv6   80     Neighbor Solicitation for fe80::250:56ff:fe29:ef20
Frame 12: 80 bytes on wire (640 bits), 80 bytes captured (640 bits) on interface 0
Linux cooked capture
    Packet type: Sent by us (4)
    Link-layer address type: 1
    Link-layer address length: 6
    Source: Vmware_29:ef:20 (00:50:56:29:ef:20)
    Protocol: IPv6 (0x86dd)
Internet Protocol Version 6, Src: ::, Dst: ff02::1:ff29:ef20
Internet Control Message Protocol v6
Neighbor Solicitation from the Windows Host MAC
No.     Time           Source                Destination           Protocol Length Info
     13 20.935512      ::                    ff02::1:ff29:ef20     ICMPv6   80     Neighbor Solicitation for fe80::250:56ff:fe29:ef20
Frame 13: 80 bytes on wire (640 bits), 80 bytes captured (640 bits) on interface 0
Linux cooked capture
    Packet type: Multicast (2)
    Link-layer address type: 1
    Link-layer address length: 6
    Source: IntelCor_9d:b2:a0 (c8:f7:33:9d:b2:a0)
    Protocol: IPv6 (0x86dd)
Internet Protocol Version 6, Src: ::, Dst: ff02::1:ff29:ef20
Internet Control Message Protocol v6
But my Windows 10 doe not have that Local Link address advertised.
Wireless LAN adapter Wireless Network Connection:
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6235
   Physical Address. . . . . . . . . : C8-F7-33-9D-B2-A0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2a01:348:1f9::11(Preferred)
   Link-local IPv6 Address . . . . . : fe80::99c1:b8a4:3650:e511%6(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.11(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 2a01:348:1f9::2
                                       192.168.1.254
   DHCPv6 IAID . . . . . . . . . . . : 399046451
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-48-B1-63-B8-6B-23-6C-E9-0D
   DNS Servers . . . . . . . . . . . : 2a01:348:1f9::2
                                       192.168.1.2
                                       192.168.1.254
   NetBIOS over Tcpip. . . . . . . . : Enabled
  Any idea why that is happening ? 
Thank you
Markus
IPV6 setup problems on OpenSuse 
  Shadow Hawkins on Sunday, 10 April 2016 12:19:46
Sorry something went wrong with the link
Subnet Configuration
Markus
 
IPV6 setup problems on OpenSuse 
I do have a registers subnet. See route 
While you might have it, you are obviously not using it.
Apologies I did not say I run it as a guest in VMware player on Windows 10 
VMware has all kinds of weird bugs with regards to multicast and IPv6. You'll have to ask them if those problems have finally been resolved. Also note that Windows 10 is 'experimental' at most...
Also, note that Windows does not forward packets from/to an AYIYA interface.
inet6 2a01:348:1f9::29/48 scope global 
Really, configuring a full /48 on a interface is wrong.
And that prefix is part of the tunnel prefix of the PoP, only a single /64 of that is used for your subnet, nothing else.
When I disable duplicate address detection with  net.ipv6.conf.eth0.accept_dad = 0 it all works 
It cannot work as you are using the wrong prefix.
Disabling DAD is a bad thing as it means that you have duplicate addresses on the network.
Note that the 'ip addr show' output would mark an address as 'duplicate' if it was a DAD issue.
But my Windows 10 doe not have that Local Link address advertised. 
Please realize that the interfaces provided by VMware are magic. Contact VMware for the detai.s
Any idea why that is happening ? 
You are looking at the wrong interface. VMware introduces it's own interfaces to the system.
As long as you are configuring things wrong though, things will not work.
IPV6 setup problems on OpenSuse 
  Shadow Hawkins on Wednesday, 13 April 2016 21:23:26
Markus Moeller wrote:
I have searched more and found this Duplicate Address Detection misfire?
It seems more a VMware/Interface driver issue.
Markus
 
  |