John Andersen wrote:
On Friday 16 February 2007, Peter Breger wrote:
Question - in the boot sequence, what needs to be installed in what
sequence to allow DHCP etc to be successfull i.e. if maybe one item is
missing or starte din wrong sequence, then network detection, setup etc
is not possible during boot.
And you are SURE there is no firewall blacking dhcp?
Good question John - how do I check status of firewall without starting
something running? Certainly /var/boot.msg has no reference to firewall
and starting YaST shows on firewall tab that service start is set to
manual, firewall is not running and offers the button to start it. So
that seems ok to me then.
While I am on subject of boot.msg, here is a short summary of what it
has to say on network matters (sorry, cannot actually use file text cut
and paste but have to retype laboriously in this mail, [] encloses my
own comment)
setting up network interfaces:
lo IP address: 127.0.0.1/8 done
eth0 device: 3Com [and all kinds of bla bla on hardware card]
eth0 configuration: eth-bus-pci-0000:00:0f.0
eth0 (DHCP) . . . . . no IP address yet ... backgrounding.
Warning: could not set up default route via interface.
Command ip route replace to default via 192.168.1.1 returned: .RTNETLINK
answers Network is unreachable
Configuration line. default 192.168.1.1 - -
[then all kinds of other bla bla until it gets back to matter on hand]
eth0 dhcpcd is still waiting for data
waiting
eth0 interface could not be set up until now.
Sounds to me like a problem during boot process which later does not
occur. Where do I start diagnosing that?
Regards,
Peter
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
