> also, ipfw can match packets by ack#. i've used this as criteria for a
> dummynet pipe rule in the past.
Great - that is just what I am looking for - so I can drop all packets
with an ack of zero.
Can someone show me an example rule of said behavior ?
To Unsubscribe: send mail to [EMAIL PROT
On Sun, Jan 12, 2003 at 10:11:28AM -0800, Luigi Rizzo wrote:
> On Sat, Jan 11, 2003 at 04:40:53PM -0800, Josh Brooks wrote:
> ...
> > Second, it turns out that the default stream.c has ACK numbers of zero on
> > every packet. So although I realize that since ipfw is stateless I cannot
> > put in
On Sun, Jan 12, 2003 at 09:07:31PM +0200, Mikko S. Hyvarinen wrote:
> The on-board 3com MAC and Broadcom/Altima PHY are not being detected by the
> xl(4) driver in -current (cvsup done yesterday evening).
> In the Award BIOS there is only one setting for the 3com device, a supposed
> on/off switch
Hi,
I recently acquired one of these motherboards and suitable CPU + memory for it.
The on-board 3com MAC and Broadcom/Altima PHY are not being detected by the
xl(4) driver in -current (cvsup done yesterday evening).
In the Award BIOS there is only one setting for the 3com device, a supposed
on/of
Hi,
On Sat, Jan 11, 2003 at 04:40:53PM -0800, Josh Brooks wrote:
...
> After reading some more documents on DoS attacks (namely
> http://www.e-gerbil.net/ras/projects/dos/dos.txt ) I have found that there
> are two nice mechanisms to thwart a large number of ack and syn floods.
>
> First, it turn
