Joel Wiramu Pauling wrote:
> Thomas Salmen wrote:
>>Sorry, but Craig is right. Because you are on a FastIP Direct line, your
>>traffic never crosses the Orcon network. Orcon simply provides
>>authentication services; there is no way Orcon can ratelimit or throttle
>>your connection, upstream or down.
>
>
> Then why was I told by an Orcon Tech (not a helpdesker) that all the jpp
> 192kps plans were throtled and switched a few months ago, and so Why am
> I getting 160kps only?

I have no idea, and someone from Orcon can offer an answer to that.
However, as stated, Orcon cannot rate limit traffic on FastIP Direct as
the traffic never hits their network.

>>The speed as reported by your modem is simply the size of the PVC connecting
>>back to the local DSLAM. DSL lines are throttled in two places: first, by
>>the size of this PVC, and second by the profile applied to your line on the
>>aggregating B-RAS. It's entirely possible for your DSL line speed to be set
>>to 320 while a 128k traffic shaper is applied to the upstream on your PPPoA
>>session.
>
> I am aware of that, but it eliminates a line issue. Who does the pppoa auth... the ISP...
> So they get a chance here to rate limit, correct?

No. The ISP receives a proxied RADIUS authentication request from
Telecom. The PPPoA authentication happens at the Telecom access device.
  The ISP does NOT have the opportunity to inject rate limiting.

All you have proven is that you are not being ratelimited by the DSLAM,
which is one of many places that traffic can be controlled.

>>If you don't change services (whether to UBS, WSB, or some other
>>alternative), then your line will stop working, soon, permanently. That's a
>>Telecom decision, and sadly no amount of complaining will make any
>>difference.
>
>
> I have explained my situation to both telecom and orcon, so turning off
> my connection is complete BS! I am sorry it's just not acceptable
> practice. I don't pay to have my connection turned off so I can ring my
> ISP. They can RING me like any normal business would do, especially
> having it happen when it's CLEAR from my notes that I don't want to
> switch and am well aware of the options.

So it's simple: Hurry up and make the change, or you will shortly have
no service.

> Also, I have arranged for Telecom to extend the grace period, it's all
> up to Orcon now to continue to offer Auth, I have also explained this to
> orcon, and they have (well the last person I spoke too) said that if
> telecom don't turn off the connection (as they have assured me they
> wont) then they will continue to auth...

I would be highly surprised if TNZ had agreed to this. Furthermore,
Orcon will have no choice to not offer the auth when (not if) Telecom
turns off their ability to do so as per the commercial arrangements TNZ
and Orcon have.

If you haven't moved, given the opportunites given to you by TNZ and
Orcon, you are shooting yourself in the foot.

> You see I am moving end of next month. If I am forced to move to UBS for
> a month I then get extra costs involved in paying a disconect fee, orcon
> also ends up paying for the churn fee, there has to be a provisioning
> request, (taking from 14 days to 3 weeks in some cases). And so I end up
> with a downtime of at least 1-2weeks. + the UBS plans are all more
> expensive than the current one.

In my experience with UBS (which is admittedly minor, as I've only
bothered to churn one connection), it was more a fact of a few hours
downtime from the time my PPP session was dropped, to the time I
corrected my username to authenticate as a UBS user.

This was with Orcon.

It was, to my surprise, reasonably painless.

Also, don't assume that Orcon would be paying a churn fee.

> Basically Telecom was happy to keep the exchange and port "live" for
> another month, so that I don't have to endure the changeover crap.

I'd be surprised.

aj.

-- 
This message is part of the NZ ADSL mailing list. 
see http://unixathome.org/adsl/ for archives, FAQ, 
and various documents. 
To unsubscribe: send mail to majordomo@lists.unixathome.org 
with "unsubscribe adsl" in the body of the message