# Using Raspberry Pi as a NAT

**URL:** <https://forum.inductiveautomation.com/t/using-raspberry-pi-as-a-nat/8268>\
**Category:** Archived Topics\
**Created:** [April 7, 2014, 11:39am UTC](https://forum.inductiveautomation.com/t/using-raspberry-pi-as-a-nat/8268 "2014-04-07T11:39:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brett\_Yeomans](https://avatars.discourse-cdn.com/v4/letter/b/35a633/32.png) [@Brett\_Yeomans](https://forum.inductiveautomation.com/u/Brett_Yeomans)\
**Post date:** [April 7, 2014, 11:39am UTC](https://forum.inductiveautomation.com/t/using-raspberry-pi-as-a-nat/8268/1 "2014-04-07T11:39:49Z")

</div>

Perhaps not a question related directly to Ignition but…  
I have a Raspberry Pi and wanted to use it to NAT to a different network (what the 9300-NAT does but at 1/10th the cost.  
Using the PREROUTING command I can ping the PLC, RSLinx see’s it and I can go online and edit through the Pi across two networks.  
(Using POSTROUTING as well seems to have no additional affect)  
I even tried Kepware and that has no problem seeing it and can read and write to the PLC through the NAT.

The problem is Ignition will not connect. Wireshark shows a pattern of RST (resets I believe??) highlighted in red. The info for these are all ‘Ethernet-IP-2’ etc etc, protocol TCP.  
Complete NooB at Linux and networking for that matter.  
Tried a couple of Linux forums with no luck, hoping someone may shed some light on it ![:scratch:](https://us1.discourse-cdn.com/inductiveautomation/original/1X/76d1620bec252bfac07050c889ff5a91dc8a9c25.gif ":scratch:")