Problem with getting IP in VMWare machines, bridged to tap

andmed2

There is a problem with getting IP from OpenVPN in VMWare machines, bridged to tap adapter on client host.

The virtual machines are bridged to tap adapter on the client Windows host. This virtual connection works well for them if IP is manually configured, but they do not get IP via DHCP. It looks like the logic on OpenVPN's DHCP is to not allow more than one IP lease for one client, which client is a windows host. Windows host gets IP via DHCP from OpenVPN with no problem. Why not the bridged virtual machines? (I would prefer not to set up a separate DHCP server for this on the server)

I looked through the OpenVPN documentation, but could not find settings to overrule this behavior.

The config is quite straightforward:

proto udp #default
dev tap #default

#management 127.0.0.1 1194

# Tunnel IP-number plan:
# network: 10.4.0.0/24 all tunnel-endpoints (TEPs)
# IP: 10.4.0.1 server
# IP: 10.4.0.2 server p2p address (not-used)
# IP: 10.4.0.5 client-1 p2p address (not-used)
# IP: 10.4.0.6 client-1
# IP: 10.4.0.9 client-2 p2p address (not-used)
# IP: 10.4.0.10 client-2
# IP: 10.4.0.13 client-3 p2p address (not-used)
# IP: 10.4.0.14 client-3
# etc... This setup allows (2^(32-24)/4)-1=63 clients

server 10.9.8.0 255.255.255.0 # the server Tunnel-IP will be .1

# The 'server' command also established a pool of Tunnel-IPs for the clients (like DHCP)

#route 10.4.0.0 255.255.255.0 # this command is implicit with 'server' command

#cd /etc/openvpn/projectname/
#log /tmp/openvpn-projectname.log

user nobody
group nobody

dh /etc/ssl/certs/dh1024.pem
ca /etc/ssl/certs/ca_openvpn.crt
cert /etc/ssl/certs/openvpn.crt
key /etc/ssl/private/openvpn.key
verb 3
keepalive 55 155
persist-tun
persist-key
persist-local-ip
comp-lzo
ping-timer-rem
duplicate-cn # needed if all clients use same client.crt/key

# Uncomment following line if you want to allow client-to-client traffic:
# (dont use this option if you want to filter the client-to-client packets via iptables)
#client-to-client
push "dhcp-option DISABLE-NBT"
#push "dhcp-option DNS 10.9.8.1"
#push "route 10.4.0.0 255.255.255.0" # this is done automatically with client-to-client command (else do specify)

# end of "server-tls.conf"

[deleted]

debbie10t wroteAre you trying to use a bridge on your client machine to link eth0 to tap ?

No, I just use VMWare "bridged network connection". It works this way -- when bridged to, say, wi-fi adapter, it gets IP and behaves as if really on the net (bridged).

Not with OpenVPN tap adapter, though.