dhcp on ethN instead of eth0
* Mathieu GELI (mathieu.geli at gmail.com) [070624 17:56]:
> Hi,
>
> >at debconf i talked with you, Marco Amadori about my need to specify
> >that i need to get my dhcp information from the second interface
> >(eth1) not the first (eth0) when booting from tftp (during a FAI
> >install), and you were very willing to help. thank you for that.
>
> If I properly understand the need, you want to force the device used
> just before the nfsmount phase during a netboot.
yes, that is correct
> $ grep "ip=" /usr/src/linux/Documentation/nfsroot.txt
> ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>
>
> So I'll try to append to the kernel append line something like ip=:::::ethN:dhcp
the idea is good. so good that we had it, too and tried it. :-)
except we did not use the kernel commandline format but the
debian-live command line format:
append initrd=initrd.img-2.6.18-4-amd64 ip=eth0,1.2.3.4,255.255.255.254,:eth1,,, root=/dev/nfs nfsroot=89.145.106.70:/srv/fai/nfsroot FAI_FLAGS=verbose,sshd,createvt FAI_ACTION=install boot=live
unfortunatly that did not work and can not be handled with
debian-live yet, as mentioned above.
the new FAI uses debian-live initrd infrastructure to on the fly
build an initrd.img in order to detect storage and network at
early boot instead of having those drivers complied into the
kernel statically. your approach could work with the old FAI, i
guess, and i might try it to get going with the rest of the FAI
configuration.
/andreas
Reply to: