Re: question about socket with link local addr

Christian:

I'm very glad you agree with me.

This connectivity can't be achieved in currently available sockets
applications, as they have no concept of where and how to put a routing
entry in place.

And, as I said, that in the discussion, it was decided that we don't need to
care about currently shipping applications and/or stacks that may not
support this application of interconnectivity.

Best Regards

Jim Busse


----- Original Message -----
From: "Christian Huitema" <[email protected]>
To: "Jim Busse" <[email protected]>; "Philip Nye" <[email protected]>;
<[email protected]>
Sent: Thursday, July 31, 2003 6:30 PM
Subject: RE: question about socket with link local addr


> I think it's not a stack issue at all, it's a sockets issue.  A
generic
> sockets issue, not a "Mac-only" sockets issue.  And, I think all
sockets
> apps will fail this interconnectivity as a result.

We discussed that before, you should go read the archives. Having
several subnets on the same link is fairly common, and all network stack
allow you to handle it. You just have to add a routing entry for the
subnet 169.244.0.0/16.

-- Christian Huitema