| View previous topic :: View next topic |
| Author |
Message |
dspahn
Guru
Joined: 22 Jun 2006
Posts: 392
|
 Posted: Wed Oct 17, 2018 11:08 am Post subject: New install- gnome, systemd, UEFI, but manual network |
 |
|
I have a fresh gentoo gnome install on IEFI using systemd. I did run the machine I’d setup and I have the networks and resolved service set to auto at boot... but the only way to get the network up is to run dhcpcd enp0s1. Systemctl shows everything running normally and there are no dmesg errors. I’ve been back through the systemd steps on the Gentoo Wiki at least 5 times... any idea what I missed?
_________________
---
Since there is no admin beer, I stick to root beer. |
|
| Back to top |
|
 |
mike155
Advocate
Joined: 17 Sep 2010
Posts: 4438
Location: Frankfurt, Germany
|
| Posted: Wed Oct 17, 2018 1:57 pm Post subject: |
|
|
1) Do you use systemd-networkd or networkmanager to setup your network?
2) If you use systemd-networkd: please show us the output of 'ls -la /etc/systemd/network' and the contents of the files in this directory (especially 50-static.network). Please also show us the output of 'ifconfig -a' and of 'systemctl status systemd-networkd'. |
|
| Back to top |
|
|
dspahn
Guru
Joined: 22 Jun 2006
Posts: 392
|
| Posted: Wed Oct 17, 2018 3:23 pm Post subject: Used systemd-networkd |
|
|
I’ll get the ls-la output shortly. I only have the 50-dhcp.network file per the walkthrough with the Match section set to en* and the dhcp section with the dhcp=yes line. I don’t have a static network file. Ifconfig -a shows the interface with no IP address associated. /etc/resolv.conf is wrong until I run dhcpcd enp0s25 then it updates. I have the systemd -resolved service running normal, so it seems like the network doesn’t quite start. I’ll send the outputs in my next update to this post.
_________________
---
Since there is no admin beer, I stick to root beer. |
|
| Back to top |
|
|
dspahn
Guru
Joined: 22 Jun 2006
Posts: 392
|
| Posted: Thu Oct 18, 2018 1:49 am Post subject: Outputs.... |
|
|
| Quote: |
# ls -la /etc/systemd/network
total 4
drwxr-xr-x 2 root root 80 Oct 16 12:33 .
drwxr-xr-x 6 root root 376 Oct 16 10:34 ..
-rw-r--r-- 1 root root 37 Oct 16 12:33 50-dhcp.network
|
# cat /etc/systemd/network/50-dhcp.network
| Quote: | [Match]
Name=en*
[Network]
DHCP=yes
|
# ifconfig -a
| Quote: |
enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.10.236 netmask 255.255.255.0 broadcast 192.168.10.255
inet6 fe80::658b:9571:8572:e8a5 prefixlen 64 scopeid 0x20<link>
ether 34:64:a9:c8:3d:be txqueuelen 1000 (Ethernet)
RX packets 204015 bytes 254119776 (242.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 95818 bytes 8675439 (8.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xcca00000-cca20000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 10573 bytes 812237 (793.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 10573 bytes 812237 (793.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
sit0: flags=128<NOARP> mtu 1480
sit txqueuelen 1000 (IPv6-in-IPv4)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlo1: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 80:00:0b:44:4a:9e txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
|
systemctl status systemd-networkd
| Quote: |
* systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2018-10-17 06:53:52 EDT; 14h ago
Docs: man:systemd-networkd.service(
Main PID: 1644 (systemd-network)
Status: "Processing requests..."
CGroup: /system.slice/systemd-networkd.service
`-1644 /lib/systemd/systemd-networkd
Oct 17 06:53:52 USMDITLT007 systemd[1]: Starting Network Service...
Oct 17 06:53:52 USMDITLT007 systemd-networkd[1644]: Enumeration completed
Oct 17 06:53:52 USMDITLT007 systemd[1]: Started Network Service.
Oct 17 06:53:53 USMDITLT007 systemd-networkd[1644]: eth0: Interface name change detected, eth0 has been renamed to enp0s25.
Oct 17 06:53:54 USMDITLT007 systemd-networkd[1644]: wlan0: Interface name change detected, wlan0 has been renamed to wlo1.
Oct 17 07:00:36 USMDITLT007 systemd-networkd[1644]: enp0s25: Gained carrier
Oct 17 07:00:38 USMDITLT007 systemd-networkd[1644]: enp0s25: Gained IPv6LL
Oct 17 12:36:41 USMDITLT007 systemd-networkd[1644]: enp0s25: Lost carrier
Oct 17 21:17:19 USMDITLT007 systemd-networkd[1644]: enp0s25: Gained carrier
Oct 17 21:17:20 USMDITLT007 systemd-networkd[1644]: enp0s25: Gained IPv6LL
|
Honestly, I only chose the systemd-networkd because it was the first/primary recommendation in the handbook- I'd be content to swtch to networkmanager if that would make this easier- I haven't set up the wireless yet ,even though I have laid the groundwork for it, so that may be a factor as well. I will definitely have to use wpa_supplicant for it.
_________________
---
Since there is no admin beer, I stick to root beer. |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
|
| Back to top |
|
|
mike155
Advocate
Joined: 17 Sep 2010
Posts: 4438
Location: Frankfurt, Germany
|
| Posted: Thu Oct 18, 2018 9:34 am Post subject: |
|
|
1) There is nothing wrong with systemd-networkd. I also use systemd-networkd. It's smaller and easier than networkmanager.
2) The file /etc/systemd/network/50-dhcp.network looks good. Do you use IPv6? If not, try 'DHCP=ipv4' instead of 'DHCP=yes'.
3) You may also want to look at https://wiki.archlinux.org/index.php/systemd-networkd.
4) Your output of 'ifconfig -a': I see that your interface enp0s25 has got an IP address. Is this the IP address you set manually or via dhcpcd? If that's the case: please reboot your system, don't set an IP address manually, don't run dhcpcd and post the output of 'ifconfig -a' and 'systemctl status systemd-networkd ' again. |
|
| Back to top |
|
|
mike155
Advocate
Joined: 17 Sep 2010
Posts: 4438
Location: Frankfurt, Germany
|
| Posted: Thu Oct 18, 2018 9:45 am Post subject: Re: Outputs.... |
|
|
Uberlord: This is unfair. The OP has a system which uses Systemd. It doesn't help if you point him to a document which was written for non-systemd machines... |
|
| Back to top |
|
|
krinn
Watchman
Joined: 02 May 2003
Posts: 7470
|
| Posted: Thu Oct 18, 2018 12:23 pm Post subject: Re: Outputs.... |
|
|
| mike155 wrote: | | Uberlord: This is unfair. The OP has a system which uses Systemd. |
Hence the legit question, what document the user is using.
And he is not pointing anyone to anywhere just showing the reference he is using. Actually Uberlord mistake came because handbook do point to specific systemd section, but not in the networking section (there, in installation section https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Optional:_Using_systemd_as_the_init_system)
Which then point user to the right documentation for systemd https://wiki.gentoo.org/wiki/Systemd
| mike155 wrote: | | It doesn't help if you point him to a document which was written for non-systemd machines... |
ps: if you don't get the reason for the smile, you might have miss the irony that you are pointing a user to a documentation that is not for the OS the user is using |
|
| Back to top |
|
|
dspahn
Guru
Joined: 22 Jun 2006
Posts: 392
|
| Posted: Thu Oct 18, 2018 1:25 pm Post subject: Appreciate the help! |
|
|
I should have been a little clearer about how I have done this- I stepped through the amd64 handbook for the installation using systemd from the Gentoo Wiki https://wiki.gentoo.org/wiki/Systemd to fill in the gaps. almost everything else works, except I can't get Plymouth to load properly- Since I am still working on my Gnome3 window effects, I wanted to get that working in case there is a graphics problem with my framebuffer.... so I am focusing on the service problem for now with the systemd-networkd piece. Like I said, I am not beholden to using that, and NetworkManager might work better with WPA_Supplicant… just not sure which way to go or what the best method is. I will say that outside links to similar OS'es can be helpful when dealing with a core component- sometimes it reveals the approach needed and is as simple as modifiying a config by hand or finding the Gentoo equivalent...
Any ideas how to move forward? I'm looking through the links now.
Thanks again!
_________________
---
Since there is no admin beer, I stick to root beer. |
|
| Back to top |
|
|
|
Networking & Security
