> I'm only on the mesh here Rob and I can ping 44.0.0.1.
Is there a route for 44.0.0.1 in your routing table? It may be that you are actually
sending your traffic to 44.0.0.1 "direct", not via a tunnel.
(this depends on the setup of your machine and the version of the rip daemon you are running)
Rob
> I believed the problem with pinging from tunneled hosts was
> still there, but if it works for you, I must have forgotten.
It is a bit unclear what is going on. From a host that is exclusively on the IPIP
mesh the ping does not return (I see only the outgoing IPIP packet). From a host that is
both on the IPIP mesh and BGP-routed on internet it does work.
It looks like it replies "directly" (via the BGP route) to the replies sent as IPIP.
Rob
> A standard ripd won't ever see the RIP44 packets because they're
> encapsulated in an IPIP tunnel packet. The standard ripd doesn't
> know how to de-encapsulate them first.
Of course when you have a single multi-point tunnel interface like in Linux (tunl0), you
could have ripd listening on that interface and it would see the correct packet format.
However, I think the default ripd does some sanity checks that make it fail on the special
assumptions made in RIP44.
Rob
