On Sat, Aug 8, 2009 at 2:26 PM, Jason
Lixfeld wrote:
> Is there an Easy Button for allowing inbound traceroute (traceroute sourced
> from the WAN) in pfSense other than creating two rules on the WAN side that
> permit inbound ICMP as well as inbound UDP source port range 33434 to 33534
> to destina
On Sat, Aug 8, 2009 at 2:56 PM, Walter
Kugler wrote:
> Hello!
>
>
> About myself:
> I have no great knowledge about FreeBSD. I use mostly the WebGUI of pfSense,
> but i have some years experience on Debian GNU/Linux, including building a
> custom kernel.
>
> My Problem:
> I have bought a new machin
Hello!
About myself:
I have no great knowledge about FreeBSD. I use mostly the WebGUI of
pfSense, but i have some years experience on Debian GNU/Linux,
including building a custom kernel.
My Problem:
I have bought a new machine with an AMD Phenom II X3 Processor that has
3 Cores. I want to
Is there an Easy Button for allowing inbound traceroute (traceroute
sourced from the WAN) in pfSense other than creating two rules on the
WAN side that permit inbound ICMP as well as inbound UDP source port
range 33434 to 33534 to destination port range 33434 to 33534?
-
From: Eugen Leitl [mailto:eu...@leitl.org]
Sent: Friday, August 07, 2009 5:41 AM
Is any of you running pfSense in a fully redundant hosting setting?
Care to share your setup?
I'm currently running two pfSense systems (2 NICs each) in a
transparent bridge mode, as a poor man's failover. I
cu