Recent content by ichi

And yet you force that rule to be active all the time, even if no VPN is being utilised... and even if no VPN routing rule is being utilised... Because saving any OVPN config just immediately hardcodes and activates the killswitch from the next boot... Regardless if you have activated a VPN...

Are you using secure DNS?

They don't want to understand. Their ego's wont allow them. In their mind, they are the only user that matters. And everyone else has to put up with their bad designs. I'm starting to think they are intentionally inserting vulnerabilities into their code... And that this person is a State Actor...

But whatever. Goodluck.

You actually wrote leaks into your rewrite that weren't there before. Not sure if you realise... It's actually way worse for leaks after you touched it. You tried to fix one problem, and you created 2 more that are way worse.

Removing this and applying it to everything, auto-start or not, was a huge error.... CHANGED: At boot time, OpenVPN killswitch will only be applied for clients set to auto-start with WAN.

Or did you think my spending time telling you about it, was for MY benefit...... ?

We've already fixed it. 😂 Not that hard to maintain one model... You're ego is obviously bigger than then pride you have in the quality of your work. The change you were trying to implement, which was when it reboots, that it would act the same as wireguard and block connections until the VPN...

Rubbish. No changes to the killswitch or the VPN occurred in that version. It was entirely on your version. Don't BS me. I've checked the code.

That's completely incorrect. start_vpnclient2 is exactly the same as toggling the VPN on or off in the WebUI. No settings are being changed. But that's all completely irrelevant.... You're just looking for excuses not to be wrong. Your killswitch issues happen BEFORE I decide I want to use the...

You're still not listening.... I will explain it again.... When I go into the WebUI and enable the killswitch.... It doesn't work.... Deactivating the setting in any VPN setting works. But not the other way around. It requires a reboot of the router to work.... If I have any VPN setting that...

Then you're still not understanding the problem 😆 You can't just go in and activate the killswitch. It doesn't work. Until you reboot the router. It's only activated on boot. Activating the killswitch after boot does nothing. You can only deactivate the killswitch after boot. Why would you...

Not if he doesn't rewrite things that aren't broken that are working perfectly fine. But I can imagine that doing things for no reason and ending up with a huge mess, would make things complicated.

Sorry but I've been gaslit over and over since the beta. Constantly being told that "It's supposed to block your internet, that's what killswitch does".. 🤦‍♂️ I don't get why its gone from: Activate VPN (killswitch activates automatically) Deactivate VPN (killswitch deactivates automatically)...

Have you tried it bro? I'm getting real sick of people gaslighting me like I'm some noob. I'm 25 year Network Engineer and I own a Software Development company. I know what a frigging killswitch it supposed to do!! And it's not supposed to block your internet when you have all your VPN's...