> On 14 Dec 2015, at 21:38, murdoch.j...@moumantai.de wrote:
> yes, the machine runs on Amazon and yes again -tso fixed the problem.
>
> Could I have seen this somehow watching the pf log? Maybe package length?
It’d be hard to spot. The problem was related to the checksums, so you’d have
to exp
"murdoch" == murdoch john writes:
murdoch> Thanks you so much. I spent hours tracking this down.
Welcome to the club :-)
--
All the best,
Berend de Boer
pgpxPe8nnIfBD.pgp
Description: OpenPGP Digital Signature
Hi Kristof,
yes, the machine runs on Amazon and yes again -tso fixed the problem.
Could I have seen this somehow watching the pf log? Maybe package length?
Thanks you so much. I spent hours tracking this down.
Best,
JOERG
> On 14 Dec 2015, at 21:19, Kristof Provost wrote:
>
>
>> On 14 Dec
> On 14 Dec 2015, at 21:04, murdoch.j...@moumantai.de wrote:
> this might sound as a strange question, but when I activate the PF
> firewall using a minimal rule set (see below), uploading files to
> AWS S3 becomes impossible.
...
> I am lost. Anyone any ideas.
Am I right in assuming that the Fre
Hi there,
this might sound as a strange question, but when I activate the PF
firewall using a minimal rule set (see below), uploading files to
AWS S3 becomes impossible.
The boto library throws a ‘broken pipe’ exception. But if I deactivate
the firewall, everything works fine.
> uname -a
FreeBSD
E-MAIL DISCLAIMER & CONFIDENTIALITY CLAUSE.
This message and any documents and/or files transmitted with it may
contain confidential and proprietary information. They therefore constitute a
privileged, private and confidential communication intended only for the use of
the addressee.
Hello Andrej
This is exactly my issue. Thanks a lot!
Krzysiek Barcikowski
W dniu 2015-12-14 o 10:54, Kolontai Andrej pisze:
Hello Krzysiek,
we've actually managed to resolve our problem. I guess I should have reported
that back to the list, sorry for that.
Yet, our problem was not related to
Hello Krzysiek,
we've actually managed to resolve our problem. I guess I should have reported
that back to the list, sorry for that.
Yet, our problem was not related to the issues addressed by the patch. It
turned out to be a small bug in pfctl
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?