New answers tagged netstat
Just another option: the auditd of Linux support system call logging. sudo auditctl -a entry,always -F arch=b64 -S connect Something better compare to strace: you can filter by multiple condition. For example: Audit/Log all failed connect system call: sudo auditctl -a entry,always -F arch=b64 -F success!=0 -S connect Audit/Log all connect system call by ...
strace -e trace=connect -f yourprogram or using a dump file strace -o yourprogram.strace -e trace=connect -f yourprogram
Up to FreeBSD 8.x (at least as of 8.4-RELEASE) it was possible to use the -t option with netstat -i/-I (show the state of all network interfaces/a specific interface). From FreeBSD 8.4-RELEASE netstat man: If -t is also present, show the contents of watchdog timers. This indeed had disappeared from FreeBSD 9.x (see FreeBSD 9.2-RELEASE netstat man). We ...
You can check man on the freebsd website In short review I see that -t was removed in 9. X branch for some reasons
When dealing with applications that are using up network bandwidth the best tool I've come across for tying back utilization to specific apps has got to be nethogs. You can use ip link show or netstat -i to find out your network interface names. $ netstat -i Kernel Interface table Iface MTU RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR ...
Top 50 recent answers are included