[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
routing the "wrong /32" should not happen. at least it should be impossible to
connect to each other. that would be a hard misconfiguration on more places.
that would only prove how badly it looks like to our planet's internet.
neighbor discovery does also give each node a timeout, so nodes that are not
on should not appear in the table.
On Wed, 20 Feb 2013 00:52:25 +0000 (UTC)
George Michaelson <ggm%pobox.com@localhost> wrote:
> I have accidentally participated in an apparent DoS like this, when a
> diagnostic 'is IPv6 working' account I hosted leaked to the wrong /32 and
> an ISP somewhere in South America started to get saturated by a walk
> across their announced space.
> I believe there are commercial implementations of switch logic which do
> some kind of ageing out of the ND cache to set limits on growth. Maybe a
> Ptree for this stuff in NetBSD needs a timer, and a background process to
> mark/sweep idle entries.
Main Index |
Thread Index |