NAT 1:1 on Flexy not working
Trying to get NAT 1:1 setup using Tim B's great setup guide and not having luck.
I'm trying to access both a Siemens PLC and an Automation Direct C-more HMI behing the Flexy via the Wan side.
I can access the PLC and HMI remotely just fine thru the cloud, but my customer's maintenance people want to get there also thru their plant WAN.
I have followed Tim's guide exactly and can't get it to work at all.
The Flexy's Wan port is on a static address 192.168.40.1. It's Lan ports are at 10.16.61.1.
The Siemens S7 PLC is on the Lan side as 10.16.61.10 and the HMI is 10.16.61.20.
I have Allow all traffic on Wan button checked.
I have Wan IP forwarding box checked.
I have Nat on Lan (Plug'n Route selected), and enable transparent forwarding checked.
I have Nat 1:1 on Wan mapping selected.
My Nat routes are:
Lan 192.168.40.10 mapped to 10.16.61.10 (PLC) and
Lan 192.168.40.20 mapped to 10.16.61.20 (HMI)
On the Wan side with my laptop (with laptop set to a 192.168.40.x subnet address, I can ping 192.168.40.1 (Ewon Wan IP) just fine, but I canot ping either 192.168.40.10 or 192.168.40.20, nor can I initiate a browser or other connection to either.
If I put the Laptop on the Lan side, I can do either and hit the devices just fine.
Seems my NAT is not routing thru the Ewon.
Oh, and FWRDtoWAN=1, WANITFPROT=2, NATITF=3 were already set when I looked in the tabular section.
Any ideas?
-
Sorry, I meant WANItfProt.
0 -
Hi, do you have any projection when the firmware bug for NAT 1:1 not working when you use a WAN enet card instead of the built- in Ethernet for WAN?
It's been since May that you and I finally narrowed down this bug, and I don't see updated firmware to address it.
Dave Ewaldz
Project Engineer
Martin Automatic Inc.
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
32 commentaires