Mailinglist Archive: opensuse-bugs (8869 mails)

< Previous Next >
[Bug 415034] Yast network does not set up network correctly
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 2 Sep 2008 06:21:10 -0600 (MDT)
  • Message-id: <20080902122110.0688A245391@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=415034

User kkeil@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=415034#c22





--- Comment #22 from Karsten Keil <kkeil@xxxxxxxxxx> 2008-09-02 06:21:08 MDT
---
No that would be a bad idea. The driver cannot make a difference between
"no connection" and "carrier detection in progress", so it would wait forever,
if no cable is connected.
And the testloop from comment #19 is wrong, it restarts carrier detection in
every loop, note "ifconfig down" is the same like pulling the cable.
The important things are:
YaST should not access /sys/class/net/ethX/carrier before ifconfig up was done,
this would cause an error, note on some devices a ifconfig up does not happen
immediately in the driver, it maybe delayed until the driver thread is running
again. You can examine /sys/class/net/ethX/flags, Bit0 shows up/down status.
If it read 0 for carrier it should retry, at least 3 seconds, but some cards
(and switches) maybe need more time.
One idea would be to do ifconfig up on all found interfaces early as possible,
do something else and then test carrier state.


--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >