On Tue, Nov 22, 2016 at 10:18:27AM +0100, Marc Haber wrote: > > The switch chips in consumer access points come with some limitations, > > you should check if they can meet your requrements: > > - They only support a small number of vlans, a typical limit is 15. > > Does that mean that the VLAN IDs are also limited to the 0..15 range > or can I have 15 VLANs with arbitrary IDs?
4-bit VLAN IDs (0..15 range) really. But as David Lang said, this seems to be a thing of the past. I can confirm that full 12-bit VLAN IDs work on a router based on the Lantiq VRX268 SoC. It has a limit of 64 VLANs. > > - Their ports can only be configured to carry either a single untagged > > vlan, or a number of tagged vlans, but not both simultaneously. > > I usually prefer to have the management VLAN untagged, but I can live > without that. > > How would I check whether a given hardware would support that? The default network config for your device should come with a single VLAN or two, depending on how the WAN interface is connected, and all VLANs tagged for the CPU port. This is how it is usually wired up: https://wiki.openwrt.org/doc/uci/network/switch First you can modify this config to add more VLANs, untagged towards external ports and tagged towards the CPU. https://wiki.openwrt.org/doc/uci/network/switch#the_configuration I hadn't noticed the 'switch_port' section before, maybe it helps with making untagged VLANs work in combination with tagged VLANs on a port. In the network configuration, the interface ethX.Y can be used as usual, for example to add an IP address and subnet. Then add another VLAN, assign it as tagged to both an external port and the CPU, and check if everything still works. The port numbers and the labels printed on the case usually do not match, but the mapping is documented in the wiki for some devices, or you can just find it out experimentally. Finally a few example commands for setting up VLANs and IP related network config with uci. You can modify this as needed. swconfig list swconfig dev eth0 show uci show network uci set network.vl2=switch_vlan uci set network.vl2.device='switch0' uci set network.vl2.vlan='2' uci set network.vl2.ports='2 5t 6t' # you may have to add a 'switch_port' section here uci set network.net2=interface uci set network.net2.ifname='eth0.2' uci set network.net2.proto='static' uci set network.net2.ipaddr='192.168.2.0' uci set network.net2.netmask='255.255.255.0' /etc/init.d/network reload # try if it works, decide if you want to keep this config uci changes uci commit uci revert network My example uses named switch_vlan sections, which is different from the default. An unnamed section would instead be created like this: uci add network switch_vlan and the resulting identifier used instead of 'vl2'. If you set the options through uci and don't commit them to flash yet, it is possible to recover from mistakes by power-cycling the device. Otherwise, you can always boot to the failsafe mode: https://wiki.openwrt.org/doc/howto/generic.failsafe > I would be willing to buy a cheaper accesspoint in the 50-euro-range > to try things out. Any recommendations? The TP-Link TL-WR841ND is cheap, but it has only 4 MB flash, which is very limiting if you want to add software packages. The only recent device I own is the TP-Link TD-W8980. It is within your budget, but I hesitate to recommend it to you: - installing OpenWrt/LEDE is more difficult than on other devices - the 5 GHz WLAN radio is not supported The more expensive "TP-Link Archer C7 v2" (90€) could be an option. From what I read, it should be well supported at least in the development snapshots of OpenWrt and LEDE. To get more hardware recommendations, perhaps also from other vendors, you could try the web forums: https://forum.openwrt.org/ https://forum.lede-project.org/ Regards, Mirko _______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
