![]() ![]() $ sudo pciconf card=0x22128086 chip=0x0f008086 rev=0x11 hdr=0x00ĭevice = 'Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register' I doubt that random_id is affecting this, for that same reason. it's definitely netgraph(4) related, see the statement above re: protectli testing on the same HW/SW w/o netgraph(4), and getting expected perf. so you could unset that to start with, I guess ASLR affects userland, not kernel, which is where the bulk of network performance occurs ![]() hbsd's only changes to the networking stack were to use ipv6 privacy extensions by default but, to help me out, I'd prefer if you tested your setup with vanilla fbsd. ![]() No, as this is a FW issue, and I refuse to try pfSense. ler: for opnsense questions, #opnsense would be the right channel And tag all the packets going to the ONT as VLAN0. Needs to be there to do the 802.1X dance with the ATT ONT. ![]() Can your installation be done without netgraph? Let me know what all you need/want, and I'll supply it. so that's why I'm pointing the finger at netgraph(4). the manufacturer () has run iperf tests on the raw hardware (without the netgraph(4) stuff in play) and gets ~940meg across it. I'm more than happy to work with whoever, including making access available to the FW. I'm looking for ideas on how to troubleshoot this. The tuning DEFINITELY helped the UPLOAD side, but did nothing for the DOWNLOAD side. I'm using OPNSense's 19.1.4-netmap kernel, and have done some of the em(4) tuning from their IPS/IDS forum topic. with my previous setup, a ubiquiti USG, I got ~900+ meg with this setup, my Download side is ~600 meg. I've got loading / configuring netgraph(4), and a 1g/1g ATT Fiber link. Hey all: I'm having a performance issue with netgraph(4) on OPNSense (based on HBSD-11.2). From my post to the #hardenedbsd IRC, but this *MAY* be a generic netgraph(4) perf issue. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |