On Sun, 27 Oct 2002, Blars Blarson wrote:
> weasel@debian.org writes:
>
> >I've the following setup:
> >
> > 10.200.118.0/24 (internal)
> > |
> > |
> > | eth0:10.200.118.1
> > +--------+
> > | marvin |
> > +--------+
> > | eth1: 10.2.2.20
> > |
> > |
> > 10.0.0.0/8 (external)
> >
> >Now if a host on the external network sends an 'arp who-has
> >10.200.118.1' request marvin answers on eth1.
> >Is there any way to _stop_ that behaviour?
>
> I assume what you realy want is eth1 to have all of 10.0.0.0/8 except
> 10.200.118.0/24. This is possible but ugly. Better solutions in most
> cases involve either renumbering one of the networks (the
> 172.16.0.0/12 range is available in most cases) or putting a more
> restrictive netmask on eth1.
Such a setup is quite possible and if you come to think about it, it's
not much different from having say 192.168.25.0/24 on one side and
0.0.0.0/0 on the other. One is a real subset of the other.
Therefore the routing table is checked in the order of longest prefix
first. Splitting the routes is not necessary (and would not help).
My problem is one layer below: arp. From the description the hidden
patch suggested by Emmanuel looks promising. I will have to try it
tomorrow.
yours,
peter
--
PGP signed and encrypted | .''`. ** Debian GNU/Linux **
messages preferred. | : :' : The universal
| `. `' Operating System
http://www.palfrader.org/ | `- http://www.debian.org/
Attachment:
pgpT_U4oBKS71.pgp
Description: PGP signature