@astrid Please enlighten me^^
@derrockwolf if you tcpdump without filters you get a firehose of packets dumped to the terminal. over ssh it's worse because now that firehose has to go over the series of tubes to your computer and house. very bad!
@astrid @derrockwolf I think I have some code to write. This could be solved programmatically.
alina🐾💖✨🏳️‍⚧️ (@[email protected])

thinking back to when i was a child and wondering why my ssh session and PC froze when i observed a tcpdump of said connection from the other end of it.

nyastodon

@astrid @derrockwolf

Well that, and also for every packet that's going through those hoses to your house, a packet telling you about that packet is generated and sent over that hose, too.

Which means that the number of packets per time grows by a 2^n law, i.e. exponentially.

And you might even flood yourself with tcpdumping the ssh connection you are tcpdumping over.

@astrid @derrockwolf

@wonka @astrid @derrockwolf ran into this issue 2 weeks ago lol. I was too lazy to figure out how to filter it so I switched the ssh connection to wifi so I could still dump the entire Ethernet interface

"not tcp port 22" could already be enough in a lot of cases.

@Kroppeb @astrid @derrockwolf

@wonka @Kroppeb @derrockwolf unfortunately still doesn't solve the problem of getting firehosed if you do this on a host serving prod traffic

@astrid @derrockwolf well if you're extremely lucky and using ssh -C it might work in your favor

I used to have this box once that had a funky Soekris encryption accelerator card in it which, best I could tell, OpenSSH detected and used. Those are no longer beneficial with current CPUs, but dang, that thing noticeably sped up ssh transfers. (I used to scp tons of data to and from the machine.)

@astrid oops... DONE THAT...
@astrid accidentally catting a binary file to a serial console is just as annoying but with added barrage of beeping ...
@astrid Could be worse… imagine WireShark over RDP/VNC/XDMCP…
@stuartl eh, that doesn't cause RDP/VNC/XDMCP to freeze up usually

@astrid It just generates lots and LOTS of traffic.

Probably what kills SSH and Telnet is the sheer number of packets.