Hi folks,
I have a question about below source code when I study the stack:
if (acked > so->so_snd.sb_cc) {
tp->snd_wnd -= so->so_snd.sb_cc;
>
sbdrop_locked(&so->so_snd, (int)so->so_snd.sb_cc);
ourfinisac
I would like to open an discussion about the possibility of importing relayd(8)
and its management tool relayctl(8) from OpenBSD for import to our base system.
Relayd is a level 3 and level 7 reverse proxy (with transparency support) and a
load-balancer.
It makes use of pf(4)'s advanced features
Hi folks,
I have a question about below source code when I study the stack:
if (acked > so->so_snd.sb_cc) {
tp->snd_wnd -= so->so_snd.sb_cc;
>
sbdrop_locked(&so->so_snd, (int)so->so_snd.sb_cc);
ourfinisac
Hi,
We observed the same issue on our FreeBSD6 and 7 servers. I tried to reproduce
the problem writing a simple test case but failed -- I didn't come to the idea
of shutdown()/close() sequence (as Anton did). Although looking now at the
code we had the issue with I see that shutdown()/close() sequ
The following reply was made to PR kern/146845; it has been noted by GNATS.
From: Mikolaj Golub
To: bug-follo...@freebsd.org
Cc: Anton Lavrentiev , Robert Watson
, freebsd-net@FreeBSD.org
Subject: Re: kern/146845: [libc] close(2) returns error 54 (connection reset by
peer) wrongly
Date: Fri, 28
On 27 May 2010, at 22:25, Mikolaj Golub wrote:
> We observed the same issue on our FreeBSD6 and 7 servers. I tried to reproduce
> the problem writing a simple test case but failed -- I didn't come to the idea
> of shutdown()/close() sequence (as Anton did). Although looking now at the
> code we h
The following reply was made to PR kern/146845; it has been noted by GNATS.
From: "Robert N. M. Watson"
To: Mikolaj Golub
Cc: bug-follo...@freebsd.org,
Anton Lavrentiev ,
freebsd-net@FreeBSD.org
Subject: Re: kern/146845: [libc] close(2) returns error 54 (connection reset by
peer) wrongly
Date
The following reply was made to PR kern/146845; it has been noted by GNATS.
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]"
To: "bug-follo...@freebsd.org"
Cc:
Subject: Re: kern/146845: [libc] close(2) returns error 54 (connection reset
by peer) wrongly
Date: Fri, 28 May 2010 00:07:16 -0400
Hi
9.0-CURRENT #0: Sun Apr 11 23:26:21 EEST 2010 amd64
net.my_fibnum: 0
net.add_addr_allfibs: 1
net.fibs: 3
# netstat -rn | grep default
defaultXXX.XXX.XXX.254 UGS 0 37594940 tun1
default 2001:5c0:1400:b::27e8 UGS
gif0
# setfib 1 ne
Sorry...
Instead, "add" to read "change"...
# setfib 2 route -n add -inet6 default 2001:470:27:140::1
route: writing to routing socket: File exists
add net default: gateway 2001:470:27:140::1: route already in table
# setfib 2 route -n change -inet6 default 2001:470:27:140::1
route: writing t
Months ago I reported a system freezing whenever bridge was used
with pf. This still happens now in 8.1 prerelease: after several minutes
to hours
that the bridge is active the system becomes unresponsive.
# uname -a
FreeBSD firewall1 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #0: Thu May 27
18:03:
Old Synopsis: setfb not work with ipv6
New Synopsis: [ip6] setfb not work with ipv6
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Fri May 28 06:05:53 UTC 2010
Responsible-Changed-Why:
Over to maintainer(s).
http://www.freebsd.org
The following reply was made to PR kern/147155; it has been noted by GNATS.
From: "Bjoern A. Zeeb"
To: bug-follo...@freebsd.org, univers...@ukr.net,
Julian Elischer
Cc:
Subject: Re: kern/147155: [ip6] setfb not work with ipv6
Date: Fri, 28 May 2010 06:41:59 + (UTC)
This is a documen
13 matches
Mail list logo
