[Bug 192756] SPAN port on bridge does not span packets originating locally
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sun Aug 17 17:30:23 UTC 2014
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192756
--- Comment #1 from jbw at hilltopgroup.com ---
The ifconfig from the 10-RELEASE box is as follows:
root@:~ # ifconfig
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 00:90:fb:36:78:ec
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
em1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 00:90:fb:36:78:ed
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em2: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 00:90:fb:36:78:ee
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: no carrier
em3: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 00:90:fb:36:78:ef
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether ce:52:1f:48:3f:45
inet 192.168.6.19 netmask 0xffffff00 broadcast 192.168.6.255
nd6 options=9<PERFORMNUD,IFDISABLED>
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: em1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 2 priority 128 path cost 20000
member: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 1 priority 128 path cost 200000
member: em3 flags=8<SPAN>
ifmaxaddr 0 port 4 priority 128 path cost 200000
And the tcpdumps showing the behavior:
>From the box (liveCD) in question (with the IP of 192.168.6.19):
root@:~ # ping 192.168.6.108
PING 192.168.6.108 (192.168.6.108): 56 data bytes
64 bytes from 192.168.6.108: icmp_seq=0 ttl=128 time=0.612 ms
64 bytes from 192.168.6.108: icmp_seq=1 ttl=128 time=0.464 ms
64 bytes from 192.168.6.108: icmp_seq=2 ttl=128 time=0.528 ms
And on the same box:
root@:~ # tcpdump -ni em3 host 192.168.6.108 and icmp
tcpdump: WARNING: em3: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on em3, link-type EN10MB (Ethernet), capture size 65535 bytes
capability mode sandbox enabled
15:16:07.658004 IP 192.168.6.108 > 192.168.6.19: ICMP echo reply, id 25865, seq
0, length 64
15:16:08.701353 IP 192.168.6.108 > 192.168.6.19: ICMP echo reply, id 25865, seq
1, length 64
15:16:09.763414 IP 192.168.6.108 > 192.168.6.19: ICMP echo reply, id 25865, seq
2, length 64
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-standards
mailing list