Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "andybr" <andybr@bol.com.br>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Simulation with Packet Lost and Packet Delays (How toset
Date: Wed, 24 Dec 2003 21:13:15 +0000	[thread overview]
Message-ID: <marc-lartc-107230204206871@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107202103804758@msgid-missing>


Did you try a traceroute from subnet so you can see 
where fails because if you a linux box with two nics, 
eth0: 192.168.0.1/24 and eth1: 192.168.1.1/24, behind 
the linux computer A: 192.168.0.2/24 gw 192.168.0.1, 
computer B: 192.168.1.2/24 gw 192.168.1.1, you must be 
able to ping from a to b or vice-versa unless if you set 
a rule to not do it. Check it out and return.

[]´s
Anderson



> 
> >From: Stef Coene <stef.coene@docum.org>
> >To: tony.cheung@asiayeah.com,
> >	Tony Yat-
Tung Cheung <dragonman@asiayeah.com>, lartc@mailman.ds9a.
nl
> >Subject: Re: [LARTC] Simulation with Packet Lost and P
acket Delays
> >Date: Mon, 22 Dec 2003 17:03:27 +0100
> >
> >On Sunday 21 December 2003 16:31, Tony Yat-
Tung Cheung wrote:
> >  
> >
> >>Hi All,
> >>
> >>I would like to be able to simulate network congestio
n and delay on
> >>tcp/udp connections between two hosts. I would need t
o simulate packet
> >>lost and packet delay.
> >>
> >>I think I would need to use a Linux box with two netw
ork cards to act as
> >>a pass-
through ethernet bridge. Is it the case? Does this how-
to guide
> >>provides good information in this area?
> >>    
> >>
> >http://snad.ncsl.nist.gov/itg/nistnet/
> >
> >Stef
> >  
> >
> Hi Stef and others,
> 
> Thanks. The NISTNET looks like a very decent package. I
 have tried it 
> briefly on a Red Hat 7.2 and it seems to work fine.
> 
> I have another basic question and I would if anyone cou
ld help me out.
> 
> Basically, I am trying a setup a Linux router between t
wo local subnets, 
> 192.168.0.1/24 and 192.168.1.1/24. My Linux box has two
 ethernet cards, 
> eth0 has IP address 192.168.0.1 (subnet mask 255.255.25
5.0) and eth1 has 
> IP address 192.168.1.1 (subnet mask: 255.255.255.0). No
w I wish my Linux 
> box to be able to route traffic between eth0 and eth1.
> 
> I have modified '/etc/sysctl.conf' to,
> 
> # Controls IP packet forwarding
> net.ipv4.ip_forward = 1
> 
> However, it doesn't seem to work right now. Is there an
ything else I 
> need to do? I wish to set it up quickly and would appre
ciate any advice!
> 
> Thank you.
> 
> Best Regards,
> Tony Cheung
> 
> 
> 
> 
> 

 
__________________________________________________________________________
Acabe com aquelas janelinhas que pulam na sua tela.
AntiPop-up UOL - É grátis!
http://antipopup.uol.com.br/


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2003-12-24 21:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-21 15:31 [LARTC] Simulation with Packet Lost and Packet Delays Tony Yat-Tung Cheung
2003-12-22 16:03 ` Stef Coene
2003-12-24  9:02 ` [LARTC] Simulation with Packet Lost and Packet Delays (How to Tony Yat-Tung Cheung
2003-12-24 21:13 ` andybr [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-107230204206871@msgid-missing \
    --to=andybr@bol.com.br \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox