This patch is *VERY* experimental patch to implement rfc5862 which is on
the IETF standard tracks so it could be completely wrong or has a lot of
bugs on it or wrong approaches because I'm a really newbie on TCP stack.
This patch includes two features to support `Basic FRTO algorithm' and
`SACK-En
Pyun YongHyeon (pyu...@gmail.com) [11.01.31 23:14] wrote:
>
> Then I have no idea. Does other OS work with your hardware without
> issues? As last resort, could you try vendor's FreeBSD driver? The
> vendor's driver applies a bunch of magic DSP fixups which re(4)
> does not have. I don't know whet
On 02.02.2011 00:50, Gleb Smirnoff wrote:
> On Wed, Feb 02, 2011 at 12:30:20AM +0600, Eugene Grosbein wrote:
> E> On 31.01.2011 14:20, Julian Elischer wrote:
> E>
> E> > replace with:
> E> >
> E> > 3504if ((hook == NULL) ||
> E> > 3505NG_HOOK_NOT_VALID(hook) ||
> E> >
On 2/5/2011 8:48 AM, Eugene Grosbein wrote:
>
> First: again, no dump (not even started to dump, and no "Uptime:" written to
> console):
if you try and enable dumps manually from the shell,
dumpon -v /dev/ad0s1b
(or whatever your swap partition is), what does dumpon return with ?
---Mi
On 05.02.2011 19:55, Mike Tancsa wrote:
> On 2/5/2011 8:48 AM, Eugene Grosbein wrote:
>>
>> First: again, no dump (not even started to dump, and no "Uptime:" written to
>> console):
>
> if you try and enable dumps manually from the shell,
>
> dumpon -v /dev/ad0s1b
> (or whatever your swap partit
On 05.02.2011 20:00, Eugene Grosbein wrote:
>>> First: again, no dump (not even started to dump, and no "Uptime:" written
>>> to console):
>>
>> if you try and enable dumps manually from the shell,
>>
>> dumpon -v /dev/ad0s1b
>> (or whatever your swap partition is), what does dumpon return with ?
for some time now it has been apparent that the divert socket protocol
was a little too heavily tied to IPv4.
With IPv6 coming along now, it seems that we should look at how to
extend it.
I see a couple of possible ways to do this:
--- the first way:
One would be to add an IPV6 version
Hello,
How can I help?
/ipv
On Sun, Feb 6, 2011 at 12:20 AM, Julian Elischer wrote:
> for some time now it has been apparent that the divert socket protocol was a
> little too heavily tied to IPv4.
>
> With IPv6 coming along now, it seems that we should look at how to extend
> it.
>
> I see a c
On 2/5/11 4:09 PM, Ivo Vachkov wrote:
Hello,
How can I help?
if you have ipv6 connectivity and experience, I have no experience or
connectivity, with it so
I'll be coding blind and will need a tester.
If you have an application for IPV6 testing that would be even better.
Divert is often used
On Fri, 28 Jan 2011 11:00:40 -0800, Doug Barton wrote:
> I haven't reviewed the patch in detail yet but I wanted to first thank
> you for taking on this work, and being so responsive to Fernando's
> request (which I agreed with, and you updated before I even had a
> chance to say so). :)
Thanks f
I'm in search of MSS clamping for FreeBSD servers; in particular, for
IPv6. I'm finding pretty much nothing (except iptables..) on the net.
Am I chasing wild geese?
--
Jason Fesler, email/jabber resume: http://jfesler.com
"Give a man fire, and he'll be warm for a day;
set a man on fire, a
On 02/05/11 23:07, Jason Fesler wrote:
I'm in search of MSS clamping for FreeBSD servers; in particular, for
IPv6. I'm finding pretty much nothing (except iptables..) on the net.
Am I chasing wild geese?
pf.conf(5) mentions a "max-mss" option for traffic normalization.
-Boris
On 2/5/11 8:07 PM, Jason Fesler wrote:
I'm in search of MSS clamping for FreeBSD servers; in particular,
for IPv6.
Well, there is ng_tcpmss but I see that it only works for IPv4
It may however be relatively easy to add code to allow it to work for
IPV6.
there is also the code in ports net/tc
On Fri, 4 Feb 2011, Prabhu Hariharan wrote:
When I delete an IP-address from an interface, the TCP (and other)
connections using that local IP-address are not getting purged. The telnet
or ssh sessions on the other end just get hung, as FreeBSD address-deletion
doesn't handle this situation
14 matches
Mail list logo