On
11/3/2013 1:29 PM, Jonathan Leslie wrote:
"He has two legacy
boxes with the same fixed IPs that
can't be changed."
Exactly.
I actually have four legacy boxes
with the address 1.1.1.101. I want a C
program or programs for the ts-7800
that can individually talk to each of
the legacy devices through the 4 ports
of the ts-7800.
So I
want to know if on the ts-7800 can I
set up 4 IP
stacks/SOCK/iptables/whatever so that
I can have a 4 different networks,
lets call them A, B, C, and D, all on
the same ts-7800.
so I
should be able to have a c program of
the sort:
talk_to_legacy_device
-n[A|B|C|D] -i[1.1.1.101] -m"message"
where
on
all 4 networks, I have established
that my node is 1.1.1.200.
when
I use talk_to_legacy_device, the -n
parameter lets the c program know
which of the 4 networks I want to send
the message out on, and then also has
a listener on that same network for
the response from 1.1.1.101.
eventually
I will have 4 background processes all
listening on the four different
networks, for a communication from
their respective 1.1.1.101 legacy
system, and signal a command program
to format a response and have only
that one background process send the
reply.
So
can this arrangement be set up on the
ts-7800 or not???
Yes it can, I've done something similar with
a multi-home'd router, four interfaces, two
wan to lan and keep them separate from each
other. Do I remember how? No :) I
remember lots of iproute2 and iptables
reading tho. Big thing is you'll need
either four NIC's on the TS7800, or a VAN
capable switch (for size and price a Linux
based consumer router like a WRT54 would
work) to separate the networks. You then
block the networks for seeing each other
(iptables/iproute2) and bind your C app to a
specific interface. -n would be easiest to
take a Ethernet interface (eth0, eth0.1,
eth1, whatever) instead of a label.
What do these legacy devices do? Might it
be easier to re-implement them into a single
TS7800 ?
--
Jason Stahls