From: "Ángel Carrasco" <falkom@arrakis.es>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] NETWORK ROUTES
Date: Thu, 24 Oct 2002 20:18:33 +0000 [thread overview]
Message-ID: <marc-lartc-103549058828109@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103544439008094@msgid-missing>
My little route only manage the range 172.16.16.0/24 and my public route
only manages the range 213.250.143.240/28. I cannot add new rules because
these routers are administer by other company and this company cannot
colaborate me.
Please can you help me, please?
Ángel
-----Mensaje original-----
De: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]En
nombre de Stef Coene
Enviado el: jueves, 24 de octubre de 2002 21:58
Para: Ángel Carrasco; lartc@mailman.ds9a.nl
Asunto: Re: [LARTC] NETWORK ROUTES
On Thursday 24 October 2002 14:29, Ángel Carrasco wrote:
> Ok:
>
> My office network is: 172.16.16.0/24 and his IP is: 172.16.16.1.
> My web network is: 172.16.8.0/24 and his IP is: 172.16.8.1
> My service network is: 172.16.4.0/24 and his IP is: 172.16.4.1
> My public network is:213.250.143.240/28 and his IP is: 213.250.143.242.
>
> The public router is 213.250.143.241 (and only works with the range
> 213.250.143.240/28)
> The office router is 172.16.16.254 (and only works with the range
> 172.16.16.0/24)
>
> The static default route is 172.16.16.254
>
> This is my route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 213.250.143.240 0.0.0.0 255.255.255.240 U 0 0 0
> eth0 172.16.4.0 0.0.0.0 255.255.255.0 U 0 0
> 0 eth1 172.16.16.0 0.0.0.0 255.255.255.0 U 0 0
> 0 eth3 172.16.8.0 0.0.0.0 255.255.255.0 U 0 0
> 0 eth2 0.0.0.0 172.16.16.254 0.0.0.0 UG 0 0
> 0 eth3
>
> And my dinamic route to using the public network is:
> ip rule add from 213.250.143.242 table publica
> ip route add from default via 213.250.143.241 dev eth0 table publica
> ip route flush cache
>
>
> And the problem is when I try to use 213.250.143.242 in my internals
> networks doesnt run because the information goes by 213.250.143.241 and
not
> in the normal routes.
I suppose you pinged from on of your internal hosts to 213.250.143.242 ??
213.250.143.242 is local, so no routing rule will route the packets to
somewhere else.
>
> Can you help me, please?
I'm not a rouing specialist, but shouldn't your default gateway be
213.250.143.24 ??
And I suppose you already enabled ip-forwarding?
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-10-24 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 7:23 [LARTC] NETWORK ROUTES Ángel Carrasco
2002-10-24 11:45 ` Stef Coene
2002-10-24 12:29 ` Ángel Carrasco
2002-10-24 19:57 ` Stef Coene
2002-10-24 20:18 ` Ángel Carrasco [this message]
2002-10-28 5:40 ` Martin A. Brown
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-103549058828109@msgid-missing \
--to=falkom@arrakis.es \
--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