[Xen-bugs] [Bug 184] New: iptables test failed on dom0 while passing on regular kernel

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=184

           Summary: iptables test failed on dom0 while passing on regular
                    kernel
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: hien1@xxxxxxxxxx
                CC: hohnbaum@xxxxxxxxxx,niv@xxxxxxxxxx,pl@xxxxxxxxxx,sglass@
                    us.ibm.com


system: x335-hien2.ltc.austin.ibm.com (9.3.189.226)

base OS: SLES9 SP2 

xen source : xen-unstable.hg.tar.gz
changeset:   6318:f3859247f2ed7864d3d888b05ef4b3f9ebc2b05c
tag:         tip
user:        kaf24@xxxxxxxxxxxxxxxxxxxx
date:        Mon Aug 22 14:59:58 2005
summary:     no pae by default

I ran LTP networktest.sh on both regular kernel and dom0 environment. iptables
test passed on regular kernel while it failed on dom0.

The output:
----------
iptables    0  INFO  :  INIT: Inititalizing tests.
iptables    0  INFO  :  INIT: Flushing all rules.
<<<test_start>>>
tag=iptables stime=1124813193
cmdline="iptables_tests.sh"
contacts=""
analysis=exit
initiation_status="ok"
<<<test_output>>>
***finished init() - RC = 3
incrementing stop
<<<execution_status>>>
duration=1 termination_type=exited termination_id=3 corefile=no
cutime=1 cstime=2
<<<test_end>>>
-------------
I think because of the bridge in dom0 environment.

sysctl -a|grep iptable shows:

net.bridge.bridge-nf-call-iptables = 1

Do you have any ideas ?

-------------
network info:

ethernet adapter Broadcom BCM5703X

x335-hien2:/xen-unstable.hg # ip addr show
1: eth0: <BROADCAST,MULTICAST,NOARP,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
2: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 00:11:25:3e:0c:67 brd ff:ff:ff:ff:ff:ff
3: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
4: vif0.0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
5: veth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether 00:11:25:3e:0c:66 brd ff:ff:ff:ff:ff:ff
    inet 9.3.189.226/24 brd 9.3.189.255 scope global veth0
6: xen-br0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff

x335-hien2:/xen-unstable.hg # ip route show
9.3.189.0/24 dev veth0  proto kernel  scope link  src 9.3.189.226
169.254.0.0/16 dev veth0  scope link
127.0.0.0/8 dev lo  scope link
default via 9.3.189.1 dev veth0

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs