Hi, After spending another week on this problem, I have an easy workaround that fixes the issue. In the past I used uucp for dial-up, dial-in and direct rs-232 connections, but never via networks. Being unfamiliar with the different programs available and involved to setup the "dial-in" side (e.g. inetd, systemd, in.uucpd, tcpd. etc.), as possibly other old uucp users are as well, I took quite a bit of time to find a solution. It turns out to be quite simple.
Enclosed in the uucp package is a file to start the uucpd listening daemon. The file is debian/uucp/lib/systemd/system/[email protected]. After installation the file can be found at /usr/lib/systemd/system/[email protected]. The file does not exist on a clean debian install before the uucp package is installed. The file contents is: [Unit] Description=UUCP server Wants=network.target Documentation=http://airs.com/ian/uucp.html [Service] User=uucp ExecStart=-/usr/sbin/in.uucpd StandardInput=socket I changed the ExecStart line, replacing "in.uucpd" by "uucico -l" as shown below, and now have a working system. ExecStart=-/usr/sbin/uucico -l This is a workaround, and not a solution. It will probably have security issues, but then again if you are using uucp unencrypted (like I am in a home network) you are (or should be) well aware of those issues anyway. I hope that this may help others running into the same or similar issues. PS To find out what was wrong, I created multiple virtual Debian 13.4 and FreeBSD15 machines. The problem does not occur in FreeBSD, where uucp works fine over tcp straight after installation. The problem seems to be debian related.
