Labgrid exporter ser2net fails with Invalid accepter port name/number #1416
Comments
Emantor
added a commit
to Emantor/labgrid
that referenced
this issue
Jun 21, 2024
The ser2net configuration requires the tcp argument for versions >4.6.0, since it is supported by all versions supporting the YAML configuration starting with 4.2.0, always supply the tcp argument. Fixes labgrid-project#1416 Signed-off-by: Rouven Czerwinski <[email protected]>
Emantor
added a commit
to Emantor/labgrid
that referenced
this issue
Jun 21, 2024
Always indicate that the network connection should use tcp. This was not mandatory for versions before 4.6.0, but is for versions afterwards. This should not impact the behavior for earlier versions, since all versions since the introduction of YAML configurations in 4.2.0 support this parameter. Fixes labgrid-project#1416 Signed-off-by: Rouven Czerwinski <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running labgrid 23.0.6 as an exporter on a fedora 40 server seems to fail starting ser2net (4.6.1) with the following error
❯ ser2net -d -n -Y 'connection: &con01# accepter: telnet(rfc2217,mode=server),36099' -Y ' connector: serialdev,/dev/ttyUSB0,115200n81,local' -Y ' options:' -Y ' max-connections: 10'
:5(column 0): Invalid accepter port name/number 'telnet(rfc2217,mode=server),36099': Invalid data to parameter
Adding
tcpbefore port 36099 seems to get it running, but I'm unsure if this is the right solution.ser2net version 4.6.0 works without, but 4.6.1 and 4.6.2 fails
The text was updated successfully, but these errors were encountered: