[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: CPE router acting as host on its WAN interface (RE: draft-ietf-v6ops-ipv6-cpe-router-03.txt WGLC)
> -----Original Message-----
> From: Wes Beebee (wbeebee) [mailto:firstname.lastname@example.org]
> Sent: Wednesday, January 06, 2010 6:33 AM
> To: Templin, Fred L; Hemant Singh (shemant); Fred Baker (fred); email@example.com
> Cc: firstname.lastname@example.org; email@example.com
> Subject: RE: CPE router acting as host on its WAN interface (RE: draft-ietf-v6ops-ipv6-cpe-router-
> 03.txt WGLC)
> If IsRouter is FALSE, Linux will incorrectly garbage collect the
> addresses, leading to lack of connectivity.
Linux will garbage collect FIB entries (not addresses)
but I'm not sure the behavior is incorrect. And yes,
this leads to lack of connectivity.
> What mischief happens if the CE Router always sets IsRouter to TRUE on
> both WAN and LAN interfaces?
The IsRouter flag associated with an interface (described
in Section 6.2.1) is distinct and different from the IsRouter
flag associated with neighbor cache entries (described in
Section 5.1). It seems odd that the same name (IsRouter) is
used for two different purposes in RFC4861, but the case we
are discussing is the latter (nbr cache entries).
But, the concern I have is for the IsRouter setting in
SP router neighbor cache entries; not for IsRouter settings
in the CE router. The two are unrelated, and it is the
possibility of the SP router garbage collecting FIB
entries that concerns me.
> - Wes