Communication PC <-> Router is blocked, but...

Hi @ all

I have noticed the following problem...
I created this rule on top of all rules in order to block the communication between PC <-> Router


(the mac is only a example)

My application filtering looks like this...



When I want to connect to the inet, I remove the checkbox in the first rule.
For example I connect to google and after surfing, I activate the checkbox in the first rule (so to my mind, ANY communition has to be blocked) and I close the browser.
Then this happens... (remember I allready closed Firefox)



When I choose "Block", then there is the following "connection" (?) logged. (firefox is closed and first rule is activated)



Why ?
What's wrong with my rule/filter or my understanding ?

El Nebuloso

 

Hi El_Nebuloso


The links won't work...

Is it possible for you to try again?

If you look for a good soft for screen capture you may try this one:
MWSnap : http://www.mirekw.com/winfreeware/mwsnap.html

and use the "manage attachments" button here.
It's better than a link to an other site...

 

Sorry, I will try again this evening...

 

I have no idea, why the hardcopies won't work at the first time, but now they are displayed.

Referring to my first post, does anyone has a idea whats wrong with my configuration ?

 

Guten Tag El_Nebuloso


This is simple to understand:

All communications are blocked between the PC and the router not in local looping of your PC...


I guess (I'm not sure of this...) that Firefox is still in a connection state...

Not "Established" but one of the last remaining connection state like "FIN WAIT1"...

In W xp for example the timeout allowed for all application is determined by the value of this registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\TcpTimedWaitDelay


The default value is 240 seconds = 4 minutes !!!

Ref.:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentry/58811.mspx?mfr=true

So this is (I believed) examined as a connection by LNS... This is my hypothesis about Firefox...


But there is a remaining "mystery":

The only problem here is to understand why LNS ask to be authorised again in this situation.

No more idea for this moment.



P.S. If you want to check the connection state this can be useful:
http://www.microsoft.com/technet/sysinternals/Networking/TcpView.mspx

 

Thank you very much Climenole !
Then I will concentrate on this remaining mystery.

Gruss,
El Nebuloso

 

Hi El_Nebuloso

Yes, that mystery...

"Einführung in der Phänomenologie des LNS Geistes"

Personnaly I found this "SELBST-authorisation" somewhat absurd.

In Principia Mathematica, Bertrand Russell and A.N. Whitehead developped the "Theory of Types" to avoid contradictions:

An element of a class can't be treated at the same level than the class itself... Otherwise this drive to contradictions...

My (not so ? ) humble opinion is :

LSN give the choice to be authorised by itself or not: a kind of Hegelian "Aufhebung" !!!

This "authorisation" must be "implicit" or built-in... Not at the same level than the other application to be examinded by LNS...

Did LNS is an HEGELIAN firewall ?