Just playing around with the queueing options on my own ethernet firewall box at home here (rb153).
I had problems where when uploading (with ssh scp), other interactive traffic crawled and barely worked. I changed the ethernet queue type, made some minor adjustments to it, then setup a mangle to mark ssh traffic, then made a simple queue for the mangle, so the pcq would be applied to it.
Now, multiple ssh activities behave much nicer together. ssh logins work smoothly while ssh scp is uploading. It’s a good setup now.
Anybody notice anything I am off about or should have done differently?
A connection mark applies for the two way association and is done by the help of connection tracking. Once a packet is marked then the entire conversation is remembered and bares that mark for the entire lifetime of the conversation (two way association).
A packet mark applies only for that specific packet and is not remembered if a new packet in the conversation (two way association) shows up.
However it does not prove granular enough to perform QoS on all packets in an association.
Well, I’m flattered to be considered a master, but I am certainly not omnicient in the ways of Mikrotik. I’ve just been doing IP networking for 14 years that’s all, and have figured out various practical uses for Mikrotik in the last couple.
So it looks like the type of mark (connection versus packet) make some minor difference. But I would have to use connection since i’m using pcq right?
One interface goes to an old breezecom radio (The cobbler’s children have no shoes), the other interface goes to my home LAN.
Questions: Any benefit to changing the ethernet queue type to pcq elsewhere instead of pfifo? The only downfall is that I presume I would need connection tracking turned on to use the pcq type of queueing. Any other potential side effects? This sort of fine tuning of queueing probably isn’t necessary on high bandwidth links.
There might be a benefit on other interfaces but it might also cause problems.
Are you sure you need connection tracking to use PCQ?
Using connection tracking has many side effects.
You might find it refreshingly absurd when someone decides to TCP ACK flood the connection tracking router, or anyone behind the connection tracking router.
well, if connection isn’t needed for pcq (I assumed it was because pcq stands for per connection queueing), that makes it more flexible.
I already use connection tracking on edge routers to manage p2p traffic, so connection tracking isn’t optional. I do reduce some of the timeouts there, but haven’t had problems with connection tracking.
