All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Gallati <lartc@draxinusom.ch>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] large routing table
Date: Wed, 31 Mar 2004 21:01:11 +0000	[thread overview]
Message-ID: <406B3197.9020206@draxinusom.ch> (raw)
In-Reply-To: <4069FB34.6000507@draxinusom.ch>

Hello,

 > this is exactly why ip addresses are already grouped with respect to 
location.
 >
 > So it should be possible to optimize things, maybe use some perl with 
http://search.cpan.org/~nwetters/IP-Country-2.15/lib/IP/Country.pm
 > e.g. 194.0.0.0/8 is NL


Nope its not, I have 919 prefixes starting with 194 which are located in 
Switzerland. And they really are, for example picking one out randomly:

nslookup 194.242.34.1 yields:

Name:    switch.swissix.ch
Address:  194.242.34.1

whois:
inetnum:      194.242.34.0 - 194.242.34.255
netname:      SWISSIX
descr:        swissix, Swiss Internet Exchange
country:      CH
admin-c:      MC322-RIPE
tech-c:       MC322-RIPE
status:       ASSIGNED PI
notify:       noc@sissix.ch
mnt-by:       RIPE-NCC-HM-PI-MNT
mnt-by:       SWISSIX-MNT
mnt-lower:    RIPE-NCC-HM-PI-MNT

To the best of my knowledge, region based IP-ranges are in IPv6 but not 
in IPv4.

 > And I guess you can afford to make some errors, e.g. shaping a 
destination which shouldn't be shaped is not a crime if it wouldn't 
happen too often, just make sure you shape foreign IP's, how bad would 
it be to shape some non-foreign IP's accidently?


Problem is the server runs several applications and mine is but one of 
it. I am to make as little trouble as possible. However I do have a very 
good list of which IP ranges are ok and the complement are those that 
are not. My list comes directly from a skript that pulls it out of the 
core router.

Some of the prefixes can be aggregated but that is a minor optimization.

 > And, ofcourse, either "foreign IP's" or "non foreign IP's" is the 
smallest list, use the samllest list.


I have only the non-foreign list, but I am very sure that this one is 
smaller than the rest of the internet

Its exactly 6486 prefixes atm. (without aggregating those that are 
possible). In any case too many to process linearly.

CU

René



_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-03-31 21:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-30 22:56 [LARTC] large routing table Rene Gallati
2004-03-31  1:06 ` alex
2004-03-31  1:25 ` alex
2004-03-31  1:26 ` Roy
2004-03-31  1:45 ` Roy
2004-03-31  9:50 ` Jeroen Vriesman
2004-03-31 10:26 ` Jeroen Vriesman
2004-03-31 21:01 ` Rene Gallati [this message]
2004-03-31 21:19 ` Rene Gallati
2004-03-31 21:24 ` Rene Gallati
2004-03-31 21:32 ` Rene Gallati
2004-03-31 21:41 ` Adrian Vasile

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=406B3197.9020206@draxinusom.ch \
    --to=lartc@draxinusom.ch \
    --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.