Re: Bug#901255: netcfg-static: Unable to configure fe80::1 as a gateway
Bjørn Mork, le mar. 12 juin 2018 15:19:25 +0200, a ecrit:
> Samuel Thibault <email@example.com> writes:
> > It's a matter of someone fixing the code. It seems Igor Scheller is
> > happy to work on it, he just needs a way forward, not being only told
> > that what is currently there is nonsense.
> Well, using fe80::1 as default gateway would not be a problem if it
> weren't for the existing nonsensical code. Don't know how to say that in
> any other way.
By proposing actual solutions instead.
So there was for one that netcfg-static needs to explicitly add a route
to the gateway. Now, to check that it works:
> So if you take a single default router address as input, then the
> validation bolis down to sending a Neighbor Solicitation and seeing if
> you receive a Neighbor Advertisement back.
The question is now how to do that easily in netcfg-static (i.e. not
crafting packets by hand).