#networkd — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #networkd, aggregated by home.social.
-
CW: tech, linux, networking, firewall
For a few weeks I had some strange errors with my self-hosted webmail, Snappymail. After working for some time it complained that it couldn't connect to tcp://mydomain.tld:143. My email clients worked, though. The situation got worse a few days ago when I updated the server and rebooted it.
My webmail is hosted in a systemd-nspawn system container. I use such containers for a lot of different services.
For debugging purposes I tried some telnet and openssl s_client stuff today but I've been on the wrong track with that. ping'ing from the webmail container already failed. There was something more fundamental amiss.
-
CW: tech, linux, networking, firewall
For a few weeks I had some strange errors with my self-hosted webmail, Snappymail. After working for some time it complained that it couldn't connect to tcp://mydomain.tld:143. My email clients worked, though. The situation got worse a few days ago when I updated the server and rebooted it.
My webmail is hosted in a systemd-nspawn system container. I use such containers for a lot of different services.
For debugging purposes I tried some telnet and openssl s_client stuff today but I've been on the wrong track with that. ping'ing from the webmail container already failed. There was something more fundamental amiss.
-
CW: tech, linux, networking, firewall
For a few weeks I had some strange errors with my self-hosted webmail, Snappymail. After working for some time it complained that it couldn't connect to tcp://mydomain.tld:143. My email clients worked, though. The situation got worse a few days ago when I updated the server and rebooted it.
My webmail is hosted in a systemd-nspawn system container. I use such containers for a lot of different services.
For debugging purposes I tried some telnet and openssl s_client stuff today but I've been on the wrong track with that. ping'ing from the webmail container already failed. There was something more fundamental amiss.
-
CW: tech, linux, networking, firewall
For a few weeks I had some strange errors with my self-hosted webmail, Snappymail. After working for some time it complained that it couldn't connect to tcp://mydomain.tld:143. My email clients worked, though. The situation got worse a few days ago when I updated the server and rebooted it.
My webmail is hosted in a systemd-nspawn system container. I use such containers for a lot of different services.
For debugging purposes I tried some telnet and openssl s_client stuff today but I've been on the wrong track with that. ping'ing from the webmail container already failed. There was something more fundamental amiss.
-
CW: tech, linux, networking, firewall
For a few weeks I had some strange errors with my self-hosted webmail, Snappymail. After working for some time it complained that it couldn't connect to tcp://mydomain.tld:143. My email clients worked, though. The situation got worse a few days ago when I updated the server and rebooted it.
My webmail is hosted in a systemd-nspawn system container. I use such containers for a lot of different services.
For debugging purposes I tried some telnet and openssl s_client stuff today but I've been on the wrong track with that. ping'ing from the webmail container already failed. There was something more fundamental amiss.
-
Another day, another IPv6 question. I'm on a Hetzner cloud VM. I have a static IPv6 /64 subnet / prefix¹. The system uses systemd-networkd for network management.
My eth0 does not seem to receive any RA at all but I'd like to delegate the prefix downstream to a bridge interface br0 on the same host. I have an IPv6Prefix section on eth0 with the Prefix=…, Assign=yes and Token=static:::1. It works, eth0 gets the ::1 address for this prefix.
Is there a way for br0 to get this prefix too without eth0 joining the bridge? And to announce the prefix to any interfaces joining the bridge (e.g. LX system containers)?
¹ Is this the same? I have the impression these terms are used interchangeably with IPv6.
-
Another day, another IPv6 question. I'm on a Hetzner cloud VM. I have a static IPv6 /64 subnet / prefix¹. The system uses systemd-networkd for network management.
My eth0 does not seem to receive any RA at all but I'd like to delegate the prefix downstream to a bridge interface br0 on the same host. I have an IPv6Prefix section on eth0 with the Prefix=…, Assign=yes and Token=static:::1. It works, eth0 gets the ::1 address for this prefix.
Is there a way for br0 to get this prefix too without eth0 joining the bridge? And to announce the prefix to any interfaces joining the bridge (e.g. LX system containers)?
¹ Is this the same? I have the impression these terms are used interchangeably with IPv6.
-
Another day, another IPv6 question. I'm on a Hetzner cloud VM. I have a static IPv6 /64 subnet / prefix¹. The system uses systemd-networkd for network management.
My eth0 does not seem to receive any RA at all but I'd like to delegate the prefix downstream to a bridge interface br0 on the same host. I have an IPv6Prefix section on eth0 with the Prefix=…, Assign=yes and Token=static:::1. It works, eth0 gets the ::1 address for this prefix.
Is there a way for br0 to get this prefix too without eth0 joining the bridge? And to announce the prefix to any interfaces joining the bridge (e.g. LX system containers)?
¹ Is this the same? I have the impression these terms are used interchangeably with IPv6.
-
Another day, another IPv6 question. I'm on a Hetzner cloud VM. I have a static IPv6 /64 subnet / prefix¹. The system uses systemd-networkd for network management.
My eth0 does not seem to receive any RA at all but I'd like to delegate the prefix downstream to a bridge interface br0 on the same host. I have an IPv6Prefix section on eth0 with the Prefix=…, Assign=yes and Token=static:::1. It works, eth0 gets the ::1 address for this prefix.
Is there a way for br0 to get this prefix too without eth0 joining the bridge? And to announce the prefix to any interfaces joining the bridge (e.g. LX system containers)?
¹ Is this the same? I have the impression these terms are used interchangeably with IPv6.
-
Another day, another IPv6 question. I'm on a Hetzner cloud VM. I have a static IPv6 /64 subnet / prefix¹. The system uses systemd-networkd for network management.
My eth0 does not seem to receive any RA at all but I'd like to delegate the prefix downstream to a bridge interface br0 on the same host. I have an IPv6Prefix section on eth0 with the Prefix=…, Assign=yes and Token=static:::1. It works, eth0 gets the ::1 address for this prefix.
Is there a way for br0 to get this prefix too without eth0 joining the bridge? And to announce the prefix to any interfaces joining the bridge (e.g. LX system containers)?
¹ Is this the same? I have the impression these terms are used interchangeably with IPv6.
-
Looking for a way to do downstream #ipv6 prefix delegation on Linux with dynamic prefixes. Right now I have #systemd #networkd request a delegation from my ISP. Now, I want to delegate a subprefix downstream. Systemd-networkd doesn't seem to have a DHCPv6 server, so I guess I need to run #kea or similar? Any advice?
-
Looking for a way to do downstream #ipv6 prefix delegation on Linux with dynamic prefixes. Right now I have #systemd #networkd request a delegation from my ISP. Now, I want to delegate a subprefix downstream. Systemd-networkd doesn't seem to have a DHCPv6 server, so I guess I need to run #kea or similar? Any advice?
-
Um das Netzwerk unter #Debian zu konfigurieren scheint #systemd #networkd inzwischen definitiv das bessere Werkzeug im Vergleich zu der arg in die Jahre gekommenen ifupdown Konfiguration über /etc/network/interfaces zu sein.
Jedenfalls konnte ich damit problemlos ohne zusätzliche scripts Wake-On-LAN aktivieren und addrlabel für #IPv6 setzen. -
Um das Netzwerk unter #Debian zu konfigurieren scheint #systemd #networkd inzwischen definitiv das bessere Werkzeug im Vergleich zu der arg in die Jahre gekommenen ifupdown Konfiguration über /etc/network/interfaces zu sein.
Jedenfalls konnte ich damit problemlos ohne zusätzliche scripts Wake-On-LAN aktivieren und addrlabel für #IPv6 setzen. -
Um das Netzwerk unter #Debian zu konfigurieren scheint #systemd #networkd inzwischen definitiv das bessere Werkzeug im Vergleich zu der arg in die Jahre gekommenen ifupdown Konfiguration über /etc/network/interfaces zu sein.
Jedenfalls konnte ich damit problemlos ohne zusätzliche scripts Wake-On-LAN aktivieren und addrlabel für #IPv6 setzen. -
Um das Netzwerk unter #Debian zu konfigurieren scheint #systemd #networkd inzwischen definitiv das bessere Werkzeug im Vergleich zu der arg in die Jahre gekommenen ifupdown Konfiguration über /etc/network/interfaces zu sein.
Jedenfalls konnte ich damit problemlos ohne zusätzliche scripts Wake-On-LAN aktivieren und addrlabel für #IPv6 setzen. -
Um das Netzwerk unter #Debian zu konfigurieren scheint #systemd #networkd inzwischen definitiv das bessere Werkzeug im Vergleich zu der arg in die Jahre gekommenen ifupdown Konfiguration über /etc/network/interfaces zu sein.
Jedenfalls konnte ich damit problemlos ohne zusätzliche scripts Wake-On-LAN aktivieren und addrlabel für #IPv6 setzen. -
Okay, really scary systemd-networkd moment: I replaced a lot of the #networkd config files on my server with new ones, that create bonds, bridges, etc and even move the IP address I am connected to from one of the interfaces to a bridge and move the interface onto the bridge.
I prepared the OOB connection and entered `networkctl reload` with the expectation that I will break my config.
And 2 seconds later my prompt appeared again on my SSH session. I love it when stuff magically just works.😍
-
Okay, really scary systemd-networkd moment: I replaced a lot of the #networkd config files on my server with new ones, that create bonds, bridges, etc and even move the IP address I am connected to from one of the interfaces to a bridge and move the interface onto the bridge.
I prepared the OOB connection and entered `networkctl reload` with the expectation that I will break my config.
And 2 seconds later my prompt appeared again on my SSH session. I love it when stuff magically just works.😍
-
Okay, really scary systemd-networkd moment: I replaced a lot of the #networkd config files on my server with new ones, that create bonds, bridges, etc and even move the IP address I am connected to from one of the interfaces to a bridge and move the interface onto the bridge.
I prepared the OOB connection and entered `networkctl reload` with the expectation that I will break my config.
And 2 seconds later my prompt appeared again on my SSH session. I love it when stuff magically just works.😍
-
Okay, really scary systemd-networkd moment: I replaced a lot of the #networkd config files on my server with new ones, that create bonds, bridges, etc and even move the IP address I am connected to from one of the interfaces to a bridge and move the interface onto the bridge.
I prepared the OOB connection and entered `networkctl reload` with the expectation that I will break my config.
And 2 seconds later my prompt appeared again on my SSH session. I love it when stuff magically just works.😍
-
Okay, really scary systemd-networkd moment: I replaced a lot of the #networkd config files on my server with new ones, that create bonds, bridges, etc and even move the IP address I am connected to from one of the interfaces to a bridge and move the interface onto the bridge.
I prepared the OOB connection and entered `networkctl reload` with the expectation that I will break my config.
And 2 seconds later my prompt appeared again on my SSH session. I love it when stuff magically just works.😍
-
@alexhaydock my intent is to educate myself about CLAT and solicit more input on how reasonable is it to do the translation with a bpf program within NM? What are your (anybody reading this) thoughts on it?
What about those using #systemd-#networkd or #connman? How does this compare to doing CLAT within userspace (via tunnel interface) or the kernel? Does CLAT really matter in GNU/Linux where the userspace is generally in better shape than Mac/Windows and we can just rebuild it?
[2/2]
-
@alexhaydock my intent is to educate myself about CLAT and solicit more input on how reasonable is it to do the translation with a bpf program within NM? What are your (anybody reading this) thoughts on it?
What about those using #systemd-#networkd or #connman? How does this compare to doing CLAT within userspace (via tunnel interface) or the kernel? Does CLAT really matter in GNU/Linux where the userspace is generally in better shape than Mac/Windows and we can just rebuild it?
[2/2]
-
@alexhaydock my intent is to educate myself about CLAT and solicit more input on how reasonable is it to do the translation with a bpf program within NM? What are your (anybody reading this) thoughts on it?
What about those using #systemd-#networkd or #connman? How does this compare to doing CLAT within userspace (via tunnel interface) or the kernel? Does CLAT really matter in GNU/Linux where the userspace is generally in better shape than Mac/Windows and we can just rebuild it?
[2/2]
-
@alexhaydock my intent is to educate myself about CLAT and solicit more input on how reasonable is it to do the translation with a bpf program within NM? What are your (anybody reading this) thoughts on it?
What about those using #systemd-#networkd or #connman? How does this compare to doing CLAT within userspace (via tunnel interface) or the kernel? Does CLAT really matter in GNU/Linux where the userspace is generally in better shape than Mac/Windows and we can just rebuild it?
[2/2]
-
@alexhaydock my intent is to educate myself about CLAT and solicit more input on how reasonable is it to do the translation with a bpf program within NM? What are your (anybody reading this) thoughts on it?
What about those using #systemd-#networkd or #connman? How does this compare to doing CLAT within userspace (via tunnel interface) or the kernel? Does CLAT really matter in GNU/Linux where the userspace is generally in better shape than Mac/Windows and we can just rebuild it?
[2/2]
-
Seems this is a bug in systemd-networkd unfortunately. So for now I just have to run dhclient after every suspend. https://bbs.archlinux.org/viewtopic.php?pid=2221138
-
Seems this is a bug in systemd-networkd unfortunately. So for now I just have to run dhclient after every suspend. https://bbs.archlinux.org/viewtopic.php?pid=2221138
-
Seems this is a bug in systemd-networkd unfortunately. So for now I just have to run dhclient after every suspend. https://bbs.archlinux.org/viewtopic.php?pid=2221138
-
Seems this is a bug in systemd-networkd unfortunately. So for now I just have to run dhclient after every suspend. https://bbs.archlinux.org/viewtopic.php?pid=2221138
-
Seems this is a bug in systemd-networkd unfortunately. So for now I just have to run dhclient after every suspend. https://bbs.archlinux.org/viewtopic.php?pid=2221138
-
I just hope the rest of the road is smoother. Fighting for a while with configuration is pretty darn discouraging and exhausting.
I think I was spoiled with #networkd and #netplan (with networkd backend) for the most part working just the way I like, even though netplan is missing some things I need.
-
I just hope the rest of the road is smoother. Fighting for a while with configuration is pretty darn discouraging and exhausting.
I think I was spoiled with #networkd and #netplan (with networkd backend) for the most part working just the way I like, even though netplan is missing some things I need.
-
I just hope the rest of the road is smoother. Fighting for a while with configuration is pretty darn discouraging and exhausting.
I think I was spoiled with #networkd and #netplan (with networkd backend) for the most part working just the way I like, even though netplan is missing some things I need.
-
I just hope the rest of the road is smoother. Fighting for a while with configuration is pretty darn discouraging and exhausting.
I think I was spoiled with #networkd and #netplan (with networkd backend) for the most part working just the way I like, even though netplan is missing some things I need.
-
I just hope the rest of the road is smoother. Fighting for a while with configuration is pretty darn discouraging and exhausting.
I think I was spoiled with #networkd and #netplan (with networkd backend) for the most part working just the way I like, even though netplan is missing some things I need.
