From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] [LARTC]Routing problem !!!
Date: Mon, 01 Dec 2003 07:19:57 +0000 [thread overview]
Message-ID: <marc-lartc-107026327203529@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106989922827966@msgid-missing>
: This is my configuration:
:
:
: eth0: 10.0.0.2/16
: eth1: 10.0.0.1 (inet gateway)
:
: #ip ru l :
:
: 0: from all lookup local
: 32765: from 10.0.0.2 lookup tabla1
: 32766: from all lookup main
: 32767: from all lookup default
:
:
: #ip r l t tabla1
:
:
: 10.0.0.0/16 dev eth0 scope link src 10.0.0.2
: 127.0.0.0/8 dev lo scope link
: default via 10.0.0.1 dev eth0
:
: #ip r l t main
:
: 10.0.0.0/16 dev eth0 scope link
[ local routing table snipped ]
: why can't i connect to inet ??
Probably because your router doesn't have a way to send packets to
10.0.0.1 even if the source address on the outbound packet is 10.0.0.2.
Add one more route to tabla1:
# ip route add 10.0.0.1 dev eth1 table tabla1
# ip route change default via 10.0.0.1 dev eth1 table tabla1
Once you can ping 10.0.0.1 from your policy routing device, then you
should be able to hit the Internet from the same device.
You didn't explain anything about what applications or functions this box
hosts, so there's nothing more to say here.
-Martin
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-12-01 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 1:50 [LARTC] [LARTC]Routing problem !!! Vaquer0
2003-12-01 7:19 ` Martin A. Brown [this message]
2003-12-01 13:25 ` Vaquer0
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=marc-lartc-107026327203529@msgid-missing \
--to=mabrown-lartc@securepipe.com \
--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.