Could someone please help? I''m trying to setup a ''simulation
network''
where there are two domains A and B with 3 ''routers'' between
them.
I have tried the following:
xmclient:~# ifconfig eth0 10.0.1.1
xmclient:~# route add -net 10.0.4.0 netmask 255.255.255.0 dev eth0
xmrouter1:~# ifconfig eth0 10.0.1.254
xmrouter1:~# ifconfig eth1 10.0.2.1
xmrouter1:~# route add -net 10.0.4.0 netmask 255.255.255.0 dev eth1
xmrouter2:~# ifconfig eth0 10.0.2.254
xmrouter2:~# route add -net 10.0.1.0 netmask 255.255.255.0 dev eth0
xmrouter2:~# ifconfig eth1 10.0.3.1
xmrouter2:~# route add -net 10.0.4.0 netmask 255.255.255.0 dev eth1
xmrouter3:~# ifconfig eth0 10.0.3.254
xmrouter3:~# route add -net 10.0.1.0 netmask 255.255.255.0 dev eth0
xmrouter3:~# ifconfig eth1 10.0.4.1
xmserver:~# ifconfig eth0 10.0.4.254
xmserver:~# route add -net 10.0.1.0 netmask 255.255.255.0 dev eth0
Where in A is xmclient and B is xmserver. What I expect to happen is
now that xmclient and xmserver can talk to one another, and that
packets will merrily hop from xmclient -> xmrouter1 -> xmrouter2 ->
xmrouter3 -> xmserver and backwards...
When I ping I get...
xmserver:~# ping 10.0.1.1
PING 10.0.1.1 (10.0.1.1) 56(84) bytes of data.
64 bytes from 10.0.1.1: icmp_seq=1 ttl=64 time=0.579 ms
64 bytes from 10.0.1.1: icmp_seq=2 ttl=64 time=0.184 ms
64 bytes from 10.0.1.1: icmp_seq=3 ttl=64 time=0.153 ms
64 bytes from 10.0.1.1: icmp_seq=4 ttl=64 time=0.169 ms
--- 10.0.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 0.153/0.271/0.579/0.178 ms
All good and hunkey dorey so far :-P
Now to check on the hopping...
xmserver:~# traceroute 10.0.1.1
traceroute to 10.0.1.1 (10.0.1.1), 30 hops max, 38 byte packets
1 10.0.1.1 (10.0.1.1) 0.215 ms 5.151 ms 0.180 ms
Ah... only one hop, not what I expected...
What have I done wrong? Is it a general networking mistake I''ve made
in my thinking here or is there some kind of xen magic happening where
xen knows it can route from xmserver to xmclient and so doesn''t do all
the intermediate hops I have tried to put in place? If so how can I
prevent that?
Muchos gracias!
-Rob
--
------------------------------------------------------
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@lists.xensource.com
http://lists.xensource.com/xen-users
Okay, let me make sure I understand your setup here: xmclient1(eth0) - 10.0.1.1 xmrouter1(eth0) - 10.0.1.254 xmrouter1(eth1) - 10.0.2.1 xmrouter2(eth0) - 10.0.2.254 xmrouter2(eth1) - 10.0.3.1 xmrouter3(eth0) - 10.0.3.254 xmrouter3(eth1) - 10.0.4.1 xmserver(eth0) - 10.0.4.254 Your routing tables should look something like this xmclient: 10.0.1.0 dev eth0 default router 10.0.1.254 xmrouter1 10.0.1.0 dev eth0 10.0.2.0 dev eth1 10.0.3.0 gw 10.0.2.254 10.0.4.0 gw 10.0.2.254 (could also set default gw 10.0.2.254 instead of two previous route entries) xmrouter2 10.0.2.0 dev eth0 10.0.3.0 dev eth1 10.0.1.0 gw 10.0.2.1 10.0.4.0 gw 10.0.3.254 xmrouter3 10.0.3.0 dev eth0 10.0.4.0 dev eth1 10.0.1.0 gw 10.0.3.1 10.0.2.0 gw 10.0.3.1 (could also set default gw 10.0.3.1 instead of two prevous route entries) xmserver1 10.0.4.0 dev eth0 default gw 10.0.4.1 This should get the traffic from xmclient1 to xmserver1 and back again. Also make sure you enable ipv4 packet forwarding either via sysctl or manually echoing into the correct /proc location. 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@robhulme.com> 2005/09/08 16:33 >>>Could someone please help? I''m trying to setup a ''simulation network'' where there are two domains A and B with 3 ''routers'' between them. I have tried the following: xmclient:~# ifconfig eth0 10.0.1.1 xmclient:~# route add -net 10.0.4.0 netmask 255.255.255.0 dev eth0 xmrouter1:~# ifconfig eth0 10.0.1.254 xmrouter1:~# ifconfig eth1 10.0.2.1 xmrouter1:~# route add -net 10.0.4.0 netmask 255.255.255.0 dev eth1 xmrouter2:~# ifconfig eth0 10.0.2.254 xmrouter2:~# route add -net 10.0.1.0 netmask 255.255.255.0 dev eth0 xmrouter2:~# ifconfig eth1 10.0.3.1 xmrouter2:~# route add -net 10.0.4.0 netmask 255.255.255.0 dev eth1 xmrouter3:~# ifconfig eth0 10.0.3.254 xmrouter3:~# route add -net 10.0.1.0 netmask 255.255.255.0 dev eth0 xmrouter3:~# ifconfig eth1 10.0.4.1 xmserver:~# ifconfig eth0 10.0.4.254 xmserver:~# route add -net 10.0.1.0 netmask 255.255.255.0 dev eth0 Where in A is xmclient and B is xmserver. What I expect to happen is now that xmclient and xmserver can talk to one another, and that packets will merrily hop from xmclient -> xmrouter1 -> xmrouter2 -> xmrouter3 -> xmserver and backwards... When I ping I get... xmserver:~# ping 10.0.1.1 PING 10.0.1.1 (10.0.1.1) 56(84) bytes of data. 64 bytes from 10.0.1.1: icmp_seq=1 ttl=64 time=0.579 ms 64 bytes from 10.0.1.1: icmp_seq=2 ttl=64 time=0.184 ms 64 bytes from 10.0.1.1: icmp_seq=3 ttl=64 time=0.153 ms 64 bytes from 10.0.1.1: icmp_seq=4 ttl=64 time=0.169 ms --- 10.0.1.1 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 2999ms rtt min/avg/max/mdev = 0.153/0.271/0.579/0.178 ms All good and hunkey dorey so far :-P Now to check on the hopping... xmserver:~# traceroute 10.0.1.1 traceroute to 10.0.1.1 (10.0.1.1), 30 hops max, 38 byte packets 1 10.0.1.1 (10.0.1.1) 0.215 ms 5.151 ms 0.180 ms Ah... only one hop, not what I expected... What have I done wrong? Is it a general networking mistake I''ve made in my thinking here or is there some kind of xen magic happening where xen knows it can route from xmserver to xmclient and so doesn''t do all the intermediate hops I have tried to put in place? If so how can I prevent that? Muchos gracias! -Rob -- ------------------------------------------------------ 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@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> 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@lists.xensource.com http://lists.xensource.com/xen-users
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@robhulme.com> 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@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@robhulme.com> 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@lists.xensource.com > http://lists.xensource.com/xen-users > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> The original post showed a slew of 10.X.X.X ip with no subnet > masks,errr.... I did xmclient:~# ifconfig eth0 10.0.1.1 xmclient:~# route add -net 10.0.4.0 netmask 255.255.255.0 dev eth0 etc... Doesn''t that set an appropriate netmask? -- ------------------------------------------------------ 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@lists.xensource.com http://lists.xensource.com/xen-users
> This itself is fine, but why add another entry into the rib table that > serves no purpose, any packet to addresses 10.0.0.0 - 10.255.255.255 > will be considered directly connected to eth0.Yes, I was being an idiot ! I didn''t realise what the netmask was ... I''ve now adjusted what I''m doing in light of what people have been saying (here and in the IRC channel on freenode) such that my config is now: xmclient:~# ifconfig eth0 10.0.1.1 netmask 255.255.255.0 xmclient:~# route add -net 10.0.4.0 netmask 255.255.255.0 gw 10.0.1.254 xmrouter1:~# ifconfig eth0 10.0.1.254 netmask 255.255.255.0 xmrouter1:~# ifconfig eth1 10.0.2.1 netmask 255.255.255.0 xmrouter1:~# route add -net 10.0.4.0 netmask 255.255.255.0 gw 10.0.2.254 xmrouter1:~# echo 1 > /proc/sys/net/ipv4/ip_forward xmrouter2:~# ifconfig eth0 10.0.2.254 netmask 255.255.255.0 xmrouter2:~# ifconfig eth1 10.0.3.1 netmask 255.255.255.0 xmrouter2:~# route add -net 10.0.4.0 netmask 255.255.255.0 gw 10.0.3.254 xmrouter2:~# route add -net 10.0.1.0 netmask 255.255.255.0 gw 10.0.2.1 xmrouter2:~# echo 1 > /proc/sys/net/ipv4/ip_forward xmrouter3:~# ifconfig eth0 10.0.3.254 netmask 255.255.255.0 xmrouter3:~# ifconfig eth1 10.0.4.1 netmask 255.255.255.0 xmrouter3:~# route add -net 10.0.1.0 netmask 255.255.255.0 gw 10.0.3.1 xmrouter3:~# echo 1 > /proc/sys/net/ipv4/ip_forward xmserver:~# ifconfig eth0 10.0.4.254 netmask 255.255.255.0 xmserver:~# route add -net 10.0.1.0 netmask 255.255.255.0 gw 10.0.4.1 xmserver:~# ping 10.0.1.1 PING 10.0.1.1 (10.0.1.1) 56(84) bytes of data. 64 bytes from 10.0.1.1: icmp_seq=1 ttl=61 time=35.1 ms 64 bytes from 10.0.1.1: icmp_seq=2 ttl=61 time=0.824 ms 64 bytes from 10.0.1.1: icmp_seq=3 ttl=61 time=0.889 ms This is good - I know the routers are being used because the ttl is < 64 and if I shut down one of the routers it stops working :-) Huzzah it''s solved... xmserver:~# traceroute 10.0.1.1 -d traceroute to 10.0.1.1 (10.0.1.1), 30 hops max, 38 byte packets 1 10.0.4.1 (10.0.4.1) 1.214 ms 0.228 ms 0.082 ms 2 * * * 3 * * * 4 * * 10.0.1.1 (10.0.1.1) 29.752 ms Damn - why are 2 and 3 giving me *''s? I think I''m 99.99% of the way there - I just wish I wasn''t getting *''s... Can someone please explain why I''m getting *''s and how to prevent that from happening? -Rob -- ------------------------------------------------------ My grandmother started walking five miles a day when she was sixty. She''s ninety-seven now, and we don''t know where the hell she is. - Ellen DeGeneres http://www.robhulme.com/ http://robhu.livejournal.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Robert Hulme wrote:>>This itself is fine, but why add another entry into the rib table that >>serves no purpose, any packet to addresses 10.0.0.0 - 10.255.255.255 >>will be considered directly connected to eth0. > > Yes, I was being an idiot ! I didn''t realise what the netmask was ..... snip conf ..> This is good - I know the routers are being used because the ttl is < > 64 and if I shut down one of the routers it stops working :-) > > Huzzah it''s solved... > > xmserver:~# traceroute 10.0.1.1 -d > traceroute to 10.0.1.1 (10.0.1.1), 30 hops max, 38 byte packets > 1 10.0.4.1 (10.0.4.1) 1.214 ms 0.228 ms 0.082 ms > 2 * * * > 3 * * * > 4 * * 10.0.1.1 (10.0.1.1) 29.752 ms > > Damn - why are 2 and 3 giving me *''s? > > I think I''m 99.99% of the way there - I just wish I wasn''t getting > *''s... Can someone please explain why I''m getting *''s and how to > prevent that from happening?Timing problem somewhere? Maybe an even closer look at your work, combined with tcpdump, will reveal the mising pieces. But if you do traceroute on the inet, you''ll often see *''s; it''s not exactly uncommom. Your 29ms or so might seem a bit longish on a small internal network. OTOH, postings seems to to indicate quite a lot are having routing/bridging problems with Xen, so... -- Kind regards, Mogens Valentin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > Damn - why are 2 and 3 giving me *''s? > > I think I''m 99.99% of the way there - I just wish I wasn''t getting > > *''s... Can someone please explain why I''m getting *''s and how to > > prevent that from happening? > Timing problem somewhere?It''d be highly interesting to note why it taking so long as this is going to be used for a QoS simulation (!).> Maybe an even closer look at your work, > combined with tcpdump, will reveal the mising pieces.I''m not sure what I''d look for exactly...> But if you do traceroute on the inet, you''ll often see *''s; it''s not > exactly uncommom.Yeah - but how do I stop that from happening in Linux? It must be some kind of kernel option that is off by default - does anyone have any ideas? -Rob -- ------------------------------------------------------ My grandmother started walking five miles a day when she was sixty. She''s ninety-seven now, and we don''t know where the hell she is. - Ellen DeGeneres http://www.robhulme.com/ http://robhu.livejournal.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users