Date: Tue, 23 Jul 2019 08:57:37 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 239371] epair(4) doesn't expose network traffic to bpf(4), ex. wireshark doesn't see it Message-ID: <bug-239371-227-qWcVJNyHXl@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-239371-227@https.bugs.freebsd.org/bugzilla/> References: <bug-239371-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239371 --- Comment #10 from Kristof Provost <kp@freebsd.org> --- (In reply to Yuri Victorovich from comment #9) lo0 is used for loopback traffic, and that includes connections from a publ= ic IP of your machine to a public IP from your machine. So, if your machine has re0, with 10.0.0.1/24 assigned to it, connecting to 10.0.0.1:1234 will pass over lo0, even though you might expect to see that traffic on re0. The same thing applies when that connection is made from a (non-vnet) jail to the host machine. It still applies if you have IP addres= ses in different nets. Anything to yourself will pass over lo0. If you connect to a different (i.e. non-local) IP, you will see the traffic= on re0. That's all expected behaviour. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-239371-227-qWcVJNyHXl>