Option for network lock to percist after exiting Eddie.

[Waterwater10 2]

I believe there was a glitch in a previous version of Eddie for Windows where the network lock would persist after Eddie had been closed.

 

I thought this was a feature and a handy one at that. It meant that even when booting my computer, there would be no outgoing connections, it even disabled the network on other user accounts. It also has the advantage of, if Eddie crashes, the network lock would persist.

 

I'd like to see an option in the settings that allows people to enable essentially permanent network lock.

[inradius 6]

my money is on - it's a windows glitch. What you're asking is, to let eddie manage net conn even when it's not running? Hmm does that make sense at all? How about instead of that just apply firewall rules. 

[corrado 100]

Just autostart Eddie with Windows. If Eddie crashes, network lock, i.e. firewall rules should persist as network lock is only deactivated if eddie exits cleanly - it can't do that on an unexpected crash as the shutdown routine including deactivating network lock cannot be executed in such a case as the process has already died. If you want a Eddie-independent solution you would have to configure appropriate firewall rules yourself as inradius has suggested.

[Waterwater10 2]

my money is on - it's a windows glitch. What you're asking is, to let eddie manage net conn even when it's not running? Hmm does that make sense at all? How about instead of that just apply firewall rules. 

Yep, as I said in my post, it was a glitch. A handy glitch though. Yes, I am asking for Eddie to manage connections even when it isn't on, but if you'd read my post, as an option that can be enabled and disabled in settings. Off by default, but if you want it on, you can.  Yes, it does make sense. I could do firewall rules, but it would be nice if it was integrated so I didn't have to do it on every computer.

[corrado 100]

What do you mean by manage connections exactly? If Eddie is not running, it can't manage anything. What you seem to want is that Eddie creates persistent firewall rules (across reboots?) that once set will not change regardless of Eddie running or not. But seriously, why don't you just keep Eddie running? Please specify your use case.

[inradius 6]

Still makes zero sense to me what you expect Eddie to do if it is NOT running. Like corrado said: if Eddie isn't running it can't manage anything. I don't see what's so hard to understand about that.

For my windows clients using a VPN with or without out a supplied client, I configured firewall rules for them that blocked ALL incoming and ALL outgoing connections, adding 'rules' to allow the VPN exclusive rights. If the VPN was not running there was no internet connectivity. That said, it's not so easy for the casual user but with a little research, trial and error it's totally doable. You don't have to configure the firewall to block all, there are many different features and settings to mess around with.

Now remember there is a caveat to configuring windows firewall to block all like I did: there are a bunch of services that strictly rely on net connections to function properly (update manager is one) so you'll have to figure out how to shut them off and not create errors all over the system.

OR> The best method, hands down is to use Eddie on Linux. Have fun!