Re: [MEL-NAP] Putting AUIX local domains into squid

Hi,

I have the same situation here with the Philippines IX, which is here in
Manila where all the IPLs terminate.

> Thus, squid could interrogate the host's routing tables directly to
> determine the localness of a host, working on the basis that if the
> returned route is not 'default' it should be asked directly, and not
> through a parent. Running gated on the squid machine would thus manage
> the routing tables for squid.
>
> The only catch is that 'route' is suid root so that it can read the kernel
> routing tables, and thus a separate squid-routed would be needed to
> interrogate the tables on squid's behalf.

I would propose a hook to easily allow an external process to allow
the route computation. For your case you would want to query 'route',
but, that would require a gated peering with your routers or somehow
getting the route table info. I have suggested another solution.
This is an oversimplification on network right now:

PH-IX
  |
leased
 line
  |
router2
  |
router1---main cache----router0
                        | |
                       pacific ocean
                        | |
                     sprint mci

If I were to traceroute to a site, I know that once it crosses router0, it
is a foreign site. When it crosses router2, it's a local peer on the IX.
If I wanted to be more specific I would watch out for the routers of our
peers.

Thus we can have a tracerouter helper program - either one that calls
traceroute, or a hack of the original code - that has a list of gateways
to watch out for. Once it crosses a gateway, it returns a result. We also
give it a timeout value in milliseconds (500 is OK in our setup), and also
in hops, suh that if the packets go through an unexpected path we don't
wait for it to finish.

Thoughts?

-- 
miguel a.l. paraz  <map@iphil.net>                              +63-2-893-0850
iphil communications, makati city, philippines          <http://www.iphil.net>