You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently monitor the connection to the Switch (NETWORK_STATE_INTERFACE=cat "/sys/class/net/$INTERFACE/carrier"). If THRESHOLD_DOWN * TIMER is reached, we reset the setup.
I was wondering if this is the behavior you are looking for. In our environments it is more common that the client side is changes and thus this side should be monitored (e.g. because the computer is shut down or another laptop is plugged in).
It is not a disaster to not reset the script in this case. The only real impact is that we imitate the MAC of the initial plugged in client instead of updating the MAC to the new one. There will be issues if the client is plugged into the same Swicht but on a different port (which is common with mobile workplaces).
The text was updated successfully, but these errors were encountered:
We currently monitor the connection to the Switch (NETWORK_STATE_INTERFACE=
cat "/sys/class/net/$INTERFACE/carrier"
). If THRESHOLD_DOWN * TIMER is reached, we reset the setup.I was wondering if this is the behavior you are looking for. In our environments it is more common that the client side is changes and thus this side should be monitored (e.g. because the computer is shut down or another laptop is plugged in).
It is not a disaster to not reset the script in this case. The only real impact is that we imitate the MAC of the initial plugged in client instead of updating the MAC to the new one. There will be issues if the client is plugged into the same Swicht but on a different port (which is common with mobile workplaces).
The text was updated successfully, but these errors were encountered: