IPv6 problems

classic Classic list List threaded Threaded
28 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: IPv6 problems

List
Hi,

so i removed everything from /etc/mygate and rebooted the machine.

I still cannot ping anybody.

The output of slaacctl show interface vio0 ist the following:

<hostname># slaacctl show interface vio0

slaacctl: connect: /dev/slaacd.sock: Connection refused

This is not how it is supposed to be i guess.

My provider doesn't have any BSD related examples.


Thanks for your time freda bundchen!


Regards,

Stephan

On 8/18/19 3:10 PM, [hidden email] wrote:

>> From:       list <list () md5collisions ! eu>
>> my /etc/hostname looks exactly like you proposed:
>> inet6 autoconf autoconfprivacy soii
>> inet6 <my IP6>
>> when i enter the default IPv6 gateway manually. I can ping stuff
>> but don't get a reply.  When I don't: "No route to host"
>> (With route to fe80::1%vio added and the normal hostname.vio0)
> I would suggest not specifying any routes or link-local addresses, and
> instead in /etc/hostname.vio0 make sure the IPv6 address in <my IP6>
> is the public IPv6 address given by your provider (I know there's a
> /64, but I'm just going by the example of my own provider.)
>
> Then make sure /etc/mygate doesn't have any IPv6 addresses. Then
> perhaps reboot everything to make sure you've cleared out references
> to fe80::1, if /bin/sh /etc/netstart doesn't get everything working.
>
> My provider's configuration examples said to use -autoconfprivacy and
> -soii so you might try that also. But mine works with autoconfprivacy
> and soii.
>
> What is the output of slaacctl show interface vio0?
>
>

Reply | Threaded
Open this post in threaded view
|

Re: IPv6 problems

Bastien Durel-2
In reply to this post by List
Le dimanche 18 août 2019 à 11:50 +0200, list a écrit :

> When I take a closer look and run tcpdump while pinging I see the
> following output:
> (With route to fe80::1%vio added and the normal hostname.vio0)
>
> 11:40:36.446539 fe80::<MY LL> > ff02::1:ff00:1: icmp6: neighbor sol:
> who has fe80::1
>
> This line is being repeated over and over again. I left out all the
> other traffic that is not related to my /64.
>
> Hm...
> Any ideas ?
>
> I've got a feeling that somethings wrong with that fe80::1
> address...
Hello,

A router may be configured to use fe80::1 LL address, but it may not
too. It's not a standard AFAIK. I never encountered one myself.
If no one responds to your neighbor sol packet, it's probably because
no router uses this address.

To discover routers in an unknown network, I use "ping6 ff02::2%vio0",
as ff02::2 is a standard multicast address for "ip6-allrouters" (as
ff02::1 is for all nodes)

--
Bastien

Reply | Threaded
Open this post in threaded view
|

Re: IPv6 problems

Florian Obser-2
In reply to this post by List
On Sun, Aug 18, 2019 at 07:36:55PM +0200, list wrote:
> Hi,
>
> The output of slaacctl show interface vio0 ist the following:
>
> <hostname># slaacctl show interface vio0
>
> slaacctl: connect: /dev/slaacd.sock: Connection refused
>
> This is not how it is supposed to be i guess.

it would be interesting to know why slaacd is not running though.
Because it's supposed to be always running.

It looks like this when no v6 is configured at all:

[florian@openbsd-dev:~]
> slaacctl show interface em0

[florian@openbsd-dev:~]

and like this once v6 is configured but no router advertisements are
present:
[florian@openbsd-dev:~]
> doas ifconfig em0 inet6 autoconf
[florian@openbsd-dev:~]
> slaacctl show interface em0
em0:
         index:   1 running: yes privacy: yes
        lladdr: 00:0c:29:61:52:4b
         inet6: fe80::86fa:49f4:be6c:1ca8%em0



--
I'm not entirely sure you are real.

Reply | Threaded
Open this post in threaded view
|

Re: IPv6 problems

List
In reply to this post by Bastien Durel-2
Hi,

I might be missing something right here....

I have the output of "route show" attached, because I cannot paste it in
here in a formatted form.


This is super annoying.

Just wanna get the damn thing running.


Regards,

Stephan

On 8/19/19 10:33 AM, Bastien Durel wrote:

> Le dimanche 18 août 2019 à 11:50 +0200, list a écrit :
>> When I take a closer look and run tcpdump while pinging I see the
>> following output:
>> (With route to fe80::1%vio added and the normal hostname.vio0)
>>
>> 11:40:36.446539 fe80::<MY LL> > ff02::1:ff00:1: icmp6: neighbor sol:
>> who has fe80::1
>>
>> This line is being repeated over and over again. I left out all the
>> other traffic that is not related to my /64.
>>
>> Hm...
>> Any ideas ?
>>
>> I've got a feeling that somethings wrong with that fe80::1
>> address...
> Hello,
>
> A router may be configured to use fe80::1 LL address, but it may not
> too. It's not a standard AFAIK. I never encountered one myself.
> If no one responds to your neighbor sol packet, it's probably because
> no router uses this address.
>
> To discover routers in an unknown network, I use "ping6 ff02::2%vio0",
> as ff02::2 is a standard multicast address for "ip6-allrouters" (as
> ff02::1 is for all nodes)
>

outputRouteShow.txt (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: IPv6 problems

Fernando Gont-2
On 22/8/19 21:11, list wrote:

> Hi,
>
> I might be missing something right here....
>
> I have the output of "route show" attached, because I cannot paste it in
> here in a formatted form.
>
>
> This is super annoying.
>
> Just wanna get the damn thing running.


Your default route is wrong. Namely:

default            ff02::2%vio0       UGS        0        1     -     8
vio0

If your provider says that the default router is on fe80::1, then the
default route should be:

default            fe80::1%vio0       UGS        0        1     -     8
vio0


Thanks,
--
Fernando Gont
e-mail: [hidden email] || [hidden email]
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1



Reply | Threaded
Open this post in threaded view
|

Re: IPv6 problems

Bastien Durel-2
In reply to this post by List
Le jeudi 22 août 2019 à 20:11 +0200, list a écrit :

> Hi,
>
> I might be missing something right here....
>
> I have the output of "route show" attached, because I cannot paste it
> in
> here in a formatted form.
>
>
> This is super annoying.
>
> Just wanna get the damn thing running.
>
ff02::2 is a multicast address, it's not intended to be used as a route
gateway.
It's only a way to discover routers.

for example:

fremen# ping6  ff02::2%em1
PING ff02::2%em1 (ff02::2%em1): 56 data bytes
64 bytes from fe80::6366:1356:e19:f361%em1: icmp_seq=0 hlim=64 time=0.114 ms
64 bytes from fe80::225:22ff:fe1e:bb7%em1: icmp_seq=0 hlim=64 time=0.320 ms (DUP!)
64 bytes from fe80::6366:1356:e19:f361%em1: icmp_seq=1 hlim=64 time=0.082 ms
64 bytes from fe80::225:22ff:fe1e:bb7%em1: icmp_seq=1 hlim=64 time=0.293 ms (DUP!)

Here fe80::6366:1356:e19:f361 is the LL address of em1, so
fe80::225:22ff:fe1e:bb7%em1 is the router on the other side of link.

--
Bastien

Reply | Threaded
Open this post in threaded view
|

Re: IPv6 problems

List
Hello,

@Fernando Gont:

I have tried that as well. No difference.


@ Bastien Durel

When pinging ff02::2%vio0 I don't receive any replies.

The tcpdump for those requests is the following:

<host># tcpdump -ni vio0 icmp6      
tcpdump: listening on vio0, link-type EN10MB
15:47:40.580787 fe80::22d8:b00:86fa:424c > ff02::1:ff00:0: icmp6: neighbor sol: who has 2a03:4000:21:6db:: [class 0xc0]
15:47:40.583638 fe80::22d8:b00:86fa:424c > ff02::1:ff96:189a: icmp6: neighbor sol: who has 2a03:4000:21:18a:84e:27ff:fe96:189a [class 0xc0]
15:47:41.725300 fe80::22d8:b00:86ee:ff4 > ff02::1:ff96:189a: icmp6: neighbor sol: who has 2a03:4000:21:18a:84e:27ff:fe96:189a [class 0xc0]
15:47:43.844162 fe80::2de:361a:24aa:d7a6 > ff02::2: icmp6: echo request
15:47:44.845036 fe80::2de:361a:24aa:d7a6 > ff02::2: icmp6: echo request
15:47:45.581326 fe80::22d8:b00:86fa:424c > ff02::1:ff96:189a: icmp6: neighbor sol: who has 2a03:4000:21:18a:84e:27ff:fe96:189a [class 0xc0]
15:47:45.834984 fe80::2de:361a:24aa:d7a6 > ff02::2: icmp6: echo request
15:47:46.729443 fe80::22d8:b00:86ee:ff4 > ff02::1:ff96:189a: icmp6: neighbor sol: who has 2a03:4000:21:18a:84e:27ff:fe96:189a [class 0xc0]
15:47:46.835383 fe80::2de:361a:24aa:d7a6 > ff02::2: icmp6: echo request
15:47:47.580262 fe80::22d8:b00:86fa:424c > ff02::1:ff00:3: icmp6: neighbor sol: who has 2a03:4000:21:6ef::3 [class 0xc0]
15:47:47.835361 fe80::2de:361a:24aa:d7a6 > ff02::2: icmp6: echo request
15:47:48.581182 fe80::22d8:b00:86fa:424c > ff02::1:ff00:3: icmp6: neighbor sol: who has 2a03:4000:21:6ef::3 [class 0xc0]
15:47:48.581516 fe80::8d4:7cff:fe04:a773 > ff02::1:ff00:0: icmp6: neighbor sol: who has ::
15:47:48.582270 fe80::845e:61ff:fe17:997d > ff02::1:ff00:0: icmp6: neighbor sol: who has ::
15:47:48.584608 fe80::3800:edff:fe06:769c > ff02::1:ff00:0: icmp6: neighbor sol: who has ::
15:47:48.590014 fe80::b438:86ff:fe34:b14d > ff02::1:ff00:0: icmp6: neighbor sol: who has ::
15:47:48.835487 fe80::2de:361a:24aa:d7a6 > ff02::2: icmp6: echo request
15:47:49.580501 fe80::22d8:b00:86fa:424c > ff02::1:ff00:3: icmp6: neighbor sol: who has 2a03:4000:21:6ef::3 [class 0xc0]
15:47:49.835293 fe80::2de:361a:24aa:d7a6 > ff02::2: icmp6: echo request
15:47:50.589407 fe80::22d8:b00:86fa:424c > ff02::1:ff96:189a: icmp6: neighbor sol: who has 2a03:4000:21:18a:84e:27ff:fe96:189a [class 0xc0]
15:47:51.725823 fe80::22d8:b00:86ee:ff4 > ff02::1:ff96:189a: icmp6: neighbor sol: who has 2a03:4000:21:18a:84e:27ff:fe96:189a [class 0xc0]

fe80::2de:361a:24aa:d7a6
 --> address of my interface.

Regards,
Stephan.

On 8/23/19 1:13 PM, Bastien Durel wrote:

> Le jeudi 22 août 2019 à 20:11 +0200, list a écrit :
>> Hi,
>>
>> I might be missing something right here....
>>
>> I have the output of "route show" attached, because I cannot paste it
>> in
>> here in a formatted form.
>>
>>
>> This is super annoying.
>>
>> Just wanna get the damn thing running.
>>
> ff02::2 is a multicast address, it's not intended to be used as a route
> gateway.
> It's only a way to discover routers.
>
> for example:
>
> fremen# ping6  ff02::2%em1
> PING ff02::2%em1 (ff02::2%em1): 56 data bytes
> 64 bytes from fe80::6366:1356:e19:f361%em1: icmp_seq=0 hlim=64 time=0.114 ms
> 64 bytes from fe80::225:22ff:fe1e:bb7%em1: icmp_seq=0 hlim=64 time=0.320 ms (DUP!)
> 64 bytes from fe80::6366:1356:e19:f361%em1: icmp_seq=1 hlim=64 time=0.082 ms
> 64 bytes from fe80::225:22ff:fe1e:bb7%em1: icmp_seq=1 hlim=64 time=0.293 ms (DUP!)
>
> Here fe80::6366:1356:e19:f361 is the LL address of em1, so
> fe80::225:22ff:fe1e:bb7%em1 is the router on the other side of link.
>

Reply | Threaded
Open this post in threaded view
|

Re: IPv6 problems

List
In reply to this post by Bastien Durel-2
Hi,

when doing slaacctl send solicitation vio0, tcpdump says:

mx-00# tcpdump -ni vio0 icmp6 tcpdump: listening on vio0, link-type EN10MB

16:06:54.725229 fe80::2de:361a:24aa:d7a6 > ff02::2: icmp6: router
solicitation

16:06:55.803125 fe80::22d8:b00:86fa:424c > ff02::1:ff96:189a: icmp6:
neighbor sol: who has 2a03:4000:21:18a:84e:27ff:fe96:189a [class 0xc0]

16:06:55.807067 fe80::b438:86ff:fe34:b14d > ff02::1:ff00:0: icmp6:
neighbor sol: who has ::

16:06:57.152589 fe80::22d8:b00:86ee:ff4 > ff02::1:ff96:189a: icmp6:
neighbor sol: who has 2a03:4000:21:18a:84e:27ff:fe96:189a [class 0xc0]

16:06:58.815291 fe80::22d8:b00:86fa:424c > ff02::1:ff00:0: icmp6:
neighbor sol: who has 2a03:4000:21:6db:: [class 0xc0]

16:06:59.815941 fe80::22d8:b00:86fa:424c > ff02::1:ff00:0: icmp6:
neighbor sol: who has 2a03:4000:21:6db:: [class 0xc0]

16:07:00.822213 fe80::22d8:b00:86fa:424c > ff02::1:ff00:0: icmp6:
neighbor sol: who has 2a03:4000:21:6db:: [class 0xc0]

16:07:00.823550 fe80::7452:47ff:fe16:9b9 > ff02::1:ff00:0: icmp6:
neighbor sol: who has ::

16:07:00.825485 fe80::22d8:b00:86fa:424c > ff02::1:ff96:189a: icmp6:
neighbor sol: who has 2a03:4000:21:18a:84e:27ff:fe96:189a [class 0xc0]
16:07:02.150665 fe80::22d8:b00:86ee:ff4 > ff02::1:ff96:189a: icmp6:
neighbor sol: who has 2a03:4000:21:18a:84e:27ff:fe96:189a [class 0xc0]
^C 2558 packets received by filter


Any clearance ?


Regards,

Stephan

On 8/23/19 1:13 PM, Bastien Durel wrote:

> Le jeudi 22 août 2019 à 20:11 +0200, list a écrit :
>> Hi,
>>
>> I might be missing something right here....
>>
>> I have the output of "route show" attached, because I cannot paste it
>> in
>> here in a formatted form.
>>
>>
>> This is super annoying.
>>
>> Just wanna get the damn thing running.
>>
> ff02::2 is a multicast address, it's not intended to be used as a route
> gateway.
> It's only a way to discover routers.
>
> for example:
>
> fremen# ping6  ff02::2%em1
> PING ff02::2%em1 (ff02::2%em1): 56 data bytes
> 64 bytes from fe80::6366:1356:e19:f361%em1: icmp_seq=0 hlim=64 time=0.114 ms
> 64 bytes from fe80::225:22ff:fe1e:bb7%em1: icmp_seq=0 hlim=64 time=0.320 ms (DUP!)
> 64 bytes from fe80::6366:1356:e19:f361%em1: icmp_seq=1 hlim=64 time=0.082 ms
> 64 bytes from fe80::225:22ff:fe1e:bb7%em1: icmp_seq=1 hlim=64 time=0.293 ms (DUP!)
>
> Here fe80::6366:1356:e19:f361 is the LL address of em1, so
> fe80::225:22ff:fe1e:bb7%em1 is the router on the other side of link.
>

12