#1107 closed defect (not broken)
IPv6 wireless issues
Reported by: | Owned by: | Clemens Schrimpe | |
---|---|---|---|
Priority: | major | Milestone: | ietf-099 |
Component: | wireless | Keywords: | |
Cc: | My Current Location: | ||
My MAC Address: | My OS: |
Description
I'm seeing periods of time where IPv6 goes unavailable on wireless. This seems similar to what was seen at Chicago/IETF98 where the prefix lifetimes were less than prefix intervals.
Change history (13)
comment:1 Changed 4 years ago by
Owner: | changed from llynch@… to con@… |
---|---|
Status: | new → assigned |
comment:3 Changed 4 years ago by
Component: | incoming → wireless |
---|---|
Type: | request → defect |
comment:4 Changed 4 years ago by
Owner: | changed from con@… to Clemens Schrimpe |
---|
comment:5 Changed 4 years ago by
Spoke with Jared. He believe's he was on ietf, but isn't certain. The claim is that the prefix lifetime in the RA is shorter than the unsolicited RA interval. Please check both the Junipers and the Edgerouters to ensure it's set reasonably.
comment:6 Changed 4 years ago by
Status: | assigned → accepted |
---|
... that would be embarrassing - will 👀
comment:7 follow-up: 7 Changed 4 years ago by
I'm fairly sure I was on ietf-hotel while in the meeting space based on my saved ipv6 address in my buffer, which was: 2001:67c:1232:144:8e:3d97:857d:8d32
comment:8 Changed 4 years ago by
Looks good on the Junipers. From the group templates at the top of both:
RA_Config {
protocols {
router-advertisement {
interface <*> {
max-advertisement-interval 5;
min-advertisement-interval 3;
other-stateful-configuration;
virtual-router-only;
default-lifetime 600;
dns-server-address 2001:67c:370:229::6;
dns-server-address 2001:67c:370:229::7;
}
}
}
}
comment:9 Changed 4 years ago by
On the indicated network (2001:67c:1232:144::/64 → "ietf-hotel" wireless network) the prefix lifetime is (and was) one month → 2592000 seconds.
If you keep losing connectivity we'll have to investigate - there might be different reasons.
comment:11 Changed 4 years ago by
Jared, could you please come by the NOC and work with Clemens if this reoccurs? We've been unable to reproduce.
- Jim
comment:12 Changed 4 years ago by
Resolution: | → not broken |
---|---|
Status: | accepted → closed |
As per agreement w/ Jared we are closing this ticket now. He'll re-open it if he ever encounters The Problem™ again.