> Anyways it looks like what is happening is the router trying to do
> proxy arp is (correctly) considering a /32 (the arp entry) be a more
> specific route than the /29, and the /32 refers to itself, so it
> balks.

Except the arp entry is a proxy arp entry, so it shouldn't be used for
packet delivery.  Or perhaps it's not, and that's the problem - but
then how do I fix it, how do I create an arp entry that *is* a proxy
arp entry?  Surely there must be *some* way; pppd presumably manages.

> That said sending out an icmp redirect to itself is almost certainly
> the wrong thing to do in this situation (icmp ttl-exceeded might be
> more correct).

It's not a redirect to itself as far as the IP/ICMP layer goes; A does
not have the address 10.10.10.74, only .73.  The MAC address for .74 is
the same as for .73, yes, but that's what proxy arp entries are all
about, no?

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B