Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Pool handling strategies (was: IP Addresses needed for 4048)
> 1) I want to revert the "unclean shutdown" argument. If a user drops
> his connection with TCP connections still open, these connections
> will live _forever_ - constantly retrying with a new segment every
> minute or two. This is _evil_ when you use dialed connections. If
> an IP would be reused fast, the dangling TCP connection would be
> RSTed by the new target soon. The dangling TCP lives as long as
> the IP is _not_ reused.
One thing I'm not is a TCP expert, so I may very well be wrong, but
shouldn't the sender TCP react to the ICMP Host Unreachable messages
it's going to receive in response to anything it tries to send, thus
terminating the connection just as effectively as an RST would?
> My thinking about this (likely not Ascends - bad enough):
>
> 1) Pool IPs should be handed out with a "try-my-best-to-reget-the-old-IP"
> strategy. If the IP cannot be reused or the NAS has no information
> any longer about which profile did have which IP a hour ago, it should
> be LRU - but only then.
I put exactly this into the old Max feature request box on the web site
about a year ago. You don't see it yet, do you? :-(
> 2) Pool Only needs another mode, lets call it "Relaxed". It means that
> it allows the user to get an IP of his choice as long as this IP is
> in the pool specified by the user profile and is not currently in
> use (obviously). This would allow the user to reget his old IP if
> at all possible even when the NAS has forgotten about it.
Sounds like a good extention of the previous.
-Phil
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
Follow-Ups:
References: