| 30 Jun 2023 |
 @sumner:nevarro.space | I don't know how to replicate that using just systemd.network | 17:50:45 |
 hexa | ip route? | 17:56:52 |
| @sumner:nevarro.space | root@matrix:~/ > ip route
default via 172.31.1.1 dev eth0 proto dhcp src 5.161.216.225 metric 1002
10.0.0.0/8 via 10.0.0.1 dev eth1 proto dhcp src 10.0.1.3 metric 1003 mtu 1450
10.0.0.1 dev eth1 proto dhcp scope link src 10.0.1.3 metric 1003 mtu 1450
172.31.1.1 dev eth0 proto dhcp scope link src 5.161.216.225 metric 1002
| 17:58:06 |
| hexa | legacy interface names 😲 | 17:59:22 |
| @sumner:nevarro.space | I set usePredictableInterfaceNames = false since I saw that recommended somewhere. | 18:01:14 |
| hexa | that is as silly recommendation 😄 | 18:01:24 |
| hexa | you need a mechanism to ensure the same interface comes up with the same name on every boot | 18:02:03 |
| hexa | the ethN scheme is first come, first served | 18:02:11 |
| hexa | systemd.network.enable = true;
systemd.network.networks."10-wan" = {
matchConfig.Name = "eth0";
networkConfig.DHCP = "ipv4";
};
systemd.network.networks."10-wan" = {
matchConfig.Name = "eth1";
address = [
"10.0.1.3/32"
]:
routes = [
{ routeConfig.Destination = "10.0.0.0/8"; }
];
};
| 18:03:09 |
| hexa | * systemd.network.enable = true;
systemd.network.networks."10-wan" = {
matchConfig.Name = "eth0";
networkConfig.DHCP = "ipv4";
};
systemd.network.networks."10-wan" = {
matchConfig.Name = "eth1";
networkConfig.DHCP = "ipv4";
};
| 18:04:04 |
| hexa | * systemd.network.enable = true;
systemd.network.networks."10-wan" = {
matchConfig.Name = "eth0";
networkConfig.DHCP = "ipv4";
};
systemd.network.networks."10-vpn" = {
matchConfig.Name = "eth1";
networkConfig.DHCP = "ipv4";
};
| 18:04:11 |
| @sumner:nevarro.space | should I also re-enable usePredictableInterfaceNames and update the matchConfig.Name accordingly, then? | 18:06:01 |
| hexa | in that case I would recommend going with matchConfig.MACAddress | 18:06:31 |
| hexa | because what are the new names going to be? | 18:06:55 |
| hexa | probably mentioned somewhere in dmesg | grep renamed | 18:07:19 |
 Zhaofeng Li | (apparently I missed the whole conversation) I pin against MAC addresses as well | 18:16:38 |
| Zhaofeng Li | ... and I go one step further and rename the interfaces to wan/lan/bedroom etc | 18:17:05 |
| @sumner:nevarro.space | thanks for your help, I went ahead and pinned to mac address and it seems to be working. I'll just have to wait and see if I get pinged in the middle of the night again because my server is down due to forgetting how to connect to the internet. I guess networkd is probably more reliable than using dhcpcd? | 19:10:37 |
| 2 Jul 2023 |
|  @duponin:alternativebit.fr left the room. | 20:23:43 |
| 4 Jul 2023 |
|  jlesquembre joined the room. | 09:14:55 |
| 10 Jul 2023 |
 @julian:nekover.se | Hi, why is StrictHostKeyChecking=accept-new enabled per default and is there an option to disable it? | 01:28:01 |
| @julian:nekover.se | Also I'm not sure, if it's great to that option enabled per default. While it's certainly fine for most use cases - depending on where your remote hosts are and what your threat model is - I think such an option should be opt in and not opt out.
I certainly wouldn't expect software to auto-accept remote SSH keys for me, so I was also kinda bamboozled finding out colmena did. | 01:44:40 |
