Date: Wed, 06 Nov 2019 13:33:10 +0000
From: bugzilla-noreply@freebsd.org
To: testing@freebsd.org
Subject: [Bug 239380] sys.netpfil.pf.forward.{v4,v6} and sys.netpfil.pf.set_tos.v4 fail on i386
Message-ID: <bug-239380-32464-BOOgYaJrtQ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-239380-32464@https.bugs.freebsd.org/bugzilla/>
References: <bug-239380-32464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239380 --- Comment #17 from Bjoern A. Zeeb <bz@FreeBSD.org> --- Created attachment 208911 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D208911&action= =3Dedit Fixes for scapy bpf on FreeBSD (i386) Hi, this diff is from the installed version of scapy and not relative to the po= rt. It fixes both the alignment on (32bit) platforms where sizeof(long) =3D=3D = 4 and for i386 the offset on the bpf_hdr struct as time_t still is 32bit. Scapy does not set any more specific BPF_T_* time option, so we are not switching to bpf_xhdr (which would probably be the better long-term solutio= n).=20 That said, the current situation in FreeBSD bpf is a mess until we BURN_BRI= DGES on the old bpf_hdr. I have not yet submitted a ports PR or the change upstream to scapy. This work was Sponsored by: Netflix --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-239380-32464-BOOgYaJrtQ>