Hi!
Am Sam, 21 Apr 2001 schrieb Fred Wright:
> Proxy ARP is a kludge alternative to proper subnet routing. Let's say you
> have a system connected via a serial link to another system that's also on
> your LAN. There are two ways to make this work:
>
> 1) Put the serial IPs in a different subnet from the LAN, and make sure
> that other systems on the LAN are aware that the LAN<->serial machine is
> the gateway to the serial machine's IP. If the LAN<->serial machine is
> also the default gateway, this is pretty much automatic, but otherwise it
> requires some manual routing, at least on the default gateway, and perhaps
> elsewhere.
My LAN is on 192.168.0.0 eth0. Now I want to make it possible for a caller
from outside to connect to the router on 192.168.2.3. Therefore the router
has also the IP 192.168.2.3 listening on the modemport.
A caller from outside logs in using ppp and gets the IP 192.168.2.41.
Now to make it possible to him to see the LAN, I must do some routing?
The routingtable looks like this:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.2.3 0.0.0.0 UG 0 0 0 ppp0
Should this be ok and I don´t have to use proxyarp?
> 2) Put the serial IPs in the same subnet as the LAN, and configure the
> LAN<->serial machine to answer ARP requests for the serial IP, supplying
> its own Ethernet address. Then it appears to other machines on the LAN to
> be directly connected to the LAN. This is called Proxy ARP, and has some
> disadvantages with respect to broadcast handling and things like
> traceroute, but it's an alternative if #1 doesn't work.
So you say proxyarp is only needed, if the router and the LAN are on the
same subnet and I don´ t want to do manual routing?
regards
--
Andreas Meyer http://home.wtal.de/MeineHomepage
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
