P2P queue stops working after a few hours

RouterOS General
1

I have the following queue on a MT acting as PPPoE Server:

[admin@pppoeserver] > queue simple print 
Flags: X - disabled, I - invalid, D - dynamic 
 0    name="p2p" dst-address=0.0.0.0/0 interface=ether1 parent=none direction=both priority=8 
      queue=default-small/default-small limit-at=1000000/600000 max-limit=1000000/600000 total-queue=default-small p2p=all-p2p

Ramdomnly, after a few hours, the queue just stops working as it couldn’t identify any P2P traffic… There’s no bytes incrementing either TX or RX and, if I disabled/enable the queue, it starts to work again…

What’s the catch? :slight_smile:

2

First of all target-address is necessary for ‘queue simple’ entry (it will not work unless target-addres is not specified).
interface should be used when one-way traffic limits are required for the configuration.

3

Well… As I said: It IS working… The problem is that it stops recognizing p2p traffic after a while…

4

that is because of encrypted p2p traffic

5

Elaborate?

I mean… I’m aware of encrypted traffic but it should recognize at least some traffic, I guess??? I have 800 simultaneous users on that server, I doubt they all have encryption enabled… The queue don’t recognize any traffic at all after a while and it starts working again by simply deactivating/reactivating the rule… Or, am I missing something about this encrypted p2p thing?