info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
nd6 router adv problem: valid lifetime is 0
6 views
Skip to first unread message
Stuart Henderson
Aug 5, 2016, 6:55:22 AM8/5/16
to
Running current I am hitting this on the emfcamp network.
in6_update_ifa: valid lifetime is 0 for 2a05:e201:0:1224:f00a:ed61:f722:c5d1
It's slightly annoying because the default route *is* added to the table
but obviously because the address isn't added the v6 is unusable and causes
a bunch of delays.
Destination Gateway Flags Refs Use Mtu Prio Iface
default fe80::464c:a8ff:fe73:718f%iwn0 UG 0 3 - 56 iwn0
The advs are looking like this; vltime *is* set:
09:54:03.547930 44:4c:a8:73:71:8f 8c:70:5a:62:b7:f8 86dd 118: fe80::464c:a8ff:fe73:718f > fe80::b8d2:a83e:f1af:1c58: icmp6: router advertisement(chlim=64, O, pref=medium, router_ltime=1800, reachable_time=0, retrans_time=0)(src lladdr: 44:4c:a8:73:71:8f)(mtu: mtu=1500)(prefix info: A valid_ltime=2592000, preferred_ltime=604800, prefix=2a05:e201:0:1224::/64) [icmp6 cksum ok] (len 64, hlim 255)
0000: 8c70 5a62 b7f8 444c a873 718f 86dd 6000 .pZb..DL.sq...`.
0010: 0000 0040 3aff fe80 0000 0000 0000 464c ...@:.........FL
0020: a8ff fe73 718f fe80 0000 0000 0000 b8d2 ...sq...........
0030: a83e f1af 1c58 8600 d384 4040 0708 0000 .>...X....@@....
0040: 0000 0000 0000 0101 444c a873 718f 0501 ........DL.sq...
0050: 0000 0000 05dc 0304 4040 0027 8d00 0009 ........@@.'....
0060: 3a80 0000 0000 2a05 e201 0000 1224 0000 :.....*......$..
0070: 0000 0000 0000 ......
Anyone have an idea what to poke at?
in6_update_ifa: valid lifetime is 0 for 2a05:e201:0:1224:f00a:ed61:f722:c5d1
It's slightly annoying because the default route *is* added to the table
but obviously because the address isn't added the v6 is unusable and causes
a bunch of delays.
Destination Gateway Flags Refs Use Mtu Prio Iface
default fe80::464c:a8ff:fe73:718f%iwn0 UG 0 3 - 56 iwn0
The advs are looking like this; vltime *is* set:
09:54:03.547930 44:4c:a8:73:71:8f 8c:70:5a:62:b7:f8 86dd 118: fe80::464c:a8ff:fe73:718f > fe80::b8d2:a83e:f1af:1c58: icmp6: router advertisement(chlim=64, O, pref=medium, router_ltime=1800, reachable_time=0, retrans_time=0)(src lladdr: 44:4c:a8:73:71:8f)(mtu: mtu=1500)(prefix info: A valid_ltime=2592000, preferred_ltime=604800, prefix=2a05:e201:0:1224::/64) [icmp6 cksum ok] (len 64, hlim 255)
0000: 8c70 5a62 b7f8 444c a873 718f 86dd 6000 .pZb..DL.sq...`.
0010: 0000 0040 3aff fe80 0000 0000 0000 464c ...@:.........FL
0020: a8ff fe73 718f fe80 0000 0000 0000 b8d2 ...sq...........
0030: a83e f1af 1c58 8600 d384 4040 0708 0000 .>...X....@@....
0040: 0000 0000 0000 0101 444c a873 718f 0501 ........DL.sq...
0050: 0000 0000 05dc 0304 4040 0027 8d00 0009 ........@@.'....
0060: 3a80 0000 0000 2a05 e201 0000 1224 0000 :.....*......$..
0070: 0000 0000 0000 ......
Anyone have an idea what to poke at?
Stuart Henderson
Aug 5, 2016, 6:00:49 PM8/5/16
to
An update on this.
Looking at flags after a hint from phrased - they're not setting the
on-link flag (intentionally, to prevent flooding multicast NDs over the
wlan, which makes sense) so it's hitting the XXX case in nd6_rtr.c which
replaces lifetimes with 0.
Non-OpenBSD devices are working ok with this; link local to reach the
router, the address is configured on the interface, but no prefix router,
it just sends all traffic to the default router.
Looking at flags after a hint from phrased - they're not setting the
on-link flag (intentionally, to prevent flooding multicast NDs over the
wlan, which makes sense) so it's hitting the XXX case in nd6_rtr.c which
replaces lifetimes with 0.
Non-OpenBSD devices are working ok with this; link local to reach the
router, the address is configured on the interface, but no prefix router,
it just sends all traffic to the default router.
0 new messages