Dear colleagues,
we use CHR ROSv6 as a SSTP concentrator and, for security purposes, need to gather netflow information from SSTP connections.
The current way to configure interfaces under “/ip traffic-flow” is either ‘all’ (and, thus, netflow collector will receive lot of unnecessary information like encrypted SSTP traffic) or exact list (and, thus, need to specify hundreds of interfaces and update the list upon changes).
The ways to solve the problem are:
- specify exceptions like “/ip traffic-flow set interfaces=all,!ether1” which seems to be unsupported;
- specify per-interface / per-profile export (e.g. /ppp profile x set flow-export=yes) which seems to be unsupported too;
- use kind of bridge, which will be used by SSTP server to “bind to” and which can be specified as a traffic-flow’s interface.
So, the question - whether (3) can be implemented for SSTP server or any other ways to precisely export flows are available?
Thank you.