Hi! > Where such thing can be used? Mostly for testing applications and other stuff. It's a little bit hard to wait to appear a duplicate so you can test that your application works ok. > and why you implemented such thing as sheduler, not iptables module? Why iptables module? Why do you think is better? > > > > > This is my first work for kernel, so please have mercy. :) > > > > OK, I like to announce sch_dup, a new queue discipline that, attached to a > > class (or a device, as root) duplicate packets that pass. Yes, you can > > control the frequency of duplicates. > > > > Example: > > tc qdisc add dev eth0 root dup limit 100 gap 1 > > This means: create a pfifo queue and send packets with > > a gap of 1 (0 = no dups) between duplicates: > > gap=0: no duplication > > gap=1: NDNDNDNDND > > gap=2: NNDNNDNNDNNDNND > > (N=not duplicated, D duplicated) > > > > Attached are 3 patches: 1 patch for net/sched dir, other > > for include/linux/pkg_sched.h, and the last for iproute2. > > > > Any comments are appreciated. > > > > David, please include it in 2.6. > > Alexey, please include the third patch in iproute2. > > > > Thank you! > > --- > > Catalin(ux aka Dino) BOIE > > catab at deuroconsult.ro > > > > > > _______________________________________________ > LARTC mailing list / LARTC@xxxxxxxxxxxxxxx > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ > --- Catalin(ux aka Dino) BOIE catab at deuroconsult.ro _______________________________________________ LARTC mailing list / LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
