Is there equipment that, short of a fixed ip, tries to reassign the same
ip back to the same user? Ie, puts the ip address in a fifo but pulls it
out early if it's the same user calling back.
Is there equipment that, short of a fixed ip, tries to reassign the same
ip back to the same user? Ie, puts the ip address in a fifo but pulls it
out early if it's the same user calling back.
(Lucent)Livingston Portmasters and other ComOS-based devices such as old USR
Total Controls.
Rubens Kuhl Jr.
Is there equipment that, short of a fixed ip, tries to reassign the same
ip back to the same user? Ie, puts the ip address in a fifo but pulls it
out early if it's the same user calling back.
I was working on some radius code to do this. Bascically allocate
everything out of a big ip pool and keep track of which user each IP was
assigned to last, and if when they re-connected, the IP was still
available, re-assign it to them.
However, I quit working on it when I discovered the following...
> > I bet Ms. Thorton never heard that TCP can preserve idle connections
> > when dial-up link is down. Yeah, dial-on-demand is such a hard thing
> > to do!
This is great and wonderful, EXCEPT the microsoft stack WILL NOT keep a
connection open across multiple "dialin sessions". This effectively
breaks any desire to be semi-statically allocated.
Microsoft's crappy stack strikes again....
- Forrest W. Christian (forrestc@imach.com)
When we started out years ago, every user got a static IP. That's since
changed, but I've always thought a decent NAT between the dialup equipment
and the net would be nice. The user would always get the same address
back and could resume their session... I actually did the inverse at home
for some time with IPFilter's NAT. I could have a bunch of term sessions
on various boxes and resume all of them when the router/pc dialed back in
after being dropped. I did have a static IP, but only one for about 5
machines...
Charles