Re: routing

[Pavel Maslov <pavel.masloff@gmail.com>]

Good! I will try CA Gateway. Thanks.

I can see that the latest release dates back to 2009. Does anybody know why is that so?

On Thu, Jan 10, 2013 at 3:39 PM, Ralph Lange <Ralph.Lange@gmx.de> wrote:

On 10.01.2013 08:35, Pavel Maslov wrote:

Hi,

I have an EPICS IOC (Linux) on the experimental field. Also, I have got a client PC (Windows) in the control room. Everything works fine.

I want to add some more clients. However, they will be on a different IP range (172.20.X.X). So in the Windows PC I have installed two NICs - one to connect to the IOC (IP range 192.168.0.X), and the other one for the clients (IP range 172.20.X.X).

How would you recommend to set up the network configuration on the Windows machine?

I remember, I once used a router, so I set up port-forwarding so the client PC would connect from the outside of the IOC subnet to the router on a specific port (EPICS_CA_ADDR_LIST=router:3333), which would then send packets directly to the IOC (192.168.0.2:5064). And it worked.

Now, I have two NICs which is similar to this.

Any thoughts?

Your questions translates as:
How do I set up a windows pc with two NICs as a router?
You might find some answers googling around, but I would not try to do this.

Instead, use a router. (That's the appropriate, good solution.)
Or, run a CA Gateway [1] on the windows machine, that forwards CA data to the outside clients. (That should work, too.)

Cheers,
~Ralph

[1] http://www.aps.anl.gov/epics/extensions/gateway/index.php

--
Best regards,


Pavel Maslov, MS
Controls Engineer at Pulsed power Lab
Efremov Institute for Electro-Physical Apparatus
St. Petersburg, Russia

Mobile: +7 (951) 672 22 19
Landline: +7 (812) 461 01 01