diff options
| author | Li RongQing <roy.qing.li@gmail.com> | 2015-10-15 16:54:36 +0800 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2015-10-18 19:23:52 -0700 |
| commit | 26fb342c734061859fec1bd9e987bb6b78061ef0 (patch) | |
| tree | 8e292c4de0611ef24b1e7ac70115c2e70cc5a1f7 /Documentation/filesystems | |
| parent | 4be3158abe1e02d24f82b34101e41d662fae2185 (diff) | |
| download | talos-obmc-linux-26fb342c734061859fec1bd9e987bb6b78061ef0.tar.gz talos-obmc-linux-26fb342c734061859fec1bd9e987bb6b78061ef0.zip | |
ipconfig: send Client-identifier in DHCP requests
A dhcp server may provide parameters to a client from a pool of IP
addresses and using a shared rootfs, or provide a specific set of
parameters for a specific client, usually using the MAC address to
identify each client individually. The dhcp protocol also specifies
a client-id field which can be used to determine the correct
parameters to supply when no MAC address is available. There is
currently no way to tell the kernel to supply a specific client-id,
only the userspace dhcp clients support this feature, but this can
not be used when the network is needed before userspace is available
such as when the root filesystem is on NFS.
This patch is to be able to do something like "ip=dhcp,client_id_type,
client_id_value", as a kernel parameter to enable the kernel to
identify itself to the server.
Signed-off-by: Li RongQing <roy.qing.li@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation/filesystems')
| -rw-r--r-- | Documentation/filesystems/nfs/nfsroot.txt | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/Documentation/filesystems/nfs/nfsroot.txt b/Documentation/filesystems/nfs/nfsroot.txt index 2d66ed688125..bb5ab6de5924 100644 --- a/Documentation/filesystems/nfs/nfsroot.txt +++ b/Documentation/filesystems/nfs/nfsroot.txt @@ -157,6 +157,9 @@ ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>: both: use both BOOTP and RARP but not DHCP (old option kept for backwards compatibility) + if dhcp is used, the client identifier can be used by following + format "ip=dhcp,client-id-type,client-id-value" + Default: any <dns0-ip> IP address of first nameserver. |
