f1dfb1f976
I'm half-pleased with this. It demonstrates how we can have complex conditional kernel config, but the way we detect if vlan exists is tacky.
52 lines
1.5 KiB
Nix
52 lines
1.5 KiB
Nix
## Bridge module
|
|
## =============
|
|
##
|
|
## Allows creation of Layer 2 software "bridge" network devices. A
|
|
## common use case is to merge together a hardware Ethernet device
|
|
## with one or more WLANs so that several local devices appear to be
|
|
## on the same network.
|
|
|
|
|
|
{ lib, pkgs, config, ...}:
|
|
let
|
|
inherit (lib) mkOption types;
|
|
inherit (pkgs.liminix.services) oneshot;
|
|
inherit (pkgs) liminix;
|
|
in
|
|
{
|
|
options = {
|
|
system.service.bridge = {
|
|
primary = mkOption { type = liminix.lib.types.serviceDefn; };
|
|
members = mkOption { type = liminix.lib.types.serviceDefn; };
|
|
};
|
|
};
|
|
config.system.service.bridge = {
|
|
primary = liminix.callService ./primary.nix {
|
|
ifname = mkOption {
|
|
type = types.str;
|
|
description = "bridge interface name to create";
|
|
};
|
|
};
|
|
members = liminix.callService ./members.nix {
|
|
primary = mkOption {
|
|
type = liminix.lib.types.interface;
|
|
description = "primary bridge interface";
|
|
};
|
|
|
|
members = mkOption {
|
|
type = types.listOf liminix.lib.types.interface;
|
|
description = "interfaces to add to the bridge";
|
|
};
|
|
};
|
|
};
|
|
config.kernel.config = {
|
|
BRIDGE = "y";
|
|
BRIDGE_IGMP_SNOOPING = "y";
|
|
} // lib.optionalAttrs (config.system.service ? vlan) {
|
|
# depends on bridge _and_ vlan. I would like there to be
|
|
# a better way to test for the existence of vlan config:
|
|
# maybe the module should set an `enabled` attribute?
|
|
BRIDGE_VLAN_FILTERING = "y";
|
|
};
|
|
}
|