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] Interdomain routing problem

from [Ted Kaczmarek] [Permanent Link][Original]
To: Nick Couchman <Nick.Couchman@xxxxxxxxx>
Subject: Re: [Xen-users] Interdomain routing problem
From: Ted Kaczmarek <tedkaz@xxxxxxxxxxxxx>
Date: Thu, 08 Sep 2005 21:29:44 -0400
Cc: Robert Hulme <rob@xxxxxxxxxxxx>, Xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 09 Sep 2005 01:28:27 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20050908T174316Z_87A6000D0001@xxxxxxxxx>
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>
References: <20050908T174316Z_87A6000D0001@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
Think of dom0 as your network core, with all of your domU directly
connected. The original post showed a slew of 10.X.X.X ip with no subnet
masks, so these would all default to a subnet 8 bits in length or a
netmask of 255.0.0.0. That essentially put all these ip interface in one
broadcast domain, 10.255.255.255. If you have all the interface with the
same broadcast address, they should all be using the same broadcast
domain.( A hub or switch no vlans is one broadcast domain, some people
like the piece of wire reference also).

dom0 eth0, domU eth0 on same host share a broadcast domain.

Draw a diagram, make sure every common broadcast address is connected to
the same broadcast domain, you probably really want to look into using
CIDR addressing(Classless Interdomain Routing).

Something like this.
24 bit subnet length
10.0.1.0 255.255.255.0
10.0.2.0 255.255.255.0
10.0.3.0 255.255.255.0

Or to get fancy

22 bit subnet length
10.0.0.0 255.255.252.0
10.0.4.0 255.255.252.0
10.0.8.0 255.255.252.0

Regards,
Ted





