From: Brendan Alderslade <balderslade@tbs.com.au>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Am I on the right Track?
Date: Tue, 15 Jan 2002 00:52:09 +0000 [thread overview]
Message-ID: <marc-lartc-101105592919269@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101101729200399@msgid-missing>
Sahil,
I'm assuming your network looks like this (appologies for bad ascii
graphics):
10.0.0.0/24 210.54.149.160/27
NET---[cisco]---------------[linux box]-----LAN/DMZ
Is that correct?
If so, your cisco needs to route 210.54.149.160/27 via 10.0.0.2 (eth0 on the
linux box), and your Linux box needs a default route via 10.0.0.1 so traffic
goes out via the cisco (if that is your default route!)
And that's it. There is no reason to add a route to the 210.54.149.160/27
range on the Linux box because it is directly connected to eth1.
> -----Original Message-----
> From: Sahil Gupta - NET4U [mailto:sahil@sahil.net.nz]
> Sent: Tuesday, January 15, 2002 12:39 PM
> To: lartc@mailman.ds9a.nl
> Subject: [LARTC] Am I on the right Track?
>
>
> Hi there,
> Is it possible to somehow have a fairly basic routing level
> in order to forward packets from eth1 to eth0? Simply using "route"?
>
> I have a Cisco that has a local network IP. It is on eth0
> interface. I have a Switch on eth1. I want to supply eth1
> with a Real World IP which comes through the Cisco.
>
> Any guidance available?
>
> I assigned 10.0.0.2 on eth0 and 210.54.149.189 on eth1.
> then I did this:
> route add -net 10.0.0.0 netmask 255.255.255.0 gw 10.0.0.1 dev
> eth0 route add -net 210.54.149.160 netmask 255.255.255.224 gw
> 10.0.0.1 (which says network unreachable)
>
> Could someone please tell me how I could solve this?
>
> Regards,
>
> Sahil Gupta
> NET4U Limited
>
> ------------------------------------
> NET4U -- www.net4u.co.nz
> Home of the new - $24.95 128k ADSL
> Nationwide Internet Service Provider
> ------------------------------------
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc > HOWTO:
> http://ds9a.nl/lartc/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2002-01-15 0:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 14:08 [LARTC] Am I on the right Track? Sahil Gupta - NET4U
2002-01-15 0:52 ` Brendan Alderslade [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-14 1:44 [LARTC] am i on the right track ? Chandrashekhar Joshi
2002-01-14 9:44 ` Martin Devera
2002-01-14 12:38 ` Chandrashekhar Joshi
2002-01-14 12:52 ` Martin Devera
2002-01-14 12:57 ` Rob Kaper
2002-01-14 13:01 ` Martin Devera
2002-01-14 13:04 ` Rob Kaper
2002-01-14 13:18 ` Martin Devera
2002-01-14 13:57 ` Chandrashekhar Joshi
2002-01-16 9:39 ` Martin Devera
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-101105592919269@msgid-missing \
--to=balderslade@tbs.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox