Re: IPv6 Setup not working on Hetzner server

[R0me0 ***]

+1
 ping -c 1 fe80::1%em0 > /dev/null

2016-12-05 11:05 GMT-02:00 Marc Peters :

> Am 12/02/16 um 13:39 schrieb Leo Unglaub:
> > I just found out that since i changed my mygate up to your suggestion
> > that i now have to ping6 fe80::1%em0 first and then i am able to
> > connecto to other hosts via IPv6. But not before i pinged the
> > fe80::1%em0. WTF?
>
> i have the same setup at hetzner and as someone suggested, i am using in
> my root crontab:
>
> @reboot sleep 10 && ping6 -c 10 fe80::1\%em0 > /dev/null
>
> works for me, at least.

Re: IPv6 Setup not working on Hetzner server

[Martin Pieuchot]

On 05/12/16(Mon) 14:05, Marc Peters wrote:
> Am 12/02/16 um 13:39 schrieb Leo Unglaub:
> > I just found out that since i changed my mygate up to your suggestion
> > that i now have to ping6 fe80::1%em0 first and then i am able to
> > connecto to other hosts via IPv6. But not before i pinged the
> > fe80::1%em0. WTF?
> 
> i have the same setup at hetzner and as someone suggested, i am using in
> my root crontab:
> 
> @reboot sleep 10 && ping6 -c 10 fe80::1\%em0 > /dev/null
> 
> works for me, at least.

Could you reports the problem on bugs@?  It would be nice to fix the
issue rather than documenting workarounds :)

Re: IPv6 Setup not working on Hetzner server

[Marc Peters]

Am 12/02/16 um 13:39 schrieb Leo Unglaub:
> I just found out that since i changed my mygate up to your suggestion
> that i now have to ping6 fe80::1%em0 first and then i am able to
> connecto to other hosts via IPv6. But not before i pinged the
> fe80::1%em0. WTF?

i have the same setup at hetzner and as someone suggested, i am using in
my root crontab:

@reboot sleep 10 && ping6 -c 10 fe80::1\%em0 > /dev/null

works for me, at least.

Re: IPv6 Setup not working on Hetzner server

[Sebastian Reitenbach]

On Friday, December 2, 2016 13:39 CET, Leo Unglaub 
wrote:

> Hey,
>
> On 12/02/16 13:14, Reyk Floeter wrote:
> > This is a link-local address, you have to specify the interface scope id:
> >
> > $ cat /etc/mygate
> > 144.76.102.193
> > fe80::1%em0
>
> thanks for the hint. I fixed this but that alone still does not help me
> to send IPv6 data.
>
> > Hetzner also needs to know your link-local address on em0,
> > do they use the fe80::921b:eff:fe8b:f34%em0 derived from the MAC (I think
they do)
> > or do you have to configure something like fe80::2%em0 on your side?
>
> Thats a good question. Sadly they dont specify that in the docs and are
> also not willing to answer that via there support staff.
>
> All i could find in the documentation is the following line:
>
> > For IPv6 on dedicated servers and virtual servers from the CX line, the
gateway is fe80::1.
> > Since this is a link-local address, the explicit specification of the
network adapter (usually eth0) is necessary:
> > # ip route add default via fe80::1 dev eth0
>
> There answer is that it works on Linux without config and OpenBSD is not
> supported officially.
>
>
> I just found out that since i changed my mygate up to your suggestion
> that i now have to ping6 fe80::1%em0 first and then i am able to
> connecto to other hosts via IPv6. But not before i pinged the
> fe80::1%em0. WTF?
>
> Here are my rountes before the first ping to fe80::1 and then after the
> ping.

I have a 5.9 snapshot running @Hetzner, and ran into the very same problem.
That same setup worked fine for years, but a couple of months ago, they did
some
change in their network infrastructure, and since then, I also have to ping6
first,
to enable proper IPv6 connectivity.
Since that 5.9 box is quite old, I haven't repored it, since the many
networking changes since then.

