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

IP address of diskless workstation expiriing



Hello all,

I'm in the process of setting up a diskless workstation. Both the
workstation and the server are running Jessie and are up-to-date. The
problem that I have is that the ip address that the workstation gets at
boot has a finite "valid_lft" (as seen in `ip a`). When this lifetime
runs out, the IP is removed from the interface. Now, I think DHCP does
try to pick up at that point, but the root file system is already
inaccessible, so the system hangs.

Does anyone have any thoughts as to where I have gone wrong?

More details
------------

My DHCP server is set to give the workstation an IP from a pool with a
max-lease-time of 86400 seconds. The PXE picks that up and connects to
tftpd-hpa which serves up PXELINUX and the kernel/initrd for the
workstation.

The kernel command line is:
  root=/dev/nfs initrd=initrd.img nfsroot=192.168.101.8:/nfsroot ip=dhcp rw panic=30

I *think*, though that the "ip=dhcp" is redundant because the Debian kernel
(linux-image-3.14-1-686-pae) doesn't support IP autoconfiguration.

As the root filesystem is NFSv4, I'm using dracut to generate the
initramfs (Bug #409271 stops me using initramfs-tools).

The workstation boots fine, but `ip a` shows me:

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:01:c0:09:9a:de brd ff:ff:ff:ff:ff:ff
    inet 192.168.101.161/24 brd 192.168.101.255 scope global dynamic eth0
       valid_lft 3181sec preferred_lft 3181sec
    inet6 2001:470:1f09:cb:201:c0ff:fe09:9ade/64 scope global mngtmpaddr dynamic
       valid_lft 86354sec preferred_lft 14354sec
    inet6 fe80::201:c0ff:fe09:9ade/64 scope link
       valid_lft forever preferred_lft forever

(Note the 192.168.101.161 address has a valid_lft of just under an hour)

Eth0 is defined in /etc/network/interfaces.d/eth0 as:

  auto eth0
  iface eth0 inet dhcp

So, what I basically what to know is, have I misconfigured something, or is this a
but somewhere?

Attachment: signature.asc
Description: Digital signature


Reply to: