Skip to content
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

Bug #904: store tx_id with alerts, update XFF -- v1.1 #577

Closed
wants to merge 3 commits into from

Conversation

inliniac
Copy link
Contributor

@inliniac inliniac commented Oct 4, 2013

Store TX id in the packet, so easy access to it by output modules. Update alert-debuglog to output this info.

Update the XFF output in unified2 to try to use this tx_id for retrieving the XFF ip.

Bug: https://redmine.openinfosecfoundation.org/issues/904
prscript: https://buildbot.suricata-ids.org/builders/inliniac/builds/19

Replaces #555.

Changes:

When generating an alert and storing it in the packet, store the tx_id
as well. This way the output modules can log the tx_id and access the
proper tx for logging.

Issue #904.
Use the tx id stored for each alert to find the correct XFF address
to add to the extra-data field.

In overwrite mode we still only grab the first available XFF addr,
as this address is set in the header preceeding the individual alerts.

Issue #904.
@inliniac
Copy link
Contributor Author

inliniac commented Oct 8, 2013

I've merged this after rebasing against master.

@serializingme
Copy link
Contributor

Hopefully I will start testing this with live traffic mid next week, as we're currently making some deep changes on our network infrastructure :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants