@Michael: I deactivate PF to make my tests (I want to have IPv6 working
before I think of fw rules)
@Giancarlo: yes, I have no log even with debug
Please find below the new tcpdump:
11:25:26.017135 fe80::200:24ff:fed1:86bc > ff02::2: icmp6: router
solicitation (src lladdr: 00:00:24:d1:86:bc) [icmp6 cksum ok] (len 16, hlim
255)
6000 0000 0010 3aff fe80 0000 0000 0000
0200 24ff fed1 86bc ff02 0000 0000 0000
0000 0000 0000 0002 8500 2413 0000 0000
0101 0000 24d1 86bc
11:25:26.031216 fe80::1 > ff02::1: icmp6: router advertisement(chlim=64, MO
router_ltime=1800, reachable_time=0, retrans_time=0)(src lladdr:
fc:48:ef:c3:41:fe)(mtu: mtu=1500) [icmp6 cksum ok] [class 0xc0] (len 32,
hlim 255)
6c00 0000 0020 3aff fe80 0000 0000 0000
0000 0000 0000 0001 ff02 0000 0000 0000
0000 0000 0000 0001 8600 fa6d 40c0 0708
0000 0000 0000 0000 0101 fc48 efc3 41fe
0501 0000 0000 05dc
11:26:00.025990 fe80::1 > ff02::1: icmp6: router advertisement(chlim=64, MO
router_ltime=1800, reachable_time=0, retrans_time=0)(src lladdr:
fc:48:ef:c3:41:fe)(mtu: mtu=1500) [icmp6 cksum ok] [class 0xc0] (len 32,
hlim 255)
6c00 0000 0020 3aff fe80 0000 0000 0000
0000 0000 0000 0001 ff02 0000 0000 0000
0000 0000 0000 0001 8600 fa6d 40c0 0708
0000 0000 0000 0000 0101 fc48 efc3 41fe
0501 0000 0000 05dc
11:26:04.025295 fe80::1 > ff02::1: icmp6: router advertisement(chlim=64, MO
router_ltime=1800, reachable_time=0, retrans_time=0)(src lladdr:
fc:48:ef:c3:41:fe)(mtu: mtu=1500) [icmp6 cksum ok] [class 0xc0] (len 32,
hlim 255)
6c00 0000 0020 3aff fe80 0000 0000 0000
0000 0000 0000 0001 ff02 0000 0000 0000
0000 0000 0000 0001 8600 fa6d 40c0 0708
0000 0000 0000 0000 0101 fc48 efc3 41fe
0501 0000 0000 05dc
11:26:26.016515 fe80::200:24ff:fed1:86bc > ff02::2: icmp6: router
solicitation (src lladdr: 00:00:24:d1:86:bc) [icmp6 cksum ok] (len 16, hlim
255)
6000 0000 0010 3aff fe80 0000 0000 0000
0200 24ff fed1 86bc ff02 0000 0000 0000
0000 0000 0000 0002 8500 2413 0000 0000
0101 0000 24d1 86bc
11:26:26.022949 fe80::1 > ff02::1: icmp6: router advertisement(chlim=64, MO
router_ltime=1800, reachable_time=0, retrans_time=0)(src lladdr:
fc:48:ef:c3:41:fe)(mtu: mtu=1500) [icmp6 cksum ok] [class 0xc0] (len 32,
hlim 255)
6c00 0000 0020 3aff fe80 0000 0000 0000
0000 0000 0000 0001 ff02 0000 0000 0000
0000 0000 0000 0001 8600 fa6d 40c0 0708
0000 0000 0000 0000 0101 fc48 efc3 41fe
0501 0000 0000 05dc
Can you try to capture the whole packet? Try setting a snaplen of 1500. I
> believe it is too early to give up on SLAAC. But you might need DHCPv6
> anyway, if your router don't advertise the dns servers. See if you ain't
> getting malformed packets from the router, or if it's advertising, but with
> no actual prefixes/routes. Per RFC 7084 [0], a router should stop
> advertising when it doesn't have global IPv6 connectivity. But, not every
> manufacturer is fond of RFC's.
I have on my settings sheet the DNS and the prefix I'm delegated.
I tried wide dhcpv6 and it works but I would like if possible to go without
it.
The modem brand is Huawei but i don't have the model here.
Thanks,
Alex
On Wed, Aug 19, 2015 at 2:26 AM, Giancarlo Razzolini <grazzol...@gmail.com>
wrote:
> Em 17-08-2015 22:41, Alexandre Westfahl escreveu:
>
> I activated debug but don't get any outputââ¬â¹ anywhere. Since I
couldn't find
> anything, I tried a global grep but without success (cat */var/log/**
|grep
> inet6 and ipv6).
>
>
> Kernel messages will appear on /var/log/messages, IIRC. And on dmesg and
> on the console. So I guess that, if there was any, you'd see them.
>
>
> Since my tcpdump result are not changed, it means I have to install
> dhcpv6client? I need the "wide" one or another one?
>
>
> Can you try to capture the whole packet? Try setting a snaplen of 1500. I
> believe it is too early to give up on SLAAC. But you might need DHCPv6
> anyway, if your router don't advertise the dns servers. See if you ain't
> getting malformed packets from the router, or if it's advertising, but with
> no actual prefixes/routes. Per RFC 7084 [0], a router should stop
> advertising when it doesn't have global IPv6 connectivity. But, not every
> manufacturer is fond of RFC's.
>
> Cheers,
> Giancarlo Razzolini
>
> [0] https://tools.ietf.org/html/rfc7084
