mesh portal discovery

David Woodhouse dwmw2 at
Wed Jan 9 14:08:55 EST 2008

On Wed, 2008-01-09 at 11:34 -0500, John Watlington wrote:
> Right now we have a problem with mesh portal discovery.
> The DHCP procedure currently being used only discovers
> the nearest mesh portal when it is first run (DHCP_DISCOVER),
> not when it tries to renew (DHCP_REQUEST).   Furthermore,
> as the address previously assigned indicates which mesh portal
> was selected, it seems like we should always be discovering, not
> renewing...

Legacy IP doesn't work well and doesn't really give us what we need in
the long term... or even the medium term. We've known that all along.

What do you propose to do about it? Throw away pointless engineering
into cobbling together some way of making Legacy IP work a bit better? I
seriously hope not. Just switch off the Legacy IP, as we should have
done months ago, and get on with making things work properly. Anything
else is a distraction.


More information about the Devel mailing list