Score:0

Difference in routing between systemd-networkd and dhcpcd?

cn flag

When using systemd-networkd with the configuration below, I cannot connect over SSH (connection time out) to a certain server on our network. Bizarrely, there are no problems when I use dhcpcd instead. Everything else works with both approaches.

/etc/systemd/network/10-enp3s0.network

[Match]
Name=enp3s0

[Network]
DHCP=yes

I think I have identified the problem in that the routing works differently:

with systemd-networkd

~$ traceroute -I  myserver.xyz
traceroute to myserver.xyz (192[...]206), 30 hops max, 60 byte packets
 1  139[...]254 (139[...]254)  1.135 ms  1.121 ms  1.141 ms
 2  myserver.xyz (192[...]206)  1.118 ms  1.117 ms  1.116 ms

with dhcpcd

~$ traceroute -I  myserver.xyz
traceroute to myserver.xyz (192[...]206), 30 hops max, 60 byte packets
 1  myserver.de (192[....]206)  0.682 ms  0.622 ms  0.614 ms

This happens with two different machines on two different ports.

As I'm not a networking expert, I don't know if that is actually the cause of the problem but this looks very strange to me. What is the cause of the difference, is that actually the problem and if yes, how can I fix that?

djdomi avatar
za flag
a lot of information is missing like routing and NAT tables, and it looks for me that on the first it tries to route over a gateway
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.