Edited for mistakes!  Sorry!

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Seb wzd4j9jxq2-at-snkmail.com
Sent: 15 December 2011 16:56
To: 'pfSense support and discussion'
Subject: Re: [pfSense] 'direction' of firewall rules for floating rules?


So, Tonino, in your example you would select all interfaces except OPT1 in
your rule, and also select [Seb] IN .  Correct?  Because if you also select
OPT1, then [Seb] IN would mean an unncessary hole in the firewall out from
OPT1.  On the other hand, if you didn't care about a few extra small holes
in the firewall like this, you could just select all interfaces (or none,
which is the same for floating rules), and then either IN or OUT or ANY and
it would still pass traffic.  Because it would either match the IN on the
near interface, or it would match OUT on the far interface (or it would
match ANY on both interfaces).  Hence why I said it seems to have little
relevance.  But I suppose one should care about those extra few small holes
in the firewall and just select all interfaces except OPT1[Seb, added comma
for clarity] ,  and IN (Or OPT1 only and OUT)...  Although in my case I have
a destination IP anyway - so it will not create any extra holes.
 
Or am I still not getting what 'OUT' rules are for?  I've just created 1 and
it seems to work fine.
 
[A further option with your example, I guess would be to just select OPT1
and OUT.]
 
Yes, I understand the benefits of floating rules.

Kind regards, 

Seb


  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Tonix (Antonio Nati) tonix-at-interazioni.it
Sent: 15 December 2011 14:57
To: pfSense support and discussion
Subject: Re: [pfSense] 'direction' of firewall rules for floating rules?


If you speak only about WAN and LAN, yes, but if you have other interfaces
interested all changes.

You could enable a service on the OPT1, available to all existing
interfaces.
So in this case, floating rule would permit any 'OUT' connection to that
service offered inside OPT1.

This permit you to avoid adding an incoming rule for every existing
interface.

Tonino



Il 15/12/2011 15:50, Seb ha scritto: 

...or the WAN interface and 'out'?  Is that not the same as LAN interface
and 'in'?  And if you are selecting all interfaces, then surely the
direction would have no effect?  Because it would either match on the LAN
side, or the WAN side...  Or am I just not getting what 'out' rules are for?

Kind regards, 

Seb


  _____  

From: [email protected]
<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Fuchs, Martin
martin.fuchs-at-trendchiller.com
Sent: 15 December 2011 13:30
To: pfSense support and discussion
Subject: Re: [pfSense] 'direction' of firewall rules for floating rules?



Hi !

Yes, the direction has some relevance for the floating rules, because when
the direction  is wrong, the packets will not pass the firewall.

When you want to allow a packet to pass the firewall from the LAN side to
the WAN side you have to select the LAN interface and as direction you have
to select "in" (from the view of the firewall)



Regards,



martin



Von: [email protected] <mailto:[email protected]>
[mailto:[email protected]] Im Auftrag von Seb
Gesendet: Donnerstag, 15. Dezember 2011 14:06
An: 'pfSense support and discussion'
Betreff: [pfSense] 'direction' of firewall rules for floating rules?



Hi list,



Does the 'direction' of a firewall rule have any relevance for floating
rules?  I can't find any explanation for what direction means in the docs,
even when it applies to individual interfaces (where I can see what it might
mean), but for floating rules that apply to all interfaces - I don't suppose
it changes much?  Perhaps just affects connections from the firewall itself
if you have it set to out but not in?



pfSense 2.0

Kind regards, 

Seb


 

_______________________________________________

List mailing list

[email protected]

http://lists.pfsense.org/mailman/listinfo/list



-- 

------------------------------------------------------------

        Inter@zioni            Interazioni di Antonio Nati 

   http://www.interazioni.it      [email protected]           

------------------------------------------------------------

_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list

Reply via email to