| 15 Jun 2021 |
|  jdyg joined the room. | 19:12:00 |
| 16 Jun 2021 |
|  Leon joined the room. | 13:22:56 |
| 18 Jun 2021 |
 Church | Hmm anyone had issue with postUp and postShutdown commands in wireguard not running correctly and setting up and tearing down your rules? | 07:34:44 |
| 19 Jun 2021 |
 hpfr | uh, is the wireguard module missing a dns option? | 18:17:35 |
| hpfr | I guess I'm supposed to use the wg-quick module instead | 18:25:43 |
| hpfr | seems weird that they overlap a lot and that the wireguard module is apparently missing options? | 18:26:21 |
| 20 Jun 2021 |
 Mic92 | the wireguard module was introduced before wg-quick existed | 06:55:54 |
| Mic92 | Otherwise there would be no wireguard module | 06:56:20 |
| Church | So what's preferred? Wireguard or wg-quick? | 22:47:22 |
| 21 Jun 2021 |
 eyJhb | ^ would like to know that as well, since I am currently using wireguard, and not wg-quick | 08:32:30 |
 Andreas Schrägle | I just generate systemd-networkd files for my wireguard interfaces 🤷♂️ | 11:28:52 |
| Leon | Yup, the networkd module works pretty flawlessly | 11:31:07 |
| Leon | Also, it doesn’t do as much magic as do the wireguard or wg-quick modules, for instance derive routes from the Allowed-IPs | 11:32:07 |
| Leon | (At least by default) | 11:32:33 |
 hexa | which is favorable when you want to do dynamic routing on top of them 😀 | 11:35:15 |
| Leon | Exactly. I run OSPF+BGP on top so unconditionally routing ::/0 doesn’t do any good :D | 11:38:01 |
| hexa | Babel https://datatracker.ietf.org/doc/html/rfc8966 :) | 11:49:48 |
|  anodae joined the room. | 20:52:21 |
| 22 Jun 2021 |
| Mic92 | Also I added wireguard support to networkd, I never really used it much afterwards. | 08:53:47 |
| 23 Jun 2021 |
|  anubhavkini joined the room. | 06:52:47 |
|  Linux Hackerman joined the room. | 14:48:12 |
 kraftnix | Does anyone have some nice tips/tricks to dealing with the systemd-networkd limits on length of interface names? I want to autoconfigure interfaces in certain ways, but sometimes they go over limit the limit (and get a fairly silent failure in systemd-networkd logs rather than the configuration actively failing (it will often fail just due to some missing networks).
The interface names I was configuring are essentially a combination a container name + bridge name, obviously a short workaround would be to just force the name down to 15 characters, but if the container name is long then potentially I could have naming conflicts for interfaces for different bridges :/, one solution would be to reduce the container name/bridge names to 6 or 7 chars each for interface configuration but that is also a bit messy :(
| 15:15:28 |
| kraftnix | * Does anyone have some nice tips/tricks to dealing with the systemd-networkd limits on length of interface names? I want to autoconfigure interfaces in certain ways, but sometimes they go over the limit (and get a fairly silent failure in systemd-networkd logs rather than the configuration actively failing (it will often fail just due to some missing networks).
The interface names I was configuring are essentially a combination a container name + bridge name, obviously a short workaround would be to just force the name down to 15 characters, but if the container name is long then potentially I could have naming conflicts for interfaces for different bridges :/, one solution would be to reduce the container name/bridge names to 6 or 7 chars each for interface configuration but that is also a bit messy :(
| 15:15:48 |
| hexa | IFNAMSIZ is limit in the kernel though | 15:16:03 |
| hexa | * IFNAMSIZ is a limit in the kernel, not networkd | 15:16:45 |
| kraftnix | ok, is there any way to increase that? if not then I still need to figure out a clean workaround (hence the request for tips/tricks) | 15:19:27 |
| hexa | on wlan APs i usually use radioN_vlanXXXX and that neatly works 😂 | 15:19:43 |
| hexa | in theory there is IFALIAS | 15:20:48 |
| hexa | * in theory there is IFALIAS: ip link set alias somethinglongerthanfiveteencharacters dev lo | 15:21:17 |
| Linux Hackerman | you can also patch your kernel, but YMMV :> | 15:21:41 |
