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

[Xen-users] Configuring Routes in Dom0

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Configuring Routes in Dom0
From: "Phil Winterfield (winterfi)" <winterfi@xxxxxxxxx>
Date: Tue, 16 Sep 2008 10:09:46 -0700
Authentication-results: sj-dkim-3; header.From=winterfi@xxxxxxxxx; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
Delivery-date: Tue, 16 Sep 2008 10:09:59 -0700
Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; l=35744; t=1221584953; x=1222448953; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=winterfi@xxxxxxxxx; z=From:=20=22Phil=20Winterfield=20(winterfi)=22=20<winterfi@ cisco.com> |Subject:=20Configuring=20Routes=20in=20Dom0 |Sender:=20; bh=nqCRDo30dXSGaJjhu1cUcTtAYx3Yng+kH3fypKAYl0w=; b=AzlcTzghPEVwx3dRItaTsLZp0HicC82VT/SOMyBSfi59p1uOVZoOpgaKhO rO+K1858xEeolcSG2hDBwGr2Rq1Vblzvrf6TvaDFzRMjjqTQ/C0Gajqta8ZP KR6ypgAR0I;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
Thread-index: AckYHwVY2NyCxx3DTxC1/C7bnn/Chg==
Thread-topic: Configuring Routes in Dom0

Perhaps someone more experienced than I in Linux routing configurations may be able to offer some advice on how to configure the route tables on the dom0 side of the test set up outlined below. I am able to ping successfully from the traffic generator to the interfaces configured on the virtual router, but when traffic is started, linux is not forwarding the packets beyond the physical NIC’s, i.e. eth2 and eth3.  The packets returned to the traffic generator, when examined with a packet sniffer, are marked by linux as “Destination Unreachable (Host administratively prohibited)”.   I have been unable to find any online documentation as to what is being implied by that message and its possible remedies.  

 

Your thoughts on this will be appreciated.

 

                          

Traffic Generator   |                      Linux Dom0                    |           Virtual Router

                            |     Intel 82576 NIC             Virtual I/F    |

                            |                                                           |

      1.3.0.2  ---------------  1.3.0.1 ----------------- 1.7.0.1 ------------------ 1.7.0.3

                            |           Eth2                          vif[n].0      |               Eth0/0

                            |                                                           |

       1.5.0.2  ---------------  1.5.0.1 ----------------- 1.9.0.1 ----------------- 1.9.0.3

                            |            Eth3                          vif[n].1     |                Eth1/0

 

 

from Dom0:

 

[root@localhost ios]# ifconfig

eth0      Link encap:Ethernet  HWaddr 00:15:17:46:EF:CA 

          inet addr:192.168.102.94  Bcast:192.168.102.95  Mask:255.255.255.224

          inet6 addr: fe80::215:17ff:fe46:efca/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:135717 errors:0 dropped:0 overruns:0 frame:0

          TX packets:25911 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:100

          RX bytes:92639630 (88.3 MiB)  TX bytes:2979222 (2.8 MiB)

          Base address:0x2020 Memory:98820000-98840000

 

eth2      Link encap:Ethernet  HWaddr 00:1B:21:24:21:04 

          inet addr:1.3.0.1  Bcast:1.3.0.255  Mask:255.255.255.0

          inet6 addr: fe80::21b:21ff:fe24:2104/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:103993255 errors:7 dropped:0 overruns:0 frame:4

          TX packets:1699 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:13715734 (13.0 MiB)  TX bytes:222060 (216.8 KiB)

 

eth3      Link encap:Ethernet  HWaddr 00:1B:21:24:21:05 

          inet addr:1.5.0.1  Bcast:1.5.0.255  Mask:255.255.255.0

          inet6 addr: fe80::21b:21ff:fe24:2105/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:236160080 errors:4 dropped:0 overruns:0 frame:2

          TX packets:4876 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:3517471211 (3.2 GiB)  TX bytes:704726 (688.2 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:540 errors:0 dropped:0 overruns:0 frame:0

          TX packets:540 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:66558 (64.9 KiB)  TX bytes:66558 (64.9 KiB)

 

vif6.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 

          inet addr:1.7.0.1  Bcast:1.7.0.255  Mask:255.255.255.0

          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:59233 errors:0 dropped:0 overruns:0 frame:0

          TX packets:861 errors:0 dropped:32 overruns:0 carrier:0

          collisions:0 txqueuelen:1

          RX bytes:2736103 (2.6 MiB)  TX bytes:53524 (52.2 KiB)

 

vif6.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 

          inet addr:1.9.0.1  Bcast:1.9.0.255  Mask:255.255.255.0

          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:59096 errors:0 dropped:0 overruns:0 frame:0

          TX packets:657 errors:0 dropped:28 overruns:0 carrier:0

          collisions:0 txqueuelen:1

          RX bytes:2727410 (2.6 MiB)  TX bytes:37450 (36.5 KiB)

 

[root@localhost ios]# ip route show

1.9.0.0 dev vif6.1  scope link

1.7.0.0 dev vif6.0  scope link

192.168.102.64/27 dev eth0  proto kernel  scope link  src 192.168.102.94

1.9.0.0/24 dev vif6.1  proto kernel  scope link  src 1.9.0.1

1.3.0.0/24 via 1.3.0.1 dev eth2  scope link

1.3.0.0/24 dev eth2  proto kernel  scope link  src 1.3.0.1

1.7.0.0/24 dev vif6.0  proto kernel  scope link  src 1.7.0.1

1.5.0.0/24 via 1.5.0.1 dev eth3  scope link

1.5.0.0/24 dev eth3  proto kernel  scope link  src 1.5.0.1

169.254.0.0/16 dev eth3  scope link

default via 192.168.102.65 dev eth0

 

from Virtual Router:

 

interface Ethernet0/0

 ip address 1.7.0.3 255.255.255.0

 no clns route-cache

!        

interface Ethernet1/0

 ip address 1.9.0.3 255.255.255.0

 no clns route-cache

!

ip default-gateway 192.168.102.65

!

ip classless

ip route 1.3.0.0 255.255.255.0 Ethernet0/0

ip route 1.5.0.0 255.255.255.0 Ethernet1/0

ip route 1.7.0.0 255.255.255.0 Ethernet0/0

ip route 1.9.0.0 255.255.255.0 Ethernet1/0

no ip http server

 

 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Configuring Routes in Dom0, Phil Winterfield (winterfi) <=