[Bug 239371] epair(4) doesn't expose network traffic to bpf(4), ex. wireshark doesn't see it

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Jul 22 18:18:26 UTC 2019


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239371

--- Comment #9 from Yuri Victorovich <yuri at 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.


More information about the freebsd-bugs mailing list