[nSLUG] Aliant vs Eastlink
dteed at artistic.ca
Tue Jul 1 21:04:47 ADT 2003
Hmmm, so perhaps the limited pool of IPs and their problem
with continuous active connections is more of a thing from the past?
I've seen some recent interruptions from Eastlink in my area, but
the IP stays the same when it comes back.
On Tue, 1 Jul 2003, Rory wrote:
> Aliant's service agreement is used to provide leverage against "abusers". I
> think the main problem is filesharing/P2P which tends to drive constant
> traffic volumes and messes up revenue models and infrastructure costs.
> In practice, you can remain connected for days at a time with no problem
> that I've seen. Also the PIX comments that Dop makes are true, but no
> longer relavent to new users since the Mpowered service is being phased out
> and isn't available to new subscribers. With the new service (PPPoE) the
> public IP is assigned to your machine directly instead of through PIX.
> ----- Original Message -----
> From: "Dop Ganger" <nslug at fop.ns.ca>
> To: <nslug at nslug.ns.ca>
> Sent: Tuesday, July 01, 2003 2:32 PM
> Subject: Re: [nSLUG] Aliant vs Eastlink
> > On Tue, 1 Jul 2003, Donald Teed wrote:
> > > Unlimited Service for an account does not translate into
> > > allowing an account holder to remain connected even while
> > > away from the computer or to use a 'ping' type program to
> > > keep their connection alive, such as, but not limited to,
> > > checking email every 5 minutes 24 hours a day).
> > >
> > > I have a couple of accounts at home that are being fed
> > > with fetchmail every few minutes. I didn't think this would
> > > be excessive in contrast with running a server or using
> > > the current P2P stuff. Can anyone with experience running
> > > Aliant's DSL service comment on what the real world picture is?
> > I suspect this is due to the Cisco PIX that Mpowered runs. The way the PIX
> > works is it doles out IP addresses as needed, and when a connection has
> > been unused (no open TCP connections, no UDP traffic) for a set period of
> > time the IP address goes back in the pool, and the user gets assigned a
> > new address if they make a new outbound connection. Back when I was
> > working on Mpowered (admittedly several years ago now) the default timeout
> > was 5 minutes, which more than likely has not been changed - hence the
> > "checking email every 5 minutes" comment.
> > The reasoning behind not allowing users to keep idle connections open is
> > to make sure there's IP addresses in the pool. Similar to a dialup ISP's
> > modems, the IP addresses are oversubscribed (or at least they were), so if
> > all the IP addresses get used up no-one else can get out. It used to be
> > that if the connection table filled up, the PIX would reboot, and
> > *everyone* would lose their IP; I think now it may just drop any new
> > connections instead, judging by the "sometimes it just goes to sleep and
> > wakes up after a while" comments I've heard from a few users.
> > Cheers... Dop.
> > _______________________________________________
> > nSLUG mailing list
> > nSLUG at nslug.ns.ca
> > http://nslug.ns.ca/cgi-bin/mailman/listinfo/nslug
> nSLUG mailing list
> nSLUG at nslug.ns.ca
More information about the nSLUG