Kennedy van Dam Eric a écrit :
Salut les non vacanciers.
Je rencontre un petit problème et google ne m'aide pas à trouver de
solution.
J'essaye d'avoir un système où la configuration IP se fait au niveau
kernel.
Lorsque je passe ip=dhcp à mon kernel (2.4.27), pas de problèmes, il
récupère bien son adresse IP. Par contre, lorsque je passe directement
sa config, ça ne marche pas. Voici ce que j'ai fait:
Par le make menuconfig
--> Networking Options
--> TCP/IP networking
--> IP: kernel level autoconfiguration
--> IP: DHCP support
dans le lilo.conf:
APPEND vga=normal ip=172.16.37.2:::255.255.255.0
nfsroot=172.16.37.3:/images/NFSrootwinst menu_img
Quelqu'un peut-il m'aider ?
Bon sang, RTFM (Je m'auto-répond et m'auto-aide)
vi /usr/src/linux/Documentation/nfsroot.txt
(...)
ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>
This parameter tells the kernel how to configure IP addresses of devices
and also how to set up the IP routing table. It was originally called
`nfsaddrs',
but now the boot-time IP configuration works independently of NFS, so it
was renamed to `ip' and the old name remained as an alias for
compatibility
reasons.
If this parameter is missing from the kernel command line, all fields are
assumed to be empty, and the defaults mentioned below apply. In general
this means that the kernel tries to configure everything using both
RARP and BOOTP (depending on what has been enabled during kernel confi-
guration, and if both what protocol answer got in first).
<client-ip> IP address of the client. If empty, the address will either
be determined by RARP or BOOTP. What protocol is used de-
pends on what has been enabled during kernel configuration
and on the <autoconf> parameter. If this parameter is not
empty, neither RARP nor BOOTP will be used.
<server-ip> IP address of the NFS server. If RARP is used to determine
the client address and this parameter is NOT empty only
replies from the specified server are accepted. To use
different RARP and NFS server, specify your RARP server
here (or leave it blank), and specify your NFS server in
the `nfsroot' parameter (see above). If this entry is blank
the address of the server is used which answered the RARP
or BOOTP request.
<gw-ip> IP address of a gateway if the server is on a different
subnet. If this entry is empty no gateway is used and the
server is assumed to be on the local network, unless a
value has been received by BOOTP.
<netmask> Netmask for local network interface. If this is empty,
the netmask is derived from the client IP address assuming
classful addressing, unless overridden in BOOTP reply.
<hostname> Name of the client. If empty, the client IP address is
used in ASCII notation, or the value received by BOOTP.
<device> Name of network device to use. If this is empty, all
devices are used for RARP and BOOTP requests, and the
first one we receive a reply on is configured. If you have
only one device, you can safely leave this blank.
<autoconf> Method to use for autoconfiguration. If this is either
'rarp' or 'bootp', the specified protocol is used.
If the value is 'both' or empty, both protocols are used
so far as they have been enabled during kernel configura-
tion. 'off' means no autoconfiguration.
The <autoconf> parameter can appear alone as the value to the `ip'
parameter (without all the ':' characters before) in which case auto-
configuration is used.
(...)
begin:vcard
fn:Eric Kennedy van Dam
n:Kennedy van Dam;Eric
org:It-Optics
adr;dom:;;Boulevard Initialis 7/7;Mons;;7000
email;internet:[EMAIL PROTECTED]
title:Linux Engineer
tel;work:+32.65.842385 (ext. 6004)
x-mozilla-html:FALSE
url:http://www.it-optics.com
version:2.1
end:vcard
_______________________________________________________
Linux Mailing List - http://www.unixtech.be
Subscribe/Unsubscribe: http://www.unixtech.be/mailman/listinfo/linux
Archives: http://www.mail-archive.com/linux@lists.unixtech.be
IRC: chat.unixtech.be:6667 - #unixtech
NNTP: news.gname.org - gmane.org.user-groups.linux.unixtech
