LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Setting up Fieldpoint ethernet for Internet access

Highlighted
Besides NAT and routing issues, are there any other hurdles?

Anyone with experiance?

Thanks,

Martin
0 Kudos
Message 1 of 3
(1,074 Views)
Highlighted
The other things you need to be concerned with are security and firewall configurations for the module.

For security, if you are using a FP-1600, security is added on in firmware revision 0410 downloadable from ftp.ni.com/support/fieldpoint/Update/FPEthernet0410.zipand FieldPoint Explorer 3.0.0. For FP-20XX series modules, security is supported in all released versions.

For information on configuring firewalls for use with FieldPoint Ethernet Modules, please look at the following document. Whereas the title implies that it is for Lookout and the LabVIEW-Datalogging and Supervisory Module only, the information also applies to FieldPoint Ethernet systems.
http://zone.ni.com/devzone/conceptd.nsf/2d17d611efb58b22862567a9006ffe76/7d0e7f20b1a7c8e486256a39005747
f2?OpenDocument

Regards,
Aaron
0 Kudos
Message 2 of 3
(1,073 Views)
Highlighted
Thanks for the info, although a little general.
I'm sure the IT guys know exactly what to do, if they know thier stuff.

I did find out if the field point module is behind a firewall, it may be
possible to use NAT port mapping to send the client data (controlling
application) thru the fire wall to the fieldpoint on the internal network.
Accesing a mapped port sends the incomming packet to a the matching local IP
entry in the mapping table. This is, of course, if we know the port number
the field point communicates on. This may also be considered 'Rules' in some
proxy products, but I really don't know at this point.
Otherwise, NAT and proxy servers do not allow incomming packets to go to the
field point (hence a firewall). They only wrap the outbound packets with the
registered IP of the ISP, and unwrap the incomming packets(replys) and send
them back to the machine that sent the request. Again this translation info
is kept in a dynamic table.

I was also suggested that a seperate server could be used, much like Yahoo
messanger and AOL. Where the server keeps a dynamic table of all clients and
their IP's. So the Client application would lookup the ip of a registered
field point module that has checked into the server, getting the return path
thru the proxy that the field point is using. But this would require extra
hardware, and would rely on that 2nd server to make the connection. This
would not work for us, I need something simple and fairly easy to implement.
This is mainly because of the interaction with the IT crew of the
customer(s).

Martin

"Aaron G" wrote in message
news:506500000005000000DB5B0000-1011517314000@exchange.ni.com...
> The other things you need to be concerned with are security and
> firewall configurations for the module.
>
> For security, if you are using a FP-1600, security is added on in
> firmware revision 0410 downloadable from
> ftp.ni.com/support/fieldpoint/Update/FPEthernet0410.zipand FieldPoint
> Explorer 3.0.0. For FP-20XX series modules, security is supported in
> all released versions.
>
> For information on configuring firewalls for use with FieldPoint
> Ethernet Modules, please look at the following document. Whereas the
> title implies that it is for Lookout and the LabVIEW-Datalogging and
> Supervisory Module only, the information also applies to FieldPoint
> Ethernet systems.
>
http://zone.ni.com/devzone/conceptd.nsf/2d17d611efb58b22862567a9006ffe76/7d0
e7f20b1a7c8e486256a39005747f2?OpenDocument
>
> Regards,
> Aaron
0 Kudos
Message 3 of 3
(1,072 Views)