a. I will have one 4M/4M symmetrical line and 2 x 10Mb/330kb adsl lines.
b. I will have 200+ users and growing.
c. 95% of client have 3Mb/256k contract.
d. I have many Voip/Skype clients in need of 100% quality link.
e. I have some clients paying for high download speed (>4M)
f. I have no objections to P2P but don’t like client seeding disrupting my HQ line. Download no prob but from adsl.
g. Heavy http download preferably to be routed to adsl lines too. Streaming video on HQ (low latency) line.
- I need to Qos on service.
- I want to shape clients bandwith and assign IP and auth at my gateway (=central location, =border gateway)
- I want to route P2P and tft and possibly long http downloads to adsl lines.
- I want to route all other traffic to symmetrical line.
Can this all be done in one rb1000?
1a. Prerouting Ch.+incoming interface+service id (port/protocol/L7) > conn.marking>package marking>passthrough=no
1b. Queue tree with prioritizing based on these package marks.
2a. Forward Ch.+src.addrs>conn.marking>package marking>passthrough=no
2b. Queue tree with limiting and prioritzing based on subscription classes.
Where to do the routing marking for policy marking?
Or,
two routers:
A: 1. Traffic shaping based on services with mangle (extensive detail, +/- 40 types) and queue tree. Forward chain. (simple)
B: 1. Client bw control based on subscription mangle and queue tree. (Or simple queue?) Mangle Forward chain.
2. Policy routing. Mangle forward chain for connection followed by routing mark for policy routing. Prerouting chain.
3. Router can also do user manager and thus assigns IP and limits by address list. B1 uses address list for speed
limiting of clients and prioritization of business user above moderate and basic user.
I have one rb1000 available and one rb493 and one rb600A available. Which router to use where?
Which process is most in need of cpu power?
I would like to hear some advices without getting into too many details. Just need a pointing in the right direction in stead of inventing the wheel again…
Presently QoS running on main gateway (rb1000) but client shaping and auth remote (dhcp server with simple queues in towers)
Presently third party loadbalancer with 5x adsl lines. Not ideal. Plenty download, shortage in upload. Low quality (high latency, saturation, no dns etc. etc.) at times.