Bug 81539 - ypbind should punch a hole in the firewall when starting
Summary: ypbind should punch a hole in the firewall when starting
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ypbind   
(Show other bugs)
Version: 8.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Ben Levenson
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-01-10 04:49 UTC by Phil Anderson
Modified: 2007-04-18 16:49 UTC (History)
1 user (show)

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: ---


Attachments (Terms of Use)

Description Phil Anderson 2003-01-10 04:49:47 UTC
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


Note You need to log in before you can comment on or make changes to this bug.