Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Taylor, Grant" <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Routing Problem
Date: Wed, 13 Dec 2006 15:05:34 +0000	[thread overview]
Message-ID: <458016BE.9010005@riverviewtech.net> (raw)
In-Reply-To: <marc-lartc-101530055025659@msgid-missing>

Javier A Toledano wrote:
> Routing Problem

<snip>

> The problem is that forwarding is enabled but when I try to probe
> connectivity from a host in the 10.0.0.0 net , eg 10.0.0.1 making an
> echo request
> to a host in 192.168.10.0 net , eg 192.168.10.49 the icmp packets
> arrive to the linux box (interface eth0) but don't traverset it.
> After I iniate an echo request from 192.168.10.49 to 10.0.0.1, the
> packets iniatated in 10.0.0.0 net starts to traverse the router
> magically.
> It seems that It needs a packet from the 192.168.10.0 to start working.
> 
> I would appreciate any idea.

I'm not a CentOS user so I can not say for sure.  However I would expect
that (despite what you say) that there is some sort of IPTables stateful
packet inspection going on from your 10/ network to your 192.168/
network.  If this is indeed the case and the rule is a basic state of
ESTABLISHED, RELATED, then any traffic from 10/ to 192.168/ AFTER you
sent traffic from 192.168/ to 10/ would be considered RELATED and thus
allowed through.

However, if as you say, there are no IPTables rules in play at all
something else is interfering with your traffic, what it would be, I'm
not sure.

Try running iptables-save to make sure that there are absolutely no
rules in effect any where.



Grant. . . .

(Reposted to the mailing list verses directly back to the OP.)
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2006-12-13 15:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-05  3:55 [LARTC] routing problem suresh
2002-03-05 17:28 ` Ard van Breemen
2002-03-06  6:44 ` suresh
2002-11-20 17:31 ` [LARTC] Routing problem Mauro Cerboni
2002-11-22  0:03 ` Jose Luis Domingo Lopez
2002-11-22  0:32 ` George J. Jahchan, Eng.
2002-12-17 16:53 ` [LARTC] ROUTING Problem Andre Lorenz
2003-09-05 16:12 ` [LARTC] Routing problem gaston
2003-09-07 23:03 ` Damion de Soto
2003-09-08  6:41 ` Ronny Aasen
2003-09-08 14:46 ` gaston
2003-09-09 13:59 ` gaston
2003-11-10 12:29 ` [LARTC] routing problem Meretei Balázs
2003-11-10 23:55 ` Damion de Soto
2003-11-11  4:22 ` Martin A. Brown
2004-04-06 11:09 ` [LARTC] Routing problem huffo
2004-04-06 12:28 ` huffo
2004-04-06 23:32 ` Damion de Soto
2004-04-07  1:16 ` huffo
2004-04-07  1:26 ` huffo
2006-12-12 13:07 ` [LARTC] Routing Problem Javier A Toledano
2006-12-13 15:05 ` Taylor, Grant [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=458016BE.9010005@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --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