[OpenWrt-Devel] why is 'wan' port missing in luci switch vlan setup page for Netgear WNR2200 ?

[David Lang]

On Fri, 3 Oct 2014, Urs Rau (UK) wrote:

> Hi Jo-Philipp,
>
> On 26 Sep 2014, at 09:55, Jo-Philipp Wich <jow at openwrt.org<mailto:jow at openwrt.org>> wrote:
>
> Hi.
>
> The wan port is likely a dedicated, non-switch interface (e.g. eth1) on
> this model. If you want to declare VLANs on it then simply create a new
> interface using eth1.Y as manual physical ifname where Y denotes the
> desired VLAN id.
>
> ~ Jow
>
> yes, I think you are right.
>
> eth0 is the yellow wan port
>
> and eth1 is the 4 port switch on this hardware
>
> but now I have a problem, how do i get tagged VLAN  traffic coming in on eth0.96 eth0.128 eth0.144 eth0.160 eth0.168 to ‘connect’ or ‘forward’ to the relevant eth1.VLANID ? on other models the wan port is part of the same switch and I can tick the ‘cpu’ port in luci to ‘transport’ or ‘forward’ the right wan VLAn with the right LAN port 1 - 4.
>
> How can I do this on this hardware which has one wan port that is not part of the switch and for lan ports that are part of the switch that luci shows under the ‘switch’ page?
>
> or do I have to ‘forget’ about using the ‘wan’ port and work with the lan ports 1 - 4 only?

you bridge between the eth0.x and eth1.x interfaces (where x is the VLAN)

keep in mind that since this traffic is going through the kernel to get from one 
side to the other instead of just through the switch, it is going to be slower.

David Lang
-------------- next part --------------
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
-------------- next part --------------
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel