Messages

1

22.1 Legacy Series / Re: [FIXED] - Unable to update to 22.1.8

« on: May 27, 2022, 06:08:01 am »

I'll switch to another mirror. I just chose that one as there are no mirrors close to me at all (New Zealand). Cheers!

I had exactly the same problem with Cloudfare last night (New Zealand).  Changing to LeaseWeb San Francisco worked.

I also have mixed success with Cloudflare, very fast ping times, but not always reliable.

2

22.1 Legacy Series / Re: Setting up Spark (NZ) UFB PPP settings

« on: April 20, 2022, 09:24:13 am »

Shouldn't that be 8.8.8.8 and not 8.8.8?  However if you can ping Spark's nameserver by IP address, I'd say you've got internet connectivity.  The gateway and route are set during PPPOE negotiation.

You can play with routing tables, use extra interface and create separate subnets on the device, but I've not had reason to do this.

3

22.1 Legacy Series / Re: Setting up Spark (NZ) UFB PPP settings

« on: April 19, 2022, 10:06:59 am »

Spark doesn't use DHCP.  Spark uses PPPOE.  When you get a successful PPPOE connection, an IP address will be assigned as part of the PPPOE negotiation.

For debugging PPPOE logs have a look at my earlier post.
 
I can see from your screenshots provided that you didn't have PPPOE on VLAN 10 then.  Also the two PPPOE interfaces is very odd.  Time to do a system reset and start over?

4

22.1 Legacy Series / Re: Setting up Spark (NZ) UFB PPP settings

« on: April 16, 2022, 09:44:26 am »

Hi Dazz,
I'm away in the Central North Island (Tongariro) now for the break, so I can't see my own setup for comparison. And I'm not from the Tron (aka Hamilton) 
I can see you've got two PPPOE when you should have one only.  Neither of them are on the VLAN 10, which you seem to have (good).  Looks like WAN is there too.
I would delete both PPPOE and create a new one on 'VLAN 10 on igb0'.  I think after that you should be good, but let us know how it's going (or not).

5

22.1 Legacy Series / Re: Setting up Spark (NZ) UFB PPP settings

« on: April 14, 2022, 10:49:05 am »

Firstly, I wouldn't be playing with the firewall rules.  The defaults should work fine.

In Lobby:Dashboard, look under Gateway.  Is there an IP address and a green light for WAN_PPPOE?
Just below Gateway is Interfaces.  Is WAN up (green arrow) and does it have an IP address?

Have a look at the log file under Interfaces --> Point-to-Point --> Log file.  Put the top right drop down box to 'debug'.
Does Interfaces --> Diagnostics --> Netstat --> Interfaces show PPPOE?

Finally, is PPPOE down and needs to be started the first time? I think this done when you save the settings.  I can't remember.

6

22.1 Legacy Series / Re: Setting up Spark (NZ) UFB PPP settings

« on: April 10, 2022, 11:00:24 pm »

I've been using Spark with Opnsense for quite a few years now.   

Spark uses PPPOE over VLAN 10.  Setting up a VLAN over the the WAN connection is very important.  Interfaces -- Other Types -- VLAN.  Then set up PPPOE (under point-to-point) over the VLAN.

Username and password  are not used, but Spark recommends you put 'some' value in there to keep software happy.  MTU they recommend 1500, which seems to be fine for me.  The other parameters on the Spark web page aren't important.

I'm running steadily at 300 Mbps, which is my assigned line speed.

 

7

21.7 Legacy Series / Re: NTP Time Error??

« on: July 30, 2021, 06:59:08 am »

2021-07-29T15:11:56   ntpd[49850]   kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized   
2021-07-29T15:11:56   ntpd[49850]   kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized

What this is really saying is that in the first few seconds (minutes?) after booting up the clock is unsynchronised.  After that the clock becomes synchronised and the message stops.

You can search for this in the forums - it has been confusing people for a while.  It would be good if the 'error' message was phrased better, but it is from ntp and not Opnsense. 

8

21.1 Legacy Series / Re: Can not install 21.1 from USB Stick

« on: March 25, 2021, 04:31:33 am »

This may, or may not help, but there was previous a FreeBSD bug similar to this.  I don't know if it is fixed of not.

https://forum.opnsense.org/index.php?topic=16798.msg76450#msg76450

https://forum.opnsense.org/index.php?topic=11869.0
 

9

20.7 Legacy Series / Re: Monit no longer starts

« on: December 22, 2020, 08:52:43 pm »

