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

Re: [Xen-users] Bridged networking example


  • To: xen-users@xxxxxxxxxxxxx
  • From: Alexandre Kouznetsov <alk@xxxxxxxxxx>
  • Date: Thu, 20 Dec 2012 12:44:23 -0600
  • Delivery-date: Thu, 20 Dec 2012 18:46:35 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>

Hello.

El 20/12/12 12:09, Sven escribió:
| ~# telnet 74.125.230.196 80   # google.com
| Trying 74.125.230.196...
| telnet: Unable to connect to remote host: No route to host

After googling and trying things for a few hours, I still haven't figured out
how come. :-/

Look on it with tcpdump, it can show you the network traffic, and where does it stops. Run it on Dom0. On vif1.0, you shall see the packets trying to leave DomU. If you don't see the same packets on xenbr0, then the problem is within the bridge itself.


Dom0
----

# brctl show
| bridge name   bridge id               STP enabled     interfaces
| xenbr0        8000.**********e1       no              eth0
Where is your vif1.0? I assume your DomU ID is "1", so vif1.0 should be attached to xenbr0. If it is non, than this might be the problem.

# cat /etc/sysctl.conf
| net.ipv4.ip_forward = 1
BTW, this is not needed for bridged network on Dom0.


Dom1
----

# route -n
| Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
| 0.0.0.0         **.**.97.65     0.0.0.0         UG    2      0        0 eth0
| **.**.97.64     0.0.0.0         255.255.255.224 U     0      0        0 eth0
| 127.0.0.0       127.0.0.1       255.0.0.0       UG    0      0        0 lo
Is **.**.97.65 reachable/pingable from DomU? I guess it's reachable from Dom0, since it is Dom0's gateway.

Greetings.


--
Alexandre Kouznetsov


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users


 


Rackspace

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