You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the protocol attributes are present under ndpi_private.h file which is not by default added to /use/include/ndpi folder while we install this library. Is there any way in which we can use the protocol specific fields once the flow is detected aa a protocol. For example,
STUN --> Mapped_Address, Relayed_Address.
Just need to know whether is it possible to use them when we install nDPI as library OR this is just for internal use....
Please help on this topic.
The text was updated successfully, but these errors were encountered:
ya, those are defined in ndpi_typedefs.h...Thanks for correcting...
Also, I have attached a pcap where in there are RTP packets inside the TURN channel Data, but when i process this the library flags the master-protocol as STUN and APP-Protocol as ViberVoip. But lets say in cases, where there is RTP inside TURN channel OR there is RTP inside STUN(generally as part of DATA attribute, which we see for Skype and Teams calls) can we have a way where in we can flag the packet as the containing RTP data. i mean any attribute i can access which tells me this?....I have attached both viber and skype pcaps.
Currently, the protocol attributes are present under ndpi_private.h file which is not by default added to /use/include/ndpi folder while we install this library. Is there any way in which we can use the protocol specific fields once the flow is detected aa a protocol. For example,
STUN --> Mapped_Address, Relayed_Address.
Just need to know whether is it possible to use them when we install nDPI as library OR this is just for internal use....
Please help on this topic.
The text was updated successfully, but these errors were encountered: