On Wed, 30 Jan 2008 17:59:29 -0600 (CST) Paul Armor <parmor@xxxxxxxxxxxxxxxxxxxx> wrote: > Hi, > > On Wed, 30 Jan 2008, Jeroen van Meeuwen wrote: > > > Paul Armor wrote: > >> Hi, > >> we're trying to kickstart centos 5 on machines with broadcom 5704's, using > >> jumbo mtu's (mtu=4500). > >> > >> We're setting the option mtu=4500 which is being passed to the kernel by > >> pxelinux, and then we also set mtu=4500 in the ks.cfg. > >> > >> Perhaps I'm looking in the wrong place, but from looking at > >> loader2/loader.c, I think we're doing things properly (this worked with > >> FC4's anaconda, but is failing in Cent5). > >> > >> > >> If I set it to dhcp in the pxelinux config file AND set the mtu=4500, it > >> dhcp's, but forgets the mtu. If I set a static IP/netmask/mtu in the > >> pxelinux config file, it works as expected. > >> > >> Is this to be expected? Is this a bug? > >> > > > > MTU is actually a valid setting a DHCP server can pass onto it's clients, so > > I suspect this is expected behavior: > > > > From http://linux.die.net/man/5/dhcp-options: > > > > option interface-mtu uint16; > > > > This option specifies the MTU to use on this interface. The minimum legal > > value for the MTU is 68. > > Yup, but it's not requested, so not offered. > > anaconda's discover and requests ask for the following parameters (in the > following order): > 1, 28, 2, 3, 15, 6, 12, 40, 41, 42 > > Anaconda does NOT ask for parameter 26 (Interface MTU). > > So, what's one to do, if anaconda won't request parameter 26, nor will it > accept the "mtu=" passed to the kernel for an interface that's supposed to > dhcp? It's not anaconda, it's libdhcp. Please file a bug. -- David Cantrell <dcantrell@xxxxxxxxxx> Red Hat / Honolulu, HI
Attachment:
pgp4X56IrP6XZ.pgp
Description: PGP signature
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
