-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spring Cleaning #526
Comments
Please add: ^ I'll look at the file share one because I can definitely reproduce it. |
Thank you for putting this list together -- identifying these little issues reported on the forum and putting them together into a single list like this is very helpful. However, I edited your comment to remove subnet bandwidth monitoring -- this isn't really technically possible. Once a connection has been NATed it's not possible to monitor outside the router that's doing the NATing. |
@ericpaulbishop not problem, I had not yet thought the subnet issue thru, but I knew it was an open issue on the forum. |
Can check off "File Share User Passwords" after #527 is accepted. |
I can't seem to debug the quota crash issue.
|
I am looking into the quota crash issue now. Thank you for looking into it, confirming it, and providing steps to consistently replicate. That helps, a LOT. |
The quota QoS was an IMQ issue -- the latest updates to the IMQ patch were causing it to crash. Reverting the updates fixes the issue. |
I figured it was imq. |
Interestingly we added those patches to help a previous issue someone was having with IMQ |
I'm pretty sure I could add back the multiple queue support, though I took it out to be sure. It's the other patch that's really problematic, the one that moves the destructor. |
I did a diff against the 4.4 config and they used the new destructor location as well I believe. Maybe a reversion and wait for complaints to resurface is the best action here. |
@ericpaulbishop Re "Once a connection has been NATed it's not possible to monitor outside the router that's doing the NATing," I'm wondering if you're referring to a multiple router setup. The word "outside" makes me think that, but maybe you mean in it a way that I just don't understand (I didn't see the original comment to provide context). On a single-router Gargoyle 1.9.1 setup, I enabled Guest wifi using Steps 1-4a (slightly tweaked) of this: It allows Guest wifi to be on an independent subnet. Bandwidth Usage/Distribution ignore the Guest subnet, however (it does show up in Connected Hosts). Is that scenario also not possible? Thanks. |
@lantis1008 suggested that we need to do a bit of Spring Cleaning before the next stable release so here is a list of known bugs that we can check-off.
Please reply below if you have a bug to add or are working on one of the bugs. I will tick them off as we go.
The text was updated successfully, but these errors were encountered: