Bug #2034
netctl: interface not auto up
0%
Description
Hi, a recently install parabola-gnu and netctl not auto start interface.
i found old solution on https://bugs.archlinux.org/task/54796.
the systemd not make the symlink:
/usr/lib/systemd/system/systemd-resolve.service -> /usr/lib/systemd/systemd/dbus-org.freedesktop.resolve1.service
i did manually and netctl works ok.
History
Updated by freemor over 5 years ago
if you want netctl to bring an interface up on start-up use:
sudo netctl enable <profile>
Where <profile> is the name you gave to the connection when you created it.
If you have done this already and it is still not working then can you please provide.
The steps you took
What happens
Which technology you are trying to connect via (ethernet, wifi, 2/3G)
Attach a copy of the netctl profile for the connection (found in /etc/netctl/)
Which version of Parabola you are using.
Also you probaly want to undo that manual symlink you made if you did not first:
a.) create a profile for the connection
b.) use netctl enable to that profile
Updated by bit4bit about 5 years ago
freemor wrote:
Did my suggestions help?
Should I close this?
Hello, i recently install parabola and the same bug, the interface not bring up:
/etc/netctl/publica
Description='A basic static ethernet connection'
Interface=ens6
Connection=ethernet
IP=static
Address=('10.0.0.2/29')
#Routes=('10.0.0.1')
Gateway='10.0.0.1'
DNS=('208.67.222.222')
SkipNoCarrier=yes
- netctl enable publica [OK]
- netctl start publica [PARTIAL] add ip address but not bring up interface
after do:
ln -s /usr/lib/systemd/system/systemd-resolve.service /usr/lib/systemd/system/dbus-org.freedesktop.resolve1.service
it works.
Updated by bit4bit over 4 years ago
hello, a new installation and netctl not auto up.
netctl status vpn
Oct 30 22:21:01 mail systemd[1]: Started A basic static ethernet connection. Oct 30 22:21:01 mail network[333]: Failed to set DNS configuration: Unit dbus-org.freedesktop.resolve1.> Oct 30 22:21:01 mail network[333]: Failed to bring the network up for profile 'vpn' Oct 30 22:21:01 mail systemd[1]: netctl@vpn.service: Main process exited, code=exited, status=1/FAILURE Oct 30 22:21:01 mail systemd[1]: netctl@vpn.service: Failed with result 'exit-code'.
ls /usr/lib/systemd/system/dbus-org*
lrwxrwxrwx 1 root root 25 Oct 23 17:51 dbus-org.freedesktop.hostname1.service -> systemd-hostnamed.service lrwxrwxrwx 1 root root 23 Oct 23 17:51 dbus-org.freedesktop.import1.service -> systemd-importd.service lrwxrwxrwx 1 root root 23 Oct 23 17:51 dbus-org.freedesktop.locale1.service -> systemd-localed.service lrwxrwxrwx 1 root root 22 Oct 23 17:51 dbus-org.freedesktop.login1.service -> systemd-logind.service lrwxrwxrwx 1 root root 24 Oct 23 17:51 dbus-org.freedesktop.machine1.service -> systemd-machined.service lrwxrwxrwx 1 root root 25 Oct 23 17:51 dbus-org.freedesktop.portable1.service -> systemd-portabled.service lrwxrwxrwx 1 root root 25 Oct 23 17:51 dbus-org.freedesktop.timedate1.service -> systemd-timedated.service
file dbus-org.freedesktop.resolve1.service not exists,
i fix doing symbolic link like the others.
# cd /var/lib/systemd/system/ # ln -s systemd-resolved.service dbus-org.freedesktop.resolve1.service