Upgraded to 23.1.r2: no LAN ip after reboot

[franco]

From my experience I've never had to deal with disabling flow control for speed...

> Franco, is there a way to quickly reset tunables table to default?

PS: There is a trash can icon at the right top table corner on the System: Settings: Tunables page. It will reset your tunables to the factory defaults.

Cheers,
Franco

[alexdelprete]

Sorry, I totally missed your post and the trash can.

Thanks a lot.

[Gary7]

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.

[Rowhammer]

Good day, maybe this can help someone in the future

I can also confirm that removing the tunable dev.igb.X.eee_control solves the issues I had with the interfaces.

I use a HP T620 plus with an Intel i340-t4 card running OPNsense bare metal.

Here an overview of what happened:

• After applying the update and bringing the system to v23.1, the interfaces (igb0-igb3) went up for 2 minutes.
• The PPPoE connection on igb0 dropped after two minutes, giving the error: ppp >> [opt2_link0] LCP: no reply to 1 echo request(s).
• Logically, the virtual IPTV WAN on igb1 went down as well.
• The LAN interfaces igb2 and igb3 are bonded in a LAGG, which also went down after 2 minutes.
• The internal Realtek NIC was not affected, which makes sense.

I somehow managed to get a public IP address by restoring the PPPoE connection, with the tunable still in place.
But ipv6 and the IPTV connection didn't want to connect regardless.

By removing the tunable, all is well now.
Thanks for the heads-up.

P.S. making ZFS snapshots before an update saved my day. Rollback went really smooth and was able to be back online within 10 minutes.