NIC errors on boot Couldn't write '1' to 'net/ipv4/conf/vmbr0/arp_ignore'

[harmonyp]

I am seeing a bunch of errors when my system boots I am not sure what they all mean except for the /net/ lines below

asrock X570D4U
NIC: Solarflare SF432-1012
OS: Installed Proxmox after Debian11

https://pastebin.com/Qe9HJgYv

Nov 19 11:29:52 ENT1 systemd-sysctl[820]: Couldn't write '1' to 'net/ipv4/conf/vmbr0/arp_ignore', ignoring: No such file or directory
Nov 19 11:29:52 ENT1 systemd-sysctl[820]: Couldn't write '2' to 'net/ipv4/conf/vmbr0/arp_announce', ignoring: No such file or directory
Nov 19 11:29:52 ENT1 systemd-sysctl[820]: Couldn't write '0' to 'net/ipv4/tcp_tw_recycle', ignoring: No such file or directory
Nov 19 11:29:52 ENT1 systemd-sysctl[820]: Couldn't write '60' to 'net/netfilter/nf_conntrack_generic_timeout', ignoring: No such file or directory

/etc/network/interfaces

auto lo
iface lo inet loopback

auto enp38s0
iface enp38s0 inet manual

auto enp45s0f0np0
iface enp45s0f0np0 inet manual

auto enp45s0f1np1
iface enp45s0f1np1 inet manual

iface bond1 inet manual
bond-slaves enp45s0f0np0 enp45s0f1np1
bond-miimon 100
bond-mode 802.3ad
bond-xmit-hash-policy layer2+3
up ip link set enp45s0f0np0 master bond1
up ip link set enp45s0f1np1 master bond1
mtu 9000

auto vmbr0
iface vmbr0 inet static
address 192.168.0.220/24
gateway 192.168.0.1
bridge-ports enp38s0
bridge-stp off
bridge-fd 0

auto vmbr1
iface vmbr1 inet static
address 10.0.10.220/24
gateway 10.0.10.1
bridge-ports bond1
bridge-stp off
bridge-fd 0
mtu 9000

Only mention online I could find was to manually load modprobe nf_conntrack which didn't make any difference
ls /proc/sys/net/netfilter/

nf_conntrack_acct
nf_conntrack_buckets
nf_conntrack_checksum
nf_conntrack_count
nf_conntrack_dccp_loose
nf_conntrack_dccp_timeout_closereq
nf_conntrack_dccp_timeout_closing
nf_conntrack_dccp_timeout_open
nf_conntrack_dccp_timeout_partopen
nf_conntrack_dccp_timeout_request
nf_conntrack_dccp_timeout_respond
nf_conntrack_dccp_timeout_timewait
nf_conntrack_events
nf_conntrack_expect_max
nf_conntrack_frag6_high_thresh
nf_conntrack_frag6_low_thresh
nf_conntrack_frag6_timeout
nf_conntrack_generic_timeout
nf_conntrack_gre_timeout
nf_conntrack_gre_timeout_stream
nf_conntrack_helper
nf_conntrack_icmp_timeout
nf_conntrack_icmpv6_timeout
nf_conntrack_log_invalid
nf_conntrack_max
nf_conntrack_sctp_timeout_closed
nf_conntrack_sctp_timeout_cookie_echoed
nf_conntrack_sctp_timeout_cookie_wait
nf_conntrack_sctp_timeout_established
nf_conntrack_sctp_timeout_heartbeat_acked
nf_conntrack_sctp_timeout_heartbeat_sent
nf_conntrack_sctp_timeout_shutdown_ack_sent
nf_conntrack_sctp_timeout_shutdown_recd
nf_conntrack_sctp_timeout_shutdown_sent
nf_conntrack_tcp_be_liberal
nf_conntrack_tcp_ignore_invalid_rst
nf_conntrack_tcp_loose
nf_conntrack_tcp_max_retrans
nf_conntrack_tcp_timeout_close
nf_conntrack_tcp_timeout_close_wait
nf_conntrack_tcp_timeout_established
nf_conntrack_tcp_timeout_fin_wait
nf_conntrack_tcp_timeout_last_ack
nf_conntrack_tcp_timeout_max_retrans
nf_conntrack_tcp_timeout_syn_recv
nf_conntrack_tcp_timeout_syn_sent
nf_conntrack_tcp_timeout_time_wait
nf_conntrack_tcp_timeout_unacknowledged
nf_conntrack_timestamp
nf_conntrack_udp_timeout
nf_conntrack_udp_timeout_stream
nf_flowtable_tcp_timeout
nf_flowtable_udp_timeout
nf_hooks_lwtunnel
nf_log
nf_log_all_netns

 

[bbgeek17]

These are benign messages and can be safely ignored. They mean you have configured your system to enable those features but they are not compatible/supported by vmbr type interface.

As the message indicates, its generated by systemd-sysctl service. You can review service's man page here:
https://manpages.debian.org/testing/systemd/systemd-sysctl.service.8.en.html
The configuration for the service is described here: https://manpages.debian.org/testing/systemd/sysctl.d.5.en.html
One of the files mentioned there likely has the settings that generate the messages in the log.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox