Am Sat, 21 May 2016 12:28:42 +0200
"O. Hartmann" schrieb:
> Am Fri, 20 May 2016 17:41:39 +0300
> "Andrey V. Elsukov" schrieb:
>
> > On 20.05.16 17:23, O. Hartmann wrote:
> > > The problem is simpel to trigger: have firewall type "WORKSTATION"
> > > configured, IPFW
> > > active (I have IPFW
Am Fri, 20 May 2016 17:41:39 +0300
"Andrey V. Elsukov" schrieb:
> On 20.05.16 17:23, O. Hartmann wrote:
> > The problem is simpel to trigger: have firewall type "WORKSTATION"
> > configured, IPFW
> > active (I have IPFW statically in-kernel-compiled, no modules so far). Have
> > /usr/src
> > as
Am Fri, 20 May 2016 17:41:39 +0300
"Andrey V. Elsukov" schrieb:
> On 20.05.16 17:23, O. Hartmann wrote:
> > The problem is simpel to trigger: have firewall type "WORKSTATION"
> > configured, IPFW
> > active (I have IPFW statically in-kernel-compiled, no modules so far). Have
> > /usr/src
> > as
Am Fri, 20 May 2016 17:59:17 +0300
"Andrey V. Elsukov" schrieb:
> On 20.05.16 17:23, O. Hartmann wrote:
> > I haven't checked so far whether the problem occurs also with non-SSL
> > connections
> > since all connections I see the suffering are somehow encrypted.
>
> Can you try to update up t
On 20.05.16 17:23, O. Hartmann wrote:
> I haven't checked so far whether the problem occurs also with non-SSL
> connections since
> all connections I see the suffering are somehow encrypted.
Can you try to update up to r300302?
--
WBR, Andrey V. Elsukov
signature.asc
Description: OpenPGP dig
On 20.05.16 17:23, O. Hartmann wrote:
> The problem is simpel to trigger: have firewall type "WORKSTATION"
> configured, IPFW
> active (I have IPFW statically in-kernel-compiled, no modules so far). Have
> /usr/src as a
> svn+https repository and try a svn update of the source tree.
Hi,
it look
On Fri, May 20, 2016, Jan Bramkamp wrote:
> On 20/05/16 15:51, Vladimir Zakharov wrote:
> > On Fri, May 20, 2016, Jan Bramkamp wrote:
> >> On 20/05/16 14:54, Vladimir Zakharov wrote:
> >>> Hello
> >>>
> >>> On Fri, May 20, 2016, O. Hartmann wrote:
> I reported earlier about broken pipes in ssh
Am Fri, 20 May 2016 16:01:17 +0200
Jan Bramkamp schrieb:
> On 20/05/16 15:51, Vladimir Zakharov wrote:
> > On Fri, May 20, 2016, Jan Bramkamp wrote:
> >> On 20/05/16 14:54, Vladimir Zakharov wrote:
> >>> Hello
> >>>
> >>> On Fri, May 20, 2016, O. Hartmann wrote:
> I reported earlier ab
Am Fri, 20 May 2016 15:28:35 +0200
Jan Bramkamp schrieb:
> On 20/05/16 14:54, Vladimir Zakharov wrote:
> > Hello
> >
> > On Fri, May 20, 2016, O. Hartmann wrote:
> >> I reported earlier about broken pipes in ssh sessions to remote hosts,
> >> which occur on an erratic basis. i'm investigating t
On 20/05/16 15:51, Vladimir Zakharov wrote:
On Fri, May 20, 2016, Jan Bramkamp wrote:
On 20/05/16 14:54, Vladimir Zakharov wrote:
Hello
On Fri, May 20, 2016, O. Hartmann wrote:
I reported earlier about broken pipes in ssh sessions to remote hosts,
which occur on an erratic basis. i'm invest
On Fri, May 20, 2016, Jan Bramkamp wrote:
> On 20/05/16 14:54, Vladimir Zakharov wrote:
> > Hello
> >
> > On Fri, May 20, 2016, O. Hartmann wrote:
> >> I reported earlier about broken pipes in ssh sessions to remote hosts,
> >> which occur on an erratic basis. i'm investigating this problem now and
On 20/05/16 14:54, Vladimir Zakharov wrote:
Hello
On Fri, May 20, 2016, O. Hartmann wrote:
I reported earlier about broken pipes in ssh sessions to remote hosts,
which occur on an erratic basis. i'm investigating this problem now and
it seems that it is also ipfw-related, but I'm not sure. Th
Hello
On Fri, May 20, 2016, O. Hartmann wrote:
> I reported earlier about broken pipes in ssh sessions to remote hosts,
> which occur on an erratic basis. i'm investigating this problem now and
> it seems that it is also ipfw-related, but I'm not sure. This problem
> is present since a couple of w
13 matches
Mail list logo
