[Xen-devel] Re: Qestion about the Xen network?

[Bei Guan <gbtju85@xxxxxxxxx>]

Another questions:

In order to test the network connection of the PV (such ubuntu). I use a simple cilent and server program base the linux socket API. If the server get a connection from the client, the server will print the client's ip infomation and the client will print the message got from the server.

I put the server in the Ubuntu PV (its ip is 192.168.122.187) and the client in the Dom0 (its ip is 192.168.1.129). I start the server first, and then the client. The client can connect to the server successfully. The message printed like these.

root@ubuntu:~/test1# ./server 13
Server get connection from 192.168.122.1

[root@localhost test1]# ./client 192.168.122.187 13
agrv[1] = 192.168.122.187
I have received:Hello! Are You Fine?

I can not understand why the server just print the virbr0' IP address (it is xen net bridge) other than Dom0's real IP, 192.168.1.129. What the relationship between the two IPs(192.168.1.129 and 192.168.122.1)?

If I put server in Dom0 and the client in Ubuntu. The client can not connect to the server. However, I can ping Dom0's IP (192.168.1.129) successfully from Ubuntu. What's reason?


Thanks a lot!
Best Wishes.

Bei Guan

2010/10/22 Bei Guan <gbtju85@xxxxxxxxx>

Hi,

I feel confused to the xen network.
My Dom0 is fefora8 and xen is 4.0.0. My xend network configuration is bridge. The network in the pv (which is ubuntu) configuration is like this

vif = ['bridge=virbr0']

When I start the PV, I use the command brctl to see all the bridges in my computer. The output as following.

[root@localhost ~]# brctl show
bridge name     bridge id               STP enabled     interfaces
eth0            8000.0024e839fa54       no              peth0
virbr0           8000.feffffffffff            no              vif1.0

So the interface vif1.0 is PV's backend network device. And vif1.0 can access to the internet through bridge virbr0. According the description of xen bridge in xend configuration file, which is list here, virbr0 is the bridge. Is it right?

Does the bridge virbr0 connect to outside internet through eth0? What's the relationship between the eth0 and peth0? Which is my real network device card? And what's role of the other one?


(the description of xen bridge in xend configuration file)
# To bridge network traffic, like this:
#
# dom0: ----------------- bridge -> real eth0 -> the network
#                            |
# domU: fake eth0 -> vifN.0 -+

(The network interfaces on my computer are as following. )
[root@localhost ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:24:E8:39:FA:54 
          inet addr:192.168.1.129  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::224:e8ff:fe39:fa54/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:421887 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21811 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:82335005 (78.5 MiB)  TX bytes:4166441 (3.9 MiB)

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:16436  Metric:1
          RX packets:1474 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1474 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3466544 (3.3 MiB)  TX bytes:3466544 (3.3 MiB)

peth0     Link encap:Ethernet  HWaddr 00:24:E8:39:FA:54 
          inet6 addr: fe80::224:e8ff:fe39:fa54/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:441848 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21849 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:89824688 (85.6 MiB)  TX bytes:4172186 (3.9 MiB)
          Memory:fe6e0000-fe700000

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:90 errors:0 dropped:0 overruns:0 frame:0
          TX packets:94 errors:0 dropped:4 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:8073 (7.8 KiB)  TX bytes:9696 (9.4 KiB)

virbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:90 errors:0 dropped:0 overruns:0 frame:0
          TX packets:129 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:8073 (7.8 KiB)  TX bytes:15177 (14.8 KiB)


Any advice from you is appreciated.
Thank you very much!

Bei Guan

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