http://bugzilla.novell.com/show_bug.cgi?id=512302
http://bugzilla.novell.com/show_bug.cgi?id=512302#c10
--- Comment #10 from Marius Tomaschewski 2009-12-15 08:56:38 UTC ---
Created an attachment (id=332603)
--> (http://bugzilla.novell.com/attachment.cgi?id=332603)
link_wait script
Please install the attached workaround if-up.d plugin script, e.g.:
install -m755 /tmp/link_wait /etc/sysconfig/network/if-up.d/link_wait
and set at least LINK_WAIT=yes in the ifcfg-eth* file together with
STARTMODE=auto then:
LINK_WAIT=no (or empty/unset)
- default, don't do anything
LINK_WAIT=check (or yes)
- check the link state flags (using WAIT_FOR_INTERFACES time)
LINK_WAIT=<secs>
- specifies the number of seconds to sleep without any check
additionally there is a LINK_WAIT_PING_IPV4 variable:
LINK_WAIT_PING_IPV4=<ipv4 address to ping>
It can be set to a IPv4 address that is generally reachable over
the interface (when the interface works correctly).
When LINK_WAIT_PING_IPV4 is set, the above LINK_WAIT check/sleep
is done only half of the time, rest is used as limit while pinging
the address.
About ifplugd:
It changes into a "on cable connect" behavior and starts/stops the
interfaces - to do it, it has to detect the carier. This "on cable
connect" behavior can be also enabled via yast2.
But this may not work properly with cards using bnx2 driver. It reports
false "carrier on", so it may cause ifplugd to fail.
I've been told, that this is a hardware issue - there may be a workaround
for this in later versions of the driver...
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.