From: Frans Luteijn <f.a.g.luteijn@knoware.nl>
To: netfilter@lists.netfilter.org
Subject: Re: bidirectional forwarding
Date: Thu, 29 Jul 2004 07:04:27 +0200 [thread overview]
Message-ID: <4108855B.D7624DB2@knoware.nl> (raw)
In-Reply-To: D5C9032B2B09C64EA2409D6214E91AC90511FF@asimail2.alphanumeric.com
Jason Opperisano schreef:
> > PC1 R1 R2 R3 R4 PC2
> > |---------------| |-------| |--------| |--------| |-----------|
> > 192.168.10.2 .1 12.1 12.2 13.1 13.2 16.1 16.2 11.1 11.2
> > e0 e0 e1 e0 e1 e0 e1 e0 e1 e0
>
> assuming:
>
> default gw of pc1 is 10.1
> default gw of r1 is 12.2
>
> default gw of pc2 is 11.1
> default gw of r4 is 16.1
>
> both r2 & r3 will need static routes telling them how to get to networks 10 and 11:
>
> on r2:
>
> 192.168.10.0/24 via 192.168.12.1
> 192.168.11.0/24 via 192.168.13.2
How cat r2 reach your 16-network? you will need to add a routing for
that network to.
>
>
> on r3:
>
> 192.168.10.0/24 via 192.168.13.1
> 192.168.11.0/24 via 192.168.16.2
Same for r3, but now for your 12-network.
>
>
> the output of:
>
> ip route get 192.168.10.2
> ip route get 192.168.11.2
>
> on r2 and r3 should clue you in to where the packets are going.
>
> HTH...
>
> -j
Routingprotocols are designed for this kind of problem, to get this
resolved
automaticly. In this case you might look at zebra.
Regards,
--
Frans Luteijn
PGP PblKey fprnt=C4 87 CE AF BC B6 98 C1 EF 42 A1 9A E2 C0 42 5B
GPG PblKey fprnt=ED20 0F25 C233 DC59 3FFA 170E D0BF 15F5 0BA6 1355
next prev parent reply other threads:[~2004-07-29 5:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 13:13 bidirectional forwarding Jason Opperisano
2004-07-29 5:04 ` Frans Luteijn [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-29 12:05 Jason Opperisano
2004-07-28 1:20 Itrat Rasod Quadri
2004-07-28 10:41 ` Antony Stone
2004-07-29 17:46 ` James Sneeringer
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=4108855B.D7624DB2@knoware.nl \
--to=f.a.g.luteijn@knoware.nl \
--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