Thanks for everyone's help, it has been insightful.
I did make the following changes to:
rdr on $int_if inet proto tcp from any to any port www -> \
127.0.0.1 port 3128
pass in log quick on $int_if inet proto tcp from any to \
any port 3128 flags S/SA keep state
Just now it looks like the rdr
On Sat, Jun 16, 2007 at 05:20:39PM +0200, Volker wrote:
On 06/16/07 15:26, Roger Miranda wrote:
> On Thursday 14 June 2007 10:19, Volker wrote:
>> [re-added cc:pf to have a wider audience, please keep this]
>>
>> On 06/14/07 16:21, Roger Miranda wrote:
I remember a discussion abou
On 06/16/07 15:26, Roger Miranda wrote:
> On Thursday 14 June 2007 10:19, Volker wrote:
>> [re-added cc:pf to have a wider audience, please keep this]
>>
>> On 06/14/07 16:21, Roger Miranda wrote:
I remember a discussion about your machine in stable@ some time ago.
>>> Yes. I have come a bit
On Thursday 14 June 2007 10:19, Volker wrote:
> [re-added cc:pf to have a wider audience, please keep this]
>
> On 06/14/07 16:21, Roger Miranda wrote:
> >> I remember a discussion about your machine in stable@ some time ago.
> >
> > Yes. I have come a bit further. Generally I would get nothing o
On Thursday 14 June 2007 10:19, Volker wrote:
> [re-added cc:pf to have a wider audience, please keep this]
>
> On 06/14/07 16:21, Roger Miranda wrote:
> >> I remember a discussion about your machine in stable@ some time ago.
> >
> > Yes. I have come a bit further. Generally I would get nothing o
> Roger,
>
> I don't think this message is related to your trouble. I think you can
> also avoid these messages by adding 'no scrub' to your pf.conf (I'm
> currently not aware of any side effects by adding this).
>
> Probably Max has some more suggestions on not scrubbing packets.
>
> You should ge
On Thursday 14 June 2007, Roger Miranda wrote:
> > I don't think this message is related to your trouble. I think you
> > can also avoid these messages by adding 'no scrub' to your pf.conf
> > (I'm currently not aware of any side effects by adding this).
>
> I did add it.
>
> > Probably Max has som
>
> I don't think this message is related to your trouble. I think you can
> also avoid these messages by adding 'no scrub' to your pf.conf (I'm
> currently not aware of any side effects by adding this).
I did add it.
>
> Probably Max has some more suggestions on not scrubbing packets.
>
> You sho
[re-added cc:pf to have a wider audience, please keep this]
On 06/14/07 16:21, Roger Miranda wrote:
>> I remember a discussion about your machine in stable@ some time ago.
> Yes. I have come a bit further. Generally I would get nothing on the
> screen.
> I just started getting this.
>
>>> We
On Thursday 14 June 2007, Volker wrote:
> On 06/14/07 15:33, Roger Miranda wrote:
...
> > The issue is 5-8 hours after the boot up of the machine we get PF
> > loop (Fast, continuous loop, so we can not read the message) on the
> > screen. The machine is completly un responsive. But I noticed the
On 06/14/07 15:33, Roger Miranda wrote:
> We are having a bit of a problem with Freebsd and PF. We have transfered
> 150GB (+/-), yesterday over a Freebsd 6.2 machine with IF_Bridge (acting as a
> transparent proxy)
>
> The issue is 5-8 hours after the boot up of the machine we get PF loop (Fas
We are having a bit of a problem with Freebsd and PF. We have transfered
150GB (+/-), yesterday over a Freebsd 6.2 machine with IF_Bridge (acting as a
transparent proxy)
The issue is 5-8 hours after the boot up of the machine we get PF loop (Fast,
continuous loop, so we can not read the messag
12 matches
Mail list logo
