--- Benjamin Scott <[EMAIL PROTECTED]> wrote:
For example, I've got two
hosts on my ethernet LAN. One is a Windoze
machine with address 192.168.10.5,
the other is my Linux machine with
192.168.10.1 for the address. I can ping
either box right now. But if I do
the following:
# ifconfig eth0
192.168.20.1
# route add -net 192.168.10.1 netmask 255.255.255.0 dev eth0
...
then I can no longer pass traffic between the two.
--- end of quote ---
Well,
you'd have to set a similar route up on the Windows box
as well, otherwise the
packets will get there, but not return.
I don't think it would matter, but you
might want to use the
network address of 192.168.10.0 instead of 192.168.10.1
in the
route add -net line (makes it clearer)
So if you do the above on the
linux box, and:
route add 192.168.20.0 MASK 255.255.255.0 192.168.10.2
on
the Windows box, they ought to be able to talk to one another
without a
"gateway" configured to "route" the packets.
I haven't tried it, but it
should work. I'll have to experiment
at home (I'm not interested in doing
that on our production network
at work just yet :-).
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
