Hi
i’ve just post this in the network section but it seems that i have to post this here
if a moderator ca remove this:
i’ve just install the new 12.3 RC1
there is some little bug in traduction and kde but there is something very wrong
i can’t configure network with yast and ifup
only Network Manger work ( habitually problematic !!!)
i use opensuse for server work so how can i configure network connection in text mode without ifup ???
regards
jluce
On 2013-02-08 14:06, jluce2 wrote:
>
> Hi
>
> i’ve just post this in the network section but it seems that i
> have to post this here
You were told to ask a moderator to move the post, not to create a new one.
> there is some little bug in traduction and kde but there is something
> very wrong
I suppose you mean “tranlation”.
>
> i can’t configure network with yast and ifup
>
> only Network Manger work ( habitually problematic !!!)
>
> i use opensuse for server work so how can i configure network
> connection in text mode without ifup ???
with network manager? I don’t think you can, you need a desktop. Once
configured and set to be used by all users, then it should work in text
mode too.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
When I have trouble with NETWORK MANAGER I remove it and then reboot. After that ifup should function fine. I suggest also removing APPER as it interferes with manual software updates if it is trying to find packages to update.
I hav done that with 12.3 beta 2 on a laptop with good results.
ymmv
cheers
Hopefully not on RC1 and even more so on standard release.
I hav done that with 12.3 beta 2 on a laptop with good results.
Did you mean RC1 available yesterday?
I always uninstall apper. Yes, with RC1 and with beta before that. I use either YAST or zypper for updates.
cheers,
hi
no i just want network configuration works with yast and ifup
i don’t want to use NetworkManager
regards
jluce
On 02/15/2013 09:16 AM, jluce2 wrote:
>
> no i just want network configuration works with yast and ifup
>
> i don’t want to use NetworkManager
On 12.3 RC1, ifup works fine. As usual, it requires a lot more skill and care to
get it right, whereas NetworkManager handles all the details.
Assuming you want to use the first wired interface, set the interface up using
YaST, and then post the contents of /etc/sysconfig/network/ifcfg-eth0.
Same issue here. Changing to ifup from yast does not work as of 12.3 RC1.
The desktop that I a using to type this message is running 12.3 RC1. I have the network configured for “ifup”. Yast settings seem to work.
However, there is something funky happening. It seems that NetworkManager is now managing the “ifup” settings. So, I see this:
% ps -ef | grep -i network
root 827 1 0 09:34 ? 00:00:00 /usr/sbin/NetworkManager --no-daemon
and DHCP is being handled by “dhclient”, even though it looks as if it should have defaulted to “dhcpcd”.
Presumably the “–no-daemon” option to NetworkManager does something similar to “ifup” mode.
Hello,
Here this work too.
In yast, I have ifup by default.
With this command, no sign of network.service
systemd-analyze blame
115922ms YaST2-Second-Stage.service
9791ms postfix.service
3085ms systemd-logind.service
3005ms avahi-daemon.service
2005ms NetworkManager.service
1742ms cycle.service
1308ms systemd-udev-root-symlink.service
922ms systemd-vconsole-setup.service
774ms systemd-remount-fs.service
750ms bluetooth.service
411ms cpufreq.service
409ms systemd-modules-load.service
355ms fbset.service
334ms rsyslog.service
317ms systemd-sysctl.service
309ms rc-local.service
298ms dev-hugepages.mount
293ms dev-mqueue.mount
247ms systemd-tmpfiles-setup.service
244ms xdm.service
243ms systemd-readahead-collect.service
228ms udisks2.service
169ms systemd-user-sessions.service
168ms systemd-udev-trigger.service
107ms polkit.service
74ms upower.service
62ms systemd-udevd.service
61ms home.mount
60ms console-kit-daemon.service
35ms sys-kernel-debug.mount
35ms rtkit-daemon.service
24ms var-run.mount
22ms proc-sys-fs-binfmt_misc.mount
13ms var-lock.mount
3ms sys-fs-fuse-connections.mount
(To install systemd-analyze: )
zypper in systemd-analyze
And I have the same link than @arvidjaar
LC_ALL=C ll /etc/systemd/system/network.*
lrwxrwxrwx 1 root root 46 Feb 16 10:03 /etc/systemd/system/network.service -> /usr/lib/systemd/system/NetworkManager.service
If I open NeworkManager, there is nothing in it.
And I’ve try @nrickert command. I have something different.
ps -ef | grep -i network
root 2296 5011 0 10:59 pts/1 00:00:00 grep --color=auto -i network
I’ve not change anything, this is like that just after installation. openSUSE 12.3 RC1
Some others things I’ve found.
/usr/lib/systemd/system/NetworkManager.service
[Unit]
Description=Network Manager
After=syslog.target
Wants=remote-fs.target network.target
Before=network.target
[Service]
Type=dbus
BusName=org.freedesktop.NetworkManager
ExecStart=/usr/sbin/NetworkManager --no-daemon
# Suppress stderr to eliminate duplicated messages in syslog. NM calls openlog()
# with LOG_PERROR when run in foreground. But systemd redirects stderr to
# syslog by default, which results in logging each message twice.
StandardError=null
[Install]
WantedBy=multi-user.target
Also=NetworkManager-wait-online.service
Alias=network.service
To find enabled target. From archwiki (http://wiki.archlinux.org/index.php/Systemd#Targets):
systemctl list-units --type=target
In the list I have:
network.target loaded active active Network
And from this link: systemd.unit
Alias=
Additional names this unit shall be installed under. The names listed here must have the same suffix (i.e. type) as the unit file name. This option may be specified more than once, in which case all listed names are used. At installation time, systemctl enable will create symlinks from these names to the unit file name.
If I search with find about dhcp, dhcpcd, or ifup, there is noting in systemd folders (in my archlinux system, I use dhcpcd@.service, but we don’t have it on openSUSE). There is some things in /etc/sysconfig/network.
Hope this will help.
Last thing, maybe…
I’ve disabled networkmanager service, and, after reboot, this still works.
systemctl disable NetworkManager.service
I have now network.service at boot.
systemd-analyze blame
27516ms network.service
And with find.
find / -iname network.service
/sys/fs/cgroup/cpu,cpuacct/system/network.service
/sys/fs/cgroup/systemd/system/network.service
I’ve experienced the same wireless issues with upgrades from 12.3beta1 to RC1 and further to current update repositories. The issue was fixed by downgrading pulseaudio from 3.0-x to the 12.3beta1 iso version 2.1-7.3-x86_64. My 64it system is basically 12.3beta1 with current updates of kernel and all things “Network” (except pulseaudio) in Yast Install Software. Present wireless card uses ath9k, which works fine. Hope this helps.
hi
thanks for all your answers
i fix it like this
systemctl stop NetworkManager.service
systemctl disable NetworkManager.service
systemctl enable network.service
systemctl start network.service
regards
jluce