Rune Frøysa wrote:
> > b) configure the Linux box to perform proxy-ARP for the NT box, i.e.
> >
> > arp -i eth0 -Ds 129.240.186.y eth0 pub
>
> It works! Almost. I can communicate with everyone that is not on the
> 186 net, in both directions. The NT box has IP 129.240.186.39, Netmask
> 255.255.254.0, default gw 10.0.0.1
>
> Pinging from 129.240.186.32 gives on eth0:
> 14:15:24.858122 129.240.186.32 > 129.240.186.39: icmp: echo request
> on eth1:
> 14:16:02.218759 129.240.186.32 > 129.240.186.39: icmp: echo request
> 14:16:02.219069 arp who-has 129.240.186.32 tell 129.240.186.39
>
> This arp is not seen on eth0
Right. The NT box thinks that it can talk to .32 directly.
You may need to specify a gateway route to the 129.240.186.0 network.
If the gateway is using 10.0.0.1, you will also need to specify a
route for that. On Linux you would use:
route add -net 10.0.0.0 dev eth0
route add -net 129.240.186.0 gw 10.0.0.1
I don't know the syntax for NT's route command (it does have one). I
don't think that you can set this up using the control panel.
OTOH, you may be able to use proxy-ARP instead, i.e.
arp -i eth1 -Ds 129.240.186.0 eth1 netmask 255.255.255.0 pub
> Another wierdness is that pinging from
> the linux box is shown as:
> 14:22:37.120064 0.0.0.0 > 129.240.186.39: icmp: echo request
This may be caused by the fact that the ifconfig command is incorrect.
> These commands have been run on the linux box:
>
> /sbin/ifconfig eth1 10.0.0.1 broadcast 10.0.0.255 netmask 255.0.0.0 up
This is wrong. If the netmask is 255.0.0.0, the broadcast address
should be 10.255.255.255. However, that shouldn't affect non-broadcast
traffic.
> /sbin/route add -host 129.240.186.39 metric 0 eth1
> /sbin/arp -i eth0 -Ds 129.240.186.39 eth0 pub
> echo "1" > /proc/sys/net/ipv4/ip_forward
This is OK.
--
Glynn Clements <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
