DHCP Wifi Guest Account

Dec 05, 2013 2 Replies

I am on a guest wifi account. I have been trying to use several VPNs using openvpn with little luck.



The DHCP server on my windows box is running and broadcasting packets to 255.255.255.xx get an IP, but nothing is returned, and I get destination unreachable for ips of all of the vpn servers.



Is this a problem with conflict between my guest account IP and the one that the VPN is supposed to assign for the tap0901.sys adapter (software)? Is ISP blocking my VPN attempts? There were some posts indicating this wifi host does not like VPN traffic.



I have been able to connect but very rarely and when I do I am given a 10.x.xx.xxx IP as I recall.



Anyone here a DHCP/networking expert. Below is an edited excerpt from my firewall log. As you can see there is no reply to the DHCP packets.


2,[06/Nov/2013 10:41:01] Rule 'freevpn': Permit: Out TCP, localhost:1376->localhost [127.0.0.1:13175], Owner: C:\PROGRAM FILES\freevpn TUNNEL\freevpnTUNNEL.EXE
2,[06/Nov/2013 10:41:02] Rule 'freevpn': Permit: Out TCP, localhost:1378->localhost [127.0.0.1:13175], Owner: C:\PROGRAM FILES\freevpn TUNNEL\freevpnTUNNEL.EXE
2,[06/Nov/2013 10:41:04] Rule 'freevpn': Permit: Out TCP, localhost:1380->localhost [127.0.0.1:13175], Owner: C:\PROGRAM FILES\freevpn TUNNEL\freevpnTUNNEL.EXE
2,[06/Nov/2013 10:41:05] Rule 'freevpn': Permit: Out TCP, localhost:1382->localhost [127.0.0.1:13175], Owner: C:\PROGRAM FILES\freevpn TUNNEL\freevpnTUNNEL.EXE
2,[06/Nov/2013 10:41:06] Rule 'freevpn': Permit: Out TCP, localhost:1384->localhost [127.0.0.1:13175], Owner: C:\PROGRAM FILES\freevpn TUNNEL\freevpnTUNNEL.EXE
2,[06/Nov/2013 10:41:09] Rule 'OPENVPN.EXE': Permit: Out TCP, localhost:1387->184.75.208.146:443, Owner: C:\PROGRAM FILES\freevpn TUNNEL\OPENVPN\BIN\OPENVPN.EXE
2,[06/Nov/2013 10:41:09] Rule 'ICMP DEST UNREACH': Permit: In ICMP [3] Destin Unreach, 38.122.69.122->localhost, Owner: Tcpip Kernel Driver
2,[06/Nov/2013 10:41:17] Rule 'ICMP DEST UNREACH': Permit: In ICMP [3] Destin Unreach, 38.122.69.122->localhost, Owner: Tcpip Kernel Driver
2,[06/Nov/2013 10:41:27] Rule 'DHCP ': Permit: Out UDP, localhost:68->255.255.255.255:67, Owner: C:\WINDOWS\SYSTEM32\SVCHOST.EXE
2,[06/Nov/2013 10:41:30] Rule 'DHCP ': Permit: Out UDP, localhost:68->255.255.255.255:67, Owner: C:\WINDOWS\SYSTEM32\SVCHOST.EXE
2,[06/Nov/2013 10:41:30] Rule 'ICMP DEST UNREACH': Permit: In ICMP [3] Destin Unreach, 38.122.69.122->localhost, Owner: Tcpip Kernel Driver
2,[06/Nov/2013 10:41:33] Rule 'ICMP DEST UNREACH': Permit: In ICMP [3] Destin Unreach, 38.122.69.122->localhost, Owner: Tcpip Kernel Driver
2,[06/Nov/2013 10:41:38] Rule 'DHCP ': Permit: Out UDP, localhost:68->255.255.255.255:67, Owner: C:\WINDOWS\SYSTEM32\SVCHOST.EXE
2,[06/Nov/2013 10:41:39] Rule 'ICMP DEST UNREACH': Permit: In ICMP [3] Destin Unreach, 38.122.69.122->localhost, Owner: Tcpip Kernel Driver
2,[06/Nov/2013 10:41:54] Rule 'DHCP ': Permit: Out UDP, localhost:68->255.255.255.255:67, Owner: C:\WINDOWS\SYSTEM32\SVCHOST.EXE
2,[06/Nov/2013 09:52:32] Rule 'DHCP ': Permit: Out UDP, localhost:68->255.255.255.255:67, Owner: C:\WINDOWS\SYSTEM32\SVCHOST.EXE
2,[06/Nov/2013 09:52:36] Rule 'DHCP ': Permit: Out UDP, localhost:68->255.255.255.255:67, Owner: C:\WINDOWS\SYSTEM32\SVCHOST.EXE
2,[06/Nov/2013 09:52:44] Rule 'DHCP ': Permit: Out UDP, localhost:68->255.255.255.255:67, Owner: C:\WINDOWS\SYSTEM32\SVCHOST.EXE
2,[06/Nov/2013 09:52:59] Rule 'DHCP ': Permit: Out UDP, localhost:68->255.255.255.255:67, Owner: C:\WINDOWS\SYSTEM32\SVCHOST.EXE
2,[06/Nov/2013 09:53:33] Rule 'DHCP ': Permit: Out UDP, localhost:68->255.255.255.255:67, Owner: C:\WINDOWS\SYSTEM32\SVCHOST.EXE
2,[06/Nov/2013 09:53:37] Rule 'DHCP ': Permit: Out UDP, localhost:68->255.255.255.255:67, Owner: C:\WINDOWS\SYSTEM32\SVCHOST.EXE
2,[06/Nov/2013 09:53:46] Rule 'DHCP ': Permit: Out UDP, localhost:68->255.255.255.255:67, Owner: C:\WINDOWS\SYSTEM32\SVCHOST.EXE
2,[06/Nov/2013 09:54:02] Rule 'DHCP ': Permit: Out UDP, localhost:68->255.255.255.255:67, Owner: C:\WINDOWS\SYSTEM32\SVCHOST.EXE

- You may not have a default route out to "the Internet"

- The port(s) or protocols may be blocked to stop you using VPN

Then it's likely that you also are going to struggle to use a VPN. Something like OpenVPN over tcp/443 might get you through.

Chris

I don't know the details in this specific case, but I'd bet it involves deep packet inspection.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required