#9544 NORM 1.5-F11: ad-hoc connection assigns duplicate IP address
Zarro Boogs per Child
bugtracker at laptop.org
Tue Nov 3 18:20:26 EST 2009
#9544: ad-hoc connection assigns duplicate IP address
--------------------------------+-------------------------------------------
Reporter: mikus | Owner: marco
Type: defect | Status: new
Priority: normal | Milestone: 1.5-F11
Component: sugar | Version: Development build as of this date
Resolution: | Keywords: ad-hoc, F11, OS8, B4
Next_action: diagnose | Verified: 0
Deployment_affected: | Blockedby:
Blocking: |
--------------------------------+-------------------------------------------
Changes (by Quozl):
* next_action: add to build => diagnose
Comment:
The usual way that IP addresses are assigned in the absence of a DHCP
server is IETF RFC3927 "Dynamic Configuration of IPv4 Link-Local
Addresses" ... the 169.254.0.0/16 range ... and this is a feature of
avahi-autoipd.
avahi-autoipd is included on XO-1 build 802, XO-1 build os8, and XO-1.5
build os33.
On XO-1.5 os33 and XO-1 os8 it does not seem to get started ... I too see
10.42.43.1 at both ends. If started manually it successfully negotiates.
This is a temporary workaround:
{{{
sudo avahi-autoipd --force-bind eth0
}}}
XO-1 build 802 successfully assigns an RFC3927 address to eth0 when a
simple mesh is created in the absence of a school mesh portal or XO mesh
portal.
XO-1 build 802 also successfully assigned RFC3927 address to eth1 (an
external USB ethernet dongle) when attached to a MacBook running Mac OS X
10.6.1 Snow Leopard.
Therefore this is a regression.
I don't think it is clear what we are adding to build yet, so I'm changing
action needed to diagnose. Why are we getting 10.42.43.1, and how can we
get avahi-autoipd involved instead?
--
Ticket URL: <http://dev.laptop.org/ticket/9544#comment:3>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list