Wireless Filter Not Working as Expected

Issue #33 closed
Rob Kresha created an issue

First and foremost, thank you for forking and continuing to develop tomato, much appreciated.

The issue I'm currently having is a use MAC Filtering to control clients that can connect to the access points. I've got 40+ MACs in my wireless filter table. I have the virtual interfaces set to 'Permit' and most of my clients are able to connect just fine. However I just recently added a new one and it will not connect, passwords are not an issue. I can finally get it to connect if I change the MAC Filter to 'Disabled' or 'Blocked' (which makes no sense since the MAC is on the list). Once I have set it to one of those two settings and am able to get it connected I click the WFILTER link on the clients page (just to validate that I'm not typoing it) and it truly is the same MAC as what I already have in there. To the best of my knowledge, it is only this one device that I'm having an issue with.

I'm running 2019.01 (beta).

Please let me know what else I can help or provide.

Comments (6)

  1. pedro

    And this is expected behaviour - the same as on OFW.
    You can nothing do about it, it depends on WL driver used in the given target.
    I'll add info about it on Wireless Filter page.

  2. Rob Kresha reporter

    @pedro311 @kille72 I've got 3 intel edisons all with the same image of jubilinux on them. This is the only one that is giving me a problem. I had no issue with all of them connecting when using tomato shibby's mod. Please advise.

    EDIT: Oh I see what you mean after looking at the commit. Disregard, I'll try and prune my list I guess.

  3. Rob Kresha reporter

    @pedro311 thanks much for the information. Pruning some entries as mentioned above fixed my issue.

  4. Log in to comment