From: Julian Anastasov <ja@ssi.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] routing problem AAAAAHH!!
Date: Tue, 10 Dec 2002 14:21:29 +0000 [thread overview]
Message-ID: <marc-lartc-103953018026708@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103951702215436@msgid-missing>
Hello,
On Tue, 10 Dec 2002, Luis Miguel Cruz Miranda wrote:
> My main table is:
> # ip ro ls
> 194.149.216.0/24 dev vlan2 scope link
> 10.1.0.0/24 dev eth0 scope link
> 127.0.0.0/8 dev lo scope link
> default via 10.1.0.254 dev eth0
>
> I have also these routes and rules:
> # ip ru ls
> 0: from all lookup local
> 32757: from all to 10.2.0.1 lookup 101
> 32758: from all to 194.149.216.3 lookup 21
> 32759: from all to 194.149.216.2 lookup 21
> 32760: from all to 194.149.216.1 lookup 21
> 32761: from all to 10.10.10.0/24 lookup main prohibit
> 32762: from 10.2.0.1 lookup 100
> 32763: from 194.149.216.3 lookup 20
> 32764: from 194.149.216.2 lookup 20
> 32765: from 194.149.216.1 lookup 20
> 32766: from all lookup main
> 32767: from all lookup 253
>
> #ip ro ls table 20 && ip ro ls table 21
> default via 10.1.0.254 dev eth0
> 194.149.216.2 dev vlan2 scope link
> 194.149.216.3 dev vlan2 scope link
> 194.149.216.1 dev vlan2 scope link
>
> Why 194.149.216.5 is reachable from internet?
Yes, it is reachable:
from 1.2.3.4 to 194.149.216.6 hits rule 32766, table main:
194.149.216.0/24 dev vlan2 scope link
> Luis Miguel Cruz Miranda.
> CCNA - Systems Administrator
Regards
--
Julian Anastasov <ja@ssi.bg>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-12-10 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 10:41 [LARTC] routing problem AAAAAHH!! Luis Miguel Cruz Miranda
2002-12-10 14:21 ` Julian Anastasov [this message]
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-103953018026708@msgid-missing \
--to=ja@ssi.bg \
--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.