Re: artificial latency for a network interface

2001-06-29 Thread Maksim Krasnyanskiy
> > I wanted to do that using two tun devices. > > I had hoped to have a routing like this: > > > > <-> eth0 <-> tun0 <-> userspace, waiting queue <-> tun1 <-> eth1 > >yes, that works very well. A userspace app sits on top of the >tun/tap device and pulls out packets, delays them and

Re: artificial latency for a network interface

2001-06-29 Thread Pekka Pietikainen
On Thu, Jun 28, 2001 at 11:29:38PM -0500, Burkhard Daniel wrote: > I had a similiar problem once, and wrote a module that overwrote the > loopback net device. Since it's loopback, the kernel won't care about > headers. > > Yeah, I know: Quick & Dirty. > > I made the new loopback put its packets

Re: artificial latency for a network interface

2001-06-29 Thread Pekka Pietikainen
On Thu, Jun 28, 2001 at 11:29:38PM -0500, Burkhard Daniel wrote: I had a similiar problem once, and wrote a module that overwrote the loopback net device. Since it's loopback, the kernel won't care about headers. Yeah, I know: Quick Dirty. I made the new loopback put its packets in a

Re: artificial latency for a network interface

2001-06-29 Thread Maksim Krasnyanskiy
I wanted to do that using two tun devices. I had hoped to have a routing like this: - eth0 - tun0 - userspace, waiting queue - tun1 - eth1 yes, that works very well. A userspace app sits on top of the tun/tap device and pulls out packets, delays them and reinjects them. Right. And

Re: artificial latency for a network interface

2001-06-28 Thread Burkhard Daniel
I had a similiar problem once, and wrote a module that overwrote the loopback net device. Since it's loopback, the kernel won't care about headers. Yeah, I know: Quick & Dirty. I made the new loopback put its packets in a queue and then deliver them after a (adjustable) delay. If I can still

Re: artificial latency for a network interface

2001-06-28 Thread Andrew Morton
Andreas Schuldei wrote: > > to simulate a sattelite link, I need to add a latency to a > network connection. > > What is the easiest and best way to do that? > > I wanted to do that using two tun devices. > I had hoped to have a routing like this: > > <-> eth0 <-> tun0 <-> userspace, waiting

artificial latency for a network interface

2001-06-28 Thread David McWherter
I once solved this problem using the QoS qdisc facilites: http://edge.mcs.drexel.edu/GICL/people/udmcwher/dnt/DNT.html It works on 2.2 kernels as well. -david Andreas Schuldei writes: > to simulate a sattelite link, I need to add a latency to a > network connection. > > What is the

artificial latency for a network interface

2001-06-28 Thread Andreas Schuldei
to simulate a sattelite link, I need to add a latency to a network connection. What is the easiest and best way to do that? I wanted to do that using two tun devices. I had hoped to have a routing like this: <-> eth0 <-> tun0 <-> userspace, waiting queue <-> tun1 <-> eth1 I need to do it

artificial latency for a network interface

2001-06-28 Thread Andreas Schuldei
to simulate a sattelite link, I need to add a latency to a network connection. What is the easiest and best way to do that? I wanted to do that using two tun devices. I had hoped to have a routing like this: - eth0 - tun0 - userspace, waiting queue - tun1 - eth1 I need to do it this way

artificial latency for a network interface

2001-06-28 Thread David McWherter
I once solved this problem using the QoS qdisc facilites: http://edge.mcs.drexel.edu/GICL/people/udmcwher/dnt/DNT.html It works on 2.2 kernels as well. -david Andreas Schuldei writes: to simulate a sattelite link, I need to add a latency to a network connection. What is the

Re: artificial latency for a network interface

2001-06-28 Thread Andrew Morton
Andreas Schuldei wrote: to simulate a sattelite link, I need to add a latency to a network connection. What is the easiest and best way to do that? I wanted to do that using two tun devices. I had hoped to have a routing like this: - eth0 - tun0 - userspace, waiting queue - tun1 -

Re: artificial latency for a network interface

2001-06-28 Thread Burkhard Daniel
I had a similiar problem once, and wrote a module that overwrote the loopback net device. Since it's loopback, the kernel won't care about headers. Yeah, I know: Quick Dirty. I made the new loopback put its packets in a queue and then deliver them after a (adjustable) delay. If I can still