Sebastian
>
> > Routing tables (before ping)
> >
> > Internet6:
> > DestinationGatewayFlags
Refs  Use   Mtu  Prio Iface
> > defaultfe80::1%em0UGS
0  579 - 8 em0
> > ::/96  ::1UGRS
00 32768 8 lo0
> > ::/104 ::1UGRS
00 32768 8 lo0
> > ::1::1UHl
14   14 32768 1 lo0
> > ::127.0.0.0/104::1UGRS
00 32768 8 lo0
> > ::224.0.0.0/100::1UGRS
00 32768 8 lo0
> > ::255.0.0.0/104::1UGRS
00 32768 8 lo0
> > :::0.0.0.0/96  ::1UGRS
00 32768 8 lo0
> > 2002::/24  ::1UGRS
00 32768 8 lo0
> > 2002:7f00::/24 ::1UGRS
00 32768 8 lo0
> > 2002:e000::/20 ::1UGRS
00 32768 8 lo0
> > 2002:ff00::/24 ::1UGRS
00 32768 8 lo0
> > 2a01:4f8:192:42d6::/64 2a01:4f8:192:42d6::10  UC
00 - 4 em0
> > 2a01:4f8:192:42d6::10  90:1b:0e:8b:0f:34  UHLl
0   18 - 1 em0
> > fe80::/10  ::1UGRS
01 32768 8 lo0
> > fec0::/10  ::1UGRS
00 32768 8 lo0
> > fe80::%em0/64  fe80::921b:eff:fe8b:f34%em0UC
00 - 4 em0
> > fe80::921b:eff:fe8b:f34%em090:1b:0e:8b:0f:34  UHLl
00 - 1 em0
> > fe80::1%lo0fe80::1%lo0UHl
00 32768 1 lo0
> > ff01::/16  ::1UGRS
01 32768 8 lo0
> > ff01::%em0/32  fe80::921b:eff:fe8b:f34%em0Um
01 - 4 em0
> > ff01::%lo0/32  ::1Um
01 32768 4 lo0
> > ff02::/16  ::1UGRS
01 32768 8 lo0
> > ff02::%em0/32  fe80::921b:eff:fe8b:f34%em0Um
01 - 4 em0
> > ff02::%lo0/32  ::1Um
01 32768 4 lo0
>
>
> > Routing tables (after ping)
> >
> > Internet6:
> > DestinationGatewayFlags
Refs  Use   Mtu  Prio Iface
> > defaultfe80::1%em0UGS
0  581 - 8 em0
> > ::/96  ::1UGRS
00 32768 8 lo0
> > ::/104 ::1UGRS

Re: IPv6 Setup not working on Hetzner server

[Leo Unglaub]

Hey,

On 12/02/16 13:14, Reyk Floeter wrote:

This is a link-local address, you have to specify the interface scope id:

$ cat /etc/mygate
144.76.102.193
fe80::1%em0


thanks for the hint. I fixed this but that alone still does not help me 
to send IPv6 data.



Hetzner also needs to know your link-local address on em0,
do they use the fe80::921b:eff:fe8b:f34%em0 derived from the MAC (I think they 
do)
or do you have to configure something like fe80::2%em0 on your side?


Thats a good question. Sadly they dont specify that in the docs and are 
also not willing to answer that via there support staff.


All i could find in the documentation is the following line:


For IPv6 on dedicated servers and virtual servers from the CX line, the gateway 
is fe80::1.
Since this is a link-local address, the explicit specification of the network 
adapter (usually eth0) is necessary:
# ip route add default via fe80::1 dev eth0


There answer is that it works on Linux without config and OpenBSD is not 
supported officially.



I just found out that since i changed my mygate up to your suggestion 
that i now have to ping6 fe80::1%em0 first and then i am able to 
connecto to other hosts via IPv6. But not before i pinged the 
fe80::1%em0. WTF?


Here are my rountes before the first ping to fe80::1 and then after the 
ping.



Routing tables (before ping)

Internet6:
DestinationGatewayFlags   Refs  
Use   Mtu  Prio Iface
defaultfe80::1%em0UGS0  
579 - 8 em0
::/96  ::1UGRS   0  
  0 32768 8 lo0
