On Thursday, 04/21/2016 at 07:39 GMT, Grzegorz Powiedziuk <[email protected]> wrote: > I believe Mark said that having linux to handle vlan tagging is hard.
There is nothing difficult about getting Linux to perform VLAN tagging. The question is not one of capability, but of network security management. > In your case, you let the vswitch to do vlan tagging and untaging. So > vswitch has to be vlan aware so it can receive and understand tagged frames > from the outside real, switch. > When it receives a tagged frame from the outside world it removes the vlan > tag, and send the actual frame to guests which have "granted" access to > that speciffic vlan. And when vswitch receives an untaged frame from > guest, it adds a vlan tag to it and sends it to real switch (trunk port > specifically) . > So from linux perspective, there are no vlan tags and everything is nice an > easy. A nice explanation. > define vswitch vlan aware vs vswitch .. vlan xxx I don't believe makes any > difference in your case > According to manual > "defvid > defines the virtual switch as a VLAN-aware switch supporting IEEE standard > 802.lQ. The defvid defines the default VLAN ID to be assigned to guest > ports when no VLAN ID is coded on the SET VSWITCH GRANT VLAN command" Yes, there is a difference. Please see my post. Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems & Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 [email protected] IBM Endicott ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
