Topics

1

23.7 Legacy Series / [SOLVED] Can't seem to get netdata to start on boot

« on: September 09, 2023, 02:09:02 pm »

Hi,

I've installed netdata and followed the on screen instructions but they do not seem to work.
I've tried things in other posts to no avail, but they were for versions older than 23.7.3.
I've also set netdata_enable="YES" in /etc/rc.conf.d/netdata and that results in it starting but it does not survive a reboot.

I'm not quite sure what other info I can give that will help you help me but here's some output with the instructions I've followed,

Code: [Select]

Quick start for local-only use:

1. sysrc netdata_enable="YES"
2. service netdata start
3. Go to http://localhost:19999/
4. <Optional> Connect to Netdata Cloud using the netdata-claim.sh script:
   https://learn.netdata.cloud/docs/agent/claim#claiming-script

# sysrc netdata_enable="YES"
netdata_enable:  -> YES

# service netdata start
Cannot 'start' netdata. Set netdata_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'.

# vi /etc/rc.conf.d/netdata

# service netdata start
Starting netdata.

# service netdata status
netdata is running as pid 65602 65766.

Thank you,
Jiffy

2

21.1 Legacy Series / [SOLVED] 21.1.6 possibly broke ipsec

« on: May 27, 2021, 09:08:38 pm »

** EDIT **
The workaround below is no longer needed.
A new FRR package has fixed it.
** EDIT **

** EDIT **
Routing was actually broken.
Reverting to an older version of FRR resolved this.

# opnsense-revert -r 21.1.5 frr7

Franco has mentioned that the FRR package in 21.1.6 will be replaced to prevent others from having this issue.
** EDIT **

Hi,

I'm Running OPNsense in a Proxmox VM.
During lunch today, I shut it down, took a snapshot, powered it up and upgraded to 21.1.6.
At that point everything worked except for the ipsec tunnel, the tunnel was up, OSPF neighbors were there and the correct routes were installed too, it just wasn't working.
I couldn't connect to anything nor could I ping anything.
I even went as far as installing an "any any" rule in both directions on my ipsec interface, no joy.
No other changes were made, I had to bring the tunnel back up so I restored the snapshot.
After the restore everything was fine again.
I can upgrade it again, but is there anything else I can check?
Is there something I can do/test/report that will help you help me?

Thank you,
Jiffy

3

21.1 Legacy Series / Can a received route via ospf be filtered out?

« on: April 28, 2021, 07:42:44 pm »

Hi,

I've installed opnsense and following the docs, I was able to get ipsec, qos and ospf working, but what I can't seem to figure out is how to filter out a specific route received via ospf.
I have found one topic, very old in the 17.1 forum, asking the same, but it was never answered.
I also found a similar question in the 18.1 forum with a vague answer stating refer to the frr docs.
The rest I've found explain how to not export a route.
So, basically my questions are, can this be done and can it be done through the gui?
For example, I am receiving a route for 192.168.10.0/24 and would like ospf to ignore it.

Thank you,
Jiffy