Messages

1

24.7 Production Series / Re: WARNING: failed to start ntopng

« on: September 04, 2024, 11:18:25 pm »

Yay, I got it working.

Code: [Select]

pkg install -f -r OPNsense libgcrypt libgpg-error
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
The following 2 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
libgpg-error: 1.48 -> 1.50 [OPNsense]

Installed packages to be REINSTALLED:
libgcrypt-1.11.0 [OPNsense]

Number of packages to be upgraded: 1
Number of packages to be reinstalled: 1

168 KiB to be downloaded.

Proceed with this action? [y/N]: y


2

24.7 Production Series / Re: WARNING: failed to start ntopng

« on: September 04, 2024, 11:12:26 pm »

It is already below 11?

# grep priority /usr/local/etc/pkg/repos/*.conf
/usr/local/etc/pkg/repos/OPNsense.conf:  priority: 11,
/usr/local/etc/pkg/repos/SunnyValley.conf:  priority: 7,

3

24.7 Production Series / Re: WARNING: failed to start ntopng

« on: September 01, 2024, 02:15:56 am »

Code: [Select]

/usr/local/etc/rc.d/ntopng start
Certificates generated /usr/local/share/ntopng/httpdocs/ssl/ntopng-cert.pem
Starting ntopng.
md5sum: invalid option -- q
usage: md5sum [-bctwz] [files ...]
usage: grep [-abcDEFGHhIiLlmnOopqRSsUVvwxz] [-A num] [-B num] [-C num]
[-e pattern] [-f file] [--binary-files=value] [--color=when]
[--context=num] [--directories=action] [--label] [--line-buffered]
[--null] [pattern] [file ...]
xargs: md5sum: terminated with signal 13; aborting
01/Sep/2024 02:01:59 [Ntop.cpp:4052] WARNING: Unable to find timezone: using UTC
01/Sep/2024 02:01:59 [Redis.cpp:171] Successfully connected to redis 127.0.0.1@0
01/Sep/2024 02:01:59 [Redis.cpp:171] Successfully connected to redis 127.0.0.1@0
ld-elf.so.1: /usr/local/lib/libgcrypt.so.20: Undefined symbol "gpgrt_add_post_log_func"
/usr/local/etc/rc.d/ntopng: WARNING: failed to start ntopng

Code: [Select]

find /usr/local/lib -name "libgcrypt.so*"
/usr/local/lib/libgcrypt.so
/usr/local/lib/libgcrypt.so.20
/usr/local/lib/libgcrypt.so.20.5.0

Code: [Select]

pkg install -f libgcrypt libgpg-error
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
SunnyValley repository is up to date.
All repositories are up to date.
The following 2 package(s) will be affected (of 0 checked):

Installed packages to be REINSTALLED:
libgcrypt-1.11.0 [OPNsense]
libgpg-error-1.48 [SunnyValley]

Number of packages to be reinstalled: 2

1 MiB to be downloaded.

Proceed with this action? [y/N]: y
[1/2] Fetching libgcrypt-1.11.0.pkg: 100%  818 KiB 837.5kB/s    00:01   
[2/2] Fetching libgpg-error-1.48.pkg: 100%  361 KiB 369.5kB/s    00:01   
Checking integrity... done (0 conflicting)
[1/2] Reinstalling libgpg-error-1.48...
[1/2] Extracting libgpg-error-1.48: 100%
[2/2] Reinstalling libgcrypt-1.11.0...
[2/2] Extracting libgcrypt-1.11.0: 100%
Still unable to start ntopng. That is a bummer.

Code: [Select]

opnsense-version
OPNsense 24.7.3_1


4

24.7 Production Series / WARNING: failed to start ntopng

« on: August 27, 2024, 12:58:48 am »

Code: [Select]

