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 

IPv6 Setup not working on Hetzner server

[Leo Unglaub]

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 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 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 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 

Re: IPv6 is not working at Hetzner

[Joel Wirāmu Pauling]

I've had problems with Hetzner and v6 also.

When I was configuring v6 sub-subnets from the /64 they give out, on
containers, I would get the same behavior. From what I could tell because
the container bridges also use the fe80::1 link local route for the
sub-subnets hetzners next-hop would get confused and just stop pushing any
v6.

They also have a bunch of Layer2 switch monitoring stuff they do to watch
for mainly v4 routes and IP's they are not expecting to exit from a
particular ports on their switches.

They call it 'locking' in their documentation and there isn't very precise
description of what exactly it is they are monitoring.


-Joel



On 22 May 2015 at 15:15, Thomas Bohl thomas-b...@gmx.de wrote:

 Am 22.05.2015 um 23:55 schrieb Heiko Zimmermann:

 # route delete -inet6 default
 # route add -inet6 default fe80::1%re0


 It worked one time until reboot.


 That is a problem I have too:
 http://marc.info/?l=openbsd-miscm=142249632125559w=2

 You first need to ping fe80::1%re0 in order to get it into the address
 mapping table. I tried static entries without luck. Try to add

 @reboot sleep 10  ping6 -c 10 fe80::1\%re0  /dev/null

 into your crontab. Works for me.


  Could you advise me hostname.re0 and mygate ?


 I don't use mygate. Just

 !route add -inet6 default fe80::1%re0

 in hostname.re0

Re: IPv6 is not working at Hetzner

[Heiko Zimmermann]

Hallo Thomas,

I get crazy. :/

Am 22.05.2015 um 22:15 schrieb Thomas Bohl: Please tryndp -an
 # route delete -inet6 default
 # route add -inet6 default fe80::1%re0

It worked one time until reboot.

I did a reboot to test again.


when I have this in mygate:
fe80::1

then I have NO default gw in inet6

# route add -inet6 default fe80::1%re0
# ping6 -vc 5 google.com

PING6(72=40+8+24 bytes) 2a01:4f8:160:4346::25 -- 2a00:1450:4001:80b::1000
32 bytes from 2a01:4f8::a:16:4: Neighbor Advertisement
32 bytes from 2a01:4f8::a:16:4: Neighbor Advertisement
32 bytes from 2a01:4f8::a:16:4: Neighbor Advertisement
80 bytes from 2a01:4f8:160:4346::25: Destination Host Unreachable
Vr TC  Flow Plen Nxt Hlim
 6 00 0 0020  3a   40
2a01:4f8:160:4346::25-2a00:1450:4001:80b::1000
ICMP6: type = 128, code = 0

# ndp -an
NeighborLinklayer Address  Netif ExpireS Flags
2a01:4f8:160:4346::2(incomplete) re0 permanent R l
2a01:4f8:160:4346::25   (incomplete) re0 permanent R l
2a01:4f8:160:4346::80   (incomplete) re0 permanent R l
fe80::5604:a6ff:feb4:99c2%re0  (incomplete)  re0 permanent R l


###
when I have this in /etc/mygate:
2a01:4f8:160:4346::1
fe80::1

!route add -inet6 default fe80::1%re0
was ignored in hostname.re0

then it is coming up with default gw 2a01:4f8:160:4346::1

$ route -n show -inet6
Routing tables
Internet6:
DestinationGatewayFlags
  Refs  Use   Mtu  Prio Iface
::/104 ::1UGRS
 00 32768 8 lo0
::/96  ::1UGRS
 00 32768 8 lo0
default2a01:4f8:160:4346::1   UGS
 00 - 8 re0
::1link#3 UHl
140 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:160:4346::/64 link#1 UC
 10 - 4 re0
2a01:4f8:160:4346::1   link#1 UHLc
 10 - 4 re0
2a01:4f8:160:4346::2   link#1 HLl
 00 - 1 lo0
2a01:4f8:160:4346::25  link#1 HLl
 00 - 1 lo0
2a01:4f8:160:4346::80  link#1 HLl
 00 - 1 lo0
fe80::/10  ::1UGRS
 00 32768 8 lo0
fe80::%re0/64  link#1 UC
 00 - 4 re0
fe80::5604:a6ff:feb4:99c2%re0  link#1 HLl
 00 - 1 lo0
fe80::%lo0/64  link#3 U
 00 32768 4 lo0
fe80::1%lo0link#3 UHl
 00 32768 1 lo0
fec0::/10  ::1UGRS
 00 32768 8 lo0
ff01::/16  ::1UGRS
 00 32768 8 lo0
ff01::%re0/32  link#1 UC
 00 - 4 re0
ff01::%lo0/32  link#3 UC
 00 32768 4 lo0
ff02::/16  ::1UGRS
 00 32768 8 lo0
ff02::%re0/32  link#1 UC
 00 - 4 re0
ff02::%lo0/32  link#3 UC
 00 32768 4 lo0


$ ndp -an
Neighbor Linklayer Address  Netif Expire
S Flags
2a01:4f8:160:4346::1 (incomplete) re0 expired   N
2a01:4f8:160:4346::2 (incomplete) re0 permanent R l
2a01:4f8:160:4346::25(incomplete) re0 permanent R l
2a01:4f8:160:4346::80(incomplete) re0 permanent R l

SOLEVED Re: IPv6 is not working at Hetzner

[Heiko Zimmermann]

You are great!

That's it.

Thank you

 -Heiko

Am 23.05.2015 um 00:15 schrieb Thomas Bohl:
 Am 22.05.2015 um 23:55 schrieb Heiko Zimmermann:
 # route delete -inet6 default
 # route add -inet6 default fe80::1%re0

 It worked one time until reboot.
 
 That is a problem I have too:
 http://marc.info/?l=openbsd-miscm=142249632125559w=2
 
 You first need to ping fe80::1%re0 in order to get it into the address
 mapping table. I tried static entries without luck. Try to add
 
 @reboot sleep 10  ping6 -c 10 fe80::1\%re0  /dev/null
 
 into your crontab. Works for me.
 
 
 Could you advise me hostname.re0 and mygate ?
 
 I don't use mygate. Just
 
 !route add -inet6 default fe80::1%re0
 
 in hostname.re0

Re: IPv6 is not working at Hetzner

[Thomas Bohl]

Am 22.05.2015 um 21:54 schrieb Heiko Zimmermann:
 Hello Thomas,

 Am 22.05.2015 um 21:38 schrieb Thomas Bohl: A dedicated or a virtual
 server? One needs fe80::1%re0 the other
 2a01:4f8:160:::1%re0 as the default gateway.
 http://wiki.hetzner.de/index.php/Zusaetzliche_IP-Adressen/en#Gateway

 Dedicated.
 So my fe80::1 is correct?

Yes, but it's not in your routing table though.

 # route -n show -inet6

 Internet6:
 DestinationGatewayFlags
Refs  Use   Mtu  Prio Iface

 default2a01:4f8:160:4346::1   UGS
   05 - 8 re0

Please try
# route delete -inet6 default
# route add -inet6 default fe80::1%re0

[demime 1.01d removed an attachment of type application/pkcs7-signature which 
had a name of smime.p7s]

Re: IPv6 is not working at Hetzner

[Thomas Bohl]

Am 22.05.2015 um 23:55 schrieb Heiko Zimmermann:

# route delete -inet6 default
# route add -inet6 default fe80::1%re0


It worked one time until reboot.


That is a problem I have too:
http://marc.info/?l=openbsd-miscm=142249632125559w=2

You first need to ping fe80::1%re0 in order to get it into the address 
mapping table. I tried static entries without luck. Try to add


@reboot sleep 10  ping6 -c 10 fe80::1\%re0  /dev/null

into your crontab. Works for me.



Could you advise me hostname.re0 and mygate ?


I don't use mygate. Just

!route add -inet6 default fe80::1%re0

in hostname.re0

Re: IPv6 is not working at Hetzner

[Heiko Zimmermann]

Hello Thomas,

Am 22.05.2015 um 21:38 schrieb Thomas Bohl: A dedicated or a virtual
server? One needs fe80::1%re0 the other
 2a01:4f8:160:::1%re0 as the default gateway.
 http://wiki.hetzner.de/index.php/Zusaetzliche_IP-Adressen/en#Gateway

Dedicated.
So my fe80::1 is correct?


 $ ping6 ipv6.google.com
 PING6(72=40+8+24 bytes) 2a01:4f8:160:::25 --
 2a00:1450:4001:80c::1002
 ^C
 -- not working

 Please post the results of
 # ping6 -vc 5 google.com

PING6(72=40+8+24 bytes) 2a01:4f8:160:::25 -- 2a00:1450:4001:80b::1008
80 bytes from 2a01:4f8:160:::25: Destination Host Unreachable
Vr TC  Flow Plen Nxt Hlim
 6 b8 0 0020  3a   40
2a01:4f8:160:::25-2a00:1450:4001:80b::1008
ICMP6: type = 128, code = 0

80 bytes from 2a01:4f8:160:::25: Destination Host Unreachable
Vr TC  Flow Plen Nxt Hlim
 6 b8 0 0020  3a   40
2a01:4f8:160:::25-2a00:1450:4001:80b::1008
ICMP6: type = 128, code = 0

--- google.com ping6 statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss


 # route -n show -inet6

Internet6:
DestinationGatewayFlags
  Refs  Use   Mtu  Prio Iface
::/104 ::1UGRS
 00 32768 8 lo0
::/96  ::1UGRS
 00 32768 8 lo0
default2a01:4f8:160:4346::1   UGS
 05 - 8 re0
::1link#3 UHl
140 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:160:4346::/64 link#1 UC
 00 - 4 re0
2a01:4f8:160:4346::2   link#1 UHLl
 00 - 1 lo0
2a01:4f8:160:4346::25  link#1 UHLl
 0   15 - 1 lo0
2a01:4f8:160:4346::80  link#1 UHLl
 00 - 1 lo0
