I'm thinking about the concept of block-caid-mismatch and as you may know
ca-profiles/block-caid-mismatch
Code
true/false (default: true) Block all replies where the request had a different ca-id. Determines whether M flag transactions are blocked or not (i.e returned as failures to the clients). Since the cache is global, it is possible for a client to send requests to the wrong port and still get valid replies (which may cause it to ignore the caid in the card-data and keep sending to the wrong port - potentially destroying the service mapping for that profile).
NOTE: As of 0.9.1, this will also apply to cross-profile cache hits that have the same ca-id (but where ecms were sent to different profiles). Such configurations with several profiles receiving the same traffic aren't really supported, but if you you know what you're doing and you're sure you understand the implications - it will continue to work as before if you set this to false.1) As above said it is possible for a client to send requests to the wrong port and still get valid replies how a client gets valid cw reply when he send a wrong caid in a wrong port and that reader only sorted to receive and process only one specific caid in oscam!
2) what is cross-profile? how it works?
