Member Avatar for humbll

Heres my situation:
I have a securetunnel.com select package which gives me a "Secure Tunnel Private Network" (STPN)which encrypts my internet traffic keeping it from being viewed by my nosey isp.

This STPN creates a new LAN connection in my network settings under control panel in Windows XP.

It works great but has one serious flaw: When the secure connection is lost, as has happened to me some 4-5 times now, the little icon for the STPN still says "connected and secure" when the mouse is hovered above it. The only way i know i am browsing unsecure is to navigate to one of the securetunnel.com webpages where it gives me a warning at the top of the page in red letters that my ip address is not secure. When the STPN software is connected it gives me the message that my ip is secure in green letters. The STPN software gives me NO WARNING whatsoever that I am now browsing unsecure. I would ideally like there to be an instant popup message alerting me that my traffic is now unsecure, but i get no response to my complaints from their support section.

Here is what I am here to ask: Is there some way, perhaps through Comodo firewall that I can route ALL traffic through the secure LAN connection, and allow only the secure LAN connection to access the unsecure LAN connection? So that if the secure connection is broken for any reason, the traffic will not just revert to using the unsecure connection.

The STPN software creates a secure LAN connection, then routes all traffic through that and out the unsecure connection through my ISP to its servers then on to its final destination. I have tried disabling the unsecure connection after the STPN software has created the secure LAN but that just kills the secure connection as well.

Thanks in advance for reading this, and I will welcome any suggestions. Have a great day!

Edited by humbll because: n/a
  • 2 Contributors
  • 1 Reply
  • 245 Views
  • 12 Hours Discussion Span
  • Latest Post Latest Post by caperjack

Dani AI

Generated

A concise plan that fixes the leak instead of depending on the STPN client’s icon: the tunnel is a virtual adapter that still needs the real NIC to reach the VPN server, so disabling the physical interface will break the tunnel. The reliable ways to get a “fail‑closed” setup are (A) host firewall rules that allow only the VPN client to talk to the VPN server and block everything else, (B) bind only those apps that must use the tunnel to the VPN adapter, or (C) enforce the rule on the router so the whole LAN cannot pass traffic when the tunnel is down. (techtarget.com)

Host solution (Comodo): find the STPN server IP(s) with TCPView or netstat, then create a Comodo Network Zone for those IPs and build these rules in order: 1) allow outbound to the VPN server addresses (and allow the STPN client process), 2) allow local LAN traffic, 3) an explicit “block all outbound” fallback/global rule. Put the log action on the block rule so you can see leaks. Comodo’s Network Zones / Global Rules support exactly this pattern. Test by stopping the tunnel and verifying only the VPN-server IPs remain reachable. (learn.microsoft.com)

App-level binding (partial fix): use ForceBindIP to launch a browser or other app bound to the VPN adapter IP:

"C:\Program Files\ForceBindIP\ForceBindIP.exe" 10.8.0.5 "C:\Program Files\Mozilla Firefox\firefox.exe"

ForceBindIP works for many programs but has limits (DNS requests and some modern browsers may still leak; injection can trigger AV). Use it for high-value apps if you can’t change the host firewall. (r1ch.net)

Router-level kill‑switch (recommended for full safety): run the STPN/VPN on the gateway (pfSense, OpenWrt, Tomato/AsusWRT‑Merlin) and add a firewall rule that drops WAN forwarding unless the VPN interface is up. This prevents leaks from any client and removes race conditions at boot. After any change, verify with an IP/DNS leak test (dnsleaktest / whatismyipaddress) and monitor firewall logs. Note: VPN kill‑switches and clients are convenient but can fail; router enforcement is the most robust option. (slideshare.net)

Summary: for a Windows XP desktop the Comodo/global host firewall approach is usually the quickest fix; ForceBindIP helps individual apps; moving enforcement to a router gives the strongest protection.

Member Avatar for caperjack

hi, i dont have fix ,but a suggestion ,securetunnel.com has a support link and contact us link on it ,good luck

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.