Date: Sat, 13 Jan 2018 07:03:27 +0100 From: Wojciech Macek <wma@semihalf.com> To: Michael Tuexen <tuexen@freebsd.org> Cc: freebsd-arm@freebsd.org Subject: Re: tcpdump reporting strange packets on RPi3 Message-ID: <CANsEV8e_6mjwyh6kKjpJHqaPM_u%2Bbo7eJ0zha%2BmS5B___bfLMA@mail.gmail.com> In-Reply-To: <CANsEV8d9-5Wu5hQpagOqz45vPGmQWxLwDYjdUsfcU0H_EVAQ_g@mail.gmail.com> References: <FC434226-29C0-4942-83DA-4EEF84192252@freebsd.org> <CANsEV8d9-5Wu5hQpagOqz45vPGmQWxLwDYjdUsfcU0H_EVAQ_g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Adding missing list... W dniu sobota, 13 stycznia 2018 Wojciech Macek <wma@semihalf.com> napisa=C5=82(a): > Yes, its a problem with 32-bit BPF ioctl compat support. I'm planning to submit a patch next week. > > Regards, > Wojtek > wma@ > > W dniu pi=C4=85tek, 12 stycznia 2018 Michael Tuexen <tuexen@freebsd.org> napisa=C5=82(a): >> Dear all, >> >> when running FreeBSD head on a RPi and using tcpdump on the ue0 interface, I do >> see strange packets. Something like >> >> 01:59:44.000000 a5:a5:a5:a5:a5:a5 > a5:a5:a5:a5:a5:a5, ethertype Unknown (0xa5a5), length 666370074: >> 0x0000: a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 ................ >> 0x0010: a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 ................ >> 0x0020: a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 ................ >> 0x0030: a5a5 a5a5 .... >> >> gets reported... Any ideas what went wrong? >> >> Best regards >> Michael >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANsEV8e_6mjwyh6kKjpJHqaPM_u%2Bbo7eJ0zha%2BmS5B___bfLMA>