"
I've noticed this problem for some time even on previous releases, but only have gotten around to gather logs to recently. I have a dual WAN setup(WAN on igc0, LAN on igc1, WAN2 on igc2). Internally on the LAN I'm just using IPv4. I have TMobile Home Internet on WAN interface and it works fine. TMobile gateway does not do passthrough so I'm in a double NAT here. If gets marked down it will come back up when the connection recovers. I have Verizon 5g Home Internet on WAN2, and their gateway does support IPv4 passthrough, which I am using. If the opnsense gateway gets marked down on this interface I have to restart dpinger for it to be marked back up. It seems like something with it getting an new IPv4. Attaching fuller logs, but here are I believe the relevant snippets:
the arpresolve error then just repeats until I restart dpinger. Here is gateway configs:
Let me know if there is other relevant config. Right now I have the dual WAN setup in failover.
Code Select
<165>1 2024-02-26T05:39:28-06:00 OPNsense.localdomain dpinger 31005 - [meta sequenceId="5"] ALERT: WAN2_DHCP6 (Addr: 2606:4700:4700:
:1001 Alarm: none -> down RTT: 52.2 ms RTTd: 65.8 ms Loss: 32.0 %)
<165>1 2024-02-26T05:39:28-06:00 OPNsense.localdomain dpinger 31005 - [meta sequenceId="6"] ALERT: WAN2_DHCP (Addr: 1.0.0.1 Alarm: n
one -> down RTT: 42.1 ms RTTd: 17.6 ms Loss: 30.0 %)
<12>1 2024-02-26T05:39:34-06:00 OPNsense.localdomain dpinger 62306 - [meta sequenceId="7"] exiting on signal 15
<12>1 2024-02-26T05:39:34-06:00 OPNsense.localdomain dpinger 7094 - [meta sequenceId="8"] send_interval 1000ms loss_interval 4000ms
time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 0ms loss_alarm 0% alarm_hold 10000ms
dest_addr 1.0.0.1 bind_addr 97.155.204.164 identifier "WAN2_DHCP "
<165>1 2024-02-26T05:39:34-06:00 OPNsense.localdomain dpinger 31005 - [meta sequenceId="9"] Reloaded gateway watcher configuration o
n SIGHUP
<165>1 2024-02-26T05:39:46-06:00 OPNsense.localdomain dpinger 31005 - [meta sequenceId="10"] ALERT: WAN_DHCP6 (Addr: 2001:4860:4860:
:8888 Alarm: delay -> none RTT: 196.8 ms RTTd: 234.5 ms Loss: 3.0 %)
<165>1 2024-02-26T05:39:46-06:00 OPNsense.localdomain dpinger 31005 - [meta sequenceId="11"] ALERT: WAN_DHCP (Addr: 8.8.8.8 Alarm: d
elay -> none RTT: 194.5 ms RTTd: 229.2 ms Loss: 3.0 %)
<165>1 2024-02-26T05:42:07-06:00 OPNsense.localdomain dpinger 31005 - [meta sequenceId="1"] ALERT: WAN_DHCP6 (Addr: 2001:4860:4860::
8888 Alarm: none -> loss RTT: 111.8 ms RTTd: 221.2 ms Loss: 12.0 %)
<165>1 2024-02-26T05:42:18-06:00 OPNsense.localdomain dpinger 31005 - [meta sequenceId="2"] ALERT: WAN_DHCP6 (Addr: 2001:4860:4860::
8888 Alarm: loss -> down RTT: 127.1 ms RTTd: 239.9 ms Loss: 26.0 %)
<165>1 2024-02-26T05:42:18-06:00 OPNsense.localdomain dpinger 31005 - [meta sequenceId="3"] ALERT: WAN_DHCP (Addr: 8.8.8.8 Alarm: no
ne -> down RTT: 160.1 ms RTTd: 279.2 ms Loss: 28.0 %)
<12>1 2024-02-26T05:43:09-06:00 OPNsense.localdomain dpinger 60397 - [meta sequenceId="4"] exiting on signal 15
<12>1 2024-02-26T05:43:09-06:00 OPNsense.localdomain dpinger 7156 - [meta sequenceId="5"] send_interval 1000ms loss_interval 4000ms
time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 0ms loss_alarm 0% alarm_hold 10000ms
dest_addr 2001:4860:4860::8888 bind_addr 2607:fb91:128d:cc89:d429:5ad7:0:9e0 identifier "WAN_DHCP6 "
<165>1 2024-02-26T05:43:09-06:00 OPNsense.localdomain dpinger 31005 - [meta sequenceId="6"] Reloaded gateway watcher configuration o
n SIGHUP
Code Select
<13>1 2024-02-26T05:39:31-06:00 OPNsense.localdomain dhclient 59625 - [meta sequenceId="2847"] dhclient-script: Reason ARPSEND on igc2 executing
<13>1 2024-02-26T05:39:32-06:00 OPNsense.localdomain opnsense 49595 - [meta sequenceId="2848"] /usr/local/etc/rc.newwanipv6: No IP change detected (current: 2600:100c:a121:6777:6662:66ff:fe21:9089, interface: opt1)
<13>1 2024-02-26T05:39:33-06:00 OPNsense.localdomain dhclient 74909 - [meta sequenceId="2849"] dhclient-script: Reason ARPCHECK on igc2 executing
<27>1 2024-02-26T05:39:33-06:00 OPNsense.localdomain dhclient 72391 - [meta sequenceId="2850"] unknown dhcp option value 0x7d
<13>1 2024-02-26T05:39:33-06:00 OPNsense.localdomain dhclient 77546 - [meta sequenceId="2851"] dhclient-script: Reason BOUND on igc2 executing
<13>1 2024-02-26T05:39:33-06:00 OPNsense.localdomain dhclient 79293 - [meta sequenceId="2852"] dhclient-script: New IP Address (igc2): 97.155.204.164
<13>1 2024-02-26T05:39:33-06:00 OPNsense.localdomain dhclient 82053 - [meta sequenceId="2853"] dhclient-script: New Subnet Mask (igc2): 255.255.255.248
<13>1 2024-02-26T05:39:33-06:00 OPNsense.localdomain dhclient 83765 - [meta sequenceId="2854"] dhclient-script: New Broadcast Address (igc2): 97.155.204.167
<13>1 2024-02-26T05:39:33-06:00 OPNsense.localdomain dhclient 86185 - [meta sequenceId="2855"] dhclient-script: New Routers (igc2): 97.155.204.165
<13>1 2024-02-26T05:39:33-06:00 OPNsense.localdomain dhclient 89934 - [meta sequenceId="2856"] dhclient-script: Creating resolv.conf
<13>1 2024-02-26T05:39:33-06:00 OPNsense.localdomain kernel - - [meta sequenceId="2857"] <7>arpresolve: can't allocate llinfo for 97.155.103.104 on igc2
<13>1 2024-02-26T05:39:34-06:00 OPNsense.localdomain kernel - - [meta sequenceId="2858"] <7>arpresolve: can't allocate llinfo for 97.155.103.104 on igc2
<13>1 2024-02-26T05:39:34-06:00 OPNsense.localdomain kernel - - [meta sequenceId="2859"] <7>arpresolve: can't allocate llinfo for 97.155.103.104 on igc2
<13>1 2024-02-26T05:39:34-06:00 OPNsense.localdomain opnsense 92410 - [meta sequenceId="2860"] /usr/local/etc/rc.newwanip: IP renewal starting (new: 97.155.204.164, old: 97.155.103.103, interface: opt1, device: igc2, force: yes)
<13>1 2024-02-26T05:39:34-06:00 OPNsense.localdomain opnsense 92410 - [meta sequenceId="2861"] /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'opt1'
<13>1 2024-02-26T05:39:34-06:00 OPNsense.localdomain kernel - - [meta sequenceId="2862"] <7>arpresolve: can't allocate llinfo for 97.155.103.104 on igc2
<13>1 2024-02-26T05:39:34-06:00 OPNsense.localdomain opnsense 92410 - [meta sequenceId="2863"] /usr/local/etc/rc.newwanip: ROUTING: setting inet interface route to 97.155.204.165 via igc2
<13>1 2024-02-26T05:39:34-06:00 OPNsense.localdomain opnsense 92410 - [meta sequenceId="2864"] /usr/local/etc/rc.newwanip: ROUTING: ignoring down gateways: WAN2_DHCP6, WAN2_DHCP
<13>1 2024-02-26T05:39:34-06:00 OPNsense.localdomain opnsense 92410 - [meta sequenceId="2865"] /usr/local/etc/rc.newwanip: ROUTING: configuring inet default gateway on wan
<13>1 2024-02-26T05:39:34-06:00 OPNsense.localdomain opnsense 92410 - [meta sequenceId="2866"] /usr/local/etc/rc.newwanip: ROUTING: keeping inet default route to 192.168.12.1
<13>1 2024-02-26T05:39:34-06:00 OPNsense.localdomain opnsense 92410 - [meta sequenceId="2867"] /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN2_DHCP)
<13>1 2024-02-26T05:39:34-06:00 OPNsense.localdomain opnsense 92410 - [meta sequenceId="2868"] /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN2_DHCP))
<13>1 2024-02-26T05:39:34-06:00 OPNsense.localdomain kernel - - [meta sequenceId="2869"] <7>arpresolve: can't allocate llinfo for 97.155.103.104 on igc2
<13>1 2024-02-26T05:39:34-06:00 OPNsense.localdomain kernel - - [meta sequenceId="2870"] <7>arpresolve: can't allocate llinfo for 97.155.103.104 on igc2
<13>1 2024-02-26T05:39:34-06:00 OPNsense.localdomain kernel - - [meta sequenceId="2871"] <7>arpresolve: can't allocate llinfo for 97.155.103.104 on igc2
<13>1 2024-02-26T05:39:35-06:00 OPNsense.localdomain kernel - - [meta sequenceId="2872"] <7>cannot forward src fe80:1::de8d:8aff:fee8:e477, dst 2001:470:baaf:1:6662:66ff:fe21:9087, nxt 58, rcvif igc0, outif igc1
<13>1 2024-02-26T05:39:35-06:00 OPNsense.localdomain kernel - - [meta sequenceId="2873"] <7>arpresolve: can't allocate llinfo for 97.155.103.104 on igc2
<13>1 2024-02-26T05:39:35-06:00 OPNsense.localdomain opnsense 92410 - [meta sequenceId="2874"] /usr/local/etc/rc.newwanip: IP address change detected, killing states of old ip 97.155.103.103
<13>1 2024-02-26T05:39:35-06:00 OPNsense.localdomain opnsense 92410 - [meta sequenceId="2875"] /usr/local/etc/rc.newwanip: plugins_configure vpn (,opt1)
<13>1 2024-02-26T05:39:35-06:00 OPNsense.localdomain opnsense 92410 - [meta sequenceId="2876"] /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : ipsec_configure_do(,opt1))
<13>1 2024-02-26T05:39:35-06:00 OPNsense.localdomain opnsense 92410 - [meta sequenceId="2877"] /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : openvpn_configure_do(,opt1))
<13>1 2024-02-26T05:39:35-06:00 OPNsense.localdomain opnsense 92410 - [meta sequenceId="2878"] /usr/local/etc/rc.newwanip: Resyncing OpenVPN instances for interface WAN2.
<13>1 2024-02-26T05:39:35-06:00 OPNsense.localdomain opnsense 92410 - [meta sequenceId="2879"] /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : wireguard_configure_do(,opt1))the arpresolve error then just repeats until I restart dpinger. Here is gateway configs:
Code Select
<Gateways version="1.0.0">
<gateway_item uuid="c817844c-d501-4f1b-8a4a-104412d842e1">
<disabled>0</disabled>
<name>WAN_DHCP6</name>
<descr>Interface WAN_DHCP6 Gateway</descr>
<interface>wan</interface>
<ipprotocol>inet6</ipprotocol>
<gateway/>
<defaultgw>0</defaultgw>
<fargw>0</fargw>
<monitor_disable>0</monitor_disable>
<monitor_noroute>0</monitor_noroute>
<monitor>2001:4860:4860::8888</monitor>
<force_down>0</force_down>
<priority>253</priority>
<weight>1</weight>
<latencylow/>
<latencyhigh/>
<losslow/>
<losshigh/>
<interval/>
<time_period/>
<loss_interval/>
<data_length/>
</gateway_item>
<gateway_item uuid="5d58e044-8b3c-486d-957b-6bb4382b803f">
<disabled>0</disabled>
<name>WAN_DHCP</name>
<descr>Interface WAN_DHCP Gateway</descr>
<interface>wan</interface>
<ipprotocol>inet</ipprotocol>
<gateway/>
<defaultgw>0</defaultgw>
<fargw>0</fargw>
<monitor_disable>0</monitor_disable>
<monitor_noroute>0</monitor_noroute>
<monitor>8.8.8.8</monitor>
<force_down>0</force_down>
<priority>253</priority>
<weight>1</weight>
<latencylow/>
<latencyhigh/>
<losslow/>
<losshigh/>
<interval/>
<time_period/>
<loss_interval/>
<data_length/>
</gateway_item>
<gateway_item uuid="99e1628e-035c-45d3-82b9-a1813ed4f09f">
<disabled>0</disabled>
<name>WAN2_DHCP6</name>
<descr>Interface WAN2_DHCP6 Gateway</descr>
<interface>opt1</interface>
<ipprotocol>inet6</ipprotocol>
<gateway/>
<defaultgw>0</defaultgw>
<fargw>0</fargw>
<monitor_disable>0</monitor_disable>
<monitor_noroute>0</monitor_noroute>
<monitor>2606:4700:4700::1001</monitor>
<force_down>0</force_down>
<priority>254</priority>
<weight>1</weight>
<latencylow/>
<latencyhigh/>
<losslow/>
<losshigh/>
<interval/>
<time_period/>
<loss_interval/>
<data_length/>
</gateway_item>
<gateway_item uuid="606953cd-81c2-46c3-b073-05e78b01dccb">
<disabled>0</disabled>
<name>WAN2_DHCP</name>
<descr>Interface WAN2_DHCP Gateway</descr>
<interface>opt1</interface>
<ipprotocol>inet</ipprotocol>
<gateway/>
<defaultgw>0</defaultgw>
<fargw>0</fargw>
<monitor_disable>0</monitor_disable>
<monitor_noroute>0</monitor_noroute>
<monitor>1.0.0.1</monitor>
<force_down>0</force_down>
<priority>254</priority>
<weight>1</weight>
<latencylow/>
<latencyhigh/>
<losslow/>
<losshigh/>
<interval/>
<time_period/>
<loss_interval/>
<data_length/>
</gateway_item>
</Gateways>Let me know if there is other relevant config. Right now I have the dual WAN setup in failover.
