WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 		  
Home Products Support Community News
 
   
 

xen-users

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

[Xen-users] Xen DomU with 2 interfaces LAN & WAN with dummy

from [jerome . gaulin] [Permanent Link][Original]
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Xen DomU with 2 interfaces LAN & WAN with dummy
From: jerome.gaulin@xxxxxxxxxxxxxxxxx
Date: Thu, 1 Feb 2007 15:00:37 +0100
Delivery-date: Thu, 01 Feb 2007 06:00:47 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Internet Messaging Program (IMP) 3.2.3 
Hi,

First post here so a BIG Thanks to dev-team & Co for open source.
Sorry for my poor knowledge in english...

The problem : My physical machine ( 2 interfaces : 1 LAN, 1 WAN ) as a public IP
outside the public ip's pool of my DomUs.
I can reach the LAN, but not the WAN.

I run a Xen Dom0 on a debian etch  ( core duo ).

I have :

-1 public IP like this :
212.212.52.26 with gateway 212.212.52.25, network 212.212.52.24 and
212.212.52.27 as broadcast address.

-1 /29 pool like :
212.212.35.224/29 so 212.212.35.224 as network address, 212.212.25.231 as
broadcast address.

-1 LAN network 192.168.2.0/24

on Dom0 :
/etc/network/interfaces :
allow-hotplug eth0
iface eth0 inet static
>-------address 212.212.52.26
>-------netmask 255.255.255.252
>-------network  212.212.52.24
>-------broadcast 212.212.52.27
>-------gateway 212.212.52.25

allow-hotplug
iface eth1 inet static
>-------address 192.168.2.54
>-------netmask 255.255.255.0
>-------broadcast 192.168.2.255

auto dummy0
iface dummy0 inet static
>-------address 212.212.35.225
>-------netmask 255.255.255.248
>-------broadcast 212.212.35.231

ip route show :

212.212.52.24/30 dev eth0  proto kernel  scope link  src 212.212.52.26
212.212.35.224/29 dev dummy0  proto kernel  scope link  src 212.212.35.225
192.168.2.0/24 dev eth1  proto kernel  scope link  src 192.168.2.54
default via 212.212.52.25 dev eth0

iptables -nL :

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
ACCEPT     0    --  212.212.35.226       0.0.0.0/0           PHYSDEV match
--physdev-in vif2.0
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           PHYSDEV match
--physdev-in vif2.0 udp spt:68 dpt:67

ifconfig : ( with 1 domU start )

XenBrLAN  Lien encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          adr inet6: fe80::200:ff:fe00:0/64 Scope:Lien
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:926 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          RX bytes:478332 (467.1 KiB)  TX bytes:0 (0.0 b)

XenBrWAN  Lien encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          adr inet6: fe80::200:ff:fe00:0/64 Scope:Lien
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:29 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          RX bytes:1496 (1.4 KiB)  TX bytes:0 (0.0 b)

dummy0    Lien encap:Ethernet  HWaddr DE:23:51:FB:AC:F5
          inet adr:212.212.35.225  Bcast:212.212.35.231  Masque:255.255.255.248
          adr inet6: fe80::dc23:51ff:fefb:acf5/64 Scope:Lien
          UP BROADCAST RUNNING NOARP  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 lg file transmission:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

eth0      Lien encap:Ethernet  HWaddr 00:18:8B:24:9C:10
          inet adr:212.212.52.26  Bcast:212.212.52.27  Masque:255.255.255.252
          adr inet6: fe80::218:8bff:fe24:9c10/64 Scope:Lien
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:312 errors:0 dropped:0 overruns:0 frame:0
          TX packets:204 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          RX bytes:30105 (29.3 KiB)  TX bytes:34219 (33.4 KiB)

eth1      Lien encap:Ethernet  HWaddr 00:15:17:19:9A:9E
          inet adr:192.168.2.54  Bcast:192.168.2.255  Masque:255.255.255.0
          adr inet6: fe80::215:17ff:fe19:9a9e/64 Scope:Lien
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:923 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          RX bytes:491272 (479.7 KiB)  TX bytes:716 (716.0 b)

lo        Lien encap:Boucle locale
          inet adr:127.0.0.1  Masque:255.0.0.0
          adr inet6: ::1/128 Scope:Hôte
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          RX bytes:560 (560.0 b)  TX bytes:560 (560.0 b)

peth0     Lien encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:299 errors:0 dropped:0 overruns:0 frame:0
          TX packets:209 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000
          RX bytes:30243 (29.5 KiB)  TX bytes:35445 (34.6 KiB)
          Interruption:16

peth1     Lien encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:977 errors:0 dropped:0 overruns:0 frame:0
          TX packets:75 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000
          RX bytes:501812 (490.0 KiB)  TX bytes:7216 (7.0 KiB)
          Adresse de base:0xdce0 Mémoire:fd7e0000-fd800000

vif0.0    Lien encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:204 errors:0 dropped:0 overruns:0 frame:0
          TX packets:312 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          RX bytes:34219 (33.4 KiB)  TX bytes:30105 (29.3 KiB)

vif0.1    Lien encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:923 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          RX bytes:716 (716.0 b)  TX bytes:491272 (479.7 KiB)

vif2.0    Lien encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:9 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          RX bytes:524 (524.0 b)  TX bytes:926 (926.0 b)

vif2.1    Lien encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:67 errors:0 dropped:0 overruns:0 frame:0
          TX packets:691 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          RX bytes:5340 (5.2 KiB)  TX bytes:343091 (335.0 KiB)

brctl show :
bridge name     bridge id               STP enabled     interfaces
XenBrLAN                8000.feffffffffff       no              vif0.1
                                                        peth1
                                                        vif2.1
XenBrWAN                8000.feffffffffff       no              vif0.0
                                                        peth0
                                                        vif2.0

My /etc/xen/domu1.cfg :
vif  = [ 'ip=212.212.35.226,mac=AE:B3:94:0E:F0:00,bridge=XenBrWAN',
'ip=192.168.2.70,mac=AE:B3:94:0E:F1:11,bridge=XenBrLAN' ]

on DomU :
/etc/network/interfaces :
auto eth0
iface eth0 inet static
 address 212.212.35.226
 network 212.212.35.224
 broadcast 212.212.35.231
 netmask 255.255.255.248
 gateway 212.212.35.225
# post-up  ethtool -K eth0 tx off
auto eth1
iface eth1 inet static
 address 192.168.2.70
 network 192.168.2.0
 broadcast 192.168.2.255
 netmask 255.255.255.0


ip route show :
212.212.35.224/29 dev eth0  proto kernel  scope link  src 212.212.35.226
192.168.2.0/24 dev eth1  proto kernel  scope link  src 192.168.2.70
default via 212.212.35.225 dev eth0


i have created a script called by xend-config.sxp with :
#! /bin/sh
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=XenBrWAN
"$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=XenBrLAN

Thats it. I can join the LAN, but not the WAN. with netdev=dummy0 and not
netdev=eth0, xen create a pdummy0 and it s the same.. i havnt internet connec.
'(


Any idea please fellows?


Merci !

--
---

Jérôme G.


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Xen DomU with 2 interfaces LAN & WAN with dummy, jerome . gaulin <=
Previous by Date:  Re: [Xen-users] Problem with dom0_mem and tmpfs on SLES10, Henning Sprang
Next by Date:  RE: [Xen-users] RE: How to add additional drivers to xen-kernel ?, Petersson, Mats
Previous by Thread:  Re: [Xen-users] VNC, framebuffer at boot, Jim
Next by Thread:  [Xen-users] Networking problem, George Mavrogonatos
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy