Open fwt-dot-fr opened 8 years ago
+1
+1
Same here with raspberry pi and 4.9 kernel. Tested with other PC Linux and same result.
Same here.... weird thing is... ser2nets does receive the data.... if I connect on the monitoring port and issue a 'monitor term
+1 use older version, don't remeber which exactly.
All later versions seem to be the same for my use-case... tried all seemingly relevant commits
commit 52ae6ec6e5c004f5fdbbd8304dd7cb18f76353b4 --> First version that allows multiple connections, but doesn't print serial output again
commit 94bcba0359cd90dbd75ab408850cac904a97fa79 --> last version that prints serial-output to the network, but doesn't alllow multiple connections
This project is pretty much obsolete now that the original ser2net program has been updated to support multiple connections.
Thanks.... seems the upstream version does indeed do this... with the 'max-connections=X' option... Doesn't work for the version in debian currently... but works with the git-version.
I receive nothing from the tcp port, device to tcp state: unconnected is always unconnected.
with the same configuration /etc/ser2net.conf 6000:raw:600:/dev/ttyUSB0:115200 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS
with ser2nets: -> showport TCP Port 6000 enable state: raw timeout: 600 connected to (or last connection): 600:, device: /dev/ttyUSB0 device config: 115200 1STOPBIT 8DATABITS NONE device controls: RTSHI DTRHI tcp to device state: waiting input device to tcp state: unconnected bytes read from TCP: 10 bytes written to TCP: 0 bytes read from device: 290 bytes written to device: 10
with ser2net -> showport TCP Port 6000 enable state: raw timeout: 600 connected to (or last connection): ::ffff:192.168.1.6,39162 device: /dev/ttyUSB0 device config: 115200 1STOPBIT 8DATABITS NONE device controls: RTSHI DTRHI tcp to device state: waiting input device to tcp state: waiting input bytes read from TCP: 0 bytes written to TCP: 0 bytes read from device: 0 bytes written to device: 0
Idea ?
Regards.