OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of macafee »
  • Show Posts »
  • Topics
  • Profile Info
    • Summary
    • Show Stats
    • Show Posts...
      • Messages
      • Topics
      • Attachments

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

  • Messages
  • Topics
  • Attachments

Topics - macafee

Pages: [1] 2
1
Chinese - 中文 / Chinese mirror site upgrade complete
« on: January 01, 2021, 04:31:25 pm »
We had upgraded our dedicated lines for the server of the Chinese mirror site. Now the HK and TW users can connect the server via HK-IX BGP dedicated lines. The mainland of china users can connect the server via CN2 BGP lines. Have a nice day!

2
18.7 Legacy Series / How to upgrade the OPNsense 16.1.20-amd64
« on: October 16, 2018, 12:26:34 pm »
I don't want to reinstall the new system.

How to upgrade the OPNsense 16.1.20-amd64 to current production version 18.7?


3
17.1 Legacy Series / GRE TUNNEL SUPPORT DYNAMIC IP?
« on: October 07, 2017, 09:44:28 am »
Recently, my brother want  to make a opnsense box and conect my opnsense box with using GRE tunnel mode. Our opnsense boxes connected the internet with dynamic ip. But I don't know whether the gre tunnel support the dynamic ip. Did anybody try it?

4
17.1 Legacy Series / [SOLVED] OpenVPN Client Export Error!
« on: March 06, 2017, 11:22:31 am »
Versions    OPNsense 17.1.2-amd64
FreeBSD 11.0-RELEASE-p7
OpenSSL 1.0.2k 26 Jan 2017

I use the wizard to create a new OPENVPN server and add a user with  the certificate. But the system error when I want to use the Client Export. What's wrong? Does any new openvpn setup of User Manual that I can use?

The following input errors were detected:
Could not locate the CA reference for the server certificate.
Failed to export config files!

5
16.1 Legacy Series / DynDns Update Error!
« on: June 01, 2016, 12:57:04 pm »
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.

6
16.1 Legacy Series / GeoIP alias so cool!!!
« on: May 22, 2016, 04:49:43 am »
Franco, I have tested the function of GeoIP alias today. It's awesome! Could you tell me how to update the GeoIP address regularly?

7
16.1 Legacy Series / PowerD Bug!
« on: May 14, 2016, 10:51:13 am »
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'

8
16.1 Legacy Series / [SOLVED] L2TP kernel panic
« on: March 10, 2016, 02:54:32 pm »
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.

9
15.7 Legacy Series / [SOLVED] 15.7.24 BUG
« on: January 17, 2016, 07:18:28 am »
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

10
15.7 Legacy Series / OPENVPN BUG
« on: August 07, 2015, 11:59:15 am »
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

11
15.7 Legacy Series / Dynamic DNS clients didn't auto update the DNS Record.
« on: July 27, 2015, 02:45:17 pm »
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.

12
15.7 Legacy Series / [SOLVED] DHCPD cant work!
« on: July 27, 2015, 01:53:32 pm »
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'

13
15.7 Legacy Series / How to setup a mirror site for updating the opensense?
« on: July 26, 2015, 05:08:42 pm »
I'm in Shanghai which is a modern city in China. I want to update my opensense to 15.7.4 but the download speed only 10K/s and the connect always failed. Unfortunately, I didn't finish the updating from 9AM to 23PM. How to setup a mirror site  for updating the opensense or an other method to accelerating the updating?

14
15.1 Legacy Series / OPNsense 15.1.12-amd64 BUG!!!
« on: June 20, 2015, 10:05:50 am »
System Information:
FreeBSD 10.1-RELEASE-p12 #0 84c8e2b(master): Mon Jun 15 11:30:19 CEST 2015     root@sensey64:/usr/obj/usr/src/sys/SMP
OPNsense 15.1.12-eac7cdde6 (amd64)
OpenSSL 1.0.2c 12 Jun 2015

PHP Errors:
[20-Jun-2015 15:42:18 Asia/Shanghai] PHP Fatal error:  Uncaught exception 'Exception' with message 'Failed to connect: No such file or directory' in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Backend.php:67
Stack trace:
#0 /usr/local/etc/inc/util.inc(148): OPNsense\Core\Backend->configdRun('sshd restart', false)
#1 /usr/local/etc/rc.bootup(194): configd_run('sshd restart')
#2 {main}
  thrown in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Backend.php on line 67

The opnsense can't startup. I have tried to reinstall the opnsense with OPNsense-15.1.12_OpenSSL-vga-amd64.img but the system has same error!

15
15.1 Legacy Series / [SOLVED] apinger and miniupnpd not work!
« on: May 04, 2015, 06:31:57 pm »
Versions    OPNsense 15.1.10-amd64
FreeBSD 10.1-RELEASE-p9
OpenSSL 1.0.1m 19 Mar 2015

The apinger(Gateway Monitoring Daemon) not worked after upgrade to the new version. But I can restart it manually. There is the error log:
May 5 00:24:50    opnsense: /status_services.php: The command '/bin/pgrep -nF '/var/run/apinger.pid'' returned exit code '1', the output was ''

The miniupnpd(UPnP Service) not worked too. But I cant restart it. There is no erros in system logs. Why?

Pages: [1] 2
OPNsense is an OSS project © Deciso B.V. 2015 - 2023 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2