All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Kaczmarek <tedkaz@optonline.net>
To: xen-devel@lists.xensource.com
Subject: domU's on 802.1q on unstable, where talking to dom0 now can't
Date: Wed, 28 Sep 2005 08:18:08 -0400	[thread overview]
Message-ID: <1127909888.4079.45.camel@pluto.linsolutions.com> (raw)

FC4 dom0
xen_changeset : Tue Sep 27 10:11:59 2005 +0100 a172340ae3f3

I was testing domU's on 802.1q ethernets and it was working fine. I
added the interfaces after all my domU's where already up, set up a dhcp
server on my dom0 for a few of the vms and connectivity between the
domU's and dom0 on the vlan was working. 

If I try to bring up everything from scratch with 802.1q interfaces the
domU's can't talk to the dom0. They can talk to each other though.


I tried lowering mtu size as far as 1460 to no avail.

The dom0 does not have any traces of any of the domU's in its arp table.


Any insight would be appreciated.

Regards,
Ted

             reply	other threads:[~2005-09-28 12:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 12:18 Ted Kaczmarek [this message]
2005-09-28 13:39 ` domU's on 802.1q on unstable, where talking to dom0 now can't Ted Kaczmarek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1127909888.4079.45.camel@pluto.linsolutions.com \
    --to=tedkaz@optonline.net \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.