Messages

Today, I found the dyndns didn't auto update after the device rebooted. I checked the log file and found that the dyndns reported error 'opnsense: /usr/local/etc/rc.dyndns.update: Dynamic DNS (home.aivian.org) There was an error trying to determine the public IP for interface - wan(pppoe0). Probably interface is not a WAN interface.'
I think the pppoe services still didn't connect the ISP server in that moment so that the wan interface couldn't get the ip address. Maybe opnsense need check the inferface's ip address before dyndns services auto update.

AdSchellevis, Thank you!

Franco, I have tested the function of GeoIP alias today. It's awesome! Could you tell me how to update the GeoIP address regularly？

Z87+I3-4610

Version:OPNsense 16.1.13-amd64

LOG:opnsense: /system_advanced_misc.php: The command '/usr/sbin/powerd -b adp -a adp -n hadp' returned exit code '69', the output was 'powerd: no cpufreq(4) support -- aborting: No such file or directory'

I updated the opnsense to 16.1.9 and enable the l2tp services again. Now everything is ok. Thank you.

Ok, I see. Thank you.

The problem is still existence. I will retest this problem because I see the new image is released.

Sorry Franco. The config file includes a lot of sensitive information so that I can't email it to you.

The l2tp services is out of services since opnsense16.1.4. The l2tp services led to kernel panic. You must disable the l2tp services if you want to use the new version of opnsense. The image of attachment is the infomation of kernel panic.

configd.py: [3bac9f3c-fd77-4bb4-b3c8-2983612fad7b] Inline action failed at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/processhandler.py", line 488, in execute return ph_inline_actions.execute(self, inline_act_parameters) File "/usr/local/opnsense/service/modules/ph_inline_actions.py", line 52, in execute filenames = tmpl.generate(parameters) File "/usr/local/opnsense/service/modules/template.py", line 300, in generate for filename in self._generate(template_name, create_directory): File "/usr/local/opnsense/service/modules/template.py", line 248, in _generate content = j2_page.render(cnf_data) File "/usr/local/lib/python2.7/site-packages/jinja2/environment.py", line 989, in render return self.environment.handle_exception(exc_info, True) File "/usr/local/lib/python2.7/site-packages/jinja2/environment.py", line 754, in handle_exception reraise(exc_type, exc_value, tb) File "/usr/local/opnsense/service/modules/../template

OPNsense 15.7.6-amd64
FreeBSD 10.1-RELEASE-p16
OpenSSL 1.0.2d 9 Jul 2015

I'm using openvpn p2p sharekey mode but the openvpn server can't startup when I select the option of Duplicate Connections.

Duplicate Connections "Allow multiple concurrent connections from clients using the same Common Name.
NOTE: This is not generally recommended, but may be needed for some scenarios. "

The openvpn log:
Aug 7 17:38:39    openvpn[39539]: Use --help for more information.
Aug 7 17:38:39    openvpn[39539]: Options error: --duplicate-cn requires --mode server

YES! I'm waiting for next release version.

OPNsense 15.7.4-amd64
FreeBSD 10.1-RELEASE-p15
OpenSSL 1.0.2d 9 Jul 2015

Currently, I'm using the Zoneedit Dynamic DNS services with PPPOE services for WAN. The Dynamic DNS clients didn't auto update the DNS Record after you reboot the server.

OPNsense 15.7.4-amd64
FreeBSD 10.1-RELEASE-p15
OpenSSL 1.0.2d 9 Jul 2015

Jul 27 19:50:02    opnsense: /status_services.php: The command '/usr/local/sbin/dhcpd -user dhcpd -group dhcpd -chroot /var/dhcpd -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid igb1' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.2.8 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ no such user: dhcpd If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help. If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. If you intend to request help from the dhcp-bugs at isc.org mailing list, please read the section on the README about submitting bug reports and requests for help. Please do not under any circumstances send requests for help directly to the authors of this software - please send them to the appropriate mailing list as described in the README file. exitin

Jul 27 19:50:01    opnsense: /status_services.php: The command '/bin/sh /tmp/dhcpd.sh' returned exit code '1', the output was 'chown: dhcpd: illegal group name'