Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Jaga]

After spending some time with my new DIR-655, I have come to the conclusion that it is a solid and good piece of hardware.  The software for it however has some areas that could be improved upon.

One of those areas is wireless Guest access - allow us the ability to throttle guest bandwidth use (up and down streams) so that we can have this option on and not have it affect either our network performance, or broadband limitations.

I for one would gladly provide a neighborhood wireless network, to be used either as a backup when someone's goes down, or when a guest is in the area and cannot find an open network.  But I can't have them adversely impacting my primary WAN connection, and right now if I left guest wireless on 24/7 they could.

Even something as simple as a checkbox and two linked dropdown lists that allow you to pick kbps/KBps to throttle them to.

[Lycan]

We've made several requests for feature changes to the guest wireless account.
1) Bandwidth throttling.
2) Custom DNS servers
3) Locking of the Band. (e.g. 802.11B/G/N)

[Jaga]

Those would all be very welcome I am sure.

Thanks for the update Lycan!

[Jaga]

Only have one other suggestion for guest wireless features, since there's a list going:  a limit for the number of wireless guest connections at the same time, and perhaps even a forcible disconnect for those without activity after X minutes.

Opening up a guest channel and limiting the bandwidth can be a nice thing, but if you saturate that SSID with a large number of wireless clients, it could kill it from a usability perspective.  5 clients sharing 100kbps are one thing..  25 or more might ruin it.

Granted - I'm shooting for the moon here.  But since there are suggestions for improvement on the table, I thought I'd add this one.

[Lycan]

Noted.

[EddieZ]

We've made several requests for feature changes to the guest wireless account.
1) Bandwidth throttling.
2) Custom DNS servers
3) Locking of the Band. (e.g. 802.11B/G/N)

When they're at it, let them get some overall bandwidth throttling, not only with Guest access.
And separate DNS servers are usefull sometimes, but for the sole purpose of blocking certain sites through OpenDNS it would be a waste.
Locking the band though is a very good one, as well as the limit on connected guests.