Opened 5 years ago

Closed 4 years ago

#1447 closed defect (fixed)

Class P routers

Reported by: zzz Owned by: zzz
Priority: minor Milestone: 0.9.20
Component: router/general Version: 0.9.17
Keywords: Cc:
Parent Tickets: Sensitive: no

Description

Have an easy checkbox on /config to set 'unlimited', say that it's for data center only (unnatted), verify by checking for interface with public IP, make bw and conn limits huge, call it class P in caps… or maybe class X, to leave room for future classes higher than O but not unlimited.

Subtickets

Change History (4)

comment:1 Changed 5 years ago by zzz

Also required: a max memory check, and a new bloom filter setting, as the false positive rate will get really bad over 4 MBps

comment:2 Changed 5 years ago by somewon

My vote would be for this to be class X, with an additional class P for routers with bandwidth 256KB/s+, or possibly even 1024KB/s or more. Many home users these days have fiber to the premises or other high-bandwidth connections that provide symmetric 25-100mbps, and the number of users with these connections is growing all the time. I feel like it would be great to be able to utilize that bandwidth more effectively by adding a class that's somewhere well above the current "O," but perhaps not quite all the way to "unlimited," even if the router's bandwidth usage wouldn't actually be "unlimited" in practice.

I know that I have personally been disappointed by how little of my own very high speed home connection has been utilized for the network.

comment:3 Changed 5 years ago by zzz

Owner: set to zzz
Status: newaccepted

stubbed out (only) in f6ee726959d1d72b6ecb55ed17a8f5373c6433e7 0.9.17-12

comment:4 Changed 4 years ago by zzz

Milestone: 0.9.190.9.20
Resolution: fixed
Status: acceptedclosed

P/X in 663b04c71b280e860821cfe71fa8f5f5207b0a4a 0.9.19-14. There's no checkbox as suggested in OP; it's simply class X if over 2000 KBps share bandwidth. X still has limits, but they are really high.

Larger Bloom filter checked in early in 0.9.19-x cycle - see #1505.

Closing ticket, although we may adjust the limits and thresholds later.

Note: See TracTickets for help on using tickets.