Problem building 19.7a

[bimmerdriver]

I updated to OPNsense 19.7.a_572-amd64 and the previously mentioned issues seem to have gone away. It's working as expected.

[bimmerdriver]

Updated to OPNsense 19.7.a_586-amd64. The gateway monitor for WAN_DHCP6 will not start. Searched in the log for dpinger messages, but didn't find any. Maybe I'm not looking in the right place. Since it's otherwise working properly. I'll try upgrading to the next release and will report back if the problem goes away.

[mimugmail]

Maybe you should follow every commit on core so you would know there is heavy work on this right now

[bimmerdriver]

Maybe you should follow every commit on core so you would know there is heavy work on this right now

I'm aware that it's under development and things may or may not work on any given day. I'm just giving anyone who might upgrade heads-up. I'm running it on a VM so it only takes a click to return to a previous version.

[franco]

This thread is an idea by bimmerdriver and I've grown rather fond of it for a two reasons:

1. Users updating to latest development versions reporting it works ok or this or that some things looks odd.

2. If updates are not working people can report it and we can help them through it.

So by all means please continue.


Cheers,
Franco

[franco]

Updated to OPNsense 19.7.a_586-amd64. The gateway monitor for WAN_DHCP6 will not start. Searched in the log for dpinger messages, but didn't find any. Maybe I'm not looking in the right place. Since it's otherwise working properly. I'll try upgrading to the next release and will report back if the problem goes away.

I would have to test this at the office next week. I haven't seen an issue after Ad worked through a few loose ends this week. Does that also happen on a clean reboot with the latest code?


Cheers,
Franco

[bimmerdriver]

Updated to OPNsense 19.7.a_586-amd64. The gateway monitor for WAN_DHCP6 will not start. Searched in the log for dpinger messages, but didn't find any. Maybe I'm not looking in the right place. Since it's otherwise working properly. I'll try upgrading to the next release and will report back if the problem goes away.

I would have to test this at the office next week. I haven't seen an issue after Ad worked through a few loose ends this week. Does that also happen on a clean reboot with the latest code?


Cheers,
Franco

The system is currently running OPNsense 19.7.a_588-amd64. I rebooted and the WAN_DHCP6 gateway is still not starting. If you tell me where to find dpinger log messages, I can post them, if that would help.

Update: There are no symptoms other than the gateway monitor. IPv6 is working fine.

[franco]

Can you restart the particular monitor and go to system log for clues? (System: Log Files: General)


Thanks,
Franco

[bimmerdriver]

Can you restart the particular monitor and go to system log for clues? (System: Log Files: General)


Thanks,
Franco

There aren't any dpinger messages at all in the log for either the IPv4 or the IPv6 gateway monitor. When I attempt to start the IPv6 gateway monitor, no new messages from any source appear in the log. It's the same if I restart the IPv4 gateway monitor.

[franco]

Nothing in the system log as well?

# clog /var/log/system.log | grep dpinger

The office FW is working fine with native IPv6 and gateway monitoring for it on the latest master code.

Please also check System: Gateways: Single if it shows the same gateways or IPv6 is missing. I saw something just out of sync with how Dpinger is "deciding" which monitors it can use and then they are basically offline because they don't exist which is ok because they are not configured...


Cheers,
Franco

[franco]

Added more system.log logging to master. If you press "play" on the broken monitor it should reveal what's going on.

Maybe WAN has DHCPv6 enabled, but your WAN doesn't give an IPv6. The system used to ignore this, but these days we try to show that IPv6 is not working so it can be disabled manually in the WAN config.


Cheers,
Franco

[marjohn56]

He has an ISP that does not issue an address on the WAN, only PD - I set up a fake monitor for him a while back.

@Bimmnerdriver contact me and I'll remote in and take a look.

[bimmerdriver]

Upgraded to OPNsense 19.7.a_623-amd64. Big step backwards. IPv6 not working.

@marjohn56 Let me know when is a good time for you to take a look. I'll check for your email in the morning, UTC-7.

[marjohn56]

@franco - there are issues with 19.7.a_661 - getting this:

Code: [Select]

Fatal error: Uncaught Error: Call to undefined function services_dhcpd_configure() in /usr/local/etc/inc/interfaces.inc:2573 Stack trace: #0 /usr/local/www/interfaces.php(598): interface_configure(false, 'lan', true) #1 {main} thrown in /usr/local/etc/inc/interfaces.inc on line 2573.
Also there was a previous call that failed in interfaces.inc, had to add require_once("services.inc"); to interfaces.inc to resolve it, cannot remember what the function was that was missing, I'll try and force it again.

[franco]

@marjohn56: Sorry, my bad. I am trying to get rid of most services.inc requirements.

https://github.com/opnsense/core/commit/b140e91b7

@bimmeldriver: please try opnsense-devel-19.7.a_666 and dump the system.log here if the issue continues.


Cheers,
Franco