Eddie Network lock while switching servers with browser open

[iwih2gk 93]

I am not quite smart enough to confirm Eddie's firewall relating to my thread title.  Assuming I leave my browser open and then bring up Eddie to change servers with the browser still open ------- during that brief second the original server is dropped and before the next selected server is connected is my ISP IP being exposed to workspace?????  I try to remember to close my browser but this question has been on my mind several times.  Today, I thought about this while I am logged in and thought I could get a definitive answer.

[OpenSourcerer 1434]

It all hinges on whether you've got NetLock enabled and how you reconnect.
If you disconnect, then connect again while General > Activate Network Lock at startup is selected (or you engage it manually), Network Lock is engaged throughout the reconnect. If something in the browser, like Ajax or a WebSocket, tries to request something, it will time out.
If only Network Lock > Ensure in Session is selected and you disconnect before connecting again, Network Lock is briefly disengaged. If you select a different server while connected, NetLock will be kept engaged.

So, do you need to close your browser? No, not really. Depends a little on the websites you use, but generally, HTTP is only active when website content is requested, after which you are viewing any webpage offline. Barring dynamic website updates via JavaScript or active WebSockets, that is.

[iwih2gk 93]

On 8/10/2024 at 2:19 AM, OpenSourcerer said:

It all hinges on whether you've got NetLock enabled and how you reconnect.
If you disconnect, then connect again while General > Activate Network Lock at startup is selected (or you engage it manually), Network Lock is engaged throughout the reconnect. If something in the browser, like Ajax or a WebSocket, tries to request something, it will time out.
If only Network Lock > Ensure in Session is selected and you disconnect before connecting again, Network Lock is briefly disengaged. If you select a different server while connected, NetLock will be kept engaged.

So, do you need to close your browser? No, not really. Depends a little on the websites you use, but generally, HTTP is only active when website content is requested, after which you are viewing any webpage offline. Barring dynamic website updates via JavaScript or active WebSockets, that is.


So if I understand your explanation I am good.  Just to be sure here is the exact situation, since you described several postures.  I am connected via Eddie with Network Lock ON using a flavor of Linux.  While still connected I bring up the list of servers in the Eddie client and select to connect to the next server.  Eddie then disconnects from the current server and connects to the second server while Eddie itself is still up and running in all other regards.  Your post seems to say that in this scenario there is NO loss of protection and my ISP  IP never gets exposed to workspace???

Can you confirm my understanding based upon the connection scenario I just described, please!

[OpenSourcerer 1434]

2 hours ago, iwih2gk said:

Your post seems to say that in this scenario there is NO loss of protection and my ISP  IP never gets exposed to workspace???

Can you confirm my understanding based upon the connection scenario I just described, please! 

You can easily verify this yourself by checking the log, as I did when I wrote this. A connect to a different server while being connected does not disengage NetLock.

[iwih2gk 93]

Thank you OpenSourcerer!!

These types of questions must seem trivial to YOU.  Some of us/I sometimes need to check in to make sure we are safe.  I buy this service because I trust it and need it for my life.  Just want to make sure I don't do something stupid and flash my real IP all over the place.

[OpenSourcerer 1434]

16 hours ago, iwih2gk said:

These types of questions must seem trivial to YOU.  Some of us/I sometimes need to check in to make sure we are safe.  I buy this service because I trust it and need it for my life.  Just want to make sure I don't do something stupid and flash my real IP all over the place.

It must seem to you that everything I write about seems trivial to me, but there is actual research involved in most of my answers, since I don't know all the answers from the get-go. As I wrote:

On 8/12/2024 at 12:04 AM, OpenSourcerer said:

You can easily verify this yourself by checking the log, as I did when I wrote this

I did check this myself. And now that I checked, I will know this for future reference. So keep those questions coming, even if they seem "simple". There are people who don't ask them out of a multitude of reasons.