local traffic, international traffic?

naeem

naeem

Expert Member
Joined
Feb 16, 2004
Messages
1,066
Reaction score
108
Location
South Africa.
Ok, might be a dumb question but hope someone can clear up stuff.

How does the ISP or Telkom differentiate with local & international.

eg. 1)
Say i have a website .co.za domain but hosted in USA ?

eg. 2)
using a local torrent site, and if theres an international user who is seeding, then what?

Also, anyone know if Imagine offer concurrent log-ins?
 
domain doent count at all...if its in the states ist int traffic and trust me you cant cheat that

same for the seeds...if theyre overseas its int traffic
 
naeem said:
How does the ISP or Telkom differentiate with local & international?
Click to expand...
They dont (from a product not routing point of view).

Thats why both local & international traffic both count toward your international cap.
 
IP addresses and the actual country where they physically are is stored in a rather large database. This database kept up to date by the ISP's and the peeps who sell IP Address ranges [classes]. This database is also used by routers to route effectively and hopefully - efficiently.

One such database is AFRINIC, which is usually quite accurate [well....]
Try it : http://www.afrinic.net/cgi-bin/whois

So - teklom examines a request, and if it's for an ip address that i knows is not local according to one of these databases, then, if u're capped, they block the request.
 
They softcap you based on all your traffic. If you got a 2Gig account and you decide to download a 2.1 Gig file locally on the 1st, you would get no international for that month.
 
yes i agree my point was just that they need to be ABLE to distinguish to implement a soft cap....and stoke i dont think they do it on an ip level. Its based on the actuall routes taken (the account is done by the edge routers on all their peering and upling links)
 
Bob, I think the problem is that most international content is cached so when you are browsing "international" often you're not actually connected to international servers, thus they cannot differentiate between local and international while calculating your cap.

Once you're capped however they simply limit your ip range and voila.. only local.

I may be wrong but i dont think so, this does raise many questions though:

If it is coming from a local server (cached) why should it count towards your cap since local is abundant and very cheap?

If most international comes from local server why dont they let you access it when you are capped?
 
If its international traffic that is fetched from local cache, it shouldnt count as international traffic in the first place.

This can be done but currently I think the telkom IPconnect costs locally work out very similar to international costs, so from the first tier side, its pretty pointless to impliment or differentiate between local and international.

I really think if IPconnect fees get dropped, lowered, humane.. local and international differentiation will start to make sense and will be offered.
 
Last edited:
BobTheUglgBunny said:
...and stoke i dont think they do it on an ip level. Its based on the actuall routes taken (the account is done by the edge routers on all their peering and upling links)
Click to expand...
Yup - once they've calculated that you've exceeded your cap they give you a new ip address that is routed differently.
But I was anwering the original question of "How does the ISP or Telkom differentiate with local & international", and this is how they would have done it if they were not counting local towards the international cap, which is theft in my mind, but newayz ... we're all saying the same thing.
 
Telkom don't actualy differentiate from local and international traffic at all. It's easy to restrict your international access since you get lumped in a low prioity queue on the international link its self, other stuff will automaticly go via local routes.

If they wanted to then all they need do is check what BGP4 AS the IP is destined for. More generaly this is "anything other" than what is a local peer, or the current AS ;)
 
Its pretty easy, to differentiate local traffic from international.. How do you think we do it with our proxy?

In layman's terms, you need one public ip for each client.. he gets hooked on the serverside system via his ip to an account... whenever the client access ip'X', it will either tunnel via the international gateway, or local gateway.. all traffic accounted for via the international gateway can be billed at Rx and all via local at Rx.

Effectively eliminating the whole SAIX method of using different ip ranges. Im very sure IS do their monitoring the way I just mentioned, except.. atm they do get more profit out of counting local/international to the cap.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X