OPNsense Forum
Archive => 22.1 Legacy Series => Topic started by: malcom13 on January 29, 2022, 02:35:41 am
-
Upgraded to 22.1 yesterday and I am seeing my internal VLANs go offline after a few hours. This is what the system.log is showing:
<11>1 2022-01-29T12:15:45+11:00 OPNsense.localdomain opnsense 12937 - [meta sequenceId="4467"] /usr/local/etc/rc.linkup: DEVD: Ethernet detached event for static lan
(re1)
<11>1 2022-01-29T12:15:45+11:00 OPNsense.localdomain opnsense 19953 - [meta sequenceId="4468"] /usr/local/etc/rc.linkup: DEVD: Ethernet detached event for static opt
2(re1_vlan4)
<11>1 2022-01-29T12:15:45+11:00 OPNsense.localdomain opnsense 29786 - [meta sequenceId="4469"] /usr/local/etc/rc.linkup: DEVD: Ethernet detached event for static opt
1(re1_vlan5)
<11>1 2022-01-29T12:15:49+11:00 OPNsense.localdomain opnsense 42294 - [meta sequenceId="4470"] /usr/local/etc/rc.linkup: DEVD: Ethernet attached event for static lan
(re1)
<11>1 2022-01-29T12:15:49+11:00 OPNsense.localdomain opnsense 42863 - [meta sequenceId="4471"] /usr/local/etc/rc.newwanip: IPv4 renewal is starting on 're1'
<11>1 2022-01-29T12:15:49+11:00 OPNsense.localdomain opnsense 42863 - [meta sequenceId="4472"] /usr/local/etc/rc.newwanip: On (IP address: 192.168.1.1) (interface: L
AN[lan]) (real interface: re1).
<13>1 2022-01-29T12:15:49+11:00 OPNsense.localdomain opnsense 42863 - [meta sequenceId="4473"] plugins_configure hosts ()
<13>1 2022-01-29T12:15:49+11:00 OPNsense.localdomain opnsense 42863 - [meta sequenceId="4474"] plugins_configure hosts (execute task : dnsmasq_hosts_generate())
<13>1 2022-01-29T12:15:49+11:00 OPNsense.localdomain opnsense 42863 - [meta sequenceId="4475"] plugins_configure hosts (execute task : unbound_hosts_generate())
<11>1 2022-01-29T12:15:49+11:00 OPNsense.localdomain opnsense 45006 - [meta sequenceId="4476"] /usr/local/etc/rc.linkup: DEVD: Ethernet attached event for static opt
2(re1_vlan4)
<11>1 2022-01-29T12:15:49+11:00 OPNsense.localdomain opnsense 45724 - [meta sequenceId="4477"] /usr/local/etc/rc.newwanip: IPv4 renewal is starting on 're1_vlan4'
<11>1 2022-01-29T12:15:49+11:00 OPNsense.localdomain opnsense 45724 - [meta sequenceId="4478"] /usr/local/etc/rc.newwanip: On (IP address: 192.168.4.1) (interface: I
OT[opt2]) (real interface: re1_vlan4).
<13>1 2022-01-29T12:15:49+11:00 OPNsense.localdomain opnsense 45724 - [meta sequenceId="4479"] plugins_configure hosts ()
<13>1 2022-01-29T12:15:49+11:00 OPNsense.localdomain opnsense 45724 - [meta sequenceId="4480"] plugins_configure hosts (execute task : dnsmasq_hosts_generate())
<13>1 2022-01-29T12:15:49+11:00 OPNsense.localdomain opnsense 45724 - [meta sequenceId="4481"] plugins_configure hosts (execute task : unbound_hosts_generate())
<27>1 2022-01-29T12:15:50+11:00 OPNsense.localdomain upsmon 82747 - [meta sequenceId="4482"] UPS [cyberpower@192.168.1.6]: connect failed: Connection failure: Operat
ion timed out
<11>1 2022-01-29T12:15:50+11:00 OPNsense.localdomain opnsense 48082 - [meta sequenceId="4483"] /usr/local/etc/rc.linkup: DEVD: Ethernet attached event for static opt
1(re1_vlan5)
<11>1 2022-01-29T12:15:50+11:00 OPNsense.localdomain opnsense 48996 - [meta sequenceId="4484"] /usr/local/etc/rc.newwanip: IPv4 renewal is starting on 're1_vlan5'
<11>1 2022-01-29T12:15:50+11:00 OPNsense.localdomain opnsense 48996 - [meta sequenceId="4485"] /usr/local/etc/rc.newwanip: On (IP address: 192.168.5.1) (interface: GUEST[opt1]) (real interface: re1_vlan5).
I am running suricata on the internal VLANs and suspect it may be related to the issue as a previous suricata update also caused a similar issue.
Any idea how I can investigate further?
Thanks!
-
Also running a Realtek NIC which could be the culprit. Changed from the re vendor driver to the built-in BSD driver. Will see how it goes.
-
Hi,
similar problem to me.
First, after hours, no DHCP from ISP (DOWN).
Somtimes no internet connection.
Tonight, can´t reach OPNSense.
How do you change the driver? I can login via ssh...
Greets
Byte
-
The builtin BSD driver appears to be more unstable. I ended up going back to the vendor re driver. I've also added the following options to /boot/loader.conf.local which I found in another thread. Hopefully this improves stability.
hw.re.msi_disable=1
hw.re.msix_disable=1
hw.re.eee_enable=0
hw.re.phy_power_saving=0
hw.re.phy_mdix_mode=0
-
OK, you createt this new file?
/boot/loader.conf.local ??
How can I install the vendor driver?
Greets
Byte
-
The builtin BSD driver appears to be more unstable. I ended up going back to the vendor re driver. I've also added the following options to /boot/loader.conf.local which I found in another thread. Hopefully this improves stability.
I've installed the vendor driver too, but without these options. However, I set hw.re.max_rx_mbuf_sz="2048" in Tunables, because this was mentioned in the driver install message.
Let's see how stable it is...
-
OK, you createt this new file?
/boot/loader.conf.local ??
Yes, I created that file but I guess as fraenki mentioned, you can probably add it through Tunables. May also be worthwhile to try the max_rx_mbuf_sz option as well.
How can I install the vendor driver?
Install the plugin os-realtek-re.
-
OK, thanks.
I´ve overlook the plugin first time.
Should I try to use Tunables?
It´s better in updates I think and restore config..
Should I enter following?
Tunable: hw.re.msi_disable Value: 1
Tunable: hw.re.msix_disable Value: 1
Tunable: hw.re.eee_enable Value: 0
Tunable: hw.re.phy_power_saving Value: 0
Tunable: hw.re.phy_mdix_mode Value: 0
Tunable: hw.re.max_rx_mbuf_sz Value: 2048
By the way, there is an red entry in my list:
NAme Description Type Value
debug.pfftpproxy Disable the pf ftp proxy handler. unsupported unknown
Greets Byte
-
Should I try to use Tunables?
It´s better in updates I think and restore config..
Definitely; do not modify files locally. Setting Tunables from the GUI is the better approach.