I have a script that changes my hotspot queues that of course now doesn't work on 6.34.2 and need to have this functionality restored. What was the reasoning for doing away with this?
Can you with a ROS loaded PC with the Dude package, tell it to monitor only a certain ethernet port ? Such as ether1 is a public IP and ether2 is a private/hotspot side and you want to Dude to monitor only the devices on the private/hotspot side. Those devices have static ip addresses and you want t...
I get this as well and so far as I have read, it's not supposed to mean anything. However, you have to wonder why it's there if they know about it. Cause actually I have a problem with the hotspot in one instance that I can't figure out at all. With an error before the eyes, it makes me wonder.
I am using Mikrotik-Rate-Limit and it will set the queues properly, but I've still got the problem where Mikrotik will only take the first four characters , no matter what they are.
Is it rate-limit or is it Mikrotik-Rate-Limit ? I'm still having the problem where Mikrotik only takes the first four characters of the Mikrotik-Rate-Limit value from vircom radius.