* Matt Van Mater [2011-08-22 23:14]:
> I am looking into why my
> pflog has these ambiguous entries that show source and destination as all
> zeros e.g. 0.0.0.0.0 > 0.0.0.0.0.
this fixes it. nsaddr/port and ndaddr/port were set up in pf_test_rule
and thus not set up if we passed a packet stateful
* Matt Van Mater [2011-08-22 23:14]:
> See my configuration at the bottom of this email. I am looking into why my
> pflog has these ambiguous entries that show source and destination as all
> zeros e.g. 0.0.0.0.0 > 0.0.0.0.0.
>
> I saw that there was a related thread earlier this year asking que
Can one of th PF developers weigh in?
Is there anything more that I can do to help? E.g. formally list a
bug report, provide additional detail, act as tester, etc?
On 8/25/11, Kevin Chadwick wrote:
> On Thu, 25 Aug 2011 20:10:12 + (UTC)
> Stuart Henderson wrote:
>
>> Yes these are from the
On Thu, 25 Aug 2011 20:10:12 + (UTC)
Stuart Henderson wrote:
> Yes these are from the "log (all)", looks like a bug to me.
I wondered if it was the result of one of the optimisations. The state
making SYNs show the correct IP.
Yes these are from the "log (all)", looks like a bug to me.
On 2011-08-25, Matt Van Mater wrote:
> I thought that this might be a common occurrence and that it simply wasn't
> in the documentation (where I looked). Is no one else seeing this same
> behavior?
>
> By the way, this host is running
I thought that this might be a common occurrence and that it simply wasn't
in the documentation (where I looked). Is no one else seeing this same
behavior?
By the way, this host is running as a virtual machine inside VMWare ESXi 4.1
(I chose FreeBSD as the guest OS when I initially created the VM
6 matches
Mail list logo
