[SOLVED]Fresh install on VirtualBox, no internet outside the ISO setup

xerxys · 2021-02-22 20:21:06

SOLUTION

systemd-networkd.service
dhcpcd@enp0s3.service
NetworkManager.service

These 3 network managers were conflicting and I didn't have a network resolver enabled. In the chroot section of the installation media:

systemctl disable systemd-networkd.service
systemctl disable NetworkManager.service
systemctl enable systemd-resolved.service

ORIGINAL POST START

I followed all the setup guide and everything went smoothly until I tried to launch an existing OS. When I ping 8.8.8.8 I get packets in return but when I ping google.com I get "Temporary failure in name resolution". I've been at this for 8 hours or so and cannot find any forum posts or guides that fix my issue.

I have tried using the following commands that others have suggested and they didn't work:
systemctl enable dhcpcd

systemctl enable dhcpcd@enp0s3.service

dhcpcd

ip link set enp0s3 up

When I enter "ip a" I am returned:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisk noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisk fq_codel state UP group default qlen 1000
link/ether 08:00:27:d1:83:53 brd ff:ff:ff:ff:ff:ff
inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic noprefixroute enp0s3
valid_lft 85596sec preferred_lft 85596sec
inet6 fe80::15f1:a5b2:f483:1198/64 scope link noprefixroute
valid_lft forever prefered_lft forever
inet6 fe80::6335:f61b:82d4:b733/64 scope link noprefixroute
valid_lft forever preferred_lft forever

I have installed dhcpcd as well as NetworkManager. I have tried "systemctl enable NetworkManager.service" to no effect. when I run "nmcli" the first line returned back is "enp0s3: connected to Wired connection 1"

Posting on forums is my absolute last resort but I have absolutely no clue what to do now.

Last edited by xerxys (2021-02-22 21:50:34)

tucuxi · 2021-02-22 20:49:02

You need a resolver, e.g. https://wiki.archlinux.org/index.php/Systemd-resolved.

xerxys · 2021-02-22 21:06:15

tucuxi wrote:

You need a resolver, e.g. https://wiki.archlinux.org/index.php/Systemd-resolved.

I'm very new to this but when I run "pacman -Q systemd" It shows that it's installed. I -S it and it updated but it didn't solve the issue. I did however find more information about it.

I ran "systemctl status dhcpcd@enp0s3 and it's returning me:

dhcpcd@enp0s3.service: Can't open PID file /run/dhcpcd/enp0s3.pid (yet?) after start: Operation not permitted"
"dhcpcd@enp0s3.service: Failed with result 'protocol'."

Is this still a resolver issue?

Last edited by xerxys (2021-02-22 21:06:49)

xerxys · 2021-02-22 21:14:12

xerxys wrote:

tucuxi wrote:
You need a resolver, e.g. https://wiki.archlinux.org/index.php/Systemd-resolved.
I'm very new to this but when I run "pacman -Q systemd" It shows that it's installed. I -S it and it updated but it didn't solve the issue. I did however find more information about it.
I ran "systemctl status dhcpcd@enp0s3 and it's returning me:
dhcpcd@enp0s3.service: Can't open PID file /run/dhcpcd/enp0s3.pid (yet?) after start: Operation not permitted"
"dhcpcd@enp0s3.service: Failed with result 'protocol'."
Is this still a resolver issue?

I have since run "systemctl start systemd-resolved.service" outside of the ISO setup/root manager bit (I don't know what it's called) and it works. My question now: is it possible to set that up to always run on start up?

loqs · 2021-02-22 21:16:24

The systemd package is required by base so is expected to always be installed. If you are using networkmanager you should not use dhcpcd@enp0s3.service as it will conflict.
What is the output of:

file /etc/resolv.conf 
cat /etc/resolv.conf
find /etc/systemd -name \*.service -type l -a -xtype f -printf %f\\n

loqs · 2021-02-22 21:17:57

xerxys wrote:

I have since run "systemctl start systemd-resolved.service" outside of the ISO setup/root manager bit (I don't know what it's called) and it works. My question now: is it possible to set that up to always run on start up?

Systemd#Enabling
Edit:
Sorry for the double post.

Last edited by loqs (2021-02-22 21:18:25)

xerxys · 2021-02-22 21:22:32

loqs wrote:

The systemd package is required by base so is expected to always be installed. If you are using networkmanager you should not use dhcpcd@enp0s3.service as it will conflict.
What is the output of:
file /etc/resolv.conf 
cat /etc/resolv.conf
find /etc/systemd -name \*.service -type l -a -xtype f -printf %f\\n

"file /etc/resolv.conf" outputs:
/etc/resolv.conf: symbolic link to /ver/run/systemd/resolve/resolv.conf

"cat /etc/resolv.conf" outputs:
nameserver 192.168.1.1
search .

