User Tools

Site Tools


doc:uci:network:switch

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
doc:uci:network:switch [2014/08/16 19:15]
gregorg Wrong option name for VLAN ID
doc:uci:network:switch [2015/06/04 11:53] (current)
taeuber [Switch Documentation]
Line 8: Line 8:
  
 If you want to change how these ports are connected to each other you need to configure the **switch** of your device (see also [[doc/​networking/​network.interfaces]]) If you want to change how these ports are connected to each other you need to configure the **switch** of your device (see also [[doc/​networking/​network.interfaces]])
 +
 +Different routers have different switch layouts, so look at the Wiki for your specific device. The TP-Link Archer C7 has eth0 = WAN, and eth1 = LAN (the 4 switch ports). Port 0 of the switch = eth1 (labelled CPU in Luci), Port 6 = eth0. Port 1 is labelled WAN in Luci. Look at the wiki for your router. Every router is different. The popular TP-Link WDR4300 only has eth0.
 +
  
 ===== UCI config, swconfig style ===== ===== UCI config, swconfig style =====
 +
 +==== Known problems ====
 +  * if a switch interface (for the cpu point of view) is controlling several '​physical interfaces',​ every time than one physical interface is connected all the switch interface result connected (that means all the ports ''​ethN.Y''​ are UP) and therefore every rule (routing for example) is applied. This could cause serious problem, for example if one relies on the automatic mechanism of routing metric when one route is not available anymore.
 +    * One way to detect this is: ''​swconfig dev <​switch_interface_name>​ show | grep link''​ or see [[doc:​techref:​swconfig]]
  
  
Line 107: Line 114:
  
 See also [[wp>​backplane]]. See also [[wp>​backplane]].
 +
 +==== Examples ====
 +
 +==== Example on the asus wl500gp v2 , openwrt 10.03, every physical port ====
 +<​code>​
 +config '​switch'​ '​eth0'​
 + option '​enable'​ '​1'​
 +
 +
 +config '​switch_vlan'​ '​eth0_0'​
 + option '​device'​ '​eth0'​
 + option '​vlan'​ '​0'​
 + option '​ports'​ '4 5' #wan
 +
 +config '​switch_vlan'​ '​eth0_1'​
 + option '​device'​ '​eth0'​
 + option '​vlan'​ '​1'​
 + option '​ports'​ '3 5' #lan 1
 +
 +config '​switch_vlan'​ '​eth0_2'​
 + option '​device'​ '​eth0'​
 + option '​vlan'​ '​2'​
 + option '​ports'​ '2 5' #lan2
 +
 +config '​switch_vlan'​ '​eth0_3'​
 + option '​device'​ '​eth0'​
 + option '​vlan'​ '​3'​
 + option '​ports'​ '1 5' #lan3
 +
 +config '​switch_vlan'​ '​eth0_4'​
 + option '​device'​ '​eth0'​
 + option '​vlan'​ '​4'​
 + option '​ports'​ '0 5' #lan4
 +
 +#note that to use a particular port in an interface the ifname
 +#should be '​devicename.vlan'​ . So for example ifname '​eth0.3'​
 +</​code>​
 +
 +==== Example vmware linux guest, openwrt x86 generic 12.09 combined, 2virtualized intel e1000 ====
 +:!: More research on vlan on x86 devices has to be done to collect more information on the wiki.
 +
 +The majority of x86 devices do not have any programmable switch,
 +but it does not seem to be a problem. The syntax used
 +on devices with programmable switches seems completely not necessary.
 +
 +For example we want to create two '​virtual interfaces'​ associated to the same
 +physical interface, ''​eth1''​. To do this, we do the following in ''/​etc/​config/​network''​
 +
 +<​code>​
 +..other lines...
 +
 +config interface lan1
 +        option ifname eth1.100
 +        ...further config...
 +        ​
 +config interface lan2
 +        option ifname eth1.101
 +        ... further config ...
 +</​code>​
 +According to what the contributors of this section have read online, ​
 +so far seems that the packet will be tagged by default, ​
 +because they are associated to one physical ports that 
 +at most will have one PVID (port vlan id) but more than one virtual interfaces.
 +Therefore, having multiple virtual interfaces, the packets must be tagged else it
 +won't make sense, they won't be able to reach the interfaces or to go out.
 +
 +The tests seems to confirm that because (using a vmware switch and portgroups) to let two
 +openwrt x86 vmware guests reach each other the portgroups had to be configured with the trunk
 +vlan id (that is: vlan id 4095,
 +According to white papers: //VMware Virtual Networking Concepts// and //VMware ESX Server 3 802.1Q VLAN Solutions//​).
 +
 +Side note: if different virtual interfaces related to different vlan are in the same logical network, there will be conflict in terms of metrics, in that case bridging the interfaces could be a solution (has to be tested).
doc/uci/network/switch.1408209308.txt.bz2 · Last modified: 2014/08/16 19:15 by gregorg