David Allen wrote:
On Fri, Jul 25, 2008 at 10:12 AM, Matthew Seaman
<[EMAIL PROTECTED]> wrote:
Chris Pratt wrote:
Carefully not answering the 'why do these packets come from the
wrong address' question,
Deliberately addressing the question of 'why do these packets come
from the wrong address' question which Mr. Seaman avoided
...heh, heh heh. Good job with the wording guys. I smiled brightly when
I went through this ;)
Since I've replied but clipped out any further context, I'll add a
bit... I agree with David in that this is purely a routing issue.
What (IMHO) it comes down to is 'source address selection'.
I've been more focused in this scope within IPv6, but it is apparently a
problem as well with IPv4, in a different manner.
Perhaps this will become more of an issue as more people get used to the
understanding that having multiple addresses per interface is the design
goal, not an alias workaround.
At one point I was advised that there is the ability to use multiple
route tables within -current. If the box is being designed for only one
application, could you try the new implementation of routing as opposed
to making the application fit?
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"