After numerous articles on the web on using VLANS with VMWare, there's a general consensis that it works for some and not for others. I fell into the "not" category. After a couple days of searching, there's two issues apparent…
1. anything over 8 characters in the network identifier will give you grief…ie eth1.1001 will fail. v1.1001 is fine. In the case of ubuntu, editing the /etc/udev/rules.d/70-persistent-net.rules and changing the label for your network to something shorter will solve this problem.
2. setting the bridge up fails for some reason on some installations with a "can't bridge with eth1.1, bad header length 18"
This turned out to be the real challenge. Fortunately, the thread at http://communities.vmware.com/thread/148334 put me onto the right track…the user mblasis seems to have found a hack. To make the hack work for me…here's the steps (modified from his slightly)..Yes, probably breaking a copyright by providing the file but it's here for my own purposes. Use at your own risk.
cd /tmp
wget http://www.davebour.com/misc/vmware-any-any-update-116.gz
tar -zxf vmware-any-any-update-116.gz
mv /usr/lib/vmware/modules/source/vmnet.tar /usr/lib/vmware/modules/source/vmnet.tar.old
cp /tmp/vmware-any-any-update116/vmnet.tar /usr/lib/vmware/modules/source/vmnet.tar
/usr/bin/vmware-config.pl –compile
*** NOTE THE LAST STEP – you need to ensure it recompiles the vmnet module otherwise, you're no further ahead.
It is using the server 1.0 vmnet files, but so far everything is working as it should.
Recent Comments