sorry bout that..
You need to somehow have a listening interface on the same subnet as the windows machines. Since you need to listen on two networks at the same time you must have routes:
broadcasts do not cross broadcast domains and networks are the delimiters of broadcast domains.
Make sense?
In linux to set up routing you must (at least):
echo 1 > /proc/sys/net/ipv4/ip_forward; to enable
forwarding packets if you will route from network to network.
your linux ethernet interface can be aliased, or
subinterfaced with a command similar to this:
ifconfig eth0:1 ip address netmask state
where ifconfig is the command ; eth0:1 is the subinterface,
address is the ip address, netmask is the subnet mask; and
state is up or down. Very flexible.
So if i were in your shoes i would create a subinterface to listen on the target network, route packets, and
run the routed daemon with the -t option if i had trouble
seeing where my routes needed to be, or jut run routed anyway as a dynamic routing solution.
I have had so-so luck with routed, but it has often shown me oversights in my routing that i was able to fix manually.
Try this url:
on the windows side:
I would (as explained above)use linux as my router.
It is the only way to do it in this situation unless
you are using win2k/nt for proxy/routing..in which case
you only need to connect to the local linux subinterface for your ftp and telnet needs.
I am assuming throughout this that there is some
really important reason for your linux machine not to be on the same subnet as the windows machines....if there
isn't just configure linux on the same subnet,
or if you are using dhcp run the dhcp client for linux.
