My configuration uses port 8010 to access the serial port via either the internet or local network. So if I understand your requirements, ser2net would be running on the machine with the serial port and accessed via the IP address and allocated port of the machine eg 192.168.1.5:8010. (or www.yourUrl.org:8010) The port needs to be opened on the router and the machine firewall if one is used.
ser2net listens receives and sends via port 8010. Only one connection at a time is permitted, other connection attempts are rejected.
This is the ser2net config file for my system, change to suit:
8010:raw:60:/dev/ttyACM0:9600 NONE 1STOPBIT 8DATABITS XONXOFF
Here's a link which may explain better than I can:
http://techtinkering.com/2013/04/02/conn...ver-tcpip/
Hope that helps, as I find ser2net provides all my serial requirements very reliably.
ser2net listens receives and sends via port 8010. Only one connection at a time is permitted, other connection attempts are rejected.
This is the ser2net config file for my system, change to suit:
8010:raw:60:/dev/ttyACM0:9600 NONE 1STOPBIT 8DATABITS XONXOFF
Here's a link which may explain better than I can:
http://techtinkering.com/2013/04/02/conn...ver-tcpip/
Hope that helps, as I find ser2net provides all my serial requirements very reliably.
1) Lenovo T520 i5 LL3.8 8GB ram, fast & stable
2) Medion P4 32bit LL3.8 1GB ram, quite fast & stable
3) eeePC 901 32bit LL3.8 1GB ram, fast & stable
4) eeePC 701 32bit LL3.8 1GB ram, slower & stable but small and light enough to travel with me to New Zealand when visiting family in Blenheim.
2) Medion P4 32bit LL3.8 1GB ram, quite fast & stable
3) eeePC 901 32bit LL3.8 1GB ram, fast & stable
4) eeePC 701 32bit LL3.8 1GB ram, slower & stable but small and light enough to travel with me to New Zealand when visiting family in Blenheim.