[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Interdomain routing problem


  • To: Xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Robert Hulme <rob@xxxxxxxxxxxx>
  • Date: Fri, 9 Sep 2005 23:40:42 +0100
  • Delivery-date: Fri, 09 Sep 2005 22:38:38 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FUNYlpoSdPcXmWl6XRTV/MU33yTi9fovm59dhqeZcA1vPUli8uy3qw6kvbGEtOXQFTP+p/2Nj4o+T6ZjbfEsGUC2MupjGRqKFB1WiIu+mjglojSNNIzMHl50O064E9unf2RPkOlpMMEcqZegmX8tjEyRNOxrqG0UTKgVESvqyUw=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.