nearxos/Rina-deployment
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

test

Browse Source
This commit is contained in:
nearxos
2026-02-17 15:14:51 +02:00
parent d670e8cd85
commit 9b1b4cef44
1 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/vlan40-bridge-systemd-networkd.md
View File

@@ -106,29 +106,28 @@ Adjust the address to match your VLAN 40 subnet. Remove the `Address=` line if y
## 6. Add VLAN to the parent interface (.network) ## 6. Add VLAN to the parent interface (.network)
Edit **`20-eth1.network`** so that eth1 explicitly carries VLAN 40. Add a `VLAN=eth1.40` line under the `[Network]` section. Edit **`20-eth1.network`** so that eth1 explicitly carries VLAN 40. Your file currently looks like:
If the file currently looks like:
```ini ```ini
[Match] [Match]
Name=eth1 Name=eth1
[Network] [Network]
# ... other options (e.g. no config if eth1 is only used by br1) Bridge=br1
``` ```
add: Add **`VLAN=eth1.40`** under `[Network]` (same pattern as `10-eth0.network`, which has `VLAN=eth0.50`, `VLAN=eth0.60`, `VLAN=eth0.201`). After editing:
```ini ```ini
[Match] [Match]
Name=eth1 Name=eth1
[Network] [Network]
Bridge=br1
VLAN=eth1.40 VLAN=eth1.40
``` ```
If there are already other keys under `[Network]`, add `VLAN=eth1.40` on a new line in that same section. This ties the VLAN to eth1 so it is created when eth1 is configured. This ties the VLAN to eth1 so it is created when eth1 is configured. eth1 stays in br1; eth1.40 will be created and then attached to br1.40 by the 21-eth1.40.network file.
--- ---