On Mon, Mar 04, 2002 at 02:08:20PM -0500, Fengrui Gu wrote:
> When trying to set queue size (>100) with ipfw,
> I found ipfw actually hard-coded the queue size limit to 100.
>
> I am trying to simulation network link with very high delay and relatively
> low bandwidth. However, I don't want to su
> what is curious is that I am using a 4-port D-link on our
> test boxes as primary development cards and they do not seem
> to freeze. The card uses 21143 and seems quite reliable.
>
> I know of a bug in the code on my web site whose symptoms look like
> a freeze, but that is presumably related
I am wondering if there is any chance that someone has implemented
netgraph nodes for slip or 802.11 interfaces? If so I would appreciate any
pointers.
-- Roop
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of
no, as far as I kow neither has been done.
I'm intersted in knowing exactly what you mena by 802.11 in netgraph..
Do you mean the Beaconning etc, needed for AP operation?
On Wed, 6 Mar 2002, Roop Mukherjee wrote:
> I am wondering if there is any chance that someone has implemented
> netgraph
Hi,
Currently, every clonable interface which uses the if_clone_*()
framework has a chunk of duplicated rman code to handle unit allocation.
This is exactly the same code in every clonable interface driver.
Moreover, this code is only used in the case of a "wildcard" creation,
i.e. when
am looking for the same info too.
Vinod
--- Roop Mukherjee <[EMAIL PROTECTED]>
wrote:
> I am wondering if there is any chance that someone
> has implemented
> netgraph nodes for slip or 802.11 interfaces? If so
> I would appreciate any
> pointers.
>
> -- Roop
> ___
Actually my interest is for using it at the mobile node.
I was also hoping that someone could answer a quick question about the
code.
I was thinking that the netgraph nodes that represent the network
interfaces,
forward packets to the drivers and let them do framing and control etc.
But I can't s
There are redundant calls to the in_pcblookup_hash() in the
ip_fw_chk() function called via (*ip_fw_chk_ptr)() in the
ip_input path.
Would it be useful to modify the (*pr_input) function pointer
in the struct ipprotosw to take a fourth argument (perhaps it
should be cast to a "void *" to keep it
sounds good..
can you send us a patch to look at?
On Wed, 6 Mar 2002, Terry Lambert wrote:
> There are redundant calls to the in_pcblookup_hash() in the
> ip_fw_chk() function called via (*ip_fw_chk_ptr)() in the
> ip_input path.
>
> Would it be useful to modify the (*pr_input) function point
