Network setup with Ubuntu 22.04 LTS intsalled on RPi4

[John245]

Try changing the "accepter" line to "accepter: telnet,2000"

accepter "tcp" corresponds to field 2 = "raw" in the old .conf format.

Thanks for the suggestion, bit no luck.

[stefxx]

What is "telnet: 600" in your yaml file? in the conf file, 600 refers to timeout, so I think it should be "timeout: 600", right?

[stefxx]

I will try to update my ser2net and see if I can get it working with the yaml configuration file, hopefully later today.

I am running Pi OS 5.10, and I can't find a ser2net 4.x package for it. So I can't test it myself at the moment.

[John245]

What is "telnet: 600" in your yaml file? in the conf file, 600 refers to timeout, so I think it should be "timeout: 600", right?

Bases on the input fro zwolfpack my yaml file is:

connection: &con0096
    accepter: telnet,2000
    enable: on
    options:
      banner: *banner
      kickolduser: true
      telnet-brk-on-sync: true
    connector: serialdev,
              /dev/ttyS0,
              115200n81,local
​

[John245]

I am running Pi OS 5.10, and I can't find a ser2net 4.x package for it. So I can't test it myself at the moment.

It seems that v3.5 has also the yaml config.

[stefxx]

But you are using ttyS0 again??

[John245]

But you are using ttyS0 again??

I tried with both.

[John245]

I am running Pi OS 5.10, and I can't find a ser2net 4.x package for it. So I can't test it myself at the moment.

OS 5.10 seems to be a legacy OS.

[John245]

stefxx
Not related to this issue.

I try to set-up two (2) meters one for the Primary Allocation Point (PAP) and the other for the Secondary Allocation Point (SAP). As the SAP is currently not installed (will be installed on 31MAY2023) I did split the signal from the PAP. Only one (1) meter is created in HomeSeer. Is this the expected behavior?

[stefxx]

So you've splitted the signal from a single P1 port, and fed them both into the plugin? Yes, that means it will simply receive the same data twice and won't create an additional meter in HS4. So that is indeed expected.

[John245]

So you've splitted the signal from a single P1 port, and fed them both into the plugin? Yes, that means it will simply receive the same data twice and won't create an additional meter in HS4. So that is indeed expected.

Good to know. Then I need for this to wait till the SAP is installed.

[stefxx]

I just upgraded my Pi4 with Ubuntu 22.04 LTS and installed ser2net 4.3.4. I used this ser2net.yaml:

connection: &con0096
    accepter: tcp,2000
    connector: serialdev,
              /dev/ttyUSB0,
              115200n81,local
​

Tested it with "telnet ipaddress 2000" and I received P1 data as expected.

[John245]

I just upgraded my Pi4 with Ubuntu 22.04 LTS and installed ser2net 4.3.4. I used this ser2net.yaml:

connection: &con0096
accepter: tcp,2000
connector: serialdev,
/dev/ttyUSB0,
115200n81,local
​

Tested it with "telnet ipaddress 2000" and I received P1 data as expected.

Although I have an identical yaml file connection gets refused

%YAML 1.1
---
# This is a ser2net configuration file, tailored to be rather
# simple.
#
# Find detailed documentation in ser2net.yaml(5)
# A fully featured configuration file is in
# /usr/share/doc/ser2net/examples/ser2net.yaml.gz
#
# If you find your configuration more useful than this very simple
# one, please submit it as a bugreport

#define: &banner \r\nser2net port \p device \d [\B] (Debian GNU/Linux)\r\n\r\n

connection: &con0096
    accepter: tcp,2000
    connector: serialdev,
              /dev/ttyUSB0,
              115200n81,local
​

[stefxx]

Really, all I did was a clean (remote) install of Ubuntu 22.04 Server (no desktop, ssh enabled) using the Raspberry installer, and installed ser2net using "apt install ser2net". No other configuration has been done, except editing the ser2net.yaml file.

Don't understand why it doesn't work for you. If there was anything else (like a firewall) it would impact the ser2net.conf setup as well.

Anything in the ser2net log that might be helpful?

[John245]

Really, all I did was a clean (remote) install of Ubuntu 22.04 Server (no desktop, ssh enabled) using the Raspberry installer, and installed ser2net using "apt install ser2net". No other configuration has been done, except editing the ser2net.yaml file.

Don't understand why it doesn't work for you. If there was anything else (like a firewall) it would impact the ser2net.conf setup as well.

Anything in the ser2net log that might be helpful?

I don't expect a firewall issue. Otherwise the old config should also not work.

Under /var/log there is no log file for ser2net

My install method was identical, except that I also installed Webmin.