PF + BRIDGE + PFSYNC causes system freezing

Giulio Ferro auryn at zirakzigil.org
Wed Mar 17 16:37:39 UTC 2010


On 17.03.2010 16:50, Greg Hennessy wrote:
> A possible corner case with the virtual hosting platform ?
>
> Try changing the NICS from EM to something else supported RL on vmware IIRC.
>
>
>    

Nope, I'm not using virtualization, that's the other guy.

I'm using a physical machine...


> Greg
>
> ________________________________________
> From: owner-freebsd-pf at freebsd.org [owner-freebsd-pf at freebsd.org] On Behalf Of Giulio Ferro [auryn at zirakzigil.org]
> Sent: 17 March 2010 15:46
> To: Daniel Hartmeier
> Cc: freebsd-net at freebsd.org; freebsd-pf at freebsd.org
> Subject: Re: PF + BRIDGE + PFSYNC causes system freezing
>
> On 17.03.2010 11:47, Giulio Ferro wrote:
>    
>> On 17.03.2010 09:12, Daniel Hartmeier wrote:
>>      
>>> On Tue, Mar 16, 2010 at 03:19:51PM -0400, kevin wrote:
>>>
>>>        
>>>> I would like to assist in diagnosing this issue so if anyone wants
>>>> me to
>>>> check anything or test, please let me know. I would really like to
>>>> understand this problem.
>>>>          
>>> What are your settings for
>>>
>>>     $ sysctl -a | grep bridge.pfil
>>>        
>> net.link.bridge.pfil_local_phys: 0
>> net.link.bridge.pfil_member: 1
>> net.link.bridge.pfil_bridge: 1
>> net.link.bridge.pfil_onlyip: 1
>>
>>
>>      
>>> Have you tried filtering only on one of the physical bridge interfaces,
>>> with net.link.bridge.pfil_bridge=0 and set skip on { lo0, bridge0,
>>> em1 }?
>>>
>>> Daniel
>>>        
>> Ok, I'm trying "set skip on {lo0, bridge0}".
>> I'll let you know if  there is any improvement.
>>      
>
> No, no improvement.
>
> The system froze anyway after about 3-4 hours this time.
>
> Please advise!
> _______________________________________________
> freebsd-pf at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-pf
> To unsubscribe, send any mail to "freebsd-pf-unsubscribe at freebsd.org"



More information about the freebsd-pf mailing list