All of lore.kernel.org
 help / color / mirror / Atom feed
From: ben soo <lnx-kern@soo.com>
To: "Carlos Narváez" <crakup@gmail.com>,
	"Kernel Mailing list" <linux-kernel@vger.kernel.org>
Subject: Re: Linux Router
Date: Sat, 22 Sep 2007 22:10:16 -0400	[thread overview]
Message-ID: <46F5CB08.9060108@soo.com> (raw)
In-Reply-To: <e660b2250709221609l1475c061t5a1a78de4fa529f@mail.gmail.com>

i used to add proxy arp's on the router when i had problems like 
this.  Dunno if it's the recommended fix, but it worked.

http://en.wikipedia.org/wiki/Proxy_arp

Carlos Narváez wrote:
>  This is starting to frustrate me, because it should be much simpler
> than it seems to be, and I feel like I'm missing something small and
> obvious.
> 
> I have two private networks, we'll say 192.168.254.0/24 and
> 192.168.251.0/24. And I have a linux box in the middle with addresses
> 192.168.254.17 and 192.168.251.10:
> 
> 
> +---------------+ . +----------------+
> ¦ 192.168.251.1 +---+ 192.168.251.10 ¦ . +----------------+
> +---------------+ . ¦ 192.168.254.17 +---+ 192.168.254.16 ¦
> . . . . . . . . . . +----------------+ . +----------------+
> 
> 
> There is no NAT involved.. I just want the box in the middle to pass
> traffic between the two networks. Here is what I have done:
> 
> - IP Forwarding has been enabled on the router via "echo 1 >
> /proc/sys/net/ipv4/ip_forward"
> 
> - A route has been configured on 192.168.251.1 to point all traffic
> for 192.168.254.0/24 to 192.168.251.10.
> 
> - A route has been configured on 192.168.254.16 to point all traffic
> for 192.168.251.0/24 to 192.168.254.17.
> 
> - The command "iptables -I FORWARD -j ACCEPT" has been executed.
> 
> Now.. here's what happens. 192.168.251.10 can ping both interfaces on
> the router. 192.168.254.16 can also ping both interfaces on the
> router. However, 192.168.251.1 cannot ping 192.168.254.16, and
> likewise, 192.168.254.16 cannot ping 192.168.251.1.
> 
> What have I forgotten?
> 


  parent reply	other threads:[~2007-09-23  2:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-22 23:09 Linux Router Carlos Narváez
2007-09-22 23:38 ` Not kernel dev related story (Re: Linux Router) Oleg Verych
2007-09-23  2:10 ` ben soo [this message]
2007-09-23  6:25   ` Linux Router Jan Engelhardt
2007-09-23  6:39 ` Benny Amorsen
  -- strict thread matches above, loose matches on Subject: below --
2005-02-06 17:36 spdesai
2005-02-06 19:46 ` Jason Opperisano
2005-02-07 20:43 ` srg
     [not found] <F4D3DB9A18752A4F99FD880ABC5407179D136B@ccdc-exchg.careerco mmunity.com>
2002-05-20 17:49 ` Linux router Ray Olszewski
2002-05-20 10:59 Sridhar J
2002-05-20 20:38 ` Petre Bandac
2002-05-21  0:57 ` Vince Coen

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=46F5CB08.9060108@soo.com \
    --to=lnx-kern@soo.com \
    --cc=crakup@gmail.com \
    --cc=linux-kernel@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.