🚀 go-pugleaf

Bruce Esquibel <bje@ripco.com> wrote:
> dye <dye@adsl-64-108-194-61.dsl.chcgil.ameritech.net> wrote:
> 
>> At the time, chicagonet.net didn't detect two 64k connections,
>> so I got all the computers in the network 128K access for
>> $15/month....a bit of an improvement over 40k "dialout"
> 
> Hmm, that doesn't sound right.
> 
> Maybe they didn't detect it but must of permitted it, the channel bonding
> for ISDN was mostly an option to support, I don't think it was "on" by
> default with most hardware.
> 
> Besides the profile to support the bonding, the stuff we used (livingston
> and 3com) I think used a stock profile setting "Line-Limit=1" so if someone
> borrowed someone elses login and tried to use it, both connections were
> dropped.
> 
> I'm just saying, was probably more intentional than accidental.
> 
> Maybe they outsourced.

I think I used chicagonet if it was the NT (really) based ISP that just 
rented dialup pool connections from level3 or something like that.

lots of those places really didn't know if you had both channels up. It 
took RCN years to notice I (and everybody) was doing that.

When that changed, I got the phone bill that I though would be thousands 
of dollars, but due to new regulations was capped and each call was just 
fractions of a cent or something like that. My router had been dialing on 
that second channel for a week or something before I noticed.

Since it was a real router (cisco 2620 I think), I never really noticed 
all the dozens of usually meaningless lights flashing as on a modem or 
terminal adapter. Traffic shaping on that thing with whatever IOS I had 
caused it to crash too. So yeah, in the mid 2000s I was using traffic 
shaping based off traffic types to get the most out of my ISDN.