> >>> A better approach would probably be to set a semaphore before
> >>> starting, and release it at the end, and keep interrupts enabled
> >>
> >> As I set "net.inet.ip.dummynet.expire=0", if it will affect
> >> only to ip addresses founded newly when a semaphore is introduced,
> >> I'll be h
>>> A better approach would probably be to set a semaphore before
>>> starting, and release it at the end, and keep interrupts enabled
>>
>> As I set "net.inet.ip.dummynet.expire=0", if it will affect
>> only to ip addresses founded newly when a semaphore is introduced,
>> I'll be happy.
>
> n
> > A better approach would probably be to set a semaphore before
> > starting, and release it at the end, and keep interrupts enabled
...
>
> Dear, luigi-san.
>
> Thank you for mail.
> As I set "net.inet.ip.dummynet.expire=0", if it will affect
> only to ip addresses founded newly when a
>> When I typed 'ipfw pipe list', packet loss occur.
>
> unfortunately the "pipe list" has to navigate through a list of
> pipe/flow/queue descriptors to report its output, and at the moment
> it does this with interrupts disabled to avoid that the data
> structure changes while it is working.
> I use dummynet and bridge on FreeBSD 4.2-Stable to see traffic
> statics on Celeron 466MHz with 256 mega bytes ram as follows.
>
> ipfw pipe 1 config mask dst-ip 0x buckets 1024
> ipfw pipe 2 config mask src-ip 0x buckets 1024
> ipfw add pipe 1 all from any to any bridged via
I use dummynet and bridge on FreeBSD 4.2-Stable to see traffic
statics on Celeron 466MHz with 256 mega bytes ram as follows.
ipfw pipe 1 config mask dst-ip 0x buckets 1024
ipfw pipe 2 config mask src-ip 0x buckets 1024
ipfw add pipe 1 all from any to any bridged via fxp0 in
ipfw
