| Summary: | tcpdump -i tun0 not port/host x shows incoming traffic for that host/port | ||
|---|---|---|---|
| Product: | Base System | Reporter: | ue <ue> |
| Component: | bin | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 5.0-CURRENT | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
ue
2000-06-19 16:50:01 UTC
Some additional datapoints: - the problem also exists in both 4.0-RELEASE and RELENG-4 as of 08-JUN - "postive" filtering (e.g. tcpdump -i tun0 port foo) works as expected - Doing a tcpdump -i tun0 -w file and then tcpdump -r file not port foo show the same symptoms. Using the same commandline on a file captured from an ethernet device works as expected Can you follow up with the output of tcpdump -d -i tun0 port foo tcpdump -d -i tun0 not port foo Thanks, Bill > tcpdump -d -i tun0 port foo (000) ld [0] (001) jeq #0x1c000000 jt 2 jf 9 (002) ldb [10] (003) jeq #0x6 jt 5 jf 4 (004) jeq #0x11 jt 5 jf 21 (005) ldh [44] (006) jeq #0x50 jt 20 jf 7 (007) ldh [46] (008) jeq #0x50 jt 20 jf 21 (009) jeq #0x2000000 jt 10 jf 21 (010) ldb [13] (011) jeq #0x6 jt 13 jf 12 (012) jeq #0x11 jt 13 jf 21 (013) ldh [10] (014) jset #0x1fff jt 21 jf 15 (015) ldxb 4*([4]&0xf) (016) ldh [x + 4] (017) jeq #0x50 jt 20 jf 18 (018) ldh [x + 6] (019) jeq #0x50 jt 20 jf 21 (020) ret #96 (021) ret #0 > tcpdump -d -i tun0 not port foo (000) ld [0] (001) jeq #0x1c000000 jt 2 jf 9 (002) ldb [10] (003) jeq #0x6 jt 5 jf 4 (004) jeq #0x11 jt 5 jf 21 (005) ldh [44] (006) jeq #0x50 jt 20 jf 7 (007) ldh [46] (008) jeq #0x50 jt 20 jf 21 (009) jeq #0x2000000 jt 10 jf 21 (010) ldb [13] (011) jeq #0x6 jt 13 jf 12 (012) jeq #0x11 jt 13 jf 21 (013) ldh [10] (014) jset #0x1fff jt 21 jf 15 (015) ldxb 4*([4]&0xf) (016) ldh [x + 4] (017) jeq #0x50 jt 20 jf 18 (018) ldh [x + 6] (019) jeq #0x50 jt 20 jf 21 (020) ret #0 (021) ret #96 Good hunting! State Changed From-To: open->closed Fixed in -current |