bandwidth management

[emonkey]

---

guys, id like to solicit info from intenet cafe owners or anyone maintaining
a considerable size of network, be it commercial or not. i'd like to ask
if you have bandwidth management system configured in your network.
lets say, for an internet cafe, how are you going to guarantee that
one user (end-pc) do not consume all the bandwidth of your pipe?
basically how do you efficienty manage the distribution of bandwidth for
each user. take globe and smart, for their dsl subscription, they have
CIR and MIR. CIR is the guaranteed bandwidth.

i'm asking this because we will be rolling out a commerial service
offering to configure bandwidth management to anyone, initially
targeting internet cafes and call centers.

i'll appreciate any info. thanks
:mrgreen:

[dagget]

you call it QOS.

some routers have QOS usually its more expensive.

ordinary routers don't have QOS so bottlenecks happen.

Some would use linux in a low-cost pc and use it as a router with QOS.

another way to manage bandwidth is traffic shaping.

[emonkey]

its one of the bells and whistles to realize QoS...

you need to basically bundle it with other technologies such as ACL, congestion control,
priority, integrated services, differentiated services, etc..

for most subscribers, QoS should be end-to-end, not just from your pc to your ISP...

[dagget]

so QOS has to be end to end

you can sell it to PLDT or GLOBE then............. so we can get efficient bandwidth.....

[carlou]

this is interesting, actualy i have heard of a device that may do such needed bandwith management?

[emonkey]

so QOS has to be end to end

you can sell it to PLDT or GLOBE then............. so we can get efficient bandwidth.....

it should be end to end, like if your downloading files, it should be from your
client PC and the remote file server. but the cost and complexity of implementing it is
too high. telco's and service providers usually hav QoS on their core network. if you
subscribe to smart/globe DSL, that already includes QoS features. your CIR is the
guaranteed bandwidth. its usually 30-50% of your allocated bandwidth.

for internet cafes or DLS subscribers that is sharing bandwidth to clients, you still need
to manage your allocated bandwidth such that no one client can saturate your CIR. if
one client is downloading 2G of files through bittorrent, other clients should still be able
to browse the internet, or do voip.

[onenet.cebu]

:mrgreen:

[djereza]

Some routers has features that can manage bandwidths...CCProxy is a proxy software and can do bandwidth management as well per client. =)

[dagget]

it all boils down with your router.

there are routers with QOS that can assign bandwidth to each client.

if you are selling is a piece of software more like a traffic shaping software it would be useful for customers who want to control bandwidth using a server.

your competitors are routers also with built-in QOS features. There are only a few routers with QOS and they cost 7,000 to 10,000.

So customers have 2 choices for bandwidth control

1. software like linux or the software products you are promoting.

2. router based QOS. built-in feature. Most Router Operating system is based on Linux.

[emonkey]

some routers specially the one for edge, enterprise and core networks has QoS function...
but a lot of them do not provide the best QoS that fits your requirement and if your unlucky,
your router's QoS simply do not work well. when checking how QoS works for a typical
network device(router or switch or software based-router/switch), the basic rule of thumb is to
check what resource reservation, queueng and linksharing algorithms/protocols are used.
most of these algorithms/protocols are industry starndard such as RSVP, OSPF-TE, LMP for
resource reservation. Popular queueng and linksharing algorithms includes CBQ (Class
Based Queueng, HFSC (Hierarchical Fair Service Curve), Priority Queueng, etc. some routers
particularly cisco's have their own proprietary algorithmns.

my personal opinion on linux based routers is that, they're not really good. linux kernel is not
suitable for a router platform because of its inherent design. there are a lot of linux router
projects, such as LRP, but they're good for home use, small office and toy projects. for
commercial use and critical networks, the worry-free and less risky approach is to use
non-linux routers, such as ciscos, vxworks, BSD and proprietary OS based routers. this is just
my personal opinion based on experience, no offense to anyone using linux
:mrgreen: