[Server-devel] One server NIC - using Sugar on Linux, not OLPCs

[Tom Parker]

On Fri, 2010-12-31 at 13:44 -0800, Rob Echlin wrote:
> I tried xs-swapnics, but that did not put the LAN stuff on eth0. It
> eliminated eth0, and gave me a phantom eth1 with no ethernet address.
> Actually, it may have put the eth1 on the NIC, but since it no longer
> had an IP address, it was hard to tell.

Strange. What is the content
of /etc/udev/rules.d/*persistent-net.rules ? xs-swapnics simply renames
your first ethernet device "eth1", and if you have one, your second
ethernet device "eth0". So it makes sense that you will have an eth1.
The XS has a very funky network configuration, so having no ip address
on the eth1 itself might actually be normal.

> Also, since my IP address on the Sugar box is 192.168, I am not sure
> that I can ping a 178.18.10.X address through my Belkin home router.
> Should that work?

It probably won't work if your sugar box has a 192.168 ip address.

> I could turn off DHCP on the router and give my other machines fixed
> addresses, so having the XS DHCP on my network would not be a problem.
> I would prefer to turn it off, though.

You'll either have to give the rest of your network fixed IPs and let
the XS manage the sugar box via DHCP, or turn off the XS's DHCP and give
the sugar box a fixed address and network setup so it can talk to the XS
box. I don't recall which address range the XS expects the XO's to
appear on, but there is a network diagram on the olpc wiki somewhere
which ought to tell you.

When I run an XS on a laptop, I put the XO lan on the wired ethernet
port and plug it into a separate wireless router with DHCP turned off.
This gives you a completely isolated network which doesn't interfere
with your home network. I then connect the laptop to my home WLAN via
it's built in wifi (instructions are on the wiki). This way the XO's get
internet via the XS, but it does require two wireless routers (my normal
home one and another one for the XO WLAN).