| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] Interdomain routing problem
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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home