[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 05:23:20 UTC 2019


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

            Bug ID: 239371
           Summary: epair(4) doesn't expose network traffic to bpf(4), ex.
                    wireshark doesn't see it
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: yuri at freebsd.org

The epair instance is assigned IP addresses:
epair0a: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8<VLAN_MTU>
        ether 02:30:0a:fb:89:0a
        inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
        groups: epair
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8<VLAN_MTU>
        ether 02:30:0a:fb:89:0b
        inet 10.0.0.2 netmask 0xffffff00 broadcast 10.0.0.255
        groups: epair
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>

Jail is created with 10.0.0.2. Jail can connect to the host on ssh to 10.0.0.2,
but wireshark shows zero packets on epair0b.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list