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

Re: [Xen-users] no ssh login


  • To: Ralph Passgang <ralph@xxxxxxxxxxxxx>
  • From: Jayesh Salvi <jayeshsalvi@xxxxxxxxx>
  • Date: Tue, 17 Jan 2006 13:42:03 -0600
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 17 Jan 2006 19:49:41 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=FLU5MhPKZXa2CgHrKBQTfn5IjRf2S3VMzv3bJ4B/jgzwKCQEwmbaFLWZSD+J7nvOdtWKwUxgLeAHCcTQwH9oZj6F5mKS0KHk0ILMVv9KuoRePKkk8XJtx2+Dzc1xWw+G1uEiV80Z3v6QAR1daCPwNsgf0rAc4jsNByTLV9mrcLk=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>


You don't need a bridge when you want to NAT the domUs. So maybe the solution
is as easy as just don't use the bridge scripts at all.

That is right. You need not use bridge if you are using NAT. If you could post your routing tables, that could give some clue. Just do 'route -n' in both dom0 and domU.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

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