Daniel,
If you are getting a self-assigned IP address, it is
because the laptop is not discovering the MPP.
This is probably due to a short cut in the MPP
discovery process.
The original process was:
- Discover the MPP by broadcasting an MPP discovery
request using the MPP anycast MAC
On Tue, Jul 7, 2009 at 8:03 AM, John Watlingtonw...@laptop.org wrote:
The XS server software should set up any mesh interfaces
to accept the anycast MAC address, but this might have
been lost in more recent builds.
Interesting. When was this last seen to work? I can do some quick
archeology
Hi John,
On Tue, 2009-07-07 at 02:03 -0400, John Watlington wrote:
If you are getting a self-assigned IP address, it is
because the laptop is not discovering the MPP.
This is probably due to a short cut in the MPP
discovery process.
The NM-0.6 code *definitely* ignores the IP address
On Tue, Jul 7, 2009 at 8:03 AM, John Watlingtonw...@laptop.org wrote:
The XS server software should set up any mesh interfaces
to accept the anycast MAC address, but this might have
been lost in more recent builds.
Interesting. When was this last seen to work? I can do some quick
archeology
Hi John,
On Tue, 2009-07-07 at 02:03 -0400, John Watlington wrote:
If you are getting a self-assigned IP address, it is
because the laptop is not discovering the MPP.
This is probably due to a short cut in the MPP
discovery process.
The NM-0.6 code *definitely* ignores the IP address
Hi,
When connecting to a MPP-based mesh, the XO ignores the IP address from
the MPP DHCP server and instead picks one using autoipd. Does anyone
know the motivation behind this?
http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/nm-device-802-11-mesh-olpc.c?h=nm-0-6-olpc
I'm
