Date: Wed, 21 Nov 2018 22:10:09 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 233341] 12.0-RC1 i386 vnet does not behave like the amd64 vnet version. Message-ID: <bug-233341-227-CdOjuUzFgU@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-233341-227@https.bugs.freebsd.org/bugzilla/> References: <bug-233341-227@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=3D233341 --- Comment #7 from Joe Barbish <qjail1@a1poweruser.com> --- I got the tcpdump on xl0 and the vnet pflog and the host pflog. I was surpr= ised at the results. None of those flood packets show up. So I had to think about what was different this time. My production config is the gateway host is 11.2 amd64 and the LAN developm= ent host where previous vnet jail testing was done was i386 11.0-RC1.=20 To prepare for 12.0 testing I installed 12.0-RC1 on a empty HD which I swap= ped with the 11.2 hd on the gateway host. I also installed 12.0-RC1 on the LAN development i386 host.=20=20 The previous posted test pflogs are from a config where the gateway host is 12.0-RC1 and the LAN development host is 12.0-RC1. This is the config where= the pflogs on the development LAN host are flooded with all those packets This test I did not swap the gateway host 11.2 HD with the 12.0-RC1 HD, and kept the development LAN host at 12.0-RC1. This resulted in the pflogs on t= he development host to no longer have the flood packets. I attached the tcpdump, host pflog, and vnet jail pflog as separate files --=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-233341-227-CdOjuUzFgU>