EdgeMax Lite
-
Looks like the EdgeMax OS is a new beast (at least completely new to me)
I have it setup and routing traffic to the internet fine.
Port 0 - WAN
Port 1 - LAN
Port 2 - VLAN10 - wireless
Port 2 - VLAN20 - Guest wirelessHow Do I configure non tagged traffic on port 2 to be on the default VLAN that is (hopefully) on the same VLAN as traffic on Port 1?
-
@Dashrender You don't. because the ERL is a router only. There is no switch infrastructure built into it. The EdgeMax PoE is the first model with a switch chip on some of the ports (3,4,5).
Now, you can create a bridge interface and make eth2 and eth1 members of that bridge, but that does involve a performance hit as that is all done on the CPU not a dedicated switch chip. For the basic SOHO that is likely not a problem, but it could be.
-
@JaredBusch said:
@Dashrender You don't. because the ERL is a router only. There is no switch infrastructure built into it. The EdgeMax PoE is the first model with a switch chip on some of the ports (3,4,5).
Now, you can create a bridge interface and make eth2 and eth1 members of that bridge, but that does involve a performance hit as that is all done on the CPU not a dedicated switch chip. For the basic SOHO that is likely not a problem, but it could be.
Alright, that makes since. So let's not bother with creating a single VLAN - how do I get traffic to flow from one VLAN to another through the ERL?
-
@Dashrender said:
Alright, that makes since. So let's not bother with creating a single VLAN - how do I get traffic to flow from one VLAN to another through the ERL?
It is a router, thus by default it will route between all the networks on the device. You have to add firewall rules to tell it to not do so.
So if you are having a problem routing, remove the firewall information form the firewall.
configure delete interfaces ethernet eth1 firewall delete interfaces ethernet eth2 firewall delete interfaces ethernet eth2.10 firewall delete interfaces ethernet eth2.20 firewall commit save -
Aww.. I guess I'm to used to working on Firewalls, not routers.
-
@Dashrender said:
Aww.. I guess I'm to used to working on Firewalls, not routers.
A firewall is a set of extensions on top of a router, typically. You can have a layer 2 firewall (a bridging firewall) but those are very rare in the SMB. I've seen them, but almost never. Those that I do see are normally Untangle devices set to bridging rather than routing mode because they make crappy routers. In the enterprise space, bridged firewalls are pretty common because they want the firewall functionality separate from the routing appliance.
What you are used to is an "all in one" device that puts a router, switch, firewall and access point (wireless hub) all into one device. So what you are seeing with the VLANs is the switch functionality, not the router nor the firewall components.
