Closed els0r closed 5 months ago
Assessment on the affected system shows that this is caused by a Bogus IPv6 packet as expected (in this case: incorrect / invalid IP protocol ID):
# tcpdump -ni any -c 10 "(ip6 and length < 44) or (length < 19) "
tcpdump: data link type LINUX_SLL2
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on any, link-type LINUX_SLL2 (Linux cooked v2), snapshot length 262144 bytes
14:46:20.286223 peth1 M IP6 version error: 5 != 6
14:46:20.286223 peth1 M IP6 version error: 5 != 6
14:46:20.286223 peth1 M IP6 version error: 5 != 6
14:46:20.286223 peth1 M IP6 version error: 5 != 6
14:46:20.286223 peth1 M IP6 version error: 5 != 6
14:46:20.286223 peth1 M IP6 version error: 5 != 6
14:46:20.286223 peth1 M IP6 version error: 5 != 6
14:46:20.286223 peth1 M IP6 version error: 5 != 6
14:46:20.286240 peth1 M IP6 version error: 5 != 6
14:46:20.286240 peth1 M IP6 version error: 5 != 6
10 packets captured
115 packets received by filter
0 packets dropped by kernel
A packet dump has been obtained and will be added to the testing facilities (after sanitization).
Seen on one of the hosts in the sensor fleet:
Occurs during
dport
assignment: https://github.com/els0r/goProbe/blob/main/pkg/capture/flow.go#L179. It appears the packet data doesn't match the assumptions made about an IPv6 packets.From https://pkg.go.dev/golang.org/x/net/ipv6:
DoD