ipfw: Can't see other flows in pipe

Hi everyone! I've got the following ipfw rules: cmd=ipfw webclient_upload_bandwidth=1024kbit/s webclient_download_bandwidth=6144Kbit/s bottleneck_bandwidth=100Mbit/s client_rtt_delay=10 queue=50 client1_subnet=192.168.5.0/26 server1_subnet=192.168.7.0/24 $cmd pipe 100 config mask all bw

Re: IPFW DUMMYNET: Several pipes after each other

Ian Smith wrote: That's a very good ipfw tutorial, given parts of it are a bit outdated (FreeBSD 4.x) but it covers a lot of useful background. I just skimmed lots of it now but nothing I read jarred, unlike the Handbook section. If I choose the default (50 packets) it means that it takes

Re: IPFW DUMMYNET: Several pipes after each other

Ian Smith wrote: On Thu, 22 Jan 2009 08:10:09 +0100 (CET) So far I've got those rules: in_if=em0 out_if=em1 management_if=em2 in_ip=100.100.100.1 out_ip=200.200.200.1 management_ip=172.16.0.201 client1_subnet=192.168.5.0/26 client2_subnet=192.168.6.0/26

Re: shell scripting, how to auto-timeout?

The java process has the potential to run forever, and I want it to run for at most 1 second then get killed. I could write a parent script that somehow gets the PID of the child script, but the problem is that the java program writes to standard out, the result of the program is written to

IPFW DUMMYNET: Several pipes after each other

Hi! I'm using FreeBSD 7.0 with IPFW DUMMYNET enabled. I've got a problem with creating a ruleset which allows me to limit the overall bandwidth of a link and afterwards pass the packets to another pipe for processing. So far I've got those rules: in_if=em0 out_if=em1 management_if=em2