esxi and freebsd vlans
Hi, I ran into the ESXi limit of 4 NICs per VM, so I figured I would work around this using FreeBSD's vlan devices. I made 2 test installs with the following interface configuration: test1: ifconfig em0 inet 10.10.10.1 netmask 255.255.255.0 ifconfig vlan create ifconfig vlan0 inet 192.168.1.1 netmask 255.255.255.0 vlan 22 vlandev em0 test2: ifconfig em0 inet 10.10.10.2 netmask 255.255.255.0 ifconfig vlan create ifconfig vlan0 inet 192.168.1.2 netmask 255.255.255.0 vlan 22 vlandev em0 I can ping the other machine using the 10.10.10.x IP address no problem, but the 192.168.1.x addresses don't work. I've tried setting the vlan id on the vSwitch to none and to 22, but in neither of the two cases does it work. Does anybody have FreeBSD vlan's working on ESXi or know how to get it working? Many thanks, Sebastiaan van Erk smime.p7s Description: S/MIME Cryptographic Signature
RE: esxi and freebsd vlans
Hello Sebastian: Hi, I ran into the ESXi limit of 4 NICs per VM, so I figured I would work around this using FreeBSD's vlan devices. I made 2 test installs with the following interface configuration: test1: ifconfig em0 inet 10.10.10.1 netmask 255.255.255.0 ifconfig vlan create ifconfig vlan0 inet 192.168.1.1 netmask 255.255.255.0 vlan 22 vlandev em0 test2: ifconfig em0 inet 10.10.10.2 netmask 255.255.255.0 ifconfig vlan create ifconfig vlan0 inet 192.168.1.2 netmask 255.255.255.0 vlan 22 vlandev em0 I can ping the other machine using the 10.10.10.x IP address no problem, but the 192.168.1.x addresses don't work. I've tried setting the vlan id on the vSwitch to none and to 22, but in neither of the two cases does it work. [Michael K. Smith - Adhost] You will need to make sure the switchport facing your server is set to 802.1Q trunk and has VLAN 22 allowed. The IP address on em0 itself is untagged so it will work regardless of the port settings on the switch. VLAN 22 has the 4-byte header attached so the other side has to recognize the tag. Regards, Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: esxi and freebsd vlans
Hi, Thanks for your response! :-) Michael K. Smith - Adhost wrote: Hello Sebastian: Hi, I ran into the ESXi limit of 4 NICs per VM, so I figured I would work around this using FreeBSD's vlan devices. I made 2 test installs with the following interface configuration: test1: ifconfig em0 inet 10.10.10.1 netmask 255.255.255.0 ifconfig vlan create ifconfig vlan0 inet 192.168.1.1 netmask 255.255.255.0 vlan 22 vlandev em0 test2: ifconfig em0 inet 10.10.10.2 netmask 255.255.255.0 ifconfig vlan create ifconfig vlan0 inet 192.168.1.2 netmask 255.255.255.0 vlan 22 vlandev em0 I can ping the other machine using the 10.10.10.x IP address no problem, but the 192.168.1.x addresses don't work. I've tried setting the vlan id on the vSwitch to none and to 22, but in neither of the two cases does it work. [Michael K. Smith - Adhost] You will need to make sure the switchport facing your server is set to 802.1Q trunk and has VLAN 22 allowed. The IP address on em0 itself is untagged so it will work regardless of the port settings on the switch. VLAN 22 has the 4-byte header attached so the other side has to recognize the tag. Just to clarify, both VM's are on a single ESXi server on a virtual switch, so no network hardware is involved. It is possible to configure the virtual switch to be on no vlan and on a specific vlan, but in both cases it didn't work. I'll see if I there are more settings I can change on the virtual switch. Regards, Mike Regards, Sebastiaan smime.p7s Description: S/MIME Cryptographic Signature
Re: esxi and freebsd vlans
Hi, Michael K. Smith - Adhost wrote: Hello Sebastian: Hi, I ran into the ESXi limit of 4 NICs per VM, so I figured I would work around this using FreeBSD's vlan devices. I made 2 test installs with the following interface configuration: test1: ifconfig em0 inet 10.10.10.1 netmask 255.255.255.0 ifconfig vlan create ifconfig vlan0 inet 192.168.1.1 netmask 255.255.255.0 vlan 22 vlandev em0 test2: ifconfig em0 inet 10.10.10.2 netmask 255.255.255.0 ifconfig vlan create ifconfig vlan0 inet 192.168.1.2 netmask 255.255.255.0 vlan 22 vlandev em0 I can ping the other machine using the 10.10.10.x IP address no problem, but the 192.168.1.x addresses don't work. I've tried setting the vlan id on the vSwitch to none and to 22, but in neither of the two cases does it work. [Michael K. Smith - Adhost] You will need to make sure the switchport facing your server is set to 802.1Q trunk and has VLAN 22 allowed. The IP address on em0 itself is untagged so it will work regardless of the port settings on the switch. VLAN 22 has the 4-byte header attached so the other side has to recognize the tag. Your reply inspired me to google 802.1Q and ESXi, and I found a document describing different VLAN solutions on ESXi (http://www.vmware.com/pdf/esx3_vlan_wp.pdf). In this document it says that to make guest tagging work I have to set the VLAN ID of the port group on the virtual switch to 4095. After I did this, the above configuration works. Regards, Mike Regards, Sebastiaan smime.p7s Description: S/MIME Cryptographic Signature
