#5854 LOW Future : Wired devices not activating correctly
Zarro Boogs per Child
bugtracker at laptop.org
Sat Jan 19 15:26:38 EST 2008
#5854: Wired devices not activating correctly
------------------------------+---------------------------------------------
Reporter: mikus | Owner: dcbw
Type: enhancement | Status: new
Priority: low | Milestone: Future Release
Component: network manager | Version:
Resolution: | Keywords: wired ethernet
Verified: 0 | Blocking:
Blockedby: |
------------------------------+---------------------------------------------
Changes (by mikus):
* cc: mikus at bga.com (added)
Comment:
Let me clarify what I was doing at the time when I wrote this ticket. I
have a home LAN. All systems on it have 'permanent, manually set' IP
addresses. I was doing the same with the XO -- taking eth0 (and the
radio) down, then bringing eth0 up with a manually-specified IP address.
After seeing that what I did had confused NetworkManager, I wrote the
ticket on the assumption that if a "dummy" device (one *not* used by
NetworkManager) were provided by the XO, then the user could manually
assign (e.g., via ifconfig) an interface (e.g., eth2 with a 'permanent,
manually set' IP address) to his external adapter -- without risking
NetworkManager confusion.
Since I wrote this ticket, I've set up a DHCP server on my LAN, for the
sole purpose of assigning the XO an appropriate IP address whenever the XO
gets booted with its USB-ethernet adapter plugged in (it works, and gives
LAN access to the XO). But setting up a server was considerably more work
than issuing a manual ifconfig at the XO -- so I think it would still be a
good idea to define an extra device (not used by NetworkManager),
available for users who want to try adding external adapters.
--
Ticket URL: <http://dev.laptop.org/ticket/5854#comment:3>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system
More information about the Bugs
mailing list