Handmatig invullen van een adres heb ik zojuist ook geprobeerd, maar dat werkte ook niet. Op de een of andere manier werkt het nu weer wel, nadat ik de Knetworkmanager een paar keer handmatig op 'automatisch via DHCP een ip-adres verkrijgen' had ingesteld.
Ik heb de systeemlogs er even op nagekeken, en op dat punt staan er de volgende logs:
09/19/2008 04:18:25 PM pvhekke NetworkManager Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
09/19/2008 04:18:25 PM pvhekke NetworkManager Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
09/19/2008 04:18:25 PM pvhekke NetworkManager Activation (eth0) Stage 1 of 5 (Device Prepare) started...
09/19/2008 04:18:25 PM pvhekke NetworkManager Activation (eth0) Stage 2 of 5 (Device Configure) complete.
09/19/2008 04:18:25 PM pvhekke NetworkManager Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
09/19/2008 04:18:25 PM pvhekke NetworkManager Activation (eth0) Stage 2 of 5 (Device Configure) starting...
09/19/2008 04:18:25 PM pvhekke NetworkManager Activation (eth0) Stage 2 of 5 (Device Configure) successful.
09/19/2008 04:18:25 PM pvhekke NetworkManager Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
09/19/2008 04:18:25 PM pvhekke NetworkManager Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
09/19/2008 04:18:25 PM pvhekke NetworkManager Activation (eth0) started...
09/19/2008 04:18:25 PM pvhekke NetworkManager Device eth0 activation scheduled...
09/19/2008 04:18:25 PM pvhekke NetworkManager DHCP daemon state is now 11 (unknown) for interface eth0
09/19/2008 04:18:25 PM pvhekke NetworkManager DHCP daemon state is now 14 (normal exit) for interface eth0
09/19/2008 04:18:25 PM pvhekke NetworkManager SWITCH: no current connection, found better connection 'eth0'.
09/19/2008 04:18:25 PM pvhekke NetworkManager Will activate connection 'eth0'.
09/19/2008 04:18:27 PM pvhekke dhclient There is already a pid file /var/run/dhclient.eth0.pid with pid 0
09/19/2008 04:18:27 PM pvhekke NetworkManager Activation (eth0) Beginning DHCP transaction.
09/19/2008 04:18:27 PM pvhekke NetworkManager Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
09/19/2008 04:18:27 PM pvhekke NetworkManager DHCP daemon state is now 12 (successfully started) for interface eth0
09/19/2008 04:18:28 PM pvhekke dhclient DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
09/19/2008 04:18:28 PM pvhekke NetworkManager DHCP daemon state is now 1 (starting) for interface eth0
09/19/2008 04:18:29 PM pvhekke avahi-daemon[5124] Interface eth0.IPv4 no longer relevant for mDNS.
09/19/2008 04:18:29 PM pvhekke avahi-daemon[5124] Joining mDNS multicast group on interface eth0.IPv4 with address ************.
09/19/2008 04:18:29 PM pvhekke avahi-daemon[5124] Joining mDNS multicast group on interface eth0.IPv4 with address ************.
09/19/2008 04:18:29 PM pvhekke avahi-daemon[5124] Leaving mDNS multicast group on interface eth0.IPv4 with address ***********.
09/19/2008 04:18:29 PM pvhekke avahi-daemon[5124] New relevant interface eth0.IPv4 for mDNS.
09/19/2008 04:18:29 PM pvhekke avahi-daemon[5124] New relevant interface eth0.IPv4 for mDNS.
09/19/2008 04:18:29 PM pvhekke avahi-daemon[5124] Registering new address record for ********** on eth0.IPv4.
09/19/2008 04:18:29 PM pvhekke avahi-daemon[5124] Registering new address record for *********** on eth0.IPv4.
09/19/2008 04:18:29 PM pvhekke avahi-daemon[5124] Withdrawing address record for ************* on eth0.
09/19/2008 04:18:29 PM pvhekke dhclient DHCPACK of ************* from **************
09/19/2008 04:18:29 PM pvhekke dhclient DHCPOFFER of **************** from *************
09/19/2008 04:18:29 PM pvhekke dhclient DHCPREQUEST of ************ on eth0 to 255.255.255.255 port 67
Het lijkt er dus op dat dhclient nu wel iets gedaan heeft, terwijl hij de vorige keren faalde. Begrijpt iemand er iets van? En belangrijker, hoe kan ik voorkomen dat ik bij een volgende keer mijn pc opstarten niet weer hetzelfde probleem ontstaat?