[Pkg-freeradius-maintainers] Bug#977590: freeradius: After upgrade to buster, freeradius doesn't talk over the network anymore
Harald Hannelius
harald at arcada.fi
Thu Dec 17 13:16:11 GMT 2020
Package: freeradius
Version: 3.0.17+dfsg-1.1
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
I upgraded debian 9 to debian 10, this upgrading freeradius-3.0.12 to freeradius-3.0.17
at the same time.
After the upgrade freeradius starts, but doesn't answer any network requests. The
end of the output of 'freeradius -X' says the following;
radiusd: #### Opening IP addresses and Ports ####
listen {
type = "control"
listen {
socket = "/var/run/freeradius/freeradius.sock"
peercred = yes
}
}
Listening on command file /var/run/freeradius/freeradius.sock
Ready to process requests
EOF
I didn't allow the upgrade process to do any changes in the config
files.
I then copied the whole /etc/freeradius directory from the previous
setup, and started freeradius -X again. The output is now as it should;
listen {
type = "acct"
ipv6addr = ::
port = 0
limit {
max_connections = 16
lifetime = 0
idle_timeout = 30
}
}
Listening on command file /var/run/freeradius/freeradius.sock
Listening on auth address * port 1812 bound to server default
Listening on acct address * port 1813 bound to server default
Listening on auth address :: port 1812 bound to server default
Listening on acct address :: port 1813 bound to server default
Listening on proxy address * port 45082
Listening on proxy address :: port 38835
Ready to process requests
EOF
I would have expected a minor software version number upgrade to
lead to a little smoother end result.
I put this as critical, since a radius server might be quite
important for infrastructures. Sorry if that sounded an alarm
or something like that.
There's clearly some changes that have happened during the
upgrade to debian 10 that shouldn't have been done.
I have a recursive diff of both config dirs, but haven't been
able to see what has done what. I still have a test-server so
I can help with providing more info is so needed.
Thank You all for freeradius!
-- System Information:
Debian Release: 10.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-13-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages freeradius depends on:
ii freeradius-common 3.0.17+dfsg-1.1
ii freeradius-config 3.0.17+dfsg-1.1
ii libc6 2.28-10
ii libcap2 1:2.25-2
ii libct4 1.00.104-1+deb10u1
ii libfreeradius3 3.0.17+dfsg-1.1
ii libgdbm6 1.18.1-4
ii libpam0g 1.3.1-5
ii libpcre3 2:8.39-12
ii libperl5.28 5.28.1-6+deb10u1
ii libreadline7 7.0-5
ii libsqlite3-0 3.27.2-3+deb10u1
ii libssl1.1 1.1.1d-0+deb10u4
ii libtalloc2 2.1.14-2
ii libwbclient0 2:4.9.5+dfsg-5+deb10u1
ii lsb-base 10.2019051400
Versions of packages freeradius recommends:
ii freeradius-utils 3.0.17+dfsg-1.1
Versions of packages freeradius suggests:
pn freeradius-krb5 <none>
ii freeradius-ldap 3.0.17+dfsg-1.1
pn freeradius-mysql <none>
pn freeradius-postgresql <none>
pn freeradius-python2 <none>
ii snmp 5.7.3+dfsg-5+deb10u1
-- no debconf information
More information about the Pkg-freeradius-maintainers
mailing list