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

RE: [Xen-users] 3.0.2 NAT headaches

To: "'John Wells'" <groups@xxxxxxxxxxxxxxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] 3.0.2 NAT headaches
From: "Roger Lucas" <roger@xxxxxxxxxxxxx>
Date: Tue, 8 Aug 2006 17:33:37 +0100
Delivery-date: Tue, 08 Aug 2006 09:34:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <55395.66.192.236.118.1155055656.squirrel@xxxxxxxxxx>
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
Thread-index: Aca7CAVRk9sp4LmfT3WjzKtfxwRuCQAADfEQ
Hi John,

Have you applied the fix for the potential packed header corruption on Xen
DomU interfaces?

root@harpseal:~# cat /etc/network/if-up.d/fix-xen
#!/bin/bash
if [ $IFACE != "lo" ] ; then
        ethtool -K $IFACE tx off
fi

root@harpseal:~#

I have to have this script on all my DomUs to make the networking reliable.

- Roger

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of John Wells
> Sent: 08 August 2006 17:48
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] 3.0.2 NAT headaches
> 
> Guys,
> 
> I'm struggling to make NAT work on Debian Sarge. Bridging works fine, but
> when I try to switch to NAT, I can't ping anything.
> 
> Here is what I have done:
> 
> Switch /etc/xen/xend-config.sxp network-script and vif-script from
> network-route and vif-route to:
> 
> (network-script network-nat)
> (vif-script vif-nat)
> 
> In my domU config:
> vif=[ 'ip=10.0.0.1' ]
> dhcp="off"
> hostname="vm01.example.com"
> ip="10.0.0.1"
> netmask="255.0.0.0"
> gateway="10.0.0.254"
> extra="3"
> 
> When I boot the domU, I set eth0 to be 10.0.0.1/8 and the default route as
> 10.0.0.254. I cannot ping out at all.
> 
> When I look at dom0 after booting the domU, I see the following
> interfaces:
> 
> eth0      Link encap:Ethernet  HWaddr 00:0E:0C:68:64:37
>           inet addr:72.232.35.21  Bcast:72.232.35.31  Mask:255.255.255.248
>           inet6 addr: fe80::20e:cff:fe68:6437/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:1708 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:2325 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:176884 (172.7 KiB)  TX bytes:200160 (195.4 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:16436  Metric:1
>           RX packets:20 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:1560 (1.5 KiB)  TX bytes:1560 (1.5 KiB)
> 
> peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
>           RX packets:26668 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:17706 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:3907182 (3.7 MiB)  TX bytes:2379910 (2.2 MiB)
> 
> vif0.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:5218 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:6337 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:632298 (617.4 KiB)  TX bytes:585057 (571.3 KiB)
> 
> vif7.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet addr:10.0.0.128  Bcast:0.0.0.0  Mask:255.255.255.255
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:1496 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:191 errors:0 dropped:6 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:85219 (83.2 KiB)  TX bytes:8022 (7.8 KiB)
> 
> xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:259 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:66206 (64.6 KiB)  TX bytes:468 (468.0 b)
> 
> Can anyone tell me what I'm missing/doing wrong? I really appreciate any
> help you may provide.
> 
> Thanks!
> 
> John
> 
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users


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