Bug 41309
| Summary: | xinetd doesn't have IPv6 not enabled | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Dan Anderson <redhatbugzilla> |
| Component: | xinetd | Assignee: | Trond Eivind Glomsrxd <teg> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | CC: | pekkas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO-3.html#xinetd | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2001-05-18 16:23:39 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: | |||
|
Description
Dan Anderson
2001-05-18 16:20:48 UTC
Not a bug - I didn't enable it because I'm not confident in the way it does it, and having IPv4 work without problems is much more important. That said, I'm considering enabling it for now (in Rawhide). I just learned there's a problem with enabling IPv6 with xinetd. If it's running in a IPv4-only kernel (one with ipv6 not compiled in and the module not loaded), xinetd will start, but it won't listen to anything (IPv4 or IPv6). One can load the IPv6 module (or compile it in) and IPv4 services will work without any further IPv6 configuration. So it sounds like the alternatives are: 1. leave things as it 2. xinetd code needs to be a little smarter or 3. the /etc/init.d/xinetd script could dynamically decide whether to load a special xinetd daemon only when IPv6 is enable.d This also appears to be a FAQ item at http://synack.net/xinetd/ : --- Q. No services start with IPv6! What's the deal? A. When you compile IPv6 support in, all sockets are IPv6 sockets. If your kernel doesn't understand what an IPv6 socket is, all attempts to create sockets will fail, and no services will start. Only compile xinetd with IPv6 support if your kernel supports IPv6. --- In reality, this is just developer laziness. The software could do something like: 1) first check whether ipv6 binding works, if not, use AF_INET for bindings 2) "force" options could be given when starting xinetd, so that if ipv6 is not available, fallback would not occur (e.g. -6, -4) 3) per-service binding should be controllable, with for example either with like: - protocol= tcp (default) | tcp4 | tcp6 | tcp46 , or - family = inet4 | inet6 | unspecified (default) I suggest you make the above suggestion on the xinetd mailing list The support is non-trivial to add, so a workaround would be preferable for now; see #49621 for a possible approach. |