Bug 56665
Summary: | nfsd fails to server exports after a few minutes uptime in 2.4.9-12smp | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Paul Raines <raines> |
Component: | kernel | Assignee: | Steve Dickson <steved> |
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | zaitcev |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-08-11 10:54:09 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
Paul Raines
2001-11-23 18:17:21 UTC
I discovered this problem was related to iptables. The machine serves as a bridge between a private network and the main network and is setup to masquerade using iptables. Below is how it is configure. As soon as I turn off iptables, the NFS problem goes away. So the IP filters looks like it is breaking NFS somehow. # /etc/init.d/iptables status Table: nat Chain PREROUTING (policy ACCEPT) target prot opt source destination Chain POSTROUTING (policy ACCEPT) target prot opt source destination MASQUERADE all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Table: filter Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Make sure "-o <public_ethN>" is used in iptables. Don't let it masquerade what goes inside, or else the connection tracker chokes. The output of "iptables -L -t nat" does not show additional options such as -o. I tried adding the "-o <public_ethN>" option and it still broke NFS. It made no difference. Specifically, I added "-o 192.168.100.0/255.255.255.0" |