Re: [Xen-users] new xen guest cannot communicate with the network

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Tue, Feb 04, 2014 at 08:40:37AM -0800, sbdcunha wrote:
> 
> Dear All,
> 
> I have a fresh new setup of the below on new cisco UCS Blade server
> 
> Centos 6.5 x 64
> Xen 4.2.3 
> 
> now I did install a new centos 6.5 virtual machine domU and selected the
> network as a bridge
> the issue I have is the domu can ping the xen server that is domain 0 and
> vice versa but from the DOMU machine I cannot reach any other machine
> 
> from the Xen server that is Domain 0 there is absolutely no problem. its can
> reach any machine in our network
> 

Perhaps you need to modify some bridge options.

Here is what I have (sysctl -a | grep bridge)

  net.bridge.bridge-nf-call-arptables = 1
  net.bridge.bridge-nf-call-ip6tables = 1
  net.bridge.bridge-nf-call-iptables = 1
  net.bridge.bridge-nf-filter-pppoe-tagged = 0
  net.bridge.bridge-nf-filter-vlan-tagged = 0
  net.bridge.bridge-nf-pass-vlan-input-dev = 0

You probably also need to check your iptable configuration.

Wei.

> 
> below is the config of the xen domain server
> 
> ----
> [root@xenserver1 log]# ifconfig
> br1       Link encap:Ethernet  HWaddr 00:25:B5:10:00:05  
>           inet addr:172.16.2.52  Bcast:172.16.2.255  Mask:255.255.255.0
>           inet6 addr: fe80::225:b5ff:fe10:5/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:16355 errors:0 dropped:88 overruns:0 frame:0
>           TX packets:1969 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
>           RX bytes:1178766 (1.1 MiB)  TX bytes:331166 (323.4 KiB)
> 
> eth1      Link encap:Ethernet  HWaddr 00:25:B5:10:00:05  
>           inet6 addr: fe80::225:b5ff:fe10:5/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:16049 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1534 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000 
>           RX bytes:1481245 (1.4 MiB)  TX bytes:296899 (289.9 KiB)
> 
> lo        Link encap:Local Loopback  
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:65536  Metric:1
>           RX packets:6 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
>           RX bytes:504 (504.0 b)  TX bytes:504 (504.0 b)
> 
> vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:340 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:14844 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:32 
>           RX bytes:52561 (51.3 KiB)  TX bytes:1317477 (1.2 MiB)
> 
> virbr0    Link encap:Ethernet  HWaddr 8A:B9:0F:8B:8D:95  
>           inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
> 
> ----
> 
> [root@xenserver1 log]# route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> default         172.16.2.254    0.0.0.0         UG    0      0        0 br1
> link-local      *               255.255.0.0     U     1004   0        0 br1
> 172.16.2.0      *               255.255.255.0   U     0      0        0 br1
> 192.168.122.0   *               255.255.255.0   U     0      0        0
> virbr0
> 
> ---
> 
> now on the xen dom U 
> 
> ip is 172.16.2.53 and gateway is 172.16.2.254
> -------
> 
> [root@xenserver1 log]# brctl show
> bridge name     bridge id               STP enabled     interfaces
> br1             8000.0025b5100005       no              eth1
>                                                         vif1.0
> virbr0          8000.000000000000       yes
> 
> ------------
> 
> what I am missing ..
> 
> really appreciate your kind help
> 
> regards
> 
> simon
>  
> 
> 
> 
> 
> 
> --
> View this message in context: 
> http://xen.1045712.n5.nabble.com/new-xen-guest-cannot-communicate-with-the-network-tp5721108.html
> Sent from the Xen - User mailing list archive at Nabble.com.
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users

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