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.

Sign up for GitHub

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

Jump to bottom

Prepare for release 1.6.2 #264

Open
catap opened this issue Jun 17, 2024 · 7 comments
Open

Prepare for release 1.6.2 #264

catap opened this issue Jun 17, 2024 · 7 comments
Milestone
Release 1.6.2

Comments

@catap
Copy link
Contributor

catap commented Jun 17, 2024 •
edited
Loading

Hey,

Sorry for pushing you but I feel that following changes is worth to be released:

Thus, since 1.6.1 it hasn't got too many changes, that is good because it can be a kind of bugfix release without revolution.
@simsong
Copy link
Owner

simsong commented Jun 17, 2024 via email

@simsong
Copy link
Owner

simsong commented Dec 19, 2024

Honestly, I had no idea that people were still using this. Yes, I think that we'll have a release over the next week.

@simsong simsong changed the title Make a new release? Prepare for release 1.6.2 Dec 19, 2024
@simsong simsong added this to the Release 1.6.2 milestone Dec 19, 2024
@catap
Copy link
Contributor Author

catap commented Dec 19, 2024

Well, tcpflow is the most easy way to dump traffic to stdin in text format. tcpdump -A is noisy, and tcpflow prints only packet payload which is quite useful if you need to see L7 traffic only :)

@catap
Copy link
Contributor Author

catap commented Dec 19, 2024

Just an example:

~ $ doas tcpdump -i lo0 -Anq port 80  
tcpdump: listening on lo0, link-type LOOP
15:12:20.679784 127.0.0.1.7190 > 127.0.0.1.80: tcp 0 (DF)
E..@'.@.@..............P...n......@..4.................
.r......
15:12:20.679854 127.0.0.1.80 > 127.0.0.1.7190: tcp 0 (DF)
E..@K.@.@............P...._d...o..@..4.................
.#!..r..
15:12:20.679878 127.0.0.1.7190 > 127.0.0.1.80: tcp 0 (DF)
E..4 .@.@..............P...o.._e.....(.....
.r...#!.
15:12:20.680329 127.0.0.1.7190 > 127.0.0.1.80: tcp 73 (DF)
E..}..@.@..............P...o.._e.....q.....
.r...#!.GET / HTTP/1.1
Host: 127.0.0.1
User-Agent: curl/8.11.1
Ac
15:12:20.680379 127.0.0.1.80 > 127.0.0.1.7190: tcp 0 (DF)
E..4..@.@............P...._e.........(.....
.#!..r..
15:12:20.680915 127.0.0.1.80 > 127.0.0.1.7190: tcp 294 (DF)
E..Z.W@.@............P...._e.........N.....
.#!..r..HTTP/1.1 404 Not Found
Server: nginx
Date: Thu, 19 Dec 202
15:12:20.680937 127.0.0.1.7190 > 127.0.0.1.80: tcp 0 (DF)
E..4j8@.@..............P......`......(.....
.r...#!.
15:12:20.681760 127.0.0.1.7190 > 127.0.0.1.80: tcp 0 (DF)
E..4..@.@..............P......`......(.....
.r...#!.
15:12:20.681780 127.0.0.1.80 > 127.0.0.1.7190: tcp 0 (DF)
E..4}.@.@............P....`..........(.....
.#!..r..
15:12:20.681834 127.0.0.1.80 > 127.0.0.1.7190: tcp 0 (DF)
E..4..@.@............P....`..........(.....
.#!..r..
15:12:20.681874 127.0.0.1.7190 > 127.0.0.1.80: tcp 0 (DF)
E..4.L@.@..............P......`......(.....
.r...#!.
^C
11 packets received by filter
0 packets dropped by kernel
~ $

vs

~ $ doas tcpflow -i lo0 -c port 80        
tcpflow: listening on lo0
127.000.000.001.32164-127.000.000.001.00080: GET / HTTP/1.1
Host: 127.0.0.1
User-Agent: curl/8.11.1
Accept: */*


127.000.000.001.00080-127.000.000.001.32164: HTTP/1.1 404 Not Found
Server: nginx
Date: Thu, 19 Dec 2024 14:13:45 GMT
Content-Type: text/html
Content-Length: 146
Connection: keep-alive

<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx</center>
</body>
</html>

^Ctcpflow: terminating orderly
~ $

@simsong
Copy link
Owner

simsong commented Dec 19, 2024

Great idea. DO you want this for 1.6.2 or for 1.7?

@simsong
Copy link
Owner

simsong commented Dec 19, 2024

Great idea. DO you want this for 1.6.2 or for 1.7?

Oh, it already does that!

@catap
Copy link
Contributor Author

catap commented Dec 19, 2024

@simsong yep, it is my main use case of tcpflow for many-many-many years.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Release 1.6.2
Development

No branches or pull requests
2 participants
@catap @simsong