From: Danny <dineshg@hostway.com>
To: Javier A Toledano <jatoledano@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Multihoming problem
Date: Wed, 06 Dec 2006 11:52:08 +0530 [thread overview]
Message-ID: <45766190.8040607@hostway.com> (raw)
In-Reply-To: <b06b831a0612051527p15895c7yd0b1d9bb813c4105@mail.gmail.com>
Hi,
Well, I have done this !
What does route -n say ?
You would just need one iptable rule for masquerading outgoing requests
through eth1. Do you have anything else ?
At 10.0.0.X host, do route -n : [ from where you are not able to ping to
192.168.0.X ]
- Danny
Javier A Toledano wrote:
> Hello To everyone:
>
> I've setup a linux box with 3 ethernet cards.
> One in the 10.0.0.0/8 net in the eth0,
> the other in the 192.168.10.0/24 in the eth2 and
> the other is connected to dsl modemwith with eth1.
>
> I've setup forwarding with, net.ipv4.ip_forward = 1.
> A strange phenomenon happens that I don't understantd. When I make an
> echo request from a host in the net 10.0.0.0 to a host in the
> 192.168.10.0 the packet arrives to the eth0 interface but it seems
> that it doesn't traverse the linux because with tcpdump I see no icmp
> packet in eth2
> But when a make an echo request from the 192.168.10.0 to a host in
> 10.0.0.0 , I receive the echo reply and, inmediatley the echo request
> originated in 10.0.0.0 receives the echo replies from 192.168.10.0.
>
> If would appreciate any idea, Sorry for my poor English.
>
> Thanks in advance
>
>
prev parent reply other threads:[~2006-12-06 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 23:27 Multihoming problem Javier A Toledano
2006-12-06 6:22 ` Danny [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=45766190.8040607@hostway.com \
--to=dineshg@hostway.com \
--cc=jatoledano@gmail.com \
--cc=netfilter@lists.netfilter.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