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

Re: [Xen-users] no ssh login


  • To: "B. Liu" <bl246@xxxxxxxxxxxxxxxx>
  • From: Jayesh Salvi <jayeshsalvi@xxxxxxxxx>
  • Date: Wed, 18 Jan 2006 10:12:17 -0600
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 18 Jan 2006 16:20:00 +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=FaF/4sRuhdJQ2SIkGh23S9oLXru7FkweEPIC40NllHT2FsoVot1hKrr6aWkVlZKjAbc9ASxpsfG/yDIYx27DaEJ7vqyUSqgOJXH84KMiEmIHjMFaT4Az9YpVsG12Nxvw5NcMlZBrlmXG+M+f+Kzt4QLqJKc3B9TMplMMjqU2RQk=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Your dom0 routing table is still routing the traffic to your bridge from old setup. use brctl to remove xenbr0 you have.
Then try:
ifconfig vifx.y 192.168.3.1 netmask 255.255.255.0 up (Alternatively after removing xenbr0 if you create a new domU the ifconfig will have done this step automatically, picking up some IP address for new vif)
This step should also have corrected your routing table.

Then you will have to update your domU routing table so that it now routes the traffic to the new gateway.
If you run into problems while doing this, post output of your ifconfig and route -n at that point.



On 1/18/06, B. Liu <bl246@xxxxxxxxxxxxxxxx> wrote:
OK, I stopped using the /etc/xen/scripts/network-bridge file, without the
bridge scripts, it started the network fine, but the problem is still
there, can't ssh to the dom0 and vm01 from the remote client.

the route -n on dom0 as following:
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.3.0     0.0.0.0         255.255.255.0   U     0      0        0
xenbr0
192.168.3.0     0.0.0.0         255.255.255.0   U     0      0        0
xenbr0
182.111.0.0     0.0.0.0         255.255.0.0     U     0      0        0
eth0
0.0.0.0          182.111.30.190  0.0.0.0         UG    0      0        0
eth0

and the route -n from vm01 is shown as following:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.3.0     0.0.0.0         255.255.255.0    U     0      0        0
eth0
0.0.0.0         192.168.3.1     0.0.0.0         UG    0      0        0
eth0

Any suggestions?

By the way, how to name the vm01? For example, my dom0 has a hostname
tom.localdomain, do I have to name the vm01 hostname as
cat.tom.localdomain or cat.localdomain? What should I do to make the
remote client know the existing of cat?

Thanks

Bin

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



--
Jayesh

_______________________________________________
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®.