"find /etc/systemd -name \*.service -type l -a -xtype f -printf %f\\n" outputs:
dbus-org.freedesktop.network1service
dbus-org.freedesktop.nm-dispatcher.service
systemd-networkd.service
dhcpcd@enp0s3.service
NetworkManager.service
systemd-networkd-wait-online.service
NetworkManager-wait-online.service
getty@tty1.service

Also about enabling, I ran "systemctl enable systemd-resolved.service" in the root manager section of the ISO install which caused my confusion when I had to run it manually when I launched the OS area from grub.

Last edited by xerxys (2021-02-22 21:29:07)

loqs · 2021-02-22 21:28:13

find /etc/systemd -name \*.service -type l -a -xtype f -printf %f\\n
find /etc/systemd-name \*.service -type l -a xtype f -printf %f\\n

You missed a - before xtype.

"root manager section of the ISO" You mean when you booted from the installation media and then chrooted in?
"OS area from grub" You mean when the installed system booted from grub?

xerxys · 2021-02-22 21:30:37

loqs wrote:

find /etc/systemd -name \*.service -type l -a -xtype f -printf %f\\n
find /etc/systemd-name \*.service -type l -a xtype f -printf %f\\n
You missed a - before xtype.
"root manager section of the ISO" You mean when you booted from the installation media and then chrooted in?
"OS area from grub" You mean when the installed system booted from grub?

Ya I noticed all my typos after I posted. I've edited the output into that post.

Correct
Also correct I believe. when you reboot and grub asks where you want to boot from and 2 of the options are installation media or existing OS.

loqs · 2021-02-22 21:33:32

systemd-networkd.service
dhcpcd@enp0s3.service
NetworkManager.service

You have three network management services which will compete to control enp0s3. You need to pick one and stop and disable the other two.
Did you enable systemd-networkd instead of systemd-resolved?

Slithery · 2021-02-22 21:34:52

xerxys wrote:

"find /etc/systemd -name \*.service -type l -a -xtype f -printf %f\\n" outputs:
dbus-org.freedesktop.network1service
dbus-org.freedesktop.nm-dispatcher.service
systemd-networkd.service
dhcpcd@enp0s3.service
NetworkManager.service
systemd-networkd-wait-online.service
NetworkManager-wait-online.service
getty@tty1.service

You have enabled 3 different services that are all trying to configure your networking at the same time, this is bound to cause problems.
Choose the one you wish to use and disable the other 2.

xerxys · 2021-02-22 21:36:49

That is rather likely actually. So you recommend I run "systemctl disable systemd-networkd.service' and which other one? Does it really matter which one I leave enabled? And in addition to disabling those 2 network managment services I also run "systemctl enable systemd-resolved.service" from the chroot section of the installation media?

loqs · 2021-02-22 21:43:38

Any of the three network management services you had enabled can work for your setup. systemd-networkd would need configuration to work so the one that was working so far would be one of the of other two, does not matter which one you pick if you have no preference.

xerxys · 2021-02-22 21:47:07

loqs wrote:

Any of the three network management services you had enabled can work for your setup. systemd-networkd would need configuration to work so the one that was working so far would be one of the of other two, does not matter which one you pick if you have no preference.

You are a scholar and a gentleman. Everything is working now. Thank you so much for your patience

Arch Linux

#1 2021-02-22 20:21:06

[SOLVED]Fresh install on VirtualBox, no internet outside the ISO setup

#2 2021-02-22 20:49:02

Re: [SOLVED]Fresh install on VirtualBox, no internet outside the ISO setup

#3 2021-02-22 21:06:15

Re: [SOLVED]Fresh install on VirtualBox, no internet outside the ISO setup

#4 2021-02-22 21:14:12

Re: [SOLVED]Fresh install on VirtualBox, no internet outside the ISO setup

#5 2021-02-22 21:16:24

Re: [SOLVED]Fresh install on VirtualBox, no internet outside the ISO setup

#6 2021-02-22 21:17:57

Re: [SOLVED]Fresh install on VirtualBox, no internet outside the ISO setup

#7 2021-02-22 21:22:32

Re: [SOLVED]Fresh install on VirtualBox, no internet outside the ISO setup

#8 2021-02-22 21:28:13

Re: [SOLVED]Fresh install on VirtualBox, no internet outside the ISO setup

#9 2021-02-22 21:30:37

Re: [SOLVED]Fresh install on VirtualBox, no internet outside the ISO setup

#10 2021-02-22 21:33:32

Re: [SOLVED]Fresh install on VirtualBox, no internet outside the ISO setup

#11 2021-02-22 21:34:52

Re: [SOLVED]Fresh install on VirtualBox, no internet outside the ISO setup

#12 2021-02-22 21:36:49

Re: [SOLVED]Fresh install on VirtualBox, no internet outside the ISO setup

#13 2021-02-22 21:43:38

Re: [SOLVED]Fresh install on VirtualBox, no internet outside the ISO setup

#14 2021-02-22 21:47:07

Re: [SOLVED]Fresh install on VirtualBox, no internet outside the ISO setup

Board footer