-1

I've a Windows Server 2008 R2 with 8 public IPs assigned (fixed), recently i've installed VirtualBox and create a VirtualMachine with OpenBSD.

I would like to give one IP to the VM, but every try that i tested this fails.

In Windows there's a public IP 200.100.100.208 (for this example), that IP i've configured in OpenBSD VM at the /etc/hostname.em0 file, which content is:

inet xxx.xxx.xxx.208 255.255.255.255

/etc/mygate file is:

zzz.zzz.zzz.65          Same gateway ip than windows

i put the same mask that is assigned in windows for each IPs.

At windows i've created rules for firewall to VirtualBox.exe application.

In VirtualBox VM's setting: Network the current configuration:

Attached to: Bridged Adapter
Name: Intel(R) 82574L Gigabit Networkd Connection
Advanced:
    Promiscuous Mode: Deny
    Cable connected is checked.

i can't figure out what is missing... if is needed some information, ask please, i'll give such information.

thanks!!

New information:

i've removed IP from windows config

Windows Config:

IPv4 Address:     xxx.xxx.xxx.209
IPv4 Subnet Mask: 255.255.255.255

IPv4 Address:     xxx.xxx.xxx.210
IPv4 Subnet Mask: 255.255.255.255

IPv4 Address:     xxx.xxx.xxx.211
IPv4 Subnet Mask: 255.255.255.255

IPv4 Address:     xxx.xxx.xxx.212
IPv4 Subnet Mask: 255.255.255.255

IPv4 Address:     xxx.xxx.xxx.213
IPv4 Subnet Mask: 255.255.255.255

IPv4 Address:     xxx.xxx.xxx.214
IPv4 Subnet Mask: 255.255.255.255

IPv4 Address:     xxx.xxx.xxx.215
IPv4 Subnet Mask: 255.255.255.255

IPv4 Address:     yyy.yyy.yyy.83
IPv4 Subnet Mask: 255.255.255.224

IPv4 Default Gateway  zzz.zzz.zzz.65

IPv4 DNS Servers   hhh.hhh.hhh.202
                   hhh.hhh.hhh.200

The IP xxx.xxx.xxx.208 i've removed from windows.

If i set the ip xxx.xxx.xxx.208 in windows, when i start openbsd, an error message apear: duplicate IP address xxx.xxx.xxx.208

Gabriel
  • 123
  • 1
  • 10

1 Answers1

2

Based on the info above, it appears that your subnet mask is incorrect. Based off of 8 usable IPs, your subnet mask should probably be 255.255.255.240. Try that. You'll want to change it on the Windows host as well.

Jim G.
  • 2,657
  • 1
  • 19
  • 19
  • I concur, the netmask 255.255.255.255 is probably wrong, with that mask, the host will only be able to communicate with itself. Use the same netmask that you're using for an already-working IP on the windows server. – WhyNotHugo Jul 18 '13 at 00:14
  • The problem was the netmask, I took one of the server's secondary IPs (one in the same subnet as the VM: xxx.xxx.xxx.209) and changed the netmask to 255.255.255.248, then on VM put that IP as gateway. I also had to enable the "Rounting and Remote Access" service on the windows server. – Gabriel Jul 18 '13 at 01:08