[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Can't contact dom0 but can contact dom1, dom2, etc.

On Wed, Mar 27, 2013 at 1:16 PM, Fabrice Delente <delentef@xxxxxxxxx> wrote:
> Today it has started respnding again to ssh, even though I didn't do
> anything.
> In dmesg I have scores of lines like these:
> [5800201.055609] physdev match: using --physdev-out in the OUTPUT, FORWARD
> and POSTROUTING chains for non-bridged traffic is not supported anymore.

This means you have some rules in your iptables that aren't supported.
If this is any indication of what yous issues are, it's that iptables
is misconfigured. You may want to check over your rules table and make
sure they're all sane.

> [5800201.904358] device tap55.0 entered promiscuous mode
> [5800201.904384] xen-bridge: port 3(tap55.0) entering learning state

Just general Xen networking chatter. Nothing to worry about here.

> [5800211.377315] vif55.0: no IPv6 routers present
> [5800212.181315] tap55.0: no IPv6 routers present

IPv6 stuff, obviously makes no difference if you're not on a v6 network.

> [5800216.021324] xen-bridge: port 2(vif55.0) entering forwarding state
> [5800216.901315] xen-bridge: port 3(tap55.0) entering forwarding state

More chatter. All normal.

> I don't know if it's relevant.
> I'll post an update if the problem arises again.

You may want to take a look at whatever writes your iptables. If
you're using a script to set up networking, it may be out of date.


Sent from some sort of computing device.

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.