dhclient startet nicht trotz... :

revealed · 8 Nov. 2007

Hallo!

Ich dachte meine Konfiguration währe falsch. Ist sie aber nicht! Das Problem ist, dass bei mir kein DHCP client startet trotz einstellung? Oder habe ich etwas übersehen?

SuSE 10.3:

der einfache Beleg:

Code:

WILD-THING:/etc/rc.d # grep dhclient /etc/sysconfig/network/*

/etc/sysconfig/network/dhcp:# Most of these options are used only by dhcpcd, not by the ISC dhclient (which
/etc/sysconfig/network/dhcp:# If empty, dhcpcd is tried, then dhclient
/etc/sysconfig/network/dhcp:# dhclient (ISC dhclient)
/etc/sysconfig/network/dhcpHCLIENT_BIN="dhclient"
/etc/sysconfig/network/dhcp:# /var/log/dhclient-script for ISC dhclient)
/etc/sysconfig/network/dhcp:## Type: string("dhcpcd dhclient")

Die Systemvariable "DHCLIENT_BIN="dhclient" müsste diesen doch starten?

Weiter kommt deswegen beim booten:

Code:

disk@WILD-THING:~> grep eth0 /var/log/boot.msg

<6>eth0: RTL8168b/8111b at 0xf887a000, 00:17:31:87:44:be, IRQ 17
doneWaiting for mandatory devices: eth0 __NSC__
eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
eth0 DHCP client NOT running
eth0 is down
failed eth0 interface could not be set up until now
You have new mail in /var/spool/mail/disk
disk@WILD-THING:~>

Sprich es liefe kein DHCP client programm? Also keines der die installiert sind?

Code:

WILD-THING:/etc/rc.d # dhclient --version

isc-dhclient-V3.0.6

Kann mir jemand bitte bei einem workaround helfen?

Weil wenn ich ihn nachdem KDE geladen ist, manuell starte dann kommt folgende Ausgabe und mein Internet geht:

WILD-THING:/home/disk # dhclient
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:17:31:87:44:be
Sending on LPF/eth0/00:17:31:87:44:be
Sending on Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.3 -- renewal in 952936485 seconds.
WILD-THING:/home/disk #

Also wie bewege ich dhclient dazu von allein zu starten?

Danke!

Gruß

R

revealed · 9 Nov. 2007

also was mich auch total wundert ist, dass beispielsweise:

Code:

ifup-dhcp eth0

die Konfiguration einwandfrei hoch bringt.

Woran liegt das jetzt? Bitte helft mir!

Code:

WILD-THING:/home/disk # ifup-dhcp eth0
WILD-THING:/home/disk # ps ax |grep dhc
 2522 ?        Ss     0:00 /sbin/syslog-ng -a /var/lib/dhcp/dev/log
 5704 ?        Ss     0:00 /sbin/dhclient -q eth0
 5713 pts/0    S+     0:00 grep dhc
WILD-THING:/home/disk #

Code:

WILD-THING:/home/disk # grep eth0 /var/log/boot.msg

<6>eth0: RTL8168b/8111b at 0xf8f6e000, 00:17:31:87:44:be, IRQ 17
doneWaiting for mandatory devices: eth0 __NSC__
eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
eth0 DHCP client NOT running
eth0 is down
failed eth0 interface could not be set up until now
WILD-THING:/home/disk #

Code:

WILD-THING:/home/disk # grep "DHCLIENT_BIN" /etc/sysconfig/network/*

/etc/sysconfig/network/dhcpHCLIENT_BIN="dhclient"
WILD-THING:/home/disk #

Gruß

R

revealed · 10 Nov. 2007

hallo!

Die Netzwerkkarte lässt mir keine Ruhe!

Ich hab mir grad den NTP und die boot.msg nochmal angeschaut. Folgende Kuriositäten:

doneActivating remaining swap-devices in /etc/fstab...
doneCleaning temporary directories /tmp /usr/tmpdone
Mounting securityfs on /sys/kernel/security done
Loading AppArmor module done
Loading AppArmor profiles <notice>killproc: kill(1240,29)
Creating /var/log/boot.msg
donedone
Setting current sysctl status from /etc/sysctl.conf
net.ipv4.icmp_echo_ignore_broadcasts = 1
net.ipv4.conf.all.rp_filter = 1
fs.inotify.max_user_watches = 65536
done
Enabling syn flood protectiondone
Disabling IP forwardingdone
done
Setting up hostname 'WILD-THING'done
Setting up loopback interface lo
lo IP address: 127.0.0.1/8
Checking for network time protocol daemon (NTPD): unused
Can't determine current runlevel
done
System Boot Control: The system has been set up
Skipped features: boot.cycle
System Boot Control: Running /etc/init.d/boot.local
done<notice>killproc: kill(1240,3)

INIT: Entering runlevel: 5

Can't determine runlevel? Wenn ich wüsste wer und warum? Und killproc kill?

dann ist mir etwas aufgefallen, wenn ich händisch "rcnetwork start" mache, erhalte ich folgende Ausgabe:

WILD-THING:/home/disk # rcnetwork start
Setting up network interfaces:
lo
lo IP address: 127.0.0.1/8
Checking for network time protocol daemon (NTPD): doneed
eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
eth0 IP address: 192.168.0.3/ done
Setting up service network . . . . . . . . . . . . . . done.
SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
SuSEfirewall2: Warning: no default firewall zone defined, assuming 'ext'
SuSEfirewall2: batch committing...
SuSEfirewall2: Firewall rules successfully set

Man betrachte die Zeile mit dem Networktimeprotokoll. Hat sich da ein Schreibfehler eingeschlichen?

Von der Problembeschreibung her klingt der Inhalt dieses Bugreports:
https://bugzilla.novell.com/show_bug.cgi?id=335486
Am ehesten wie mein Problem?

Allerdings mit Verlaub, dass ich vom FTP frisch installiert habe.

Bitte dringend um Hilfe! Bugzilla Account habe ich leider keinen. Fall jemand einen hat mit diesem Problem fänd ich es super nett, wenn die Person das übernehmen würde, oder ich hoff ,... eventuell stolpert ja jemand von SuSE darüber?

Dann hab ich nochwas dazu:

Code:

disk@WILD-THING:~> egrep "failed|rtc" /var/log/boot.msg

<4>Using IPI No-Shortcut mode
<3>drivers/hid/usbhid/hid-core.c: hid_fixup_sony_ps3_controller failed: -71
<6>rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
<4>rtc_cmos: probe of 00:03 failed with error -16
Starting udevd udevd-event[1870]: node_symlink: device node '/dev/rtc0' already exists, link '/dev/rtc' will not overwrite it
failed eth0 interface could not be set up until now
failedSetting up service network . . . . . . . . . . . . . . . .failed
disk@WILD-THING:~>

Gruß

R

revealed · 11 Nov. 2007

http://www.linux-club.de/viewtopic.php?p=522646#522646

Gruß

R

revealed · 18 Nov. 2007

also jetz hab ich mir die 10.3 frisch installiert MySQL PHP Apache Nagios usw... jetzt ist dieses Problem immernoch da.

Und von der Alten Installation war nichts. Und auch kene geupdatete Version.

Please provide a FIX! Thank you very much.

Gruß

R

Code:

WILD-THING:/ # grep eth0 /var/log/boot.msg
<6>eth0: RTL8168b/8111b at 0xf8f56000, 00:17:31:87:44:be, IRQ 17
MANDATORY_DEVICES = eth0 00:17:31:87:44:be __NSC__
MANDATORY_DEVICES=eth0 00:17:31:87:44:be __NSC__
Waiting for mandatory devices:  eth0 00:17:31:87:44:be __NSC__
MANDATORY_DEVICES= eth0 00:17:31:87:44:be __NSC__
MANDATORY_DEVICES= eth0 00:17:31:87:44:be __NSC__
MANDATORY_DEVICES= eth0 00:17:31:87:44:be __NSC__
MANDATORY_DEVICES= eth0 00:17:31:87:44:be __NSC__
MANDATORY_DEVICES= eth0 00:17:31:87:44:be __NSC__
MANDATORY_DEVICES= eth0 00:17:31:87:44:be __NSC__
MANDATORY_DEVICES= eth0 00:17:31:87:44:be __NSC__
MANDATORY_DEVICES= eth0 00:17:31:87:44:be __NSC__
MANDATORY_DEVICES= eth0 00:17:31:87:44:be __NSC__
MANDATORY_DEVICES= eth0 00:17:31:87:44:be __NSC__
MANDATORY_DEVICES= eth0 00:17:31:87:44:be __NSC__
MANDATORY_DEVICES= eth0 00:17:31:87:44:be __NSC__
MANDATORY_DEVICES= eth0 00:17:31:87:44:be __NSC__
MANDATORY_DEVICES= eth0 00:17:31:87:44:be __NSC__
MANDATORY_DEVICES= eth0 00:17:31:87:44:be __NSC__
eth0 -o rc onboot
    eth0      device: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
eth0 eth0 -o rc onboot
    eth0      DHCP client NOT running
    eth0      is down
eth0 eth0 -o rc onboot
'eth0' is not wireless, exiting
eth0 eth0 -o rc onboot
interface eth0 is not up
    eth0      returned 7
failed    eth0      interface could not be set up until now
MANDATORY_DEVICES= eth0 00:17:31:87:44:be __NSC__

Code:

WILD-THING:/ # rcnetwork start
start

CONFIG      =
INTERFACE   =
AVAILABLE_IFACES =   eth0
PHYSICAL_IFACES  =  eth0
DIALUP_IFACES    =
TUNNEL_IFACES    =
MANDATORY_DEVICES =
SKIP             =
Setting up network interfaces:
lo -o rc

    lo
lo lo -o rc
unknown option rc ignored
'lo' is not wireless, exiting
    lo        IP address: 127.0.0.1/8
Handling Index <>:
     IPADDR             = 127.0.0.1
     PREFIXLEN          = 8
     CHECK_DUPLICATE_IP = yes
lo lo -o rc
calling: ip route replace to 127/8 dev lo  ---> OK
lo lo -o rc
unknown option rc
No services to handle for 'lo lo'
executing additional global start script if-up.d/21-dhcpcd-hook-samba
executing additional global start script if-up.d/50-ntp
Checking for network time protocol daemon (NTPD):                    unused
executing additional global start script if-up.d/SuSEfirewall2
    lo        returned 0                                             done
eth0 -o rc

    eth0      device: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
eth0 eth0 -o rc
unknown option rc ignored
'eth0' is not wireless, exiting
eth0 eth0 -o rc
    eth0      IP address: 192.168.0.3/24 (DHCP was already running)
    eth0      IP address: 192.168.0.3/24
Handling Index <_>:
     IPADDR             = 192.168.0.3
     PREFIXLEN          = 24
     CHECK_DUPLICATE_IP = yes
    eth0:_    IP address: 192.168.0.3/24
Handling Index <__>:
     IPADDR             = 192.168.0.3
     PREFIXLEN          = 24
     CHECK_DUPLICATE_IP = no
eth0 eth0 -o rc
calling: ip route replace to 169.254.0.0/16 dev eth0  ---> OK
    eth0      returned 0                                             done
... still waiting for hotplug devices:
SUCCESS_IFACES= lo eth0
MANDATORY_DEVICES=
... final
SUCCESS_IFACES= lo eth0
MANDATORY_DEVICES=
FAILED=0
noiface -o rc
Setting up service network  .  .  .  .  .  .  .  .  .  .  .  .  .  . done.
SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
SuSEfirewall2: batch committing...
SuSEfirewall2: Firewall rules successfully set
WILD-THING:/ #

ich frag mich was da "lolo und ignored heisste" *g* LOL Bitte liebes SuSE Team macht da was... das ist grausam

Gruß

R

revealed · 11 Apr. 2008

irgendwie hatte das Update gerade nicht geholfen? Weiss jemand, warum dhclient einfach erst nach dem Booten händisch aufgerufen werden muss?

Ohne den Menschen währ ich glaube "verloren?

Code:

Here is a a workaround (NO FIX). Ugly but works for me.
Exclude the eth-interfaces from the physical/non-physical detection:

--- sysconfig-0.70.2-4/etc/init.d/network   2007-09-22 00:12:40.000000000 +0200
+++ /etc/init.d/network                     2007-10-22 12:18:54.000000000 +0200
@@ -470,7 +470,8 @@
 # later in the start section if it is considered mandatory (see next section).
 for a in $(type_filter `ls -A /sys/class/net/`); do
        case "`get_iface_type $a`" in
-               eth|tr|wlan)    
+               eth) ;;
+               tr|wlan)        
                        STAMPFILE=$STAMPFILE_STUB`cat
/sys/class/net/$a/ifindex`
                        if [ "$MODE" == onboot -a "$ACTION" == start ] ; then
                                if [ ! -e "$STAMPFILE" ] ; then


Nevertheless, the ethernet interfaces should be brought up upon boot if
configured that way (start=onboot) regardless of udev or prior module load.

Gruß

R

dhclient startet nicht trotz... :

revealed

Guru

revealed

Guru

revealed

Guru

revealed

Guru

revealed

Guru

revealed

Guru