Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
technical:ppsk-hostapd [2024/04/26 09:52] – system | technical:ppsk-hostapd [2024/04/30 08:22] (current) – [Key specific for VLAN] system | ||
---|---|---|---|
Line 91: | Line 91: | ||
</ | </ | ||
* A few additional steps are required for the VLAN tagging function of hostapd to work as intended. | * A few additional steps are required for the VLAN tagging function of hostapd to work as intended. | ||
- | + | * We need to include a few options to instruct hostapd how to handle the VLANs. | |
- | <alert type=" | + | * Refer to this snippet from / |
+ | <code bash> | ||
+ | option wpa_psk_file '/ | ||
+ | option vlan_file '/ | ||
+ | option vlan_tagged_interface ' | ||
+ | option vlan_bridge ' | ||
+ | option dynamic_vlan ' | ||
+ | </code> | ||
+ | * Then here is an example of hostapd.vlan | ||
+ | <code bash> | ||
+ | # VLAN ID to network interface mapping | ||
+ | 1 vlan1 | ||
+ | 2 vlan2 | ||
+ | 3 vlan3 | ||
+ | 4 vlan4 | ||
+ | 100 guest | ||
+ | # Optional wildcard entry matching all VLAN IDs. The first # in the interface | ||
+ | # name will be replaced with the VLAN ID. The network interfaces are created | ||
+ | # (and removed) dynamically based on the use. | ||
+ | * vlan# | ||
+ | </ | ||
+ | * hostapd will create a bridge with each VLAN and automatically create tagged interfaces and make them members of this bridge: | ||
+ | <code bash> | ||
+ | root@OpenWrt: | ||
+ | bridge name | ||
+ | br-vlan3 | ||
+ | eth0.3 | ||
+ | br-lan | ||
+ | </ | ||
------ | ------ |