2024-08-27T00:48:43 Warning ntopng 27/Aug/2024 00:48:43 [Ntop.cpp:3890] WARNING: Unable to find timezone: using UTC
2024-08-27T00:48:40 Notice root /usr/local/etc/rc.d/ntopng: WARNING: failed to start ntopng
2024-08-27T00:48:40 Warning ntopng 27/Aug/2024 00:48:40 [Ntop.cpp:3890] WARNING: Unable to find timezone: using UTC
2024-08-27T00:47:27 Notice root /usr/local/etc/rc.d/ntopng: WARNING: failed to start ntopng
2024-08-27T00:47:27 Error ntopng 27/Aug/2024 00:47:27 [Redis.cpp:157] ERROR: to specify a redis server other than the default
2024-08-27T00:47:27 Error ntopng 27/Aug/2024 00:47:27 [Redis.cpp:154] ERROR: Please start it and try again or use -r
2024-08-27T00:47:27 Error ntopng 27/Aug/2024 00:47:27 [Redis.cpp:153] ERROR: ntopng requires redis server to be up and running
2024-08-27T00:47:26 Error ntopng 27/Aug/2024 00:47:26 [Redis.cpp:98] ERROR: Connection error [Connection refused]
2024-08-27T00:47:25 Error ntopng 27/Aug/2024 00:47:25 [Redis.cpp:98] ERROR: Connection error [Connection refused]
2024-08-27T00:47:24 Error ntopng 27/Aug/2024 00:47:24 [Redis.cpp:98] ERROR: Connection error [Connection refused]

After latest update. ..
Tried stopping and starting redis, tried to stop and start ntopng, tried to reset Redis as well. Tried a reboot.

And ideas?

5

24.1 Legacy Series / Re: 24.1 - DHCP server moves to KEA - implications?

« on: July 23, 2024, 12:39:45 am »

Yeah, no bueno-- I tried to stop Zenarmor, it did not work.

I believe it is not a feature which is fully integratred yet, with KEA:
https://github.com/opnsense/core/issues/7475

I believe NSD would have to be the Authorative DNS nameserver and KEA should send updates to the NSD server which will update the relevant zone. And then one would have to restart Unbound under each update.

http://troubleshooters.com/linux/unbound_nsd/nsd.htm

6

24.1 Legacy Series / Re: 24.1 - DHCP server moves to KEA - implications?

« on: July 19, 2024, 12:40:27 am »

Anyone being able to ping hostnames instead of IP adresses, when KEA is utilized? The only host which is able to resolve is the firewall itself.

7

General Discussion / Re: Unbound cannot register DHCP leases

« on: July 19, 2024, 12:02:33 am »

I am using KEA DHCP.
I am using Unbound DNS.

I am unable to ping any machines on my network through Ping utility embedded in the OPNsense GUI, when trying to ping the hostname. Pinging the IPv4 address works as expected.

From a client on the network, hostnames does not resolve.

Except the firewall itself, that one works (I can ping "firewall" and "firewall.domain.com" and I get a reply.
This works from both client and from OPNsense itself).

There is no logging besides "Informational" in the Kia DHCP Log File section.
There are no relevant information in the Unbound log.

Register ISC DHCP4 Leases: CHECKED
Register DHCP Static Mappings: CHECKED

System > Settings > Administration
DNS Rebind Check: Disable DNS Rebinding Checks. Tried UNCHECKED here.

Does not KEA communicate DDNS entries?

8

General Discussion / Re: NordLynx (WireGuard NordVPN implementation)

« on: September 17, 2023, 12:28:32 am »

9

Intrusion Detection and Prevention / Re: Where is WAN outbound 1.1.1.1:53 coming from?

« on: April 27, 2023, 01:58:21 am »

In OPNsense, up to the right; search - "packet capture" (Interfaces > Diagnostics > Packet Capture).

Download that file and open in it Wireshark. Maybe that can help.

Perhaps something on your LAN is 'hardcoded' to use that DNS server..

For DNS, I prefer to create NAT port forward rule that redirects DNS which is not going to unbound / pi-hole:

Interface
  LAN

Proto
  TCP/UDP

Adress
  LAN net

Ports
  *

Address (Destination)
  !LAN adress (IP to pi-hole)

