client side VPN driver issue? - SOLVED! Option 121 causes Win10 DHCP client to fail
Posted: Fri Jun 08, 2018 2:24 am
Hi all,
I'm pretty new to softether, but not new to networking. However, I've been unable to get things working on my network.
As far as I can tell, everything on the softether server (CentOS 7 64 bit on a VM on VMWare 6.5) is set up correctly, but yet, my vpn clients don't get IP address from the DHCP server on the internal network (ISC). The client always ends up with a 169.254.x.x (autoconf) IP address. Note that I have enabled Promisc, forged transmits and MAC address changes on the port group the server is attached to.
I can see in packet captures as well as dhcp logs that the dhcp server sees the request coming in with the MAC address of the VPN adapter on my client. the dhcp server responds with a DHCPOFFER... but the IP never gets to the client (which is windows 10 btw).
Here's an example from the dhcp server log:
Jun 8 02:10:43 core1 dhcpd: DHCPDISCOVER from 5e:d2:9c:df:61:f1 (laptop) via ens192
Jun 8 02:10:44 core1 dhcpd: DHCPOFFER on 192.168.0.145 to 5e:d2:9c:df:61:f1 (laptop) via ens192
Jun 8 02:10:44 core1 dhcpd: DHCPREQUEST for 192.168.0.145 (192.168.0.5) from 5e:d2:9c:df:61:f1 (laptop) via ens192
Jun 8 02:10:44 core1 dhcpd: DHCPACK on 192.168.0.145 to 5e:d2:9c:df:61:f1 (laptop) via ens192
In fact, the softether server even associates the IP (in this case, 192.168.0.145) with my client session, but still no IP on the laptop.
If it matters, the softether host is dual homed. like this:
cable modem router -> ens224 (10.100.100.21)
router -> ens192 (192.168.0.11)
connections are forwarded from the cable modem router to the 10.100.100.21 address (port forwarding). Then, the SE Bridge for the Hub is bridged with ens192 on 192.168.0.0/24 network. I'm expecting that clients would get a 192.168.0.x address via the DHCP server that services all the other devices on the network...
One other thing I've observed in trying to get this all to work is that the VPN driver on the client doesn't seem to get along with windows. For example, if I do "ipconfig /renew VPN*" on the Windows 10 laptop, I get this error:
C:\Users\jbrooks>ipconfig /renew VPN*
Windows IP Configuration
An error occurred while renewing interface VPN - VPN Client : The data is invalid.
Anyway, I'm getting to the end of my rope. I thought this would be easy. Any help you can offer would be greatly appreciated!
Cheers, and thanks for such an awesome project!
Joel
I'm pretty new to softether, but not new to networking. However, I've been unable to get things working on my network.
As far as I can tell, everything on the softether server (CentOS 7 64 bit on a VM on VMWare 6.5) is set up correctly, but yet, my vpn clients don't get IP address from the DHCP server on the internal network (ISC). The client always ends up with a 169.254.x.x (autoconf) IP address. Note that I have enabled Promisc, forged transmits and MAC address changes on the port group the server is attached to.
I can see in packet captures as well as dhcp logs that the dhcp server sees the request coming in with the MAC address of the VPN adapter on my client. the dhcp server responds with a DHCPOFFER... but the IP never gets to the client (which is windows 10 btw).
Here's an example from the dhcp server log:
Jun 8 02:10:43 core1 dhcpd: DHCPDISCOVER from 5e:d2:9c:df:61:f1 (laptop) via ens192
Jun 8 02:10:44 core1 dhcpd: DHCPOFFER on 192.168.0.145 to 5e:d2:9c:df:61:f1 (laptop) via ens192
Jun 8 02:10:44 core1 dhcpd: DHCPREQUEST for 192.168.0.145 (192.168.0.5) from 5e:d2:9c:df:61:f1 (laptop) via ens192
Jun 8 02:10:44 core1 dhcpd: DHCPACK on 192.168.0.145 to 5e:d2:9c:df:61:f1 (laptop) via ens192
In fact, the softether server even associates the IP (in this case, 192.168.0.145) with my client session, but still no IP on the laptop.
If it matters, the softether host is dual homed. like this:
cable modem router -> ens224 (10.100.100.21)
router -> ens192 (192.168.0.11)
connections are forwarded from the cable modem router to the 10.100.100.21 address (port forwarding). Then, the SE Bridge for the Hub is bridged with ens192 on 192.168.0.0/24 network. I'm expecting that clients would get a 192.168.0.x address via the DHCP server that services all the other devices on the network...
One other thing I've observed in trying to get this all to work is that the VPN driver on the client doesn't seem to get along with windows. For example, if I do "ipconfig /renew VPN*" on the Windows 10 laptop, I get this error:
C:\Users\jbrooks>ipconfig /renew VPN*
Windows IP Configuration
An error occurred while renewing interface VPN - VPN Client : The data is invalid.
Anyway, I'm getting to the end of my rope. I thought this would be easy. Any help you can offer would be greatly appreciated!
Cheers, and thanks for such an awesome project!
Joel