Xen users - Aug 2008 - locked myself out with iptables

Hello,

i created a failover cluster with 2 Server where 1 VM ist replicated
through DRBD and Heartbeat,
it all worked well some days and I could reboot the first server and
the second did take over the VM..
Today I started to creating some iptables rules on server 1, after
that one VM(not replicated, runs nagios) lost connections to some
servers,
but not all!. I can ping the VM that is replicated but not the host
where it lives(Server1).
So i deleted my iptables rules and rebooted the machine, after some
time I had the VM on both servers,
another reboot got me the VM back on the server1, but I couldnt acces
it, a login did not procedd and hang after entering the password.
A third reboot did solve the problem with th VM, i can now acces with
SSH and the Site.

Back to my problem:

I still cant monitor 1 VM and the 2 hosts where drbd ist running, no
ping and no other connections,
What can be the reason of this? I removed the /eetc/sysconfig/iptables
on server1, so only the rules are active that xen creates:

 iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     udp  --  anywhere             anywhere            udp dpt:domain
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:domain
ACCEPT     udp  --  anywhere             anywhere            udp dpt:bootps
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:bootps

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
ACCEPT     all  --  anywhere             192.168.122.0/24    state
RELATED,ESTABLISHED
ACCEPT     all  --  192.168.122.0/24     anywhere
ACCEPT     all  --  anywhere             anywhere
REJECT     all  --  anywhere             anywhere
reject-with icmp-port-unreachable
REJECT     all  --  anywhere             anywhere
reject-with icmp-port-unreachable
ACCEPT     all  --  anywhere             anywhere            PHYSDEV
match --physdev-in vif2.0
ACCEPT     all  --  anywhere             anywhere            PHYSDEV
match --physdev-in vif3.0

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination


All the machines are in a VLAN, i use this for monitoring,
even if I stop the firewall on all machine I cant ping the other machines.

Does someone have an idea whats wrong here?


thx

Rupertt

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

Heiko wrote:
> 
<snip>
> 
> Does someone have an idea whats wrong here?
Yes, your posting to the wrong list, try <distroX>-users list...

-Ross

______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.


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