Vmware Server - Bridged Networking
marcround
17-03-2011, 21:20
Thank you for your help everyone!, I have submitted a support ticket to OVH for assistance and hopefully I will get a response within the next 48 hours
Until then however I'm going to run a packet capture on both the Windows server 2003 and Ubuntu virtual machines as I have noticed that I am getting a small amount of packets in/out
Edit - 03/04/2011
After being bounced between incident support and technical advisement they have identified a problem with the router and corrected it
my VPS is now working fine now :P
Thanks for all the help!
I can confirm. Unless there's some really wonky configuration issues on the host node (eg,. defining the failover IP on both the Windows host and inside the running VM), then I consider this to be something that OVH needs to look into on their end.
marcround
17-03-2011, 20:23
Originally Posted by
Myatu
First make sure you're using the netmask of 255.255.255.255. If you are, ensure you're not defining on the host node as well. If all that checks out, inform OVH and have them check the router.
let me just restore the original configuration and if that still doesn't work I'll contact support :P
edit: the original settings are now in place and TTL is still being expired
Netmask of 255.255.255.255 is correct for failover IPs, otherwise you risk having the IP/server blocked due to too many ARP requests. The Ubuntu configuration was correct as you had posted.
Pings to your failover IP exceed their TTL and a traceroute to your failover IP shows you're in a routing loop:
Code:
traceroute to 87.98.250.9 (87.98.250.9), 30 hops max, 60 byte packets
1 192.168.255.41 (192.168.255.41) 0.929 ms 0.969 ms 1.038 ms
2 vss-3-6k.fr.eu (188.165.9.134) 1.113 ms 1.287 ms 1.438 ms
3 * * *
4 vss-3-6k.fr.eu (188.165.9.134) 1.046 ms 1.150 ms 1.138 ms
5 * * *
6 vss-3-6k.fr.eu (188.165.9.134) 0.844 ms 0.881 ms 0.835 ms
7 * vss-4-6k.fr.eu (188.165.9.151) 0.836 ms *
8 vss-3-6k.fr.eu (188.165.9.134) 1.038 ms 1.103 ms 1.004 ms
9 * * *
10 vss-3-6k.fr.eu (188.165.9.134) 0.965 ms 0.783 ms 0.946 ms
11 * * *
12 vss-3-6k.fr.eu (188.165.9.134) 0.726 ms 1.041 ms 0.780 ms
13 * * vss-4-6k.fr.eu (188.165.9.151) 1.106 ms
14 vss-3-6k.fr.eu (188.165.9.134) 1.741 ms 1.709 ms 1.767 ms
15 * * *
16 vss-3-6k.fr.eu (188.165.9.134) 1.789 ms 1.923 ms 2.009 ms
17 * * *
18 vss-3-6k.fr.eu (188.165.9.134) 1.931 ms 2.015 ms 2.033 ms
19 * * *
20 vss-3-6k.fr.eu (188.165.9.134) 1.896 ms 1.845 ms 1.844 ms
21 * * *
22 vss-3-6k.fr.eu (188.165.9.134) 1.711 ms 1.397 ms 1.453 ms
23 * * *
24 vss-3-6k.fr.eu (188.165.9.134) 1.283 ms 1.140 ms 1.288 ms
25 * vss-4-6k.fr.eu (188.165.9.151) 2.554 ms *
26 vss-3-6k.fr.eu (188.165.9.134) 4.441 ms 4.448 ms 4.439 ms
27 * * *
28 vss-3-6k.fr.eu (188.165.9.134) 4.370 ms 4.359 ms 4.359 ms
29 * * *
30 vss-3-6k.fr.eu (188.165.9.134) 4.298 ms 4.288 ms 1.396 ms
First make sure you're using the netmask of 255.255.255.255. If you are, ensure you're not defining on the host node as well. If all that checks out, inform OVH and have them check the router.
marcround
17-03-2011, 19:29
lol ovh really need to update their guide then xD
I'll update the network configuration and let you know how it turns out
thanks for the help
PhonicUK
17-03-2011, 18:17
Also your default gateway should be 87.98.250.254
Edit:
Also there was a typo in my post. The secondary DNS is 8.8.4.4 not 8.8.8.4
Edit: The subnet should indeed be 255.255.255.255 despite my earlier posting.
marcround
16-03-2011, 10:03
hmm still no luck in windows or ubuntu
these are my ubuntu settings (I'm posting screenshots incase I missed something because I've never used linux before):
interfaces:
resov.conf:
my failover ip is 87.98.250.9 and host is 188.165.193.84
____
edit: I noticed that in my host machine windows firewall is dropping DHCP discovery packets from OVH containing the virtual machine name that I configured in the manager inside the packet. I tried temporarily disabling the firewall to allow the traffic through with no luck.
PhonicUK
15-03-2011, 22:04
I've set up a few linux VMs in VMWare like this:
- I used 255.255.255.255 as the subnet
- Gateway as x.x.x.254
- Nameserver set to 8.8.8.8 primary and 8.8.4.4 secondary.
Edit: The subnet should indeed be 255.255.255.255 despite my earlier posting.
marcround
14-03-2011, 10:55
Hello, I am currently running VMware-server-v2.0.2-203138 in windows server 2008 rc2 and I'm attempting to setup a windows server 2008 vm with bridged networking for learning purposes
I have followed the virtual mac and bridge client guides to configure the network settings in vmware/guest os but my vm is unable to connect to the internet and the network status reads as local only, are there any critical steps that I have missed?
Additional information:
Steps taken:
1 - Installed a Windows Server 2008 Guest OS
2 - Enabled a failover IP
3 - Configured virtual mac using failover ip and Guest OS machine name in vmware mode to get mac address
4 - Configured bridged network adapter for the 2008 VM using the given mac address
5 - Configured IP settings as stated in the guide (failover as ip, subnet mask as 255.255.255.255, gateway as host machines IP with the last octet as 254, and nameserver set to 213.186.33.99)
This didn't work so I created a windows 2003 server and followed the instructions for it as stated in the guide (same as 2008 steps but setting subnet to 255.255.0.0, changing it to 255.255.255.255 in the registry and restarting the adapter), I had no success with either.
I am also about to attempt bridging with an Ubuntu VM