Menu

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.

Show posts Menu

Messages - niclasc

#1
Under Trafic -> Reporting and "Top Talkers" the total in and out have the same value

That can't be right

Im on the latest version

LAN   192.168.1.47   0b   0b   6.63 kb   688.0 b   7 KB   7 KB   2021-07-02T14:14:27.225Z
LAN   192.168.1.49   0b   0b   8.14 kb   8.35 kb   5 KB   5 KB   2021-07-02T14:14:27.225Z
LAN   192.168.1.5   0b   0b   2.99 kb   1.82 kb   2 KB   2 KB   2021-07-02T14:14:27.225Z
LAN   192.168.1.46   0b   0b   3.75 kb   14.1 kb   5 KB   5 KB   2021-07-02T14:14:25.008Z
LAN   192.168.1.3   0b   0b   208.0 b   704.0 b   280 Bytes   280 Bytes   2021-07-02T14:14:25.008Z
LAN   192.168.1.26   0b   0b   107.06 kb   77.8 kb   56 KB   56 KB   2021-07-02T14:14:22.710Z
LAN   192.168.1.24   0b   0b   360.0 b   208.0 b   350 Bytes   350 Bytes   2021-07-02T14:14:18.111Z
LAN   192.168.1.33   0b   0b   240.0 b   240.0 b   120 Bytes   120 Bytes   2021-07-02T14:14:15.816Z
LAN   192.168.1.14   0b   0b   208.0 b   208.0 b   104 Bytes   104 Bytes
#2
20.7 Legacy Series / Re: Upgrade to 20.7 fails
September 20, 2020, 09:45:13 PM
No help on this??

Tried to update once more today and I get stuck on the same part

#3
20.7 Legacy Series / Upgrade to 20.7 fails
August 18, 2020, 05:13:35 PM
I'm trying to upgrade from 20.1.9 to 20.7. After all packages are extracted (installed?) the system hangs at:

Configuring system logging...done

If I press ctrl-c it continues and then stops at:

Starting NTP service...deferred

If I press ctrl-c there it just boots to 20.1.9

I'm running Opnsense as a VM in ESXi

Any Idea how to fix this?
#4
I'm on 20.1.4 and have checked for updates weekly but without any new updates. Today I saw 3 new updates and now I find newer than 20.1.4.

Strange
#5
I want to know why v20.1.5 and v.20.1.6 and v20.1.7 was released on the same day
#6
General Discussion / Why 3 releases in one day
May 26, 2020, 07:32:08 AM
Tried to find why there was 3 releases on the same day but haven't found any blogg or thread explaining that

So why?
#7
Quote from: franco on August 21, 2019, 05:33:17 PM
We should make the upgrade path 19.7.3 when it is released. I see FreeBSD has released new security advisories so the latest kernel would be better...


Cheers,
Franco

I have made the upgrade to 19.7.3 now and still have the same problem
If I go to Reporting -> Health and look under Quality I can see "Cloudflare" which is one of my old gateway I used to monitor. This gateway I cannot see under System -> Gateways
So I wonder if it got deleted in the gui but not in the system somehow.

Any idea where I can find Gateways in the console?
#8
@AdSchellevis tried that and now the Gateway is shown in the list but it does not work like before. It still won't start to monitor the IP like it did before

How do I set monitoring of something other than my gateway?
#9
Any ideas on this problem?
#10
19.7 Legacy Series / Re: devd errors in log
August 06, 2019, 08:47:01 PM
Great
Thanks
#11
I updated to 19.7.1 today an now one of my gateway monitor is missing av does not start
I monitored Cloudflares DNS to check online connectivity

dpinger   Gateway Monitor (Cloudflare)   
#12
19.7 Legacy Series / devd errors in log
July 26, 2019, 11:44:59 AM
After update to 19.7.1 I get lots of devd error in my log. Any ideas what's causing this? I'm running om VMWare ESXi if that helps

Jul 26 11:44:06   devd: Popping table
Jul 26 11:44:06   devd: Processing notify event
Jul 26 11:44:06   devd: Pushing table
Jul 26 11:44:06   devd: Processing event '!system=CAM subsystem=periph type=error device=cd0 serial="00000000000000000001" cam_status="0xcc" scsi_status=2 scsi_sense="70 02 3a 00" CDB="00 00 00 00 00 00 " '
Jul 26 11:44:03   devd: Popping table
Jul 26 11:44:03   devd: Processing notify event
Jul 26 11:44:03   devd: Pushing table
Jul 26 11:44:03   devd: Processing event '!system=CAM subsystem=periph type=error device=cd0 serial="00000000000000000001" cam_status="0xcc" scsi_status=2 scsi_sense="70 02 3a 00" CDB="00 00 00 00 00 00 " '
#13
Made a little typo in my first port. Obviously as was trying to upgrade to 19.1.3

But: Now I tried the upgrade one more time so I could take a picture of the console boot state.

And now after the boot completed and I waited 2-3 minutes it came alive. So now everything works fine again

So case closed I guess
#14
I try to upgrade to upgrade from 19.1.1 to 19.1.3, but after upgrade I can no longer ping OPNsense 192.168.1.1.
Interfaces have the same IP's as before the upgrade

Luckily I run Opnsense on VMware ESXi and made a snapshot before the upgrade so I could revert back to 19.1.1.
Tried to run the upgrade again but same problem.

Running OPNsense 19.1.1-amd64 on VMware 6.7 with e1000v v-nics

Any help on how to troubleshot this? And what more info you need from me


#15
Quote from: franco on January 30, 2019, 12:38:57 PM
Bummer. We will likely replace the installer due to its untraceable issues in 19.7 or 20.1.


Cheers,
Franco

So the solution is to wait 6 months to install????