Christian Korber
Christian Korber
@stintel : I am still in the process of making this optional. So far I have followed your advice with the lldp package and changed it accordingly. Nevertheless I now...
Thank you for your input. I will work further in that direction.
Hi, I looked in your issue. Could you please test in your `/etc/init.d/mwan3` if changing line 80: `for rule in $($IP rule list | grep -E '^[1-3][0-9]{3}\:' | cut -d...
So if I understand you correctly you mean that it is not useful to enable the whole range, because the first byte contains important information that should not be manipulated,...
I get what you mean, I think. The first byte holds valuable information that shouldn't be touched. But if I limit it to bytes after the oui, we should be...
Better? :) I dropped the CIDR approach and let it parse for ranges that are set or return as usual. If the range is wrong (that is if the lower...
Does that work for you @brada4 ?
ping @jow-
But I meant what I wrote? AFAIK the '!' negates the range and applies to the opposite, so it handles every MAC not in the range. I could change it...
``` If a range is specified with '!', like '!00:11:AA:00:00:00-00:11:AA:FF:FF:FF' it handles every MAC that is not within the range. ``` I rephrased it. Is it now clearer?