Date: Mon, 22 Jul 2019 16:41:50 +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-Y8oWZne8fN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-239371-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239371 --- Comment #9 from Yuri Victorovich <yuri@freebsd.org> --- (In reply to Kristof Provost from comment #8) The routing table only has 10.0.0.2 on lo1. When I send something to the host's IP 192.168.5.5 (which is in a different net), it indeed shows on lo0. But when I send something to some other IP 96.47.72.132, it doesn't show on lo0 as well. This behavior is confusing: 1. Why lo0 gets involved when it isn't used from jail? 2. Why packets to host's IP appear on lo0 and the packets to the remote IP don't even though both of the IP addresses are equally unroutable based on the jail's routing table? I guess I need to change to vnet-based jails. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-239371-227-Y8oWZne8fN>