Date: Wed, 11 Jun 2025 08:34:40 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 287229] IP reassembly issue in FreeBSD 14.1 Message-ID: <bug-287229-7501-HKDFiU7bjC@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-287229-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-287229-7501@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=3D287229 --- Comment #8 from Lucas Aubard <lucas.aubard@irisa.fr> --- Unfortunately, I have only Virtualbox-based boxes prepared. Since I don't h= ave an arm64 laptop, I can't test an adaptation of the Vagrantfile for arm64 ho= sts.=20 However, I don't think it would require much changes.=20 * The current Base box (debian/testing64) is amd64 only, but this one https://portal.cloud.hashicorp.com/vagrant/discover/generic/debian12, for example, has arm64 support.=20 * The current Target box (bento/freebsd-14.1) is also amd64 only. But, this= one has arm64 support https://portal.cloud.hashicorp.com/vagrant/discover/bento/freebsd-14. To recall, the tool deploys two Vagrant boxes: Base (a debian) and Target (freebsd 14.1). Base box is not essential; you can actually execute the commands from your host machine (Base mainly allows us to launch generic commands in our IP testing). You may prefer to run/prepare your own freebsd= VM (Target). In any case, if you change our default setup, be careful to 1) ad= apt MAC and IP addresses in the PCAP files, 2) disable NIC offloading that could interfere with freebsd host reassembly.=20 I forgot to mention that we would like the entire PCAP file set not shared publicly until our work is published. We plan to publish the entire tool af= ter that. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-287229-7501-HKDFiU7bjC>