::/104 ::1UGRS   0  
  0 32768 8 lo0
::1::1UHl   14  
 14 32768 1 lo0
::127.0.0.0/104::1UGRS   0  
  0 32768 8 lo0
::224.0.0.0/100::1UGRS   0  
  0 32768 8 lo0
::255.0.0.0/104::1UGRS   0  
  0 32768 8 lo0
:::0.0.0.0/96  ::1UGRS   0  
  0 32768 8 lo0
2002::/24  ::1UGRS   0  
  0 32768 8 lo0
2002:7f00::/24 ::1UGRS   0  
  0 32768 8 lo0
2002:e000::/20 ::1UGRS   0  
  0 32768 8 lo0
2002:ff00::/24 ::1UGRS   0  
  0 32768 8 lo0
2a01:4f8:192:42d6::/64 2a01:4f8:192:42d6::10  UC 0  
  0 - 4 em0
2a01:4f8:192:42d6::10  90:1b:0e:8b:0f:34  UHLl   0  
 18 - 1 em0
fe80::/10  ::1UGRS   0  
  1 32768 8 lo0
fec0::/10  ::1UGRS   0  
  0 32768 8 lo0
fe80::%em0/64  fe80::921b:eff:fe8b:f34%em0UC 0  
  0 - 4 em0
fe80::921b:eff:fe8b:f34%em090:1b:0e:8b:0f:34  UHLl   0  
  0 - 1 em0
fe80::1%lo0fe80::1%lo0UHl0  
  0 32768 1 lo0
ff01::/16  ::1UGRS   0  
  1 32768 8 lo0
ff01::%em0/32  fe80::921b:eff:fe8b:f34%em0Um 0  
  1 - 4 em0
ff01::%lo0/32  ::1Um 0  
  1 32768 4 lo0
ff02::/16  ::1UGRS   0  
  1 32768 8 lo0
ff02::%em0/32  fe80::921b:eff:fe8b:f34%em0Um 0  
  1 - 4 em0
ff02::%lo0/32  ::1Um 0  
  1 32768 4 lo0




Routing tables (after ping)

Internet6:
DestinationGatewayFlags   Refs  
Use   Mtu  Prio Iface
defaultfe80::1%em0UGS0  
581 - 8 em0
::/96  ::1UGRS   0  
  0 32768 8 lo0
::/104 ::1UGRS   0  
  0 32768 8 lo0
::1::1UHl   14  
 14 32768 1 lo0
::127.0.0.0/104::1UGRS   0  
  0 32768 8 lo0
::224.0.0.0/100::1UGRS   0  
  0 32768 8 lo0
::255.0.0.0/104::1UGRS   0  
  0 32768 8 lo0

Re: IPv6 Setup not working on Hetzner server

[Reyk Floeter]

Hi,

> On 02.12.2016, at 12:55, Leo Unglaub  wrote:
>
> Hey friends,
> i have the exact same problem as Heiko had more than one year ago here
> on this mailinglist. See
> http://marc.info/?l=openbsd-misc=143231965324314=2
>
> Sadly his temporary solution does not work for me so i have to bring
> this topic up again.
>
> I have a server at the german hoster "Hetzner". The IPv4 setup works
> fine, but the IPv6 setup does not work properly. I am unable to ping6
> anything other than my gateway. The gateway is reachable over IPv6, but
> thats it. Nothing more is reachable.
>
> My subnet is 2a01:4f8:192:42d6:: / 64 and i assigned
> 2a01:4f8:192:42d6::10  to this server. The IPv6 gateway is for all
> Hetzner customers fe80::1 :::::.
>

I have a similar setup that works fine at hostway.de, see below.

>
> I configured my system as follows:
>> # cat /etc/hostname.em0
>> inet 144.76.102.204 255.255.255.224 144.76.102.223 description
hetzner-uplink
>> inet6 2a01:4f8:192:42d6::10 64
>
>> # cat /etc/mygate
>> 144.76.102.193
>> fe80::1
>
>

This is a link-local address, you have to specify the interface scope id:

$ cat /etc/mygate
144.76.102.193
fe80::1%em0

