[Fedora-livecd-list] Problems with network setup on custom livecd

[Elias Hunt]

Mark,

Thanks. I'll give splitting the network lines a try later today and see if all goes well. I do have one more question. I glanced at the patch you sent and it looks like it supports only two nameservers, a primary and secondary. We actually need to put a total of four in there. Can you just confirm if that behavior is true? If so I may be able to patch things myself to support the four that we need, though it would definitely be handy if that support ended up in the main livecd-creator code so that we can upgrade along with the rest of the world. :)

Thanks again.
-Eli

-----Original Message-----
From: fedora-livecd-list-bounces at redhat.com [mailto:fedora-livecd-list-bounces at redhat.com] On Behalf Of Mark McLoughlin
Sent: Thursday, May 31, 2007 9:37 AM
To: fedora-livecd-list at redhat.com
Subject: Re: [Fedora-livecd-list] Problems with network setup on custom livecd

On Thu, 2007-05-31 at 09:27 -0400, Elias Hunt wrote:

> network --device eth0 --bootproto static --ip 192.168.1.5 --netmask 
> 255.255.255.0 --gateway 192.168.1.1 --device eth1 --bootproto dhcp 
> --nameserver 192.168.1.5,192.168.1.6,192.168.1.110,192.168.1.111
> --hostname livecd-test.m2s.com

	AFAIR you want:

  network --device eth0 --bootproto static -ip ...
  network --device eth1 --bootproto dhcp ...

> The first problem we’re having is that only the first nameserver is 
> actually being put in the /etc/resolv.conf file.

	Ah, that's a bug. Patch attached.

> The second problem is that the eth0 interface showed up unconfigured, 
> and eth1 was set to dhcp as expected.

	That sounds like it's caused by having both devices on the one network line. Split the line up.

Cheers,
Mark.