1
23.1 Legacy Series / Re: Upgraded to 23.1.r2: no LAN ip after reboot
« on: January 27, 2023, 03:18:12 pm »
I was configuring my network optimization based on information from https://calomel.org/freebsd_network_tuning.html
I disabled flow-control (dev.igb.0.fc=0 # (default 3)) as described in this section of sysctl configuration:
# Intel i350-T2 igb(4): flow control manages the rate of data transmission
# between two nodes preventing a fast sender from overwhelming a slow receiver.
# Ethernet "PAUSE" frames will pause transmission of all traffic types on a
# physical link, not just the individual flow causing the problem. By disabling
# physical link flow control the link instead relies on native TCP or QUIC UDP
# internal congestion control which is peer based on IP address and more fair
# to each flow. The options are: (0=No Flow Control) (1=Receive Pause)
# (2=Transmit Pause) (3=Full Flow Control, Default). A value of zero(0)
# disables ethernet flow control on the Intel igb(4) interface.
# http://virtualthreads.blogspot.com/2006/02/beware-ethernet-flow-control.html
#
dev.igb.0.fc=0 # (default 3)
Admittedly, on my lightly-loaded home network, it probably makes no difference whether flow control is on or off.
I'm just trying to get best performance out of my little apu2d4 firewall.
I disabled flow-control (dev.igb.0.fc=0 # (default 3)) as described in this section of sysctl configuration:
# Intel i350-T2 igb(4): flow control manages the rate of data transmission
# between two nodes preventing a fast sender from overwhelming a slow receiver.
# Ethernet "PAUSE" frames will pause transmission of all traffic types on a
# physical link, not just the individual flow causing the problem. By disabling
# physical link flow control the link instead relies on native TCP or QUIC UDP
# internal congestion control which is peer based on IP address and more fair
# to each flow. The options are: (0=No Flow Control) (1=Receive Pause)
# (2=Transmit Pause) (3=Full Flow Control, Default). A value of zero(0)
# disables ethernet flow control on the Intel igb(4) interface.
# http://virtualthreads.blogspot.com/2006/02/beware-ethernet-flow-control.html
#
dev.igb.0.fc=0 # (default 3)
Admittedly, on my lightly-loaded home network, it probably makes no difference whether flow control is on or off.
I'm just trying to get best performance out of my little apu2d4 firewall.