Unable to get synchronous throuput through OPNSense on 5Gbps synchronous link

[secdoc]

Currently having issue getting synchronous speeds. Running OPNsense 23.1.6-amd64 with NIDS and ZenArmor. I get expected speeds down (which is limited to 2.5Gbps NICs currently on current firewall, but will be replacing with new). I consistently get 2.3 Gbps down but only getting 500-600 Mbps up. I have run tests with and without IDS/Zenarmor and get same results. Any thoughts on what would be limiting throughput up? I run tests at provider edge and get roughly 5/5 Gbps, so I know the bottleneck is somewhere on my side.


Initially thought the issue might be a half-duplex issue but the WAN interface, but that is not the case:
igc0: flags=8963<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
   description: WAN (wan)
   options=4802028<VLAN_MTU,JUMBO_MTU,WOL_MAGIC,NOMAP>
   ether 00:90:27:e8:33:1f
   inet xx.xx.xx.109 netmask 0xfffffe00 broadcast xx.xx.xx.255
   media: Ethernet autoselect (2500Base-T <full-duplex>)
   status: active
   nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>

[tekgeek]

You are in a Worse mode than half-duplex....IDK how to fix it but you are in Simplex mode.

1. Simplex Mode –
In Simplex mode, the communication is unidirectional, as on a one-way street. Only one of the two devices on a link can transmit, the other can only receive. The simplex mode can use the entire capacity of the channel to send data in one direction.
 
2. Half-Duplex Mode –
In half-duplex mode, each station can both transmit and receive, but not at the same time. When one device is sending, the other can only receive, and vice versa. The half-duplex mode is used in cases where there is no need for communication in both directions at the same time. The entire capacity of the channel can be utilized for each direction.
Example: Walkie-talkie in which message is sent one at a time and messages are sent in both directions.

3. Full-Duplex Mode –
In full-duplex mode, both stations can transmit and receive simultaneously. In full_duplex mode, signals going in one direction share the capacity of the link with signals going in another direction, this sharing can occur in two ways:

Either the link must contain two physically separate transmission paths, one for sending and the other for receiving.
Or the capacity is divided between signals traveling in both directions.



Edit: Sorry, its not much help but you at least have something more accurate to google with.

Edit 2: Maybe try a different ethernet cable, or remake the ends if its running through the walls. I could just be a bad cable.

[secdoc]

I agree. but if you look at the ifconfig, it shows that the media is full duplex:

igc0: flags=8963<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
   description: WAN (wan)
   options=4802028<VLAN_MTU,JUMBO_MTU,WOL_MAGIC,NOMAP>
   ether 00:90:27:e8:33:1f
   inet xx.xx.xx.109 netmask 0xfffffe00 broadcast xx.xx.xx.255
   media: Ethernet autoselect (2500Base-T <full-duplex>)
   status: active
   nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>


but the interface flags is showing simplex. How would that get changed? Looking in the OPNSense console, I can force the interface to be 2500base-t, but nothing from a flags perspective.

[chamley]

Did you fix this?  I have a similar problem.