I'm new to RouterOS, and networking has never been a particular strong suit (I'm a software engineer by trade), so I'm not familiar with ways to properly debug this situation, especially with RouterOS. Which, this also doesn't work, and this srcnat does not show any traffic on the Rate Graph. I have also tried to configure a srcnat in case the dstnat wasn't reversing the traffic back through. Other hardware in the field currently uses a socat of UDP 9999 through a Linux box (not NAT) and that works perfectly fine, so I'd be open to figuring out how to configure a socat-like NAT for testing. To the best of my knowledge the PLC device doesn't care whether or not the src address is from the local network, as we've had the same model communicating via a NAT in the past (and I don't believe any special treatment was done). When I connect to the LAN directly and point to 192.168.88.250:9999 directly the device shows up instantly as 'Available'. When I use the communication utility I point it to the WAN address and configured port: 192.168.7.122:9999 and search for the device, the MikroTik RateGraph shows a spike (so it's coming in) but the utility reports the device as 'Missing' (e.g. Here's what I have configured right now: Chain: dstnat I've configured the dstnat similar to the webserver, changing only the port, address and protocol. I cannot, however, get the PLC to communicate through the NAT. I've successfully setup a dst-nat to exposes Device #1 webserver on port 8080 from the WAN. Device #2 is a PLC that communicates on port 9999 UDP 192.168.88.250.Device #1 is a webserver, communicating on port 80 TCP 192.168.88.254.There are two devices connected to its LAN I have a MikroTik router with v7.1beta2 firmware installed
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |