Not assigned new IP by DHCP server

Post your questions about SoftEther VPN software here. Please answer questions if you can afford.
Post Reply
ITinstaller
Posts: 5
Joined: Thu Jun 04, 2015 2:07 pm

Not assigned new IP by DHCP server

Post by ITinstaller » Fri Jun 05, 2015 4:19 pm

I have set up the VPN server software on my debian linu VM that is on our company server.
I have allowed access through the firewall for the ports it needs.
The DHCP server is set up proper (100% this is not the problem).

When I try to connect to the server it ends up connecting but not assigning me a new IP, which causes me to end up with a 169 IP.

I can't seem to figure out why it is unable to give me a new IP despite the fact the DHCP server is working.

Any potential thoughts on what could cause this?

exciter0
Posts: 21
Joined: Wed Jun 03, 2015 9:03 pm

Re: Not assigned new IP by DHCP server

Post by exciter0 » Fri Jun 05, 2015 9:23 pm

You already have a post with the same question here:
http://www.vpnusers.com/viewtopic.php?f=7&t=4734

You're right, it's not the DHCP server...it's you.
Can you describe your virtual bridge is connected?
You mentioned the VPN server is running as a VM, what hypervisor?



ITinstaller wrote:
> I have set up the VPN server software on my debian linu VM that is on our
> company server.
> I have allowed access through the firewall for the ports it needs.
> The DHCP server is set up proper (100% this is not the problem).
>
> When I try to connect to the server it ends up connecting but not assigning
> me a new IP, which causes me to end up with a 169 IP.
>
> I can't seem to figure out why it is unable to give me a new IP despite the
> fact the DHCP server is working.
>
> Any potential thoughts on what could cause this?

ITinstaller
Posts: 5
Joined: Thu Jun 04, 2015 2:07 pm

Re: Not assigned new IP by DHCP server

Post by ITinstaller » Mon Jun 08, 2015 1:34 pm

The VPN server is running on a debian linux VM, the hypervisor is ESXi 5.5

The virtual bridge is a layer 2 bridge to eth0.

promiscuous is enabled.

Not trying to do anything fancy, just basic VPN server on the local VM and the VPN client on laptops so they can connect and use the LAN.

Should also mention I am listening on 2 ports, 1194 and 5555.




exciter0 wrote:
> You already have a post with the same question here:
> http://www.vpnusers.com/viewtopic.php?f=7&t=4734
>
> You're right, it's not the DHCP server...it's you.
> Can you describe your virtual bridge is connected?
> You mentioned the VPN server is running as a VM, what hypervisor?

exciter0
Posts: 21
Joined: Wed Jun 03, 2015 9:03 pm

Re: Not assigned new IP by DHCP server

Post by exciter0 » Mon Jun 08, 2015 6:00 pm

In your other thread, you've mentioned that the vpn client is assigned an IP (not 169.x.x.x), so obviously DHCP is working.

You've also mentioned promiscuous mode is enabled, I assume you mean at the ESXi's port group right?

Then it sounds like a routing issue, perhaps your vpn client is not receiving or receiving the wrong default gateway.

After you've established your vpn connection, can you print out the routing table and ipconfig/ifconfig screen?

Also, try to set a static IP/Netmask/gateway on the vpn client's interface to see if that gives you connectivity.



ITinstaller wrote:
> The VPN server is running on a debian linux VM, the hypervisor is ESXi 5.5
>
> The virtual bridge is a layer 2 bridge to eth0.
>
> promiscuous is enabled.
>
> Not trying to do anything fancy, just basic VPN server on the local VM and the VPN
> client on laptops so they can connect and use the LAN.
>
> Should also mention I am listening on 2 ports, 1194 and 5555.
>
>
>
>
> exciter0 wrote:
> > You already have a post with the same question here:
> > http://www.vpnusers.com/viewtopic.php?f=7&t=4734
> >
> > You're right, it's not the DHCP server...it's you.
> > Can you describe your virtual bridge is connected?
> > You mentioned the VPN server is running as a VM, what hypervisor?

ITinstaller
Posts: 5
Joined: Thu Jun 04, 2015 2:07 pm

Re: Not assigned new IP by DHCP server

Post by ITinstaller » Mon Jun 08, 2015 6:19 pm

I said the opposite, it does NOT assign an IP and therefore I get a 169

"which causes me to end up with a 169 IP."

I made a new thread because this is NOT the other problem, which is why I am not posting on that one.

Will try that other stuff now though.

Also thank you very much for your help

thisjun
Posts: 2454
Joined: Mon Feb 24, 2014 11:03 am

Re: Not assigned new IP by DHCP server

Post by thisjun » Wed Jun 17, 2015 6:07 am

Did you set up the DHCP server on VM which is installed SoftEther VPN server?
If so, DHCP server doesn't work for virtual hub because localbridge can't communicate with the host itself.

gparedes
Posts: 2
Joined: Thu Jan 10, 2019 2:56 pm

Re: Not assigned new IP by DHCP server

Post by gparedes » Thu Jan 10, 2019 7:11 pm

Hello, I assume that there is already a solution to this problem, however, using Ubuntu 16 server (on KVM) and softether found the same problem, although using SecureNAT I managed to connect, this solution I do not like because the VPN clients are behind the nat. So I found this solution:

1. On the server running softether add a new network interface, and confgure to boot but without IP (as recommended by the manual softether)
2. Connect this network card to the same virtual switch where the dhcp and the vpn machine are.
3. Set up a local bridge between this new non-IP network card and the virtual hub where VPN users connect (in to SE Manager).

After this all users connect and take IP address from DHCP server successfully, clients use SSTP, L2TP (windows, mac, adndroid, iOS and vpn client from sothether for windows.
I hope this setup can help future users.

Post Reply