All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Sparks <asparks@doublesparks.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Forwarding connections/packets across interfaces
Date: Tue, 18 Apr 2006 02:12:52 +0000	[thread overview]
Message-ID: <44444B24.8000401@doublesparks.net> (raw)

Have a inter-interface routing issue, hoping someone can either throw a
clue or point me where I can get one.  This is on a CentOS 3 system.

Have interfaces eth0 and eth1.  eth0 is connected to internal network,
eth1 to separate distinct network.  The default route on the box is set
to the roter address on the eth1 network.  I have static routes defined
to send local network traffic to eth0 and eth0's router.

I have a mail server (and a test program as well) that binds to an
address on eth1, and tries to connect to an address on eth0's network.
Connections just time out.  I've tested connections where I did not bind
to a specific interface and I can make the connection.

I've set ip_forward=1, and rp_filter=0 on all interfaces, and still
cannot get a connection from eth1's address to something off of eth0's
networks.  Firewalls are disabled on the host.

Is there additional voodoo that needs to be set to allow traffic to
cross from one interface to the other?

Thanks in advance for any advice or pointers.  I hope I've made the
problem clear enough...
-Alan

-- 
Alan Sparks, UNIX/Linux Systems Integration and Administration
<asparks@doublesparks.net>



_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2006-04-18  2:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-18  2:12 Alan Sparks [this message]
2006-04-18  2:36 ` [LARTC] Forwarding connections/packets across interfaces Martin A. Brown
2006-04-18  3:28 ` Alan Sparks

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=44444B24.8000401@doublesparks.net \
    --to=asparks@doublesparks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.