4 ms·
ebtables would be the "linux and a bunch of ethernet cards" version of the solution. On the VLANs, yes, I should have been explicit. Having multiple subnets on
by gvb 11y ago
ebtables would be the "linux and a bunch of ethernet cards" version of the solution.
On the VLANs, yes, I should have been explicit. Having multiple subnets on a single shared ethernet is mostly useless security-wise, you need to use VLANs to segregate the traffic. With router/switches, you would set up the physical ethernet ports on different VLANs and then control the packet routing between the VLANs (switch ports).
Proper WiFi APs support multiple SSIDs on different VLANs. YMMV, but the reviews I've read indicate the WiFi's actual communications speed takes a hit when it has to support multiple SSIDs (probably has to go to software encryption/decription). If you pay more for the AP, maybe not.
- mindslight 11y agoLinux and one ethernet card will get the job done, using VLAN trunking. devA --notag-> switchA --tag100-> linux.eth0.100 -> ebtables (linux.br0) -> linux.eth0.101 --tag101-> switchA --notag-> devB Obviously there's a bandwidth bottleneck, but we're mostly concerned about piddly devices that exchange control messages or in the worst case stream video, not gigabit file transfers. And the latter case can obviously be scaled up with a quad port card on the Linux brouter, and/or more than one device on each VLAN. After that's setup, what's the point of the complexity of separate subnets? You don't really need to route between IP subnets when ebtables / brouting will give you the same filtering functionality, transparent to level 3.