Opened 10 months ago

Closed 10 months ago

Last modified 2 months ago

#1095 closed defect (fixed)

IPv6 RA issue on wireless

Reported by: jared@… Owned by: panda@…
Priority: tbd Milestone: ietf-098
Component: wireless Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

I'm seeing that for a period of 20 seconds there is no RA
from the IETF network, and this has been happening more than once
causing TCP timeouts and other issues.

An example:


RA seen, 600s lifetime, 
11:38:13.589236 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 96) fe80::128:1 > ff02::1: [icmp6 sum ok] ICMP6, router advertisement, length 96
        hop limit 64, Flags [other stateful], pref medium, router lifetime 600s, reachable time 0s, retrans time 0s
          source link-address option (1), length 8 (1): 00:00:5e:00:02:80
          rdnss option (25), length 40 (5):  lifetime 1800s, addr: 2001:67c:370:229::6 addr: 2001:67c:370:229::7
          prefix info option (3), length 32 (4): 2001:67c:370:128::/64, Flags [onlink, auto], valid time 2592000s, pref. time 604800s

... 600 seconds later ...

packet loss

t=600+20:

RA seen, 600s lifetime:
11:48:33.464329 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 96) fe80::128:1 > ff02::1: [icmp6 sum ok] ICMP6, router advertisement, length 96
        hop limit 64, Flags [other stateful], pref medium, router lifetime 600s, reachable time 0s, retrans time 0s
          source link-address option (1), length 8 (1): 00:00:5e:00:02:80
          rdnss option (25), length 40 (5):  lifetime 1800s, addr: 2001:67c:370:229::6 addr: 2001:67c:370:229::7
          prefix info option (3), length 32 (4): 2001:67c:370:128::/64, Flags [onlink, auto], valid time 2592000s, pref. time 604800s

ping results:

16 bytes from 2001:418:3f4::5, icmp_seq=1801 hlim=58 time=2.329 ms
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote puck.nether.net 16 chars, ret=-1
16 bytes from 2001:418:3f4::5, icmp_seq=1821 hlim=58 time=16.416 ms



-- 
Jared Mauch  | pgp key available via finger from jared@puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.

Change history (5)

comment:1 Changed 10 months ago by llynch@…

Component: incomingwireless
Owner: changed from < default > to panda@…
Status: newassigned
Type: requestdefect

comment:2 Changed 10 months ago by panda@…

Status: assignedaccepted

Hi Jared,

Sorry for the inconvenience and thank you for the report.

We've configured RA throttling to mitigate battery drain in this morning. However, the throttle period is too long compared to the lifetime of RAs. I've shorten the throttle period to 60 seconds. I think this should fix this issue, but if you still have problem, please let us know.

Thank you!
Hirochika Asai

comment:3 in reply to:  3 ; Changed 10 months ago by jared@…

I believe the RA lifetime should be at least 2x the interval as the host may not issue RS. 

I also think the RDNSS option lifetime should be the same as the RA lifetime. 

Thanks for looking at this, it interrupted me several times. 

Jared Mauch

> On Mar 30, 2017, at 11:38 AM, IETF Tickets/NOC <tickets@meeting.ietf.org> wrote:
> 
> Sorry for the inconvenience and thank you for the report.
> 
> We've configured RA throttling to mitigate battery drain in this morning.

comment:4 Changed 10 months ago by panda@…

Resolution: fixed
Status: acceptedclosed

Hi Jared,

Agree. I'll close this ticket now. Please reopen this if you will be interrupted again.

Thank you.
Hirochika Asai

comment:5 Changed 2 months ago by Rick Alfvin

Milestone: ietf-98ietf-098

Milestone renamed

Note: See TracTickets for help on using tickets.