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 - angel2040

#1
sudo dd if=OPNsense-22.7-OpenSSL-vga-amd64.img of=/dev/sdd bs=16k
#2
I got around this particular error by specifying the usb stick in uefi order.  BUT, when I got to the screen to do either a UFS or ZFS install on internal m.2 drive, it crashes with the error in attached screenshot.
#3
Hey all.  Don't know if this is the correct place to post this? 
I'm trying to install 22.7 vga off usb on this hardware:

AMD Ryzen R7 3700U/R5 3500U Windows 11 Mini PC USB3.1 2*DDR4 Slot 8GB/16GB 128GB/256GB/512GB SSD 2*1000M LAN Computer
https://www.aliexpress.us/item/3256804226152260.html?spm=a2g0o.order_detail.0.0.fd81f19c7JY4at&gatewayAdapt=glo2usa&_randl_shipto=US

This is on uefi bios.  It keeps hitting the same error and stack trace.  Tried legacy also with no luck.  The img I burned to USB looks good:

openssl dgst -sha256 -verify OPNsense-22.7.pub -signature /tmp/image.sig OPNsense-22.7-OpenSSL-vga-amd64.img.bz2

Verified OK

Anyone see this?  What can I try?

Thanks

-A
#4
I have another i7 based fanless ready to go.  How do I dump the config on my 18.7 opnsense FW via cmdline (because most things aren't working in the gui because of this missing library) so I can move the config to the new opnsense FW?
#5
I'm having the same issue.  I don't remember WTH I installed outside of opnsense repo?  How do I find out?
#6
Looks ok:

root@XXX:/var/log # opnsense-update -k
Your system is up to date.

root@XXX:/var/log # opnsense-update -b
Fetching base-18.7.4-amd64.obsolete: ... done
Fetching base-18.7.4-amd64.txz: ................... done
!!!!!!!!!!!! ATTENTION !!!!!!!!!!!!!!!
! A critical upgrade is in progress. !
! Please do not turn off the system. !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Installing base-18.7.4-amd64.txz... done
Installing base-18.7.4-amd64.obsolete... done
Please reboot.
#7
I had to powercycle it as I couldn't even log into remotely.  It came up and it was working fine.  It's displaying 18.7.5.  I ran

pkg upgrade -f

on cmdline to be sure.  No errors.  But how do I know if I got the latest kernel?

root@XXX:/var/log # uname -a
FreeBSD XXX.com 11.1-RELEASE-p14 FreeBSD 11.1-RELEASE-p14  93e30e927e5(stable/18.7)  amd64
#8
I'm using

Ram: 1.8 gigs / 16 gigs
Disk: 1% out of / 445 gigs

So that's not it. 

Hardware is relatively new, but I'll check system log for any hardware issue.
Overheating?  Would see system logs about cpu temps and such?
What pkg is that file in?  Should I reinstall it and try again?

#9
So it seems I can no longer upgrade via the gui.  I always have to remote login and do it by hand.  Anyone know how I can fix this recurring error?

Fetching base-18.7.4-amd64.obsolete: ... done
Fetching base-18.7.4-amd64.txz: .................... done
Fetching kernel-18.7.4-amd64.txz: ............ done
!!!!!!!!!!!! ATTENTION !!!!!!!!!!!!!!!
! A critical upgrade is in progress. !
! Please do not turn off the system. !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Installing kernel-18.7.4-amd64.txz... done
Installing base-18.7.4-amd64.txz..../usr/lib/libmagic.a: Lzma library error: Corrupted input data
tar: Error exit delayed from previous errors.
failed
#10
OK.  So I ended up updating at cmdline:

opnsense-update -sn "18.1\/latest"
pkg bootstrap -f
pkg upgrade -f

It re-installed pkgs that were install when failure hit.  I'm on the latest.  Everything so far is working.
#11
I was running this update from console menu.  And it produced this error:

[51/55] Upgrading opnsense from 18.1.8 to 18.1.13...
[51/55] Extracting opnsense-18.1.13: .........pkg-static:
Fail to extract /usr/local/www/wizard.php from package: Lzma library error: Corrupted input data
[51/55] Extracting opnsense-18.1.13... done
A firmware update is currently in progress.

#12
18.1 Legacy Series / Re: 18.1 update fails....
January 29, 2018, 11:23:58 PM
Filesystem         Size    Used   Avail Capacity  Mounted on
/dev/gpt/rootfs    445G    3.1G    407G     1%    /
devfs              1.0K    1.0K      0B   100%    /dev
tmpfs               30G    643M     29G     2%    /var
tmpfs               29G    584K     29G     0%    /tmp
devfs              1.0K    1.0K      0B   100%    /var/dhcpd/dev


Sorry for got to mention that I'm on the latest OPNsense 17.7.12_1-amd64.
#13
18.1 Legacy Series / 18.1 update fails....
January 29, 2018, 11:09:12 PM
I had updated to 17.7 2-3 hours ago (with reboot).  Just tried updating to 18.1 and got this:

***GOT REQUEST TO UPGRADE: maj***
Fetching packages-18.1-OpenSSL-amd64.tar: .................................. done
Fetching base-18.1-amd64.obsolete: ... done
Fetching base-18.1-amd64.txz: .................... done
Fetching kernel-18.1-amd64.txz: ............ done
!!!!!!!!!!!! ATTENTION !!!!!!!!!!!!!!!
! A critical upgrade is in progress. !
! Please do not turn off the system. !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Extracting packages-18.1-OpenSSL-amd64.tar... done
Extracting base-18.1-amd64.txz... done
Extracting base-18.1-amd64.obsolete... done
Installing kernel-18.1-amd64.txz..../boot/kernel/krpc.ko: Lzma library error: Corrupted input data
tar: Error exit delayed from previous errors.
failed
***DONE***
#14
It's been a while.  I had an i5 with 16 gigs of ram (ds81) I just now got installed with brand spanking new OPNsense 17.7.7_1-amd64. 

I can confirm it's definitely suricata.  I did about 6 speed tests all giving me desired speed.  I enabled suricata and my connection was cut in half.  Gonna have to do more research on the ruleset.  I really want an inline IDS. 
#15
I didn't have any traffic shaping or QoS configured.  But now you got me thinking. I did turn on suricata.  Every rule was on.  It was fine CPU-wise on my 75 Mps.  But I don't think I ever checked its affect on the 300 Mps connection?  Maybe, it wasn't fully up when I was running my very first test.  Crap.  I was so sure packets were getting dropped and that's what I was focusing on.