fe80::/10  ::1UGRS
 00 32768 8 lo0
fe80::%re0/64  link#1 UC
 10 - 4 re0
fe80::1%re078:fe:3d:46:ed:9d  UHLc
 02 - 4 re0
fe80::5604:a6ff:feb4:99c2%re0  link#1 UHLl
 00 - 1 lo0
fe80::%lo0/64  link#3 U
 00 32768 4 lo0
fe80::1%lo0link#3 UHl
 00 32768 1 lo0
fec0::/10  ::1UGRS
 00 32768 8 lo0
ff01::/16  ::1UGRS
 00 32768 8 lo0
ff01::%re0/32  link#1 UC
 00 - 4 re0
ff01::%lo0/32  link#3 UC
 00 32768 4 lo0
ff02::/16  ::1UGRS
 00 32768 8 lo0
ff02::%re0/32  link#1 UC
 10 - 4 re0
ff02::1:ff00:1%re0 link#1 UHLc
 00 - 4 re0
ff02::%lo0/32  link#3 UC
 00 32768 4 lo0


 # ndp -an

Neighbor Linklayer Address  Netif Expire
S Flags
2a01:4f8:160:::2 (incomplete) re0 permanent R l
2a01:4f8:160:::25(incomplete) re0 permanent R l
2a01:4f8:160:::80(incomplete) re0 permanent R l
fe80::1%re0  78:fe:3d:46:ed:9dre0 23h50m20s S R
fe80::5604:a6ff:feb4:99c2%re0(incomplete) re0 permanent R l



## BTW #

I have a output from the predefined Linux Rescue console:

eth0  Link encap:Ethernet  Hardware Adresse 54:04:a6:b4:ZZ:ZZ
  inet Adresse:176.9.YYY.76  Bcast:176.9.YYY.ZZ
Maske:255.255.255.224
  

IPv6 is not working at Hetzner

[Heiko Zimmermann]

Hello OpenBSD users,

I have a server at Hetzner, but IPv6 is not working. IPv4 is all fine.

My Net: 2a01:4f8:160::: 64

I tried this configuration:

hostname.re0

# IPv4
...
# IPv6
inet6 2a01:4f8:160:::2 64
inet6 alias 2a01:4f8:160:::80 64
inet6 alias 2a01:4f8:160:::25 64
!route add -inet6 default fe80::1%re0


mygate

176.9.YY.65
fe80::1
2a01:4f8:160:::1


pf.conf
--snip--
# for testing
pass inet6 proto icmp6
pass in on $if inet6 proto udp from any to any port 33433  33626 keep
state
--snip---


$ ifconfig -A
...
re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
lladdr 54:04:a6:b4:XX:XX
priority: 0
groups: egress
media: Ethernet autoselect (1000baseT full-duplex)
status: active
... some IPv4 ...
inet6 fe80::5604:a6ff:feb4:99c2%re0 prefixlen 64 scopeid 0x1
inet6 2a01:4f8:160:::2 prefixlen 64
inet6 2a01:4f8:160:::80 prefixlen 64
inet6 2a01:4f8:160:::25 prefixlen 64
...


$ ping6 fe80::1%re0
PING6(72=40+8+24 bytes) fe80::5604:a6ff:feb4:99c2%re0 -- fe80::1%re0
32 bytes from fe80::1%re0, icmp_seq=0 hlim=64 time=1.408 ms
...

$ ping6 2a01:4f8:160:::1
PING6(72=40+8+24 bytes) 2a01:4f8:160:::2 -- 2a01:4f8:160:::1
^C
-- not working

$ ping6 ipv6.google.com
PING6(72=40+8+24 bytes) 2a01:4f8:160:::25 -- 2a00:1450:4001:80c::1002
^C
-- not working

pftop while ping:
ipv6-icmp Out 2a01:4f8:160:::2[3709] 2a01:4f8:160:::1[128]
 NO_TRAFFIC:NO_TRAFFIC  ... Rule 125
ipv6-icmp Out 2a01:4f8:160:::2[27870]2a01:4f8:160:::1[135]
 NO_TRAFFIC:NO_TRAFFIC  ... Rule 125

Rule 125: pass inet6 proto icmp6


I dont know how to fix it. This is my first try with IPv6. Sorry when I
did a silly mistake.

I use 5.7 current on amd64.

Thank you all for your help.
 -Heiko

Re: IPv6 is not working at Hetzner

[Thomas Bohl]

Hello,

Am 22.05.2015 um 20:33 schrieb Heiko Zimmermann:

I have a server at Hetzner, but IPv6 is not working. IPv4 is all fine.


A dedicated or a virtual server? One needs fe80::1%re0 the other 
2a01:4f8:160:::1%re0 as the default gateway.

http://wiki.hetzner.de/index.php/Zusaetzliche_IP-Adressen/en#Gateway



$ ping6 ipv6.google.com
PING6(72=40+8+24 bytes) 2a01:4f8:160:::25 -- 2a00:1450:4001:80c::1002
^C
-- not working


Please post the results of
# ping6 -vc 5 google.com
# route -n show -inet6
# ndp -an