Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange

New answers tagged

0

This issue is not related to pfSense. The real cause is that hardware offload on Virtio driver seems to be not supported or broken for BSD. You don't need to switch back to E1000. Go to System -> Advanced -> Networking set mark on: Disable hardware checksum offload Right after You save settings communication starts immediately - it even doesn't need to ...


0

I'm not exactly sure what operating system your on. But, while there's probably a more elegant way to do this. The following might help. If you were to use sockstat(1), or procstat(1) on a BSD system. You could easily derive the pid that connection is running under, and simply issue a kill -HUP <pid number> Where <pid number> is the pid the ...


2

There's the -F option to nc: -F Pass the first connected socket using sendmsg(2) to stdout and exit. This is useful in conjunction with -X to have nc perform connection setup with a proxy but then leave the rest of the connection to another program (e.g. ssh(1) using the ssh_config(5) ProxyUseFdpass option). I guess you could use it along this line: ...


4

As described in this kernel documentation file,, the actual code that produces the listing is in Linux kernel source file .../net/ipv4/tcp_ipv4.c. The documentation file says that any listening sockets are listed first, then the established connections. No further sorting of any kind is promised. So the exact ordering (or non-ordering) might change if/...


0

Get a list of local IP addresses and ports listening via TCP/UDP: netstat -planu | awk '/^udp / {print $4}' Get the same info via the /proc filesystem: for h in $(awk 'NR>1{print $2}' /proc/net/tcp); do printf "%s:%d\n" $(printf "%d." $(echo ${h%:*}|sed 's/../0x& /g'|tr ' ' '\n'|tac)|sed 's/\.$/\n/') 0x${h#*:}; done Followed by ip_addr=$(echo ...


1

TCP Keep-alive was defined at a time when even the concept of firewall, let alone stateful firewall or NAT, was probably not widespread. From RFC 1122 (October 1989): 4.2.3.6 TCP Keep-Alives Implementors MAY include "keep-alives" in their TCP implementations, although this practice is not universally accepted. If keep-alives are included, the ...


Top 50 recent answers are included