Bug 70504

Summary: xinetd.conf does not properly work with factorized addresses
Product: [Retired] Red Hat Public Beta Reporter: Ralph Rodriguez <ralphr>
Component: xinetdAssignee: Trond Eivind Glomsrxd <teg>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: low Docs Contact:
Priority: medium    
Version: limbo   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-08-02 05:53:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 67218    

Description Ralph Rodriguez 2002-08-01 21:03:05 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020408

Description of problem:
According to the man page, factorized addresses are allowed in xinetd
config files such as:
only_from = 192.168.0.{98,99}
In fact, when this is in an xinetd stanza, no clients can access the service.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Edit /etc/xinetd.d/telnet
2. Just before the closing curly brace, add the line:
3. only_from = 192.168.0.{98,99}
4. Run: service xinetd reload
5. Telnet to the system from a computer with one of those IP addrs
6. Note that you cannot telnet in.
7. Replace the line with a non-factorized address such as:
       only_from = 192.168.0.99
8. Note that you can now telnet in from that computer.
	

Actual Results:  Connection refused

Expected Results:  Connection allowed

Additional info:

Comment 1 Trond Eivind Glomsrxd 2002-08-01 23:08:42 UTC
It's fixed in the current devel version of xinetd. Waiting for a real release to
upgrade, though... (xinetd-2.3.6rc6)

Comment 2 Trond Eivind Glomsrxd 2002-08-23 19:43:13 UTC
2.3.7-1 has been built.

Comment 3 Trond Eivind Glomsrxd 2002-08-23 19:43:37 UTC
*** Bug 72401 has been marked as a duplicate of this bug. ***