The web GUI will let you enter settings that don't actually match each other - and then Monit won't work.

You definitely cannot adjust the web settings without reading the Monit manual.  I've learned that myself the hard way.  It's also best to look at the file at /usr/local/monitrc and make sure it matches what is shown in the Monit manual.

Here is part of my Monit file (The rest is custom alert scripts of my own making):

Code: [Select]

set daemon 120 with start delay 120

set logfile syslog facility log_daemon



set mailserver mydomain.com port 25   

set alert user@mydomain.com   mail-format { from: opnsense_box@mydomain.com } reminder on 10 cycles

check system $HOST
   if memory usage is greater than 75% then alert
   if cpu usage is greater than 75% then alert
   if loadavg (1min) is greater than 8 then alert
   if loadavg (5min) is greater than 6 then alert

check filesystem RootFs with path "/"
   if space usage is greater than 75% then alert


Line 14 (your error line) starts with 'set alert... mail format...'

10

20.7 Legacy Series / Re: ntpd: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized

« on: August 13, 2020, 09:42:58 am »

Google says that this error message is not specific to Opnsense and often occurs during initial start up.  After a short while the clock stabilises and the message does not recur.

You can check the clock with:

Code: [Select]

# nptime

Or try chrony, pkg install os-chrony-devel

+1 for chrony

11

20.7 Legacy Series / Re: Monit no longer starts

« on: August 08, 2020, 07:20:06 am »

You need both.  The actual tests are in Service Test Settings.  The service is set up in Service Settings.

When setting up a 'service', the 'tests' are selected with the drop down box in Service Settings.

Don't modify the 'tests' in Service Test Settings, unless you have read the Monit Manual.

Don't select the 'ChangedStatus' test for the 'Host' service in Service Settings.  As you have found out, it won't work.

12

20.7 Legacy Series / Re: Monit no longer starts

« on: August 08, 2020, 12:37:09 am »

The GUI does not check what you select.  It will let you select options or tests that do not work.  You will only find out when it won't start up.  Again, you need to read the Monit Manual (and look at the examples), for guidance as to what will work.

I think the 'changed' switch is for checking the output status of shell scripts, not the status of the system.

This is what I have under 'check system':

Code: [Select]

check system $HOST
   if memory usage is greater than 75% then alert
   if cpu usage is greater than 75% then alert
   if loadavg (1min) is greater than 8 then alert
   if loadavg (5min) is greater than 6 then alert
I haven't changed it; this was what Opnsense installed.

Make sure you have the service tests CPUUsage, LoadAvg1, LoadAvg5 and LoadAvg15 set up under Service Test Settings - they are installed by default, so should be there.

13

20.7 Legacy Series / Re: Upgrade from 20.1.9_1 to 20.7 failed - no sig file found

« on: August 03, 2020, 12:17:38 pm »

O.K. Thanks for the replies.

The Jetway does not have a HDD Activity LED, so it's hard to know it's alive.  Next time, I will leave a console connected to see what is happening 

14

20.7 Legacy Series / Re: Upgrade from 20.1.9_1 to 20.7 failed - no sig file found

« on: August 03, 2020, 11:13:40 am »

Yes, after the web interface said the was system rebooting, the web interface did not change for a long, long time. I tried to ping the box, but it would not respond.  In the end I forced it off by holding the power button.  Took the box away for a closer inspection...

There was no console monitor on the box, so I had no idea what it was doing.  I had an SSH session open, but it closed when the web interface said rebooting.

Box is a Jetway NUC with 3160 processor.  Disk is a SSD SATA with ZFS.

Hmmm... I should have waited longer?

15

20.7 Legacy Series / Re: Upgrade from 20.1.9_1 to 20.7 failed - no sig file found

« on: August 03, 2020, 08:32:24 am »

Well, this may not much use, but here goes.  This is the .upgrade.log file that I have after running opnsense-bootstrap.sh.  Looking at the creation time, it may have been created at the first upgrade attempt - I just can't remember when I started exactly.

The file cuts off prematurely.  I don't why; it's the file that I have.

Just adding:  My usual mirror (Australia) gave the bad sig message and stopped immediately, and I then tried the San Francisco mirror, guessing it was a server issue.  Same thing.  I then tried again, and it didn't give an error; the upgrade continued, but the upgrade failed.

On upgrade, I saw Opnsense 20.7 being 'installed', and the installer said something along with  'Nothing to do!'. The installer moved onto FreeBSD 12 (which did install), then proceeded to reboot. 

Let me know if you need any more information.