#networkd & resolved not working together somehow.

1 messages · Page 1 of 1 (latest)

remote idol Jul 5, 2024, 8:21 PM

Tried to use a static IP on my new server install but it just won't work. I get the generic "temporary failure in name resolution" error from ping. ip command shows the interface giving "no carrier" but it's plugged directly into the router. I manually assigned an IP to the port's MAC in the router firmware. I am at a bit of a loss, but I am trying and have always tried to use the simplest tools possible. So would prefer to understand what I'm doing wrong rather than install more software with real interfaces 🙂

/etc/resolv.conf is a link to the standard stub resolver

/etc/systemd/network/wired1.network:

[Match]
Name=enp69s0f0

[Network]
Address=192.168.50.3
Gateway=192.168.50.1
DNS=127.0.0.1

Gateway is set to the router's address.

systemctl status systemd-resolved:

● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
     Active: active (running) since Fri 2024-07-05 10:27:48 PDT; 2h 39min ago
 Invocation: 06fecafae7a44ab085ebef5c6bb29c26
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://systemd.io/WRITING_NETWORK_CONFIGURATION_MANAGERS
             https://systemd.io/WRITING_RESOLVER_CLIENTS
   Main PID: 1235 (systemd-resolve)
     Status: "Processing requests..."
      Tasks: 1 (limit: 309013)
     Memory: 8.6M (peak: 9.1M)
        CPU: 62ms
     CGroup: /system.slice/systemd-resolved.service
             └─1235 /usr/lib/systemd/systemd-resolved

Jul 05 10:27:48 zenserv systemd[1]: Starting Network Name Resolution...
Jul 05 10:27:48 zenserv systemd-resolved[1235]: Positive Trust Anchors:
Jul 05 10:27:48 zenserv systemd-resolved[1235]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Jul 05 10:27:48 zenserv systemd-resolved[1235]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 170.0.0.192.in-addr.arpa 171.0.0.192.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa ipv4only.arpa resolver.arpa corp home internal intranet lan local private test
Jul 05 10:27:48 zenserv systemd-resolved[1235]: Using system hostname 'zenserv'.
Jul 05 10:27:48 zenserv systemd[1]: Started Network Name Resolution.

systemctl status systemd-networkd:

● systemd-networkd.service - Network Configuration
     Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; preset: enabled)
     Active: active (running) since Fri 2024-07-05 10:27:47 PDT; 2h 39min ago
 Invocation: 55b086d2eb3c422b8cdfc74b2b93f55f
TriggeredBy: ● systemd-networkd.socket
       Docs: man:systemd-networkd.service(8)
             man:org.freedesktop.network1(5)
   Main PID: 988 (systemd-network)
     Status: "Processing requests..."
      Tasks: 1 (limit: 309013)
   FD Store: 0 (limit: 512)
     Memory: 3.6M (peak: 4M)
        CPU: 77ms
     CGroup: /system.slice/systemd-networkd.service
             └─988 /usr/lib/systemd/systemd-networkd

Jul 05 10:27:47 zenserv systemd-networkd[988]: /etc/systemd/network/20-wired.network:5: Address '192.168.50.3' is specified without prefix length. Assuming the prefix length is 32. Please specify the prefix length explicitly.
Jul 05 10:27:47 zenserv systemd-networkd[988]: lo: Link UP
Jul 05 10:27:47 zenserv systemd-networkd[988]: lo: Gained carrier
Jul 05 10:27:47 zenserv systemd-networkd[988]: Enumeration completed
Jul 05 10:27:47 zenserv systemd[1]: Started Network Configuration.
Jul 05 10:27:47 zenserv systemd-networkd[988]: wlan0: Interface name change detected, renamed to wlp72s0.
Jul 05 10:27:49 zenserv systemd-networkd[988]: eth1: Interface name change detected, renamed to enp69s0f1.
Jul 05 10:27:49 zenserv systemd-networkd[988]: eth0: Interface name change detected, renamed to enp69s0f0.
Jul 05 10:27:49 zenserv systemd-networkd[988]: enp69s0f0: Configuring with /etc/systemd/network/20-wired.network.
Jul 05 10:27:49 zenserv systemd-networkd[988]: enp69s0f0: Link UP

ip link:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp72s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 18:26:49:ad:fe:fd brd ff:ff:ff:ff:ff:ff
3: enp69s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 18:c0:4d:8d:53:15 brd ff:ff:ff:ff:ff:ff
4: enp69s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 18:c0:4d:8d:53:14 brd ff:ff:ff:ff:ff:ff

trim escarpBOT Jul 6, 2024, 7:04 AM

This command can only be ran in a active ticket

remote idol Jul 6, 2024, 7:04 AM

i found multiple mistakes in the .network file. its working now

solved