James Carlson wrote:
Darren Reed writes:
Dan McDonald wrote:
Their "better approach" is employed by our IKEv1 daemon, but it has problems
with file-descriptor limits (when many local addresses exist), and needing to
monitor routing-socket behavior for local-address additions and deletions.
...
The question I've got to ask is, why is the IKE daemon receiving packets for
so many different IP addresses?
Is it a required part of some protocol spec?
Or is it an application design thing?
Or...?
It's the usual UDP application problem: if you're a UDP-based server,
then you're supposed to use the same IP address and port as the source
values in your reply as the client originally used in his destination.
The question in my mind was: why can't the IKE daemon use a single IP
address -
why does it need to use "every" address?
Darren
_______________________________________________
networking-discuss mailing list
[email protected]
