New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: conditional run dissector on traffic #495
Comments
Being able to dynamically map ports -> protocols in TCPDUMP would indeed be a ] Never tell me the odds! | ipv6 mesh networks [ |
There should probably be a command-line option as well, so you don't have to change the file; the file would be for more persistent port mappings. |
Skickat från min Sony Xperia™-smartphone ---- Michael Richardson skrev ----
Having port maping in a pcap-ng block might be a nice feature too which might be worth considering when designing the format.
|
Guy Harris notifications@github.com wrote: Yes, I agree, it should take what would be a single rule in the file, ] Never tell me the odds! | ipv6 mesh networks [ |
A related useful idea mentioned in #471 would be easier to implement. The |
It has been mentioned briefly in #471: with the option
-T radius
it is possible to dissect traffic over non-RADIUS ports as RADIUS, but this means all traffic will be dissected as RADIUS.A short use case as an example: FreeRADIUS has the possibility to use a RESTful server for authorization. My RESTful daemon will send a CoA/Disconnect if this user still has another session, and my NAS requires that I send it to port 1700 instead of the standard port. I want to see all the traffic that is relevant, which means UDP port 1812 for RADIUS authentication, TCP port 80 for the RESTful traffic and UDP port 1700 for RADIUS CoA/Disconnect.
Until yesterday, UDP port 1700 was not marked as RADIUS, which means that would not be dissected. If I use
-T radius
, all traffic would be dissected as RADIUS, so the HTTP traffic would be mangled.It would be nice if there was a possibility to conditionally mark traffic as a certain protocol, like saying
-T "udp port 1700 = radius, tcp port 4080 = http"
The text was updated successfully, but these errors were encountered: