Bug 177794 - Networking conflicts between xend and iptables
Networking conflicts between xend and iptables
Product: Fedora
Classification: Fedora
Component: xen (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Rik van Riel
Depends On:
Blocks: 179599
  Show dependency treegraph
Reported: 2006-01-14 00:21 EST by Stephen Tweedie
Modified: 2007-11-30 17:11 EST (History)
3 users (show)

See Also:
Fixed In Version: xen-3.0-0.20060130.fc5.3
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-02 17:23:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stephen Tweedie 2006-01-14 00:21:58 EST
Description of problem:

Networking is unreliable (often failing entirely) after the xen service is
started if iptables are enabled.

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

How reproducible:

Steps to Reproduce:
1. Install FC5test2 with default firewall enabled
2. yum install kernel-xen-hypervisor
3. boot into hypervisor kernel
Actual results:
Networking stops working once the xen service starts during boot.  Services that
run prior to that see the network fine.

Expected results:
Networking should really keep working 

Additional info:
This is almost certainly due to Xen's extensive use of bridging.  When xend
starts up, part of the process involves moving the main (usually eth0) IF to a
new name (typically peth0), then setting up a bridge and a new virtual eth0
which inherits the IP settings of the old physical IF.  The way the iptables
rules are set up does not work under this environment.

Booting after "chkconfig iptables off" runs just fine.
Comment 1 Bill Nottingham 2006-02-02 17:23:02 EST
Fixed in xen-3.0-0.20060130.fc5.3.

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