Connected clients not receiving DHCP address
-
I see two corrections that need to be made:
1. change your local network to 10.32.0.0/22
2. you have bridge dhcp checked, so you should not need anything in the "Server DHCP Bridge Start", "Server DHCP Bridge End" fields… I would clear those. If you want to keep what's in those fields... end your range at .99, so it doesn't overlap.
Also, maybe someone who uses bridged solutions more can chime in, but I'm pretty sure you want to check the Enable NETBIOS over TCP/IP box. Only because I'm not sure if setting up the bridge enables it automatically. If you don't want or need netbios traffic to traverse the tunnel… switch to routed.
It doesn't really matter, but is there a reason you're using a /22 mask on your LAN? Do you really need 1000+ IP's on your home network?
-
It's a bit complicated to explain - suffice to say, it has to do with virtualization experimentation as well as CCNA-playground :D
Didn't think of the 10.32.0.0 solution; duhhhhh
Hmm… still does not work; I took away the DHCP address range and it is now not getting an address...
-
Looks like I modified my last post as opposed to add an update -
I changed the network to 10.32.0.0 but it still does not do the trick. I can connect, but no DHCP…
Any suggestions?
Can someone perhaps post their settings and I can compare and contrast?
Thanks!
-
I just registered to say that I have the exact same problem. Clients don't get IP from DHCP. If I set the start and end range on OpenVPN, then the IP gets assigned, but it's apparently not from the LAN DHCP server, as I cannot find the lease for the client.
Subscribing to the topic, maybe someone might help us :)
-
Did you actually go to Interfaces > (assign) and assign the OpenVPN interface, then create a bridge interface between the VPN and your LAN interface? Setting the "bridge interface" in the OpenVPN config doesn't do any of that for you - it's still required, and from the sound of it, that may be what's missing since it seems that your traffic isn't making it across the gap between the VPN interface and the LAN interface.
-
Yes, manually assigned the OpenVPN interface, enabled it, and made a bridge between OpenVPN interface and LAN manually. Still no go :(
-
Yes, manually assigned the OpenVPN interface, enabled it, and made a bridge between OpenVPN interface and LAN manually. Still no go :(
Yup - same exact experience on my end.
-
Bump! Still an issue…
-
Bump! Anyone?????
-
My setup is similar to yours (TAP, etc) except I needed to rely on pfsense's DHCP server running on the LAN to provide the ip whether the box was using openvpn to connect remotely or was plugged in locally. As I needed all the traffic other than Openvpn related to pass through the tunnel (no security holes on the client going to the general lan) this was okay.
In either case the issue I had (and finally solved) was that the arp table on the client side was geting 00 00 00 00 00 (invalid) mac address for the gateway. I had to manually put an 'up' script in the client to forcibly add the lan's MAC address to the client's arp table – and then it all worked. Anyhow maybe you can get some hints from a known working setup TAP described here:
http://forum.pfsense.org/index.php/topic,54701.msg292497.html#msg292497
With openvpn server and client configs listed here:
http://community.openvpn.net/openvpn/ticket/233
