Telkom still do adsl resets

T

The_Unbeliever

Honorary Master
Joined
Apr 19, 2005
Messages
103,193
Reaction score
10,233
Location
Nkaaaaandla
Code: 
00:00:12 smoothwall PPP has gone down on ppp0
00:00:14 smoothwall PPP has gone up on ppp0
00:00:20 smoothwall Dyanmic DNS ip-update: your IP is already up-to-date
00:30:06 smoothwall System clock successfully updated; using server(s) ntp2a.mcc.ac.uk ntp.psn.ru ntp.cs.unp.ac.za louie.udel.edu ca.pool.ntp.org.
01:18:34 smoothwall PPP has gone down on ppp0
01:18:36 smoothwall PPP has gone up on ppp0
01:18:42 smoothwall Dyanmic DNS ip-update: your IP is already up-to-date
01:30:06 smoothwall System clock successfully updated; using server(s) ntp3.cs.wisc.edu ntp2.mainecoon.com ntp1.demon.co.uk clock.psu.edu ntp3.cs.wisc.edu.
02:00:14 smoothwall PPP has gone down on ppp0
02:00:16 smoothwall PPP has gone up on ppp0
02:00:22 smoothwall Dyanmic DNS ip-update: your IP is already up-to-date
02:30:06 smoothwall System clock successfully updated; using server(s) calvus.rzs-hm.si ntp.ucsd.edu zh2.ntp.carnet.hr zh2.ntp.carnet.hr ntps.net4u.it.
03:30:05 smoothwall System clock successfully updated; using server(s) fartein.ifi.uio.no fr.pool.ntp.org ntp2.theinternetone.net time.deakin.edu.au ntp.tuxfamily.net.
04:00:15 smoothwall PPP has gone down on ppp0
04:00:17 smoothwall PPP has gone up on ppp0
04:00:24 smoothwall Dyanmic DNS ip-update: your IP is already up-to-date
04:30:06 smoothwall System clock successfully updated; using server(s) ntp.ucsd.edu sushi.compsci.lyon.edu tick.tanac.net tick.tanac.net sushi.compsci.lyon.edu.
05:00:11 smoothwall PPP has gone down on ppp0
05:00:15 smoothwall PPP has gone up on ppp0
05:00:20 smoothwall Dyanmic DNS ip-update: your IP is already up-to-date
05:30:10 smoothwall System clock successfully updated; using server(s) sundial.columbia.edu tick.tanac.net reloj.kjsl.com ntp.cpsc.ucalgary.ca uk.pool.ntp.org.
06:00:15 smoothwall PPP has gone down on ppp0
06:00:19 smoothwall PPP has gone up on ppp0
06:00:25 smoothwall Dyanmic DNS ip-update: your IP is already up-to-date
06:30:14 smoothwall System clock successfully updated; using server(s) nz.pool.ntp.org tick.tanac.net si.pool.ntp.org dk.pool.ntp.org calvus.rzs-hm.si.
07:00:20 smoothwall PPP has gone down on ppp0
07:00:22 smoothwall PPP has gone up on ppp0
07:00:31 smoothwall Dyanmic DNS ip-update: your IP is already up-to-date
07:30:08 smoothwall System clock successfully updated; using server(s) ph.pool.ntp.org us.pool.ntp.org nl.pool.ntp.org uk.pool.ntp.org chronos1.umt.edu.
08:16:39 smoothwall PPP has gone down on ppp0
08:16:41 smoothwall PPP has gone up on ppp0
08:16:48 smoothwall Dyanmic DNS ip-update: your IP is already up-to-date
08:30:08 smoothwall System clock successfully updated; using server(s) at.pool.ntp.org ntp.cs.unp.ac.za ntp2a.mcc.ac.uk ntp5.tamu.edu ch.pool.ntp.org.
09:00:12 smoothwall PPP has gone down on ppp0
09:00:30 smoothwall PPP has gone up on ppp0
09:00:36 smoothwall Dyanmic DNS ip-update: your IP is already up-to-date
09:30:13 smoothwall System clock successfully updated; using server(s) ntp.shim.org it.pool.ntp.org dk.pool.ntp.org ntp.cpsc.ucalgary.ca ntp.ip.ro.
10:30:09 smoothwall System clock successfully updated; using server(s) dk.pool.ntp.org ntp.waikato.ac.nz ntp2.theinternetone.net info.cyf-kr.edu.pl uk.pool.ntp.org.

