On Mon, 27 Aug 2001, Louis A. Mamakos wrote:
> I don't think that a drive-by commit of some other related work without
> a commitment to understand the code in a very deep way is wise.
>
> If you consider the dynamic range that the TCP retransmit timers need to
> operate over, it's a truly frigh
On Mon, 27 Aug 2001, Harkirat Singh wrote:
> I agree with your comment that FCAK is only a retransmission algorithm and
> many papers recommends that FACK+SACK improves the performance for
> long-delay network (for more information look at 1996 SIGCOMM paper).
I've been reading through the pape
Can anyone tell me why the VLAN code might be causing my switches (ciscos)
to see a lot of runt frames when the interface is in 802.1q trunking mode ?
The same nic in the same port in regular ethernet mode does not cause this.
e.g.
FastEthernet0/20 is up, line protocol is up
Hardware is Fa
[EMAIL PROTECTED] wrote:
| >at least we'd get rid of the d*mned warning messages!
| >Are you not aware that most of the warning messages for a normal
| >kernel compile come from the KAME code? I am on compile number 157
| >for the KSE code. (in 3 weeks)
|
| though i have no freebsd-curre
>
> I agree with your comment that FCAK is only a retransmission algorithm and
> many papers recommends that FACK+SACK improves the performance for
> long-delay network (for more information look at 1996 SIGCOMM paper).
Most of the hair in a TCP implementation is "only" the retransmission
algori
I agree with your comment that FCAK is only a retransmission algorithm and
many papers recommends that FACK+SACK improves the performance for
long-delay network (for more information look at 1996 SIGCOMM paper).
I would say that it would be nice to have SACK+FACK+NewReno and all have a
sysctl so
On Mon, 27 Aug 2001, Alfred Perlstein wrote:
> * Mike Silbersack <[EMAIL PROTECTED]> [010827 15:57] wrote:
> >
> > The easy way to do this is to copy the top of one of the files from
> > netstat, which already has all the includes included and in the proper
> > order. :)
>
> Odd, you think it wo
On Mon, Aug 27, 2001 at 04:54:31PM -0400, Mike Silbersack wrote:
>
> On Mon, 27 Aug 2001, Jesper Skriver wrote:
>
> > On Thu, Aug 23, 2001 at 06:23:31PM -0700, Scott Renfro wrote:
> > > You have a valid point that icmp_may_rst changes nmap's behavior, even
> > > with the proposed patch. If you
* Mike Silbersack <[EMAIL PROTECTED]> [010827 15:57] wrote:
>
> On Mon, 27 Aug 2001, Alfred Perlstein wrote:
>
> > It's actually a bit more difficult than that because you need to
> > include a bunch of kernel headers (as well as defining _KERNEL)
> > to get at it from userland.
>
> The easy wa
As of now, do not have access to an environment to do the task.
BTW, always better to say "I do not know" or choose not answer.
As a child, all you have are questions. One grows up,
goes to Stanford paying a lot of money, and stops
asking questions for the fear of being perceived "stupid".
Thank
On Sun, 26 Aug 2001, Jeffrey Hsu wrote:
> Rate-halving is implemented in the PSC version of SACK. Perhaps
> we should take a look at that?
Makes sense, if we want Rate-halving. All the papers evaluating it have
sounded good, and it probably is good to incorporate. My only concern is
whether
On Mon, 27 Aug 2001, Alfred Perlstein wrote:
> It's actually a bit more difficult than that because you need to
> include a bunch of kernel headers (as well as defining _KERNEL)
> to get at it from userland.
The easy way to do this is to copy the top of one of the files from
netstat, which alre
On Mon, 27 Aug 2001, Jesper Skriver wrote:
> On Thu, Aug 23, 2001 at 06:23:31PM -0700, Scott Renfro wrote:
> > You have a valid point that icmp_may_rst changes nmap's behavior, even
> > with the proposed patch. If you want nmap's historic behavior (admin
> > prohib ==> filtered), then turning o
* Bill Fumerola <[EMAIL PROTECTED]> [010827 15:33] wrote:
> On Mon, Aug 27, 2001 at 01:32:18PM -0700, Kris Kennaway wrote:
> > I've forwarded this message to the freebsd-net mailing list where it's
> > more on-topic for discussion.
> >
> > Kris
> >
> > On Mon, Aug 27, 2001 at 11:51:30AM -0700, S
* Kris Kennaway <[EMAIL PROTECTED]> [010827 15:32] wrote:
> I've forwarded this message to the freebsd-net mailing list where it's
> more on-topic for discussion.
>
> Kris
>
> On Mon, Aug 27, 2001 at 11:51:30AM -0700, S.V. Ganesh wrote:
> > What is the size of the IPCB(struct inpcb) and TPCB(str
On Mon, Aug 27, 2001 at 01:32:18PM -0700, Kris Kennaway wrote:
> I've forwarded this message to the freebsd-net mailing list where it's
> more on-topic for discussion.
>
> Kris
>
> On Mon, Aug 27, 2001 at 11:51:30AM -0700, S.V. Ganesh wrote:
> > What is the size of the IPCB(struct inpcb) and TPC
I've forwarded this message to the freebsd-net mailing list where it's
more on-topic for discussion.
Kris
On Mon, Aug 27, 2001 at 11:51:30AM -0700, S.V. Ganesh wrote:
> What is the size of the IPCB(struct inpcb) and TPCB(struct tcpcb) structure?
> (ignoring platform specific alignment issues)
>
Julian,
Can you *please* make some attempt to pick your battles more wisely
and stop needlessly antagonizing the KAME folks? I'm sure you have
some areas of technical skill, but diplomacy is certainly not
something you excel at (in fact, you completely suck at it, let's be
honest) so perhaps you
> From: "Vladimir Terziev" <[EMAIL PROTECTED]>
> Date: Mon, 27 Aug 2001 15:02:59 +0300
> Sender: [EMAIL PROTECTED]
>
>
> Hi,
>
> I have a dual-boot machine with Cisco AIR-PCI 352 card on it. The machine
> boots FreeBSD 4.3-STABLE and Windows'98.
>
> The AIR-PCI 352 card works either wit
Jun-ichiro itojun Hagino wrote:
>
> >We are planning to fill your (and many freebsd hackers') requirements.
>
> - i have never heard from other people about (against) the use of
> varargs, therefore, it is misleading to say "many freebsd hackers".
Right. Sorry if other freebsd g
>We are planning to fill your (and many freebsd hackers') requirements.
just a nitpicking.
- i don't think julian is in the position to set the requirement
for freebsd. is he?
- i have never heard from other people about (against) the use of
varargs,
We are planning to fill your (and many freebsd hackers') requirements.
These plans include introducing some #ifdef clause to match freebsd's
prototypes if there is no other way to live with freebsd in peace,
though it increases our maintanance cost. (on the contrary, not
introducing #ifdef clause
On Thu, Aug 23, 2001 at 06:23:31PM -0700, Scott Renfro wrote:
> On Thu, Aug 23, 2001 at 04:53:26PM -0400, Barney Wolff wrote:
> >
> > As another heavy nmap user, I'd vote just the other way. It's useful
> > to differentiate between a reset coming back from the destination host
> > and an unreacha
>at least we'd get rid of the d*mned warning messages!
>Are you not aware that most of the warning messages for a normal
>kernel compile come from the KAME code? I am on compile number 157
>for the KSE code. (in 3 weeks)
though i have no freebsd-current box, i disagree. there are a lot
>I have still not heard any reason for the varargs here..
>except "it's needed for portability"..
>portability with WHO?
portability with other *BSD projects (NetBSD, OpenBSD, BSD/OS, MacOSX
maybe).
>BSD4.4 certainly didn't have varargs there
4.4BSD did not have pro
Hi,
I have a dual-boot machine with Cisco AIR-PCI 352 card on it. The machine
boots FreeBSD 4.3-STABLE and Windows'98.
The AIR-PCI 352 card works either with FreeBSD and Win98, but it has
different behaviour under both.
When it works under Win98, ping to my gateway machine is ~ 6ms. W
FWIW, sadly, Mac OS X does flirt with varargs. These seem to have
crept in via the Mach back door. I don't believe that they are
actually used anywhere, but the varargs headers are there. Our
version of the KAME stack must have pre-dated the intro of this,
because the 'bsd' side of the code
27 matches
Mail list logo