On Thu, 2005-09-08 at 17:43 -0600, Nick Couchman wrote:
> Well, you can do static routers, but you can't do it the way you're
> trying to do it.  Linux doesn't like to statically route to networks
> that it can't directly access.  The setup that I gave you is static
> routing - you assign default gateways to your end servers/clients and
> static routes on the routers in between.  When the packets get to the
> routers, the routers know how to deal with them even if the
> originating host doesn't know exactly where to go.  Unless you get
> something like the Zebra suite, you can't do dynamic routing in Linux
> (that I know of).
>  
> Nick Couchman
> Systems Integrator
> SEAKR Engineering, Inc.
> 6221 South Racine Circle
> Centennial, CO 80111
> Main: (303) 790-8499
> Fax: (303) 790-8720
> Web: http://www.seakr.com
> 
> >>> Robert Hulme <rob@xxxxxxxxxxxx> 2005/09/08 16:56 >>>
> > Okay, let me make sure I understand your setup here:
> > ... 
> Yeah that's right.
> > Your routing tables should look something like this
> > ...
> I want to do it using static routes (for reasons not apparent at this
> point)... Am I not doing that in the correct way?
> 
> 
> 
> I just realised I should maybe give some more information - this is
> all from dom0:
> 
> atlas:~# xm list
> Name Id Mem(MB) CPU State Time(s) Console
> Domain-0 0 123 0 r---- 7977.5 
> xmclient 14 127 0 -b--- 4.0 9614
> xmrouter1 15 63 0 -b--- 5.2 9615
> xmrouter2 16 63 0 -b--- 5.0 9616
> xmrouter3 17 63 0 -b--- 5.0 9617
> xmserver 18 127 0 -b--- 4.2 9618
> 
> 
> 
> atlas:~# xm info
> system : Linux
> host : atlas
> release : 2.6.11.12-xen0
> version : #1 Thu Aug 4 00:45:12 BST 2005
> machine : i686
> cores : 1
> hyperthreads_per_core : 1
> cpu_mhz : 2200
> memory : 1023
> free_memory : 431
> 
> atlas:~# ifconfig
> eth0 Link encap:Ethernet HWaddr 00:11:D8:B0:6E:64 
> inet addr:192.168.0.97 Bcast:192.168.0.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:38191 errors:0 dropped:0 overruns:0 frame:0
> TX packets:29394 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000 
> RX bytes:2809035 (2.6 MiB) TX bytes:4616890 (4.4 MiB)
> Interrupt:12 Base address:0x8800 
> 
> lo Link encap:Local Loopback 
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:80614 errors:0 dropped:0 overruns:0 frame:0
> TX packets:80614 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0 
> RX bytes:5959012 (5.6 MiB) TX bytes:5959012 (5.6 MiB)
> 
> vif14.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF 
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:11 errors:0 dropped:0 overruns:0 frame:0
> TX packets:895 errors:0 dropped:61 overruns:0 carrier:0
> collisions:0 txqueuelen:0 
> RX bytes:800 (800.0 b) TX bytes:56514 (55.1 KiB)
> 
> vif15.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF 
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2 errors:0 dropped:0 overruns:0 frame:0
> TX packets:866 errors:0 dropped:57 overruns:0 carrier:0
> collisions:0 txqueuelen:0 
> RX bytes:84 (84.0 b) TX bytes:54518 (53.2 KiB)
> 
> vif15.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF 
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2 errors:0 dropped:0 overruns:0 frame:0
> TX packets:865 errors:0 dropped:58 overruns:0 carrier:0
> collisions:0 txqueuelen:0 
> RX bytes:84 (84.0 b) TX bytes:54476 (53.1 KiB)
> 
> vif16.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF 
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2 errors:0 dropped:0 overruns:0 frame:0
> TX packets:863 errors:0 dropped:52 overruns:0 carrier:0
> collisions:0 txqueuelen:0 
> RX bytes:84 (84.0 b) TX bytes:54374 (53.0 KiB)
> 
> vif16.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF 
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2 errors:0 dropped:0 overruns:0 frame:0
> TX packets:862 errors:0 dropped:53 overruns:0 carrier:0
> collisions:0 txqueuelen:0 
> RX bytes:84 (84.0 b) TX bytes:54332 (53.0 KiB)
> 
> vif17.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF 
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2 errors:0 dropped:0 overruns:0 frame:0
> TX packets:859 errors:0 dropped:49 overruns:0 carrier:0
> collisions:0 txqueuelen:0 
> RX bytes:84 (84.0 b) TX bytes:54170 (52.9 KiB)
> 
> vif17.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF 
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2 errors:0 dropped:0 overruns:0 frame:0
> TX packets:858 errors:0 dropped:50 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:84 (84.0 b) TX bytes:54128 (52.8 KiB)
> 
> vif18.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF 
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:11 errors:0 dropped:0 overruns:0 frame:0
> TX packets:877 errors:0 dropped:17 overruns:0 carrier:0
> collisions:0 txqueuelen:0 
> RX bytes:716 (716.0 b) TX bytes:55367 (54.0 KiB)
> 
> xen-br0 Link encap:Ethernet HWaddr 00:11:D8:B0:6E:64 
> inet addr:192.168.0.97 Bcast:192.168.0.255 Mask:255.255.255.255
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:38164 errors:0 dropped:0 overruns:0 frame:0
> TX packets:29114 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0 
> RX bytes:2192948 (2.0 MiB) TX bytes:4588363 (4.3 MiB) 
> 
> 
> 
> 
> 
> -- 
> ------------------------------------------------------
> Fran: Do you know that in Tibet when they want something they give
> something away?
> Bernard: Do they? That must be why they're such a dominant global
> power. 
> -- Black Books
> 
> http://www.robhulme.com/ 
> http://robhu.livejournal.com/ 
> 
> _______________________________________________
> 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


_______________________________________________
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:  Re: [Xen-users] Interdomain routing problem, Nick Couchman
Next by Date:  Re: [Xen-users] Asynchronous IO, Priya PM
Previous by Thread:  Re: [Xen-users] Interdomain routing problem, Nick Couchman
Next by Thread:  Re: [Xen-users] Interdomain routing problem, Robert Hulme
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

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