Bug 81539
| Summary: | ypbind should punch a hole in the firewall when starting | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Phil Anderson <pza> |
| Component: | ypbind | Assignee: | Steve Dickson <steved> |
| Status: | CLOSED RAWHIDE | QA Contact: | Ben Levenson <benl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 | CC: | mitr |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-05-12 03:23:30 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 of problem: ypbind doesn't bind on any of our clients when using the default firewall created with lokkit. ypbind should probably open a port on the firewall when starting up, just as ntpd does. ypbind starts when the firewall is off, but fails to bind when the firewall is on. How reproducible: Always Steps to Reproduce: 1.set up firewall with lokkit 2.service ypbind start Actual Results: Fails to bind to NIS server Expected Results: Should bind to a server