Ports
  53

IP
  127.0.0.1 (or IP to pi-hole -- I have 127.0.0.1 as I am running unbound on the firewall)

Ports
  53

Description
  "Redirect external DNS queries to Opnsense Unbound DNS"

My Unbound DNS is configured to use DoT upstream servers.

https://1.1.1.1/help

10

22.1 Legacy Series / Re: questions about multiple WAN setup

« on: May 27, 2022, 10:52:02 pm »

I have no idea. I only have one WAN connection

I think you are the best one to answer this =D

11

22.1 Legacy Series / Re: questions about multiple WAN setup

« on: May 23, 2022, 08:41:23 am »

To get VLAN100 go over WAN_1, I would just add a pass rule on that interface which uses gateway WAN_1, on VLAN200 - make a pass rule which uses gateway WAN_2 (on the very bottom of the rule creation page).

And perhaps, when / if WAN_1 is down for VLAN100. .. You would have to disable this newly created rule, and then enable an identical rule which uses the WAN_2 gateway instead. So a manual process, I guess.

??

12

22.1 Legacy Series / Re: DHCP Question

« on: May 04, 2022, 02:20:04 pm »

On your OPNSense Box, what does it say: Interfaces > Diagnostics > ARP Table.
Which IP does the MAC Address of the server belong to?

13

21.7 Legacy Series / Re: Solved: Update problem

« on: February 13, 2022, 01:23:43 pm »

I am experiencing the same problem.

I tried to update from 21.7.7 to 21.7.8 -- clicked update, went away from the computer for a long time because I knew it had to do a reboot and that takes time.

Got back, had to log in - saw on the front page that the version was
* Versions   OPNsense 21.7.8-amd64
and thought everything was OK

Installed the Realtek plugin for my Realtek NIC -- and then I tried to update to 22.1 via "Click to check for updates"; however; checking for updates I saw the firmware and the kernel was not upgraded and was waiting for 21.7.8.

Now it is just stuck on

Code: [Select]

***GOT REQUEST TO UPDATE***
Currently running OPNsense 21.7.8 (amd64/OpenSSL) at Sun Feb 13 10:29:16 CET 2022
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
SunnyValley repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
SunnyValley repository is up to date.
All repositories are up to date.
Checking for upgrades (3 candidates): ... done
Processing candidates (3 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking integrity... done (0 conflicting)
Nothing to do.
Checking all packages: .......... done
Nothing to do.
Nothing to do.
Starting web GUI...done.
Generating RRD graphs...done.
Fetching base-21.7.8-amd64.txz: ...
Although I am not exactly sure what the problem is; probably the default mirror? Because internet works just fine? The default mirror stated on the System > Firmware > Status page was
* "Mirror   https://pkg.opnsense.org/FreeBSD:13:amd64/22.1"

For anyone coming here, go to System > Firmware > Settings to change the Firmware Mirror setting. I have changed the mirror, did a reboot, and then I was able to upgrade to 21.7.8 prior to upgrading to 22.1

14

22.1 Legacy Series / Re: bring back the vendor realtek driver

« on: February 10, 2022, 12:55:46 pm »

Update to 21.7.8 first?


Cheers,
Franco

 

Offcourse. My mistake, I did not read the update correctly. Somehow I thought pending updates was to version 22.1, but I see now 22.1 is only mentioned in the first line of the release notes and was not the actual update.

Thanks I'll try to update to 21.7.8 and then I'll try to install the plugin again before upgrading to 22.1.

15

22.1 Legacy Series / Re: bring back the vendor realtek driver

« on: February 09, 2022, 02:03:54 pm »

Hi!

I am on
* OPNsense 21.7.7-amd64
and I am using a Realtek NIC.

After reading through this, I want to make sure I use download the os-realtek-re on beforehand.

How can I do this?

Trying to install via GUI gives me:

Code: [Select]

***GOT REQUEST TO INSTALL***
Installation out of date. The update to opnsense-21.7.8 is required.
***DONE***

:p