-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What's the most interesting small town you've visited in South Africa?
assigning ports
- Thread starter dotcat
- Start date
Answer my own question sort off
This is what my friend sergie and larry tell me over at goog.
Kiwi based info but im sure it work the same way over here.
"your internet service provider (ISP) is responsible for sending you data that you request over the internet. Paradise, Xtra, Clear - whatever, it doesn't really matter - receives your login request and authenticates it to their RAS, which in some cases places a restriction on traffic at that point. Their main servers then receive your incoming request (your UPLOAD) and then routes you the appropriate data (your DOWNLOAD). This data leaves the ISP's main server, and is transported via. Frame Relay (or FRY over ATM) to the TC Data Centre (based in Auckland - possibly Wellesly St. West I suspect, but maybe not) The TC Data centre then sends the data to your local exchange (via FRY, or ATM then FRY again), where it is passed through the DSLAM to your line, and then into your house. The speed at which this happens varies, but is usually more than five thousandths of a second. When the data is received at the TC Data Centre, the server there assigns the data to the appropriate port on the DSLAM at your exchange - there are up to 800 ports on each DSLAM. If more than 800 people want DSL at that exchange, not a problem, they'll just slap another DSLAM into the exchange (if Telecom can be bothered) - it's basically just a router. The port that it sends this data to is what controls the speed that you get at your house - your telephone line is assigned to this port in the DSLAM. Therefore, no matter what login you use, jetstart/stream etc, you will only receive data at the speed the TC Data Centre sends it at - and that is governed by which port your telephone line is connected to at the exchange. The actual packet shaping server runs software that sets the physical transfer limit, and the DSLAM port (also called NAS port/routing) provides the classification between jetstart and jetstream speeds. Billing is done on layer 3 traffic, sometimes layer 4, but this is being phased out due to billing inconsistencies from what I’ve heard. You may have noticed that sometimes you'll be uncapped on jetstart - this is sometimes due to the TC Data Centre's billing server - between 11pm and 4am on Sundays this machine is compiling the weeks usage results for billing purposes - I've been told that this can sometimes lead to faster speeds on jetstart, although I haven't experienced this yet. (N.B. the bandwidth pools for jetstart/jetstream have now been separated, so this may not apply anymore) Any other instance of uncapped speed can probably be attributed to temporary hardware failure (the duties of the data server may be swiched to another server that doesn't have the ability to assign data-limited NAS ports perhaps? Routine maintenance on billing/traffic machines?) but there is certainly NO way to increase your jetstart speed beyond the 128kB/sec threshold by installing any special software, playing with the registry, or doing anything other than asking your ISP to upgrade you to jetstream. In fact, if you go to a friends house who has jetstream, and log in using your jetstart user ID, you will still download at a full jetstream speed, and your friend will still be billed as usual – the billing is gathered from usage vs. phone number, and the login is just a basic unsecured authentication method to keep the RAS happy.
Further information…
ATM circuits in New Zealand are typically fibre trunks with a capacity of 155Mbit/sec maximum, and around 30Mbit/sec minimum.
This is what my friend sergie and larry tell me over at goog.
Kiwi based info but im sure it work the same way over here.
"your internet service provider (ISP) is responsible for sending you data that you request over the internet. Paradise, Xtra, Clear - whatever, it doesn't really matter - receives your login request and authenticates it to their RAS, which in some cases places a restriction on traffic at that point. Their main servers then receive your incoming request (your UPLOAD) and then routes you the appropriate data (your DOWNLOAD). This data leaves the ISP's main server, and is transported via. Frame Relay (or FRY over ATM) to the TC Data Centre (based in Auckland - possibly Wellesly St. West I suspect, but maybe not) The TC Data centre then sends the data to your local exchange (via FRY, or ATM then FRY again), where it is passed through the DSLAM to your line, and then into your house. The speed at which this happens varies, but is usually more than five thousandths of a second. When the data is received at the TC Data Centre, the server there assigns the data to the appropriate port on the DSLAM at your exchange - there are up to 800 ports on each DSLAM. If more than 800 people want DSL at that exchange, not a problem, they'll just slap another DSLAM into the exchange (if Telecom can be bothered) - it's basically just a router. The port that it sends this data to is what controls the speed that you get at your house - your telephone line is assigned to this port in the DSLAM. Therefore, no matter what login you use, jetstart/stream etc, you will only receive data at the speed the TC Data Centre sends it at - and that is governed by which port your telephone line is connected to at the exchange. The actual packet shaping server runs software that sets the physical transfer limit, and the DSLAM port (also called NAS port/routing) provides the classification between jetstart and jetstream speeds. Billing is done on layer 3 traffic, sometimes layer 4, but this is being phased out due to billing inconsistencies from what I’ve heard. You may have noticed that sometimes you'll be uncapped on jetstart - this is sometimes due to the TC Data Centre's billing server - between 11pm and 4am on Sundays this machine is compiling the weeks usage results for billing purposes - I've been told that this can sometimes lead to faster speeds on jetstart, although I haven't experienced this yet. (N.B. the bandwidth pools for jetstart/jetstream have now been separated, so this may not apply anymore) Any other instance of uncapped speed can probably be attributed to temporary hardware failure (the duties of the data server may be swiched to another server that doesn't have the ability to assign data-limited NAS ports perhaps? Routine maintenance on billing/traffic machines?) but there is certainly NO way to increase your jetstart speed beyond the 128kB/sec threshold by installing any special software, playing with the registry, or doing anything other than asking your ISP to upgrade you to jetstream. In fact, if you go to a friends house who has jetstream, and log in using your jetstart user ID, you will still download at a full jetstream speed, and your friend will still be billed as usual – the billing is gathered from usage vs. phone number, and the login is just a basic unsecured authentication method to keep the RAS happy.
Further information…
ATM circuits in New Zealand are typically fibre trunks with a capacity of 155Mbit/sec maximum, and around 30Mbit/sec minimum.
Last edited: