action rfc2136.reload.lan not found for user root

[scottandbothered]

Fresh install of OPNsense 24.7.3_1-amd64

Every x amount of hours my box has been going offline. Doing a hard reset on it brings it back up. I see these errors in the log. I noticed that during these events my WAN port is offline.

configd.py   action rfc2136.reload.lan not found for user root

Google took me here:
https://forum.opnsense.org/index.php?topic=39236.0

Thoughts?

[franco]

It's normal because you don't have RFC 2136 plugin installed.


Cheers,
Franco

[scottandbothered]

Happened again - every 3 hours my wan interface goes offline and I need to reboot opnsense.

Can you elaborate on what RFC 2136 is? Why would that shut down my wan?

I changed my wan lease time with an option modifier to increase lease time. supersede dhcp-lease-time 946080

[doktornotor]

RFC-2136 is completely unrelated to your issue. Dig somewheres else.

[franco]

> Can you elaborate on what RFC 2136 is? Why would that shut down my wan?

It's a plugin hook that is called when you receive a new interface address. In order to let RFC 2136 plugin update its entries with the remote host.

So you are observing a disconnect. That's where to start digging... what is your WAN connectivity type, how is WAN connected, what ISP are you with, relevant logs, etc.


Cheers,
Franco

[scottandbothered]

Does anything need done after os-rfc2136 is installed?

WAN Connection: Auto IP
WAN Connected: ONT -> opnsense wan port
ISP: Verizon FIOS

General log shows:
2024-09-03T08:48:38-04:00   Critical   dhclient   exiting.   
2024-09-03T08:48:38-04:00   Error   dhclient   connection closed

[doktornotor]

Does anything need done after os-rfc2136 is installed?

Hmmm? As already noted twice, os-rfc2136 has nothing to do with your crashing connection.

[scottandbothered]

One person says it does and one person says it doesn't. I haven't had any other suggestions or found any other solutions to try so I'm looking into their option.

[franco]

I never said you need the plugin. I was trying to answer your question. I also tried to explain that jumping to conclusions on this log line is not going to get you anywhere. Your problem lies in why the WAN reconnects, not why it cannot find the RFC 2136 hook (that answer is easy and straight forward: plugin not installed). But, again, it's not your problem. The reconnecct on WAN is (my assumption based on the lack of information given already asked for).


Cheers,
Franco

[franco]

024-09-03T08:48:38-04:00   Critical   dhclient   exiting.   
2024-09-03T08:48:38-04:00   Error   dhclient   connection closed

A bit more would be helpful, so it's exiting after all

[scottandbothered]

Code: [Select]

2024-09-03T11:46:40-04:00 Error opnsense /usr/local/etc/rc.newwanip: The command '/bin/kill -'TERM' '62710''(pid:/var/run/unbound.pid) returned exit code '1', the output was 'kill: 62710: No such process'
2024-09-03T11:46:30-04:00 Critical dhclient exiting.
2024-09-03T11:46:30-04:00 Error dhclient connection closed
2024-09-03T08:48:38-04:00 Critical dhclient exiting.
2024-09-03T08:48:38-04:00 Error dhclient connection closed
2024-09-02T22:33:41-04:00 Error opnsense /usr/local/sbin/pluginctl: The command '/bin/kill -'TERM' '28895''(pid:/var/run/unbound.pid) returned exit code '1', the output was 'kill: 28895: No such process'
2024-09-02T22:33:13-04:00 Error opnsense /usr/local/sbin/pluginctl: The command '/bin/kill -'TERM' '96761''(pid:/var/run/unbound.pid) returned exit code '1', the output was 'kill: 96761: No such process'
2024-09-02T22:32:55-04:00 Error opnsense /usr/local/sbin/pluginctl: The command '/bin/kill -'TERM' '74285''(pid:/var/run/unbound.pid) returned exit code '1', the output was 'kill: 74285: No such process'
2024-09-02T22:31:19-04:00 Error opnsense /usr/local/sbin/pluginctl: The command '/bin/kill -'TERM' '42323''(pid:/var/run/unbound.pid) returned exit code '1', the output was 'kill: 42323: No such process'

[scottandbothered]

I'm going to start a new thread as this problem is deeper than the error in the title.