Red Hat Bugzilla – Bug 65743
xinetd doesn't allow /32 anymore in only_from option
Last modified: 2007-04-18 12:42:50 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.3 (X11; Linux i686; U;) Gecko/20020523
Description of problem:
The newer xinetd released with Red Hat 7.3 breaks some of our xinetd.d-scripts
that uses only_from with the following format 18.104.22.168/32. It seems that "/32"
isn't allowed (anymore) alhtough the documentation 'manual pages) still uses it
as an example.
This breaks some services on all our upgraded machines and needs manual
intervention to overcome the problem.
Using other CIDR-masks than /32 seems to work fine though. (Although doing eg.
22.214.171.124/24 doesn't work, but I don't know if it used to work either. 126.96.36.199/24
works as expected)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Try adding "only_from = 188.8.131.52/32" on a RH 7.2 (or 7.1 or 7.0)
2.Then do the same on a RH 7.3 and it fails
Actual Results: It doesn't allow connections when using /32 although it doesn't
fail whil restarting xinetd (or didn't print out a message).
Expected Results: It used to work with /32
no_access, only_from, access_times
Verified. Still a problem with 2.3.5-1
Fixed in xinetd 2.3.5-3.