Hetzner also needs to know your link-local address on em0,
do they use the fe80::921b:eff:fe8b:f34%em0 derived from the MAC (I think they
do)
or do you have to configure something like fe80::2%em0 on your side?

Reyk

> This results in the following config:
>> # ifconfig em0
>> em0: flags=8843 mtu 1500
>>lladdr 90:1b:0e:8b:0f:34
>>description: hetzner-uplink
>>index 1 priority 0 llprio 3
>>groups: egress
>>media: Ethernet autoselect (1000baseT
full-duplex,master,rxpause,txpause)
>>status: active
>>inet 144.76.102.204 netmask 0xffe0 broadcast 144.76.102.223
>>inet6 fe80::921b:eff:fe8b:f34%em0 prefixlen 64 scopeid 0x1
>>inet6 2a01:4f8:192:42d6::10 prefixlen 64
>>
>
>
> But IPv6 does not work. Here are some examples:
>
>> # ping6 -c 3 google.com
>> PING6 google.com (2a00:1450:4001:80e::200e): 24 data bytes
>> ping6: sendmsg: No route to host
>> ping6: wrote google.com 32 chars, ret=-1
>> ping6: sendmsg: No route to host
>> ping6: wrote google.com 32 chars, ret=-1
>> ping6: sendmsg: No route to host
>> ping6: wrote google.com 32 chars, ret=-1
>> --- google.com ping6 statistics ---
>> 3 packets transmitted, 0 packets received, 100.0% packet loss
>
>
>> # ping6 -c 3 fe80::921b:eff:fe8b:f34%em0
>> PING6 fe80::921b:eff:fe8b:f34%em0 (fe80::921b:eff:fe8b:f34%em0): 24 data
bytes
>> 32 bytes from fe80::921b:eff:fe8b:f34%em0, icmp_seq=0 hlim=64 time=0.188
ms
>> 32 bytes from fe80::921b:eff:fe8b:f34%em0, icmp_seq=1 hlim=64 time=0.088
ms
>> 32 bytes from fe80::921b:eff:fe8b:f34%em0, icmp_seq=2 hlim=64 time=0.087
ms
>> --- fe80::921b:eff:fe8b:f34%em0 ping6 statistics ---
>> 3 packets transmitted, 3 packets received, 0.0% packet loss
>> round-trip min/avg/max/std-dev = 0.087/0.121/0.188/0.047 ms
>
>
> Here are my routes and my ndp
>
>> # ndp -an
>> Neighbor Linklayer Address  Netif ExpireS
Flags
>> 2a01:4f8:192:42d6::1090:1b:0e:8b:0f:34em0 permanent R
l
>> fe80::921b:eff:fe8b:f34%em0  90:1b:0e:8b:0f:34em0 permanent R
l
>
>
>> # route -n show -inet6
>> Routing tables
>>
>> Internet6:
>> DestinationGatewayFlags
Refs  Use   Mtu  Prio Iface
>> ::/96  ::1UGRS
00 32768 8 lo0
>> ::/104 ::1UGRS
00 32768 8 lo0
>> ::1::1UHl
14   14 32768 1 lo0
>> ::127.0.0.0/104::1UGRS
00 32768 8 lo0
>> ::224.0.0.0/100::1UGRS
00 32768 8 lo0
>> ::255.0.0.0/104::1UGRS
00 32768 8 lo0
>> :::0.0.0.0/96  ::1UGRS
00 32768 8 lo0
>> 2002::/24  ::1UGRS
00 32768 8 lo0
>> 2002:7f00::/24 ::1UGRS
00 32768 8 lo0
>> 2002:e000::/20 ::1UGRS
00 32768 8 lo0
>> 2002:ff00::/24 ::1UGRS
00 32768 8 lo0
>> 2a01:4f8:192:42d6::/64 2a01:4f8:192:42d6::10  UC
00 - 4 em0
>> 2a01:4f8:192:42d6::10  90:1b:0e:8b:0f:34  UHLl
00 - 1 em0
>> fe80::/10  ::1UGRS
02 32768 8 lo0
>> fec0::/10  ::1UGRS
00 32768