And hourly nogal... :rolleyes:
 
Telkom Internet DOES NOT do ADSL resets and have not done so since Nov 01 2007.
Looks like your dodgy system. Check your cronjobs. It is funny how it is on the hour every hour.

But instead of investigating if it is your side - you immediately blame Telkom... very clever.
 
bonobo_slr said:
Telkom Internet DOES NOT do ADSL resets and have not done so since Nov 01 2007.
Looks like your dodgy system. Check your cronjobs. It is funny how it is on the hour every hour.

But instead of investigating if it is your side - you immediately blame Telkom... very clever.
Click to expand...

A plain smoothwall does NOT have a cronjob doing hourly resets.
 
Mine is not reset - for weeks on end.
Our office line gets reset every few hours.

Dodgy Telkom infrastructure, not planned resets.
 
The software they use to accumulate your throughput usage requires you to disconnect before the tally is forwarded to the counting server.

So, in the beginning they disconnect you once a day to tally up your totals.

Now, when you get closer to your cap limit, they disconnect you more and more frequently to tally up your totals so that you get as little "free" throughput as possible.

Unless a new system has been implemented????
 
stoke said:
The software they use to accumulate your throughput usage requires you to disconnect before the tally is forwarded to the counting server.

So, in the beginning they disconnect you once a day to tally up your totals.

Now, when you get closer to your cap limit, they disconnect you more and more frequently to tally up your totals so that you get as little "free" throughput as possible.

Unless a new system has been implemented????
Click to expand...

Aah, I see. Thanks.
 
stoke said:
The software they use to accumulate your throughput usage requires you to disconnect before the tally is forwarded to the counting server.
Click to expand...

wrong. Usage is accounted for during the session.There is no need to wait until the end of a session. Explain how someone is connected for days/weeks/months has his usage updated then?

stoke said:
So, in the beginning they disconnect you once a day to tally up your totals.
Click to expand...

wrong. Against ICASA ruling.

stoke said:
Now, when you get closer to your cap limit, they disconnect you more and more frequently to tally up your totals so that you get as little "free" throughput as possible.
Click to expand...

wrong... how is that possible to manually keep tabs on 150,000+ users?

stoke said:
Unless a new system has been implemented????
Click to expand...

New as in May2007...

It is amazing how these things are dreamed up...
 
telkom internet do disconnect you.
I have multiple routers running TI accounts, Linksys, Netgear and D-link.

No session goes over +-86309 seconds ( basically 24 hour reset) on any of them.

Not once over the last 5 months
 
The session timeouts are set by the ISP that authenticates your DSL account. Its in the radius reply packets sent back to saix. So its only saix disconnecting you when your session times out with the value set by the ISP. The accounting data is sent to the radius boxes during the session so there is no need to disconnect the sessions. ISP's do it because their systems lack the ability to send a POD (packet of disconnect) to saix after you hit your cap.

My 5c

Mufasa
 
yea, somehow magically my linksys's(3 of them all running different software to each other), d-link, netgear and telkom pots router all reset every 24 hours, at different times to each other.

or maybe i'm just sleep walking and running around and doing it manually
 
They are implying that the ISP is resetting the account,not telkom
 
thats what i said TI( Telkom internet, my ISP)
 
bonobo_slr said:
Telkom Internet DOES NOT do ADSL resets and have not done so since Nov 01 2007.
Looks like your dodgy system. Check your cronjobs. It is funny how it is on the hour every hour.

But instead of investigating if it is your side - you immediately blame Telkom... very clever.
Click to expand...

everything is to blame on telkom after all they almost hold the position for the most useless company in africa!!
 
bboy said:
thats what i said TI( Telkom internet, my ISP)
Click to expand...

hehe, Telkom dsl services don't reset it on the network anymore but its possible that Telkom ISP do by setting the session timeout to 24hours. Telkom a wonderful (*sick hurl vommit*) way to get around icasa regulations.
 
At the end of last month my TI account also reset (i.e. got disconnected, RouteSentry reconnected) every hour or so, before that it never happened and since 1 Aug it's never happened again. Nothing in my setup has changed. Oh well...

EDIT: It happened several times, not only when I got capped ;)
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X