They ran out of ports on their managed switch and will not have budget for another one for while. There are a bunch of free ports on the ASG 525 and what we want to do is turn these into access ports for the VLANs. It's not exactly supported by the GUI, but it should be possible at the command line. At least one would think, given basic linux commands.
So far we have this:
br0 -> eth6 eth0.2
We had to add eth0.2 to br0 at the command line since the GUI does not allow it as a choice.
From all the reading I've done, that should do it. Egress frames from eth0.2 should have their tag stripped, while ingress frames should have a tag added. However, we can't seem to get DHCP (bound to eth0.2) on the bridge, or even arping the eth0.2 interface from the eth6 interface.
What I *suspect* is happening, is that the frames are crossing the boundary, but only appearing on the physical port egress, and not visible to the kernel for internal routing. I have not yet confirmed this, as It's going to take a bit of work to test that theory.
The problem at this point, is I'm not sure if:
- We're just plain setting up the bridge wrong for this.
- There's something special about bridging on the ASG. (There's a bunch of poorly documented bridge settings I've seen out there and maybe something is configured that prevents what we are trying to do.)
Any advice is greatly appreciated. Thanks!
This thread was automatically locked due to age.
