How about updating the P-Throughput field to be more accurate and work in all wireless protocols.
Then we should have this field update every x often (ability to set the x).
Then have that as a $wlan1_pthoughput variable that changes.
Then have the ability to set queue tree and simple queues with simple math expressions =$wlan1_pthoughput * .25 ..
This would allow us to create pthroughput QoS systems dynamic based on the actual link. Also addition of pthroughput options on other types of interfaces including Ethernet etc, so that we can use it as well.
P.S. Add to hotspot profile - “Incoming/Outgoing packet mark” two more mangle rules. Not only packet marks but also a connection mark before them and use that conneciton mark for packet marking. This would make my life easier and my router would finally bread with full loungs beacause I must use this kind of setup, with every client seperate marked.
Support for ECMP labels for mpls ( so we can have dual or more paths to the same destination working).
Support BGP BASED LABEL Distribution for mpls
Support L2 MTU settings like Routerboards
Hi
i think its will be very usefull to add “local adress list” parameter to User Manager/Users for example in my network I have UM on border router with QoS and limitation based on PCQ and adress lists of clients,
but address lists I use for filtering, redirect to any web pages and many diferent things on this border router. will be great if i can use something to add “remote IP to” address list on the same router with “user menager”
for this moment user menager sent “adress list” to radius client but this client only terminating pppoe sesion
It would be very nice for the wirless advanced settings to be able to adjust the SIF, SLOT, and ACK timing by hand and also make it so you can see the values change when setting different distances. As it seems that is a very big part of why there are speed issues and bit erros over the air, especially in 802.11n. Also it would be nice to have the ability to adjust the beacon interval on AP and Bridge mode, this way it can deal with noise better if you can set the beacon from a range of 10ms to standard 100ms. I have helped develope many wireless products and these are a must for performance.
I would love to see Winbox support more than just CHAP protocol when authenticating winbox logins to Radius. I would really like to see it support MS-CHAP or PAP specifically. We use encrypted LDAP backend and it only supports PAP or ntlm_auth challenge tokens, which excludes CHAP. Makes it very annoying to try and maintain our login accounts.
I would really like NOS-style point to multipoint IP tunnel support backed up by proper RIP handling.
This would give backwards compatibility with current implementations and add great flexibility:
-usual endpoint setup → works the same as now
-setup without target address (anonymous target address) → allow adding multiple targets via add route commands (so that the added gateway represents a tunnel endpoint for that IP address or network via the IPIP interface)
-accept RIP broadcasts via the IPIP interface to setup these endpoints dynamically (RIP containing address/mask and gateway which will be the endpoint for that interface - this also needs a network and gateway ignore list option for own network segments on other interfaces)
-send out the interface routing via RIP (address/mask with endpoint as gateway)
I would love to see Winbox support more than just CHAP protocol when authenticating winbox logins to Radius. I would really like to see it support MS-CHAP or PAP specifically. We use encrypted LDAP backend and it only supports PAP or ntlm_auth challenge tokens, which excludes CHAP. Makes it very annoying to try and maintain our login accounts.
Please back to UM CLI commands as v4.x. Especially assign profile to user is not useful on new version.
For me, credit system was much better then profile. I couldn’t use properly.
But caller id good feature v5.x.
