Mailinglist Archive: opensuse-bugs (2150 mails)

< Previous Next >
[Bug 870370] ifup / STARTMODE=manual / network connection after boot not possible

https://bugzilla.novell.com/show_bug.cgi?id=870370

https://bugzilla.novell.com/show_bug.cgi?id=870370#c4


--- Comment #4 from Norman Gorlt <cupra2@xxxxxx> 2014-04-06 13:52:39 UTC ---
Up to openSuSE 12.3 it worked without problems in startmode "manual".
There were some changes in ifup script of openSuSE 13.1.

After boot in "manual" startmode, Qinternet do not show an interface.


Ifstatus after boot is:

linux-ye2n:/home/norman # ifstatus enp0s4
enp0s4 device: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet
(rev 90)
DHCP4 client NOT running
enp0s4 is down

a manually set up via ifup give me the following output:

linux-ye2n:/home/norman # ifup ifcfg-enp0s4 enp0s4
linux-ye2n:/home/norman # ifstatus enp0s4
enp0s4 device: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet
(rev 90)
DHCP4 client (dhcpcd) is running
. . . but is still waiting for data
2: enp0s4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UNKNOWN qlen 1000
link/ether 00:0b:6a:1b:3a:d0 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.25/24 brd 192.168.178.255 scope global enp0s4
valid_lft forever preferred_lft forever
inet6 fe80::20b:6aff:fe1b:3ad0/64 scope link
valid_lft forever preferred_lft forever
enp0s4 is up

a manually set down via ifdown give me following output:

linux-ye2n:/home/norman # ifdown enp0s4
linux-ye2n:/home/norman # ifstatus enp0s4
enp0s4 device: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet
(rev 90)
DHCP4 client NOT running
enp0s4 is down

Now Qinternet show me an interface and it's possible to connect and disconnect
without problems.
Ifstatus show me, dependent whether connect or disconnect via Qinternet, the
currently right status.

What's the different of ifstatus after boot and after ifdown ?
Maybe some Environment Variables ?

--
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 >