Static IP problem
First a bit of background information. I am auto-installing SuSE Linux (multiple versions, SLES 8, 9.0, etc.) vi HTTP. During the autoinstall process I am using DHCP, ie when the machine first boots up it gets assigned an address. However, during install I assign the machine a static ip address, which is set up in the configuration file. Now the problem. After the sucessful completion of installation when I log into the machine, the network interface is not configured with the static IP address, but with a dynamic one. I can see this through ifconfig. If I reboot the machine, then the static IP address gets bound to the NIC and everything is fine. I do have the 'Reboot after Installation' set to true ( <reboot config:type="boolean">true</reboot> ). Does anyone have an idea why this is happening and what I can do to resolve this so that the machine has the correct static IP address after installation? Thank you very much, Jeff Crow
On Thursday 25 March 2004 21:39, Jeff Crow wrote:
First a bit of background information. I am auto-installing SuSE Linux (multiple versions, SLES 8, 9.0, etc.) vi HTTP. During the autoinstall process I am using DHCP, ie when the machine first boots up it gets assigned an address. However, during install I assign the machine a static ip address, which is set up in the configuration file.
Now the problem. After the sucessful completion of installation when I log into the machine, the network interface is not configured with the static IP address, but with a dynamic one.
That's the IP# the install process gets. It is a dynamic IP#.
I can see this through ifconfig. If I reboot the machine, then the static IP address gets bound to the NIC and everything is fine.
Yes. Interface goes down, pc reboots, interface requests IP#...
I do have the 'Reboot after Installation' set to true ( <reboot config:type="boolean">true</reboot> ).
I do not think that's neccessary. Run a script at a convenient point that does a ifdown/ifup sequence: ifdown interface eth0 ifup interface eth0 Hmmm... now I think of it... as the system boots up /for the first time/, it goes through all the init-scripts, right? If so, perhaps a simple "ifdown interface eth0" before initial booting would be sufficient. Cheers, Leen
participants (2)
-
Jeff Crow
-
Leendert Meyer