Skip to main content
CollabraIT
CollabraIT
New Member
August 11, 2016
Question

Clear MAC reservation from interface

  • August 11, 2016
  • 1 reply
  • 12886 views

I'm testing the MAC reservation + Access Control on my new Wifi interface. If I set Unknown MAC Addresses to Block, it of course blocks any connections that aren't specified. If, however, I specify a MAC to test the connection and then remove it to test again, the computer can still connect even though the MAC Reservation has been removed.

 

How do I clear out the known MAC addresses so that the ones I remove are blocked like they should be?

    1 reply

    ede_pfau
    SuperUser
    ede_pfau
    SuperUser
    August 13, 2016

    Probably the session still existed when you changed the MAC address. Default session idle time is 300 seconds (?). If you don't want to wait, use a different service to test or zap the session table.

    CollabraIT
    CollabraITAuthor
    New Member
    August 15, 2016

    ede_pfau wrote:

    Probably the session still existed when you changed the MAC address. Default session idle time is 300 seconds (?). If you don't want to wait, use a different service to test or zap the session table.

    If this was the case, then surely logging in the next day would have resulted in failure? Or, Monday morning after an entire weekend? Nope, still lets me login.

     

    There has to be some way to fix this, otherwise it calls a security devices security into question...

    CollabraIT
    CollabraITAuthor
    New Member
    August 15, 2016

    Problem update. Manually adding the mac back to the reservation as a BLOCKED address, it still allows the computer to join the wifi network.

     

    So, recap of the problem.

    Unknown MAC addresses blocked

    Individual MAC assigned and allowed

    machine connects and disconnects

    Individual MAC reservation deleted

    machine still able to connect

    Individual MAC reservation assigned and set to block

    machine still able to connect, despite being blocked.

    machine still able to connect after 3 days of inactivity.

     

    I don't know about the rest of you, but I see this as a HUGE security flaw.

    Terms & ConditionsAccessibility statement