> -----Original Message----- > From: Mathias Sundman [mailto:math...@openvpn.se]
... >> When pushing an IP to an OpenVPN client and using the DHCP feature in >> the TAP-Win32 driver to have it assigned to the windows client, I >> believe OpenVPN or the TAP-Win32 driver is blocking the DHCP requests >> from traversing the VPN tunnel. This is the behavior I'd expect as >> well. >> >> Now, while testing the PocketPC port, I just realized that I recieved >> two IP addresses! One from the TAP-Win32 driver, pushed from the >> OpenVPN server, the correct one, but also one from my real DHCP >> server on the remote network. We're using TAP and bridging... So >> obviously the PocketPC >> port does not block these packets, even though the build-in >> DHCP server in >> the TAP driver is replying to the DHCP requests. ... > > What device are you using? > > Qtek 2020i with Windows Mobile PocketPC 2003 SE. > > > Also, how are you determining that there are two addresses > on the TAP > > device? > > Viewing the "Net" tab on the TAP device. > > I just realized we're not using the latest version of your > port. Have you > done any changes in the code that could/should affect this in > the latest > relases? We'll update anyway and let you know if it makes any > difference. ... It would have to be a really old one that you are using for it to potentially matter; the TAP driver was the first thing that I worked on, and the last significant fix (which was indeed in the DHCP area) was done in early May. It's entirely possible that I broke this as I did have to make modifications throughout to accommodate PocketPC's driver model.
smime.p7s
Description: S/MIME cryptographic signature
