Bug 459815 - Running RHEL5 in VMware 1.0.6 (under Windows XP) with a software bridge causes IPtables to drop ESTABLISHED connections
Summary: Running RHEL5 in VMware 1.0.6 (under Windows XP) with a software bridge cause...
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.2
Hardware: i386
OS: Linux
Target Milestone: rc
: ---
Assignee: Jiri Olsa
QA Contact: Red Hat Kernel QE team
Depends On:
TreeView+ depends on / blocked
Reported: 2008-08-22 16:08 UTC by Pete Philips
Modified: 2010-06-07 10:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-06-07 10:24:50 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Pete Philips 2008-08-22 16:08:42 UTC
Description of problem:

A RHEL5 guest under VMware 1.0.6 running on Windows XP will drop packets that should normally be ACCEPTED by the ESTABLISHED rule.

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

RHEL 5.2 + latest errata
VMware 1.0.6

How reproducible:


Steps to Reproduce:

1. Install a RHEL5 guest OS under VMware-server running on Windows XP.
2. In VMware configure 3 Ethernet interfaces using "bridged" mode.
3. Boot the RHEL5 guest
4. In the guest OS, configure 3 ethernet interfaces, eth0-eth2. eth0 and eth1 should be up but with no IP address. eth2 should have an IP address.
5. Create a bridge br0 with interfaces eth0 and eth1.
6. Use the default IPtables ruleset which uses an ESTABLISHED rule.
7. Run a script which repeatedly scp's a 1k file to a remote host and keeps a count of how many it's done.
8. If the bridge is down then this will carry on forever.
9. If the bridge is up then it will hang after less than 1000 iterations.
Actual results:

Script hangs.

Expected results:

Script continues for ever.

Additional info:

It appears that conntrack is failing and packets that should be ESTABLISHED are in fact being dropped.

Comment 1 Herbert Xu 2009-02-23 11:56:13 UTC
Do you have bridge netfilter enabled? If so please try disabling it.  Thanks!

Comment 2 Jiri Olsa 2010-05-30 21:10:01 UTC
can we close this bug? I've got no answer for quite some time,
I'll close this bug next week if I dont hear from you


Comment 3 Jiri Olsa 2010-06-07 10:24:50 UTC
I've got no response, closing as not a bug

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