Why you have to forward ALL the TCP ports for FTP on the Elspec meters

Avatar

sdg.sean
2018-11-07 12:06

  1. The Elspec meter has its own IP, which we must be able to browse
  2. So, how can you get a static IP for the Elspec, on the internet so that Adam can read it?
    1. Best practice would be if you can get the Elspec on some kind of APN
    2. But to access some kind of APN (now that TRUteq has given up on APNs), is not so easy
    3. What those guys do, is they give you a static internet IP on a SIM
    4. When you do that, you must then somehow put that into a router, and then route all TCP ports from the static IP to the Elspec device local IP
    5. the problem with ftp, is that one port is not good enough. The ftp control connection happens on a fixed port, but then the ftp server dynamically allocates another port number for the data connection, it tells the client (in this case PNPSCADA is the ftp Client), what the port is. Then the client must somehow connect to it.
  3. If the router only forwards the control connection ftp port, that will be good for the first connection, but then when it tells us: 'connect to port 12342' for instance a port number that we have never even heard of before, now somehow we have to connect to it to get the actual file so that is why the router has to forward ALL tcp ports to the Elspec.


Tags: elspecftptcp ports
Please log in to post a comment
Related by Tags: