Robert Elz wrote:
Date: Fri, 21 Jan 2011 15:05:05 -0500
From: Patrick Klos <patrick%klos.com@localhost>
Message-ID: <4D39E6F1.7090202%klos.com@localhost>
| ifconfig sixrd0 inet6 2001:55c:62d8:93c7::1 prefixlen 32
Why /32? That looks wrong, looks to be /64 to me - this looks to be
copied a bit too slavishly from stf (but even there I'd expect a /48
if not /64).
I modeled my setup after the 6to4 (stf) driver's setup. I haven't analyzed the routing implications yet - I'm just going with what stf does right now. (what you said makes more sense to me also, but I wanted to get it working first)
| It's almost as if the IPv6 stack is checking the length, and thinking | the packet is too big to send on the target interface?Unlikely, ping6 sends (by default) really small packets, way smaller than the smallest legal MTU for IPv6. More likely the error message is one of those that is being abused for some similar purpose, and just means "too much something" - perhaps internal routing table loop, orwho knows ...
Actually, it turns out I broke my MTU setting myself, so it was zero. This was my initial problem. I have since gotten my driver to work with Comcast's 6rd bridge router.
What does the kernel routing table look like
(netstat -rn -f inet6)
when the interface is configured?
Once I fixed my MTU issue, it only took a little debugging to get the rest to work. I'm considering merging my code into the stf driver rather then to have a separate sixrd driver?
Thanks for your comments. Patrick