Date: Wed, 25 May 2022 07:20:28 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 264198] bridge, ipfw: very slow network on bridge with IPFW, virtio or vtnet on 12.3-RELEASE-p5 Message-ID: <bug-264198-27103-6Smh8n0tFR@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264198-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-264198-27103@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=3D264198 --- Comment #3 from Ole <ol@dbconn.net> --- Hello, I have done some further investigations. And I could reproduce it with fewer components. My Host has one NIC. On this nic is a vlan. The vlan is bridged to an epair interface. If I turn on IPFW throughput gets slow. The setup: igb0---igb0.4030---bridge4030---epair0a---epair0b host-a # ifconfig epair create mtu 1400 host-a # ifconfig bridge4030 addm epair0a host-a # ifconfig epair0a up host-a # ifconfig epair0b inet <IP_ADDR>/28 mtu 1400 up host-a # nc -v -l 2222 > /dev/null I can now send from some other Host in the same Network via nc: host-b # dd if=3D/dev/zero bs=3D1024k count=3D6 | nc -v host-a 2222 IPFW started: 6291456 bytes transferred in 30.689174 secs (205006 bytes/sec) IPFW stopped: 6291456 bytes transferred in 0.070876 secs (88766689 bytes/se= c) this is more than 400 times faster without IPFW running on host-a. And agai= n, the only rule is host-a # ipfw list 65535 allow ip from any to any --=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-264198-27103-6Smh8n0tFR>