[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: passing static ip address to initramfs


On 2/22/09, Tim Gebbett <tim@gebbettco.com> wrote:
> Hi All,
> Does anyone know if passing static ip details to the initramfs via a
> syslinux/pxelinux menu entry works?
> The line in question reads (line split for easier reading):
> append initrd=http://x.x.x.x/otw/cz/live/initrd1.img
> console=ttyS1,57600n8 boot=live union=aufs noprompt
> ocs_live_run="ocs-live-general" ocs_live_extra_param="" ocs_live_keymap=""
> ocs_live_batch="no" ocs_lang="" nolocales
> ip=x.x.x.x::x.x.x.x:
> vga=normal fetch=http://x.x.x.x/otw/cz/live/filesystem.squashfs
> The official way defined in the manpage is:
> I have found various pages explaining how to deal with the AUTOCONF field,
> putting none, off, <blank> all to no effect. Also I am guessing that if
> you are providing static ip and loading squash_fs via a fetch: line you
> would leave the SERVER_IP field blank (I have also tried it with the
> target ip). Every combination I have tried ends up with initramfs issuing
> bootp requests regardless:
> IP-Config: eth0 hardware address 00:1e:c9:f7:56:27 mtu 1500 DHCP RARP
> [   20.146038] tg3: eth0: Link is up at 100 Mbps, full duplex.
> [   20.146038] tg3: eth0: Flow control is off for TX and off for RX.
> I do not have the ability to implement a dhcpd setup since the machines
> are based on live public connections at the datacentre.

Below is from the live-initramfs man page:

           Let you specify the name(s) and the options of the interface(s)
           that should be configured at boot time. Do not specify this if you
           want to use dhcp (default). It will be changed in a future release
           to mimick official kernel boot param specification (e.g.

Also I have a location that I too do not have the ability to get dhcp,
I don not use the boot param instead I just use chroot_local-includes
and put in an interfaces file an interfaces file in
chroot_local-includes/etc/network/ as I want the interface(s).

Reply to: