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>

Re: [Xen-users] Routing in Xen

from [Tom Jensen] [Permanent Link][Original]
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Routing in Xen
From: "Tom Jensen" <tom.jensen@xxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 6 Mar 2009 11:53:48 -0600 (CST)
Delivery-date: Fri, 06 Mar 2009 09:54:53 -0800
Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=digitaltoolbox-inc.com; h= message-id:date:subject:from:to:mime-version:content-type: content-transfer-encoding; s=mail; bh=YeRJzTsS13/e8c7Qw3D2VVkUvJ A=; b=D9rL1eOuQ6dXVCSB1nQwAko2ghNNZcQTPriUCpS7O6+eypSHJNYz8wfFMI QH/qZrSz+b6EUECNJgKRlsX+fNT94l/Z77HFUBxulxztizkVvgmFNZyv3owGbiRc bX9XkdI0DMqMo0a/QwpiMo/yTz+U1c4rlJRGIIG/aVX/sf1k4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=digitaltoolbox-inc.com; h= message-id:date:subject:from:to:mime-version:content-type: content-transfer-encoding; q=dns; s=mail; b=6Up7Yw3XPLfidkZKbECG RnxdykQ17nT0iPqDW3wA55RKQMMvJV23a084Z99JyKGOMgyvaclVarevxBUTgwyr Fz+F+hTAaTIZgwZnGTSzVt1P+c44WfcfXm60liJ24+aDeJXs+hXnYFU0/tS4Q/lo gU642UOMbUoVAHD1z5KxZe0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: SquirrelMail/1.4.13 
I am not sure that I fully understand your exact setup or whether you are
having issues connecting to Apache from inside your network (private),
outside the network (public), or both.

Usually in a situation like this, I would try connecting to DomU from
another machine on the same private subnet using the DomU IP address. 
This would confirm that Apache is up and running correctly.

Then I repeat the step using the DomU machine's FQDN.  This would confirm
that DNS settings are configured correctly for the LAN.

Once I have verified this, I would then test access from the outside.  I
have found that most of the times, it is a port forwarding issue on the
gateway router.

In my network, I am currently running Xen using bridged networking with
each physical NIC connected to a router.  The routers handle all the port
forwarding and not the DomO.

Tom Jensen | President
Digital Toolbox

> Hello all,
>
> I'm a tad confused.  I'm running SLES10SP2 (fully patched) with XEN3.2.
I
> have my first virt server running which is a NW6.5.8 box.  I can ping my
NW virt server and I can ping from the virt server to another physical
server.  All on the same subnet.  I can even ping yahoo.com from the virt
> server.  However I cannot get http traffic to work.  I have the firewall
on the host Sles box disabled.  I have Apache running on the NW virt
server.  Nothing happens, any web browser trying to get to the NW Remote
Manager or even the welcome page just sits there and chugs along. 
Guys/Gals, I'm not very good with routing.  I'd like some help.  Here is a
> posting of my   brctl show, ifconfig, and route -n.
>
> Thanks all
>
> ~ # brctl show
> bridge name     bridge id               STP enabled     interfaces eth0
          8000.001ec9ad7804       no              peth0
> eth1            8000.001ec9ad7802       no              peth1
> eth2            8000.001b2117f958       no              peth2
> eth3            8000.001b2117f959       no              peth3
> eth4            8000.001b2117f95c       no              peth4
> ~ #
> ~ #
> ~ # ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:1E:C9:AD:78:04
>           inet addr:XXX.31.24.123  Bcast:XXX.31.24.255
Mask:255.255.255.0
>           inet6 addr: fe80::21e:c9ff:fead:7804/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:10294 errors:0 dropped:0 overruns:0 frame:0 TX
packets:606 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
>           RX bytes:694913 (678.6 Kb)  TX bytes:73195 (71.4 Kb)
>
> eth2      Link encap:Ethernet  HWaddr 00:1B:21:17:F9:58
>           inet6 addr: fe80::21b:21ff:fe17:f958/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:9549 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:513410 (501.3 Kb)  TX bytes:468 (468.0 b)
>
> eth3      Link encap:Ethernet  HWaddr 00:1B:21:17:F9:59
>           inet6 addr: fe80::21b:21ff:fe17:f959/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 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:0 (0.0 b)  TX bytes:468 (468.0 b)
>
> eth4      Link encap:Ethernet  HWaddr 00:1B:21:17:F9:5C
>           inet6 addr: fe80::21b:21ff:fe17:f95c/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 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:0 (0.0 b)  TX bytes:468 (468.0 b)
>
> eth5      Link encap:Ethernet  HWaddr 00:1B:21:17:F9:5D
>           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:1000
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Memory:d38a0000-d38c0000
>
> eth6      Link encap:Ethernet  HWaddr 00:1B:21:17:EE:F8
>           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:1000
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Memory:d2ee0000-d2f00000
>
> eth7      Link encap:Ethernet  HWaddr 00:1B:21:17:EE:F9
>           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:1000
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Memory:d2ea0000-d2ec0000
>
> eth8      Link encap:Ethernet  HWaddr 00:1B:21:17:EE:FC
>           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:1000
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Memory:d28e0000-d2900000
>
> eth9      Link encap:Ethernet  HWaddr 00:1B:21:17:EE:FD
>           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:1000
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Memory:d28a0000-d28c0000
>
> 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:156 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:156 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
>           RX bytes:9982 (9.7 Kb)  TX bytes:9982 (9.7 Kb)
>
> peth0     Link encap:Ethernet  HWaddr 00:1E:C9:AD:78:04
>           inet6 addr: fe80::21e:c9ff:fead:7804/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:10398 errors:0 dropped:9749 overruns:0 frame:0 TX
packets:612 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
>           RX bytes:930044 (908.2 Kb)  TX bytes:77167 (75.3 Kb)
>           Interrupt:16 Memory:d6000000-d6012100
>
> peth1     Link encap:Ethernet  HWaddr 00:1E:C9:AD:78:02
>           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:1000
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Interrupt:16 Memory:da000000-da012100
>
> peth2     Link encap:Ethernet  HWaddr 00:1B:21:17:F9:58
>           inet6 addr: fe80::21b:21ff:fe17:f958/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:9660 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:735221 (717.9 Kb)  TX bytes:1476 (1.4 Kb)
>           Memory:d3ee0000-d3f00000
>
> peth3     Link encap:Ethernet  HWaddr 00:1B:21:17:F9:59
>           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:1000
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Memory:d3ea0000-d3ec0000
>
> peth4     Link encap:Ethernet  HWaddr 00:1B:21:17:F9:5C
>           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:1000
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Memory:d38e0000-d3900000
>
> ~ #
> ~ #
> ~ # route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
> XXX.31.24.0     0.0.0.0         255.255.255.0   U     0      0        0
eth0
> 169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0
eth0
> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0
lo
> 0.0.0.0         XXX.31.24.1     0.0.0.0         UG    0      0        0
eth0
> ~ #
>
> _______________________________________________
> 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
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [Xen-users] Routing in Xen, Hans Pfeil
Next by Date:  [Xen-users] Disk Partitioning Questions...., Phillip Roberts
Previous by Thread:  [Xen-users] Routing in Xen, Hans Pfeil
Next by Thread:  [Xen-users] Disk Partitioning Questions...., Phillip Roberts
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

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