16
General Discussion / OPNsense Command Prompt
« on: March 13, 2019, 02:50:43 am »
Does OPNsense have a command prompt, like pfSense Diagnostics / Command Prompt?
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.
Pages: 1 [2]
17
19.7 Legacy Series / Problem building 19.7a
« on: February 09, 2019, 05:44:28 am »
I'm currently running 19.7a_39. Trying to update but can't get make upgrade to complete.
Here is the shell output:
Any suggestions?
Here is the shell output:
Code: [Select]
root@OPNsense:/usr # rm -rf core
root@OPNsense:/usr # opnsense-code core
Cloning into '/usr/core'...
remote: Enumerating objects: 189, done.
remote: Counting objects: 100% (189/189), done.
remote: Compressing objects: 100% (124/124), done.
remote: Total 120845 (delta 101), reused 119 (delta 57), pack-reused 120656
Receiving objects: 100% (120845/120845), 64.08 MiB | 2.04 MiB/s, done.
Resolving deltas: 100% (86578/86578), done.
root@OPNsense:/usr # cd core
root@OPNsense:/usr/core # make upgrade
pkg: No package(s) matching squid
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
pkg: No packages available to install matching 'squid' have been found in the repositories
*** Error code 70
Stop.
make: stopped in /usr/core
root@OPNsense:/usr/core #
Any suggestions?
18
18.7 Legacy Series / ntp Questions
« on: December 15, 2018, 06:16:50 pm »
I have two opnsense systems, both running on windows server 2012r2 hyper-v. One system is running the latest release and the other is running 19.1b. I've noticed on both systems that the ntp service is taking longer to start up after rebooting than it used to. Both systems are using the default ntp settings.
I took a look at the status and I have some questions.
Here are the messages in the log, beginning after restarting the ntp service:
One of the message refers to memory. The system is currently using only 20% of memory.
Also, it appears that one of the default servers is not reachable. Refer to the screen capture.
I took a look at the status and I have some questions.
Here are the messages in the log, beginning after restarting the ntp service:
Quote
Dec 15 09:13:09 ntpd[84257]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Dec 15 09:13:09 ntpd[84257]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Dec 15 09:13:09 ntpd[84257]: mlockall(): Cannot allocate memory
Dec 15 09:13:09 ntpd[84257]: Listening on routing socket on fd #26 for interface updates
Dec 15 09:13:09 ntpd[84257]: Listen normally on 5 hn0 162.156.75.11:123
Dec 15 09:13:09 ntpd[84257]: Listen normally on 4 hn0 [fe80::215:5dff:fe5c:e233%5]:123
Dec 15 09:13:09 ntpd[84257]: Listen normally on 3 lo0 127.0.0.1:123
Dec 15 09:13:09 ntpd[84257]: Listen normally on 2 lo0 [::1]:123Dec 15 09:13:09 ntpd[84257]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Dec 15 09:13:09 ntpd[84257]: Listen and drop on 0 v6wildcard [::]:123
Dec 15 09:13:09 ntpd[84257]: restrict: 'monitor' cannot be disabled while 'limited' is enabled
Dec 15 09:13:09 ntpd[84257]: proto: precision = 0.100 usec (-23)
Dec 15 09:13:09 ntpd[84036]: Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid
Dec 15 09:13:09 ntpd[84036]: ntpd 4.2.8p12@1.3728-o Mon Sep 17 00:37:07 UTC 2018 (1): Starting
Dec 15 09:13:09 ntpd[77483]: 206.108.0.134 local addr 162.156.75.11 -> <null>
Dec 15 09:13:09 ntpd[77483]: 2001:6a0:0:31::2 local addr fe80::215:5dff:fe5c:e233%5 -> <null>
Dec 15 09:13:09 ntpd[77483]: 162.248.221.109 local addr 162.156.75.11 -> <null>
Dec 15 09:13:09 ntpd[77483]: 54.39.173.225 local addr 162.156.75.11 -> <null>
Dec 15 09:13:09 ntpd[77483]: ntpd exiting on signal 15 (Terminated)
One of the message refers to memory. The system is currently using only 20% of memory.
Also, it appears that one of the default servers is not reachable. Refer to the screen capture.
19
18.7 Legacy Series / Anyone having problems with dhcpd6?
« on: December 15, 2018, 06:04:41 pm »
I have two opnsense systems, both running on windows server 2012r2 hyper-v. One system is running the latest release and the other is running 19.1b. Yesterday, I updated both of them and now dhcpd6 is broken on both of them.
My ISP provides a /56 prefix. I also have two other *sense systems running on the same hyper-v server. Both are working properly, so I don't think this issue is related to my ISP.
Here is a message from the general log:
Note, the message is referring to /48. Not sure where that comes from.
My ISP provides a /56 prefix. I also have two other *sense systems running on the same hyper-v server. Both are working properly, so I don't think this issue is related to my ISP.
Here is a message from the general log:
Quote
opnsense: /usr/local/etc/rc.newwanipv6: The command '/usr/local/sbin/dhcpd -6 -user dhcpd -group dhcpd -chroot /var/dhcpd -cf /etc/dhcpdv6.conf -pf /var/run/dhcpdv6.pid hn1' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.4.1 Copyright 2004-2018 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ /etc/dhcpdv6.conf line 15: network mask too short prefix6 2001:560:74b0:2800:: 2001:560:74b0:2800::/48; ^ Configuration file errors encountered -- exiting If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging. exiting.'
Note, the message is referring to /48. Not sure where that comes from.
20
19.1 Legacy Series / Anyone having problems with dhcpd6?
« on: December 15, 2018, 05:56:05 pm »
I have two opnsense systems, both running on windows server 2012r2 hyper-v. One system is running the latest release and the other is running 19.1b. Yesterday, I updated both of them and now dhcpd6 is broken on both of them.
My ISP provides a /56 prefix. I also have two other *sense systems running on the same hyper-v server. Both are working properly, so I don't think this issue is related to my ISP.
Here is a message from the general log:
Note, the message is referring to /48. Not sure where that comes from.
My ISP provides a /56 prefix. I also have two other *sense systems running on the same hyper-v server. Both are working properly, so I don't think this issue is related to my ISP.
Here is a message from the general log:
Quote
opnsense-devel: /usr/local/etc/rc.newwanipv6: The command '/usr/local/sbin/dhcpd -6 -user dhcpd -group dhcpd -chroot /var/dhcpd -cf /etc/dhcpdv6.conf -pf /var/run/dhcpdv6.pid hn1' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.4.1 Copyright 2004-2018 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ /etc/dhcpdv6.conf line 15: network mask too short prefix6 2001:560:74c0:b800:: 2001:560:74c0:b800::/48; ^ Configuration file errors encountered -- exiting If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging. exiting.'
Note, the message is referring to /48. Not sure where that comes from.
21
19.1 Legacy Series / Installer hangs at "Select Task" on Hyper-V Generation 2 VM
« on: November 03, 2018, 05:40:32 pm »
There is a thread about Hyper-V Generation 2 VMs in the 18.1 Legacy Series forum: https://forum.opnsense.org/index.php?topic=7128.0.
I'm starting a new thread here, because the specific issue of font incompatibility in that thread seems to be different with the 19.1b snapshot. Changing from the default font to 8x14 no longer makes any difference. The installer hangs at the "Select Task" step. I tried using set hw.vga.textmode="0" and that also made no difference.
I'm testing on Windows Server 2012R2 Hyper-V.
I'm starting a new thread here, because the specific issue of font incompatibility in that thread seems to be different with the 19.1b snapshot. Changing from the default font to 8x14 no longer makes any difference. The installer hangs at the "Select Task" step. I tried using set hw.vga.textmode="0" and that also made no difference.
I'm testing on Windows Server 2012R2 Hyper-V.
22
18.7 Legacy Series / Text Sizing Problem on Services: DHCPv6: Leases
« on: September 08, 2018, 09:26:20 pm »
There is a text sizing problem on Services: DHCPv6: Leases. Depending on the zoom setting of the browser, the text goes off the screen.
Here is a screen capture:
Here is a screen capture:
23
18.7 Legacy Series / Update Questions
« on: July 21, 2018, 05:27:37 pm »
I am currently running this release:
OPNsense 18.7.r_10-amd64
FreeBSD 11.1-RELEASE-p11
OpenSSL 1.0.2o 27 Mar 2018
When I click check for updates, I get this message: This software release has reached its designated end of life. The next major release is: 18.7.r1
Often when I click check for updates, there is a message that the package manager is not running. If I click it again, the message goes away.
Right now, it's saying there are 10 packages. If I upgrade them, it's as if I didn't upgrade. It still gives the message, This software release has reached its designated end of life, the next major release is 18.7.r1.
Is something wrong with my installation? I was previously running the release version. Maybe when I switched to the development version it did not install properly?
OPNsense 18.7.r_10-amd64
FreeBSD 11.1-RELEASE-p11
OpenSSL 1.0.2o 27 Mar 2018
When I click check for updates, I get this message: This software release has reached its designated end of life. The next major release is: 18.7.r1
Often when I click check for updates, there is a message that the package manager is not running. If I click it again, the message goes away.
Right now, it's saying there are 10 packages. If I upgrade them, it's as if I didn't upgrade. It still gives the message, This software release has reached its designated end of life, the next major release is 18.7.r1.
Is something wrong with my installation? I was previously running the release version. Maybe when I switched to the development version it did not install properly?
24
General Discussion / OPNsense versus pfSense
« on: June 23, 2018, 03:51:42 am »
I'm not asking a rhetorical question or trying to start a controversy, but I'm wondering if someone would provide an explanation of why one would go with OPNsense rather than pfSense. I gather there are some philosophical differences, functionality differences, different objectives, etc., but these are not obvious merely by comparing the GUIs of OPNsense and pfSense. I would be interested to have a better understanding of this.
25
18.7 Legacy Series / Gateway Status Question
« on: June 04, 2018, 04:51:49 am »
On my system, the gateway status widget seems to be not working. For both the ipv4 and ipv6 gateways, the RTT is zero, which isn't possible. On my pfsense systems, it's around 6 ms for both. Also, the ipv6 gateway doesn't show the address of the gateway, which should be a link-local address.
26
General Discussion / New OPNsense User
« on: June 03, 2018, 02:00:37 am »
I'm a pfsense user, taking a first look at OPNsense. I'm running pfsense and OPNsense on Windows Server 2012R2 Hyper-V. All of the vms are connected to a shared virtual switch, which is connected to a physical NIC. The NIC is connected to a port of my modem, which is bridged. My ISP is Telus and their edge router delegates /56 prefixes. The edge router is configured to require the "directly send solicit" setting. It will not respond to an RS until it has delegated a prefix. I have one live pfsense system, running 2.4.3-p1, one test pfsense system running 2.4.4 development and one OPNsense system running 18.1.8. (Four /56 prefixes including the modem.) The client is a vm running windows 10. It's connected to the OPNsense LAN using a virtual switch.
I'm posting to report my feedback from installing OPNsense.
The "easy" installer hung. The work-around was to change the font from the default to 8x14. I found the work-around using google.
I initially ended up with OPNsense running off the CD, not actually installed. Maybe this is due to the above issue.
DHCPv6 does not appear to be working. IPv6 is working on the client, but it has a SLAAC address, not a DHCPv6 address / lease.
Other than those issues, it seems to be working okay. I will provide other feedback after I spend more time looking at the GUI.
I'm posting to report my feedback from installing OPNsense.
The "easy" installer hung. The work-around was to change the font from the default to 8x14. I found the work-around using google.
I initially ended up with OPNsense running off the CD, not actually installed. Maybe this is due to the above issue.
DHCPv6 does not appear to be working. IPv6 is working on the client, but it has a SLAAC address, not a DHCPv6 address / lease.
Other than those issues, it seems to be working okay. I will provide other feedback after I spend more time looking at the GUI.
Pages: 1 [2]