Project

General

Profile

Actions
Copy link

Bug #245

closed

http.log

Added by Peter Manev about 14 years ago. Updated about 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Gurvinder Singh
Target version:
1.1beta1
Affected Versions:
Effort:
Difficulty:
Label:

Description

Suricata's HTTP.log file logs wrongly most of the time /90%/
the ip:port -> ip:port connections as being one way
i.e InternalIP:80 -> ExternalIP:port - as if the system that Suricata is installed on is a webserver and gets all requests on its port http port 80.

Use the following command on any http.log to confirm the issue:

egrep -n ':digit:{1,3}\.:digit:{1,3}\.:digit:{1,3}\.:digit:{1,3}\::digit:{1,5}' http.log | awk '{ print $1$18$19$20$21" " }'

Files

Download all files
start_suricata.png (135 KB) start_suricata.png Suricata starts without issues Peter Manev, 11/16/2010 01:05 AM
Suricat_conf_opt.png (131 KB) Suricat_conf_opt.png conf for Suricata Peter Manev, 11/16/2010 01:05 AM
http.log (34.9 KB) http.log Suricata's http.log file Peter Manev, 11/16/2010 01:05 AM
grep-httplog.txt (7.78 KB) grep-httplog.txt Just the IP:Port->IP:Port requests extracted from http.log Peter Manev, 11/16/2010 01:05 AM
0001-fixed-the-incorrect-port-issue-in-http.log.patch (2.63 KB) 0001-fixed-the-incorrect-port-issue-in-http.log.patch Gurvinder Singh, 11/16/2010 10:07 AM
Actions
Copy link

Also available in: Atom PDF