liminix

Commit Graph

Author	SHA1	Message	Date
Daniel Barlow	cc73a98419	support setting network device names this means that net devices in devices/foo/default.nix can be specified by their sysfs paths (instead of by "eth0" and "eth1" that may change from one kernel version to the next) and given mnenomic names that are helpful for the hardware. Like "wan" and "lan[1..4]"	2023-11-26 23:15:28 +00:00
Daniel Barlow	31f0213b6f	convert network link/address to module-based-service ... and make bridge use it. We also had to convert bridge back into a pair of services. Downstreams want to depend on the bridge it self being configured even if not necessarily all the members are up. e.g. don't want to break ssh on lan if there's a misconfigured wlan device	2023-08-28 22:02:28 +01:00

Author

SHA1

Message

Date

Daniel Barlow

cc73a98419

support setting network device names

this means that net devices in devices/foo/default.nix can be
specified by their sysfs paths (instead of by "eth0" and "eth1" that
may change from one kernel version to the next) and given mnenomic
names that are helpful for the hardware. Like "wan" and "lan[1..4]"

2023-11-26 23:15:28 +00:00

Daniel Barlow

31f0213b6f

convert network link/address to module-based-service

... and make bridge use it.

We also had to convert bridge back into a pair of services.
Downstreams want to depend on the bridge it self being configured
even if not necessarily all the members are up. e.g. don't want
to break ssh on lan if there's a misconfigured wlan device

2023-08-28 22:02:28 +01:00

2 Commits