Messages

thank you Franco, for the confirmation that there is not much to do, it saves me hours of research.
I confirm that it is a physical problem of the hard disk which must be at the origin. Including new disc and new installation (this will clean house through our five years of updating. Updated a lot and continued. Sincerely,

Hello, my request was for help for a protocol in console mode to regenerate the kernel. A new installation is the simplest. This does not troubleshoot a crashed configuration. Kind regards

 hello, since an update 22.7.11 my kernel is out of service.
In console mode I can't progress because when I enter the characters are often wacky. hence the inability to pass the stage of the username and password.
I generated a 23.1 serial key, it's the same.
I generated a 23.1 key in vga, I have the hand however I do not have the level to repair the kernel alone. And I would like not to make a new installation by overwriting everything. Cordially,            ______  _____  _____
            /  __  |/ ___ |/ __  |
            | |  | | |__/ | |  | |___  ___ _ __  ___  ___
            | |  | |  ___/| |  | / __|/ _ \ '_ \/ __|/ _ \
            | |__| | |    | |  | \__ \  __/ | | \__ \  __/
            |_____/|_|    |_| /__|___/\___|_| |_|___/\___|

+-----------------------------------------+     @@@@@@@@@@@@@@@@@@@@@@@@@@@@
|                                         |   @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|  1. Boot Multi user [Enter]             |   @@@@@                    @@@@@
|  2. Boot Single user                    |       @@@@@            @@@@@
|  3. Escape to loader prompt             |    @@@@@@@@@@@       @@@@@@@@@@@
|  4. Reboot                              |         \\\\\         /////
|  5. Cons: Serial                        |   ))))))))))))       (((((((((((
|                                         |         /////         \\\\\
|  Options:                               |    @@@@@@@@@@@       @@@@@@@@@@@
|  6. Kernel: default/kernel (1 of 2)     |       @@@@@            @@@@@
|  7. Boot Options                        |   @@@@@                    @@@@@
|                                         |   @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|                                         |   @@@@@@@@@@@@@@@@@@@@@@@@@@@@
+-----------------------------------------+
   Autoboot in 0 seconds. [Space] to pause        22.7 ``Powerful Panther''  \

Loading kernel...
Failed to load kernel 'kernel'
can't load 'kernel'

can't load 'kernel'

Type '?' for a list of commands, 'help' for more detailed help.
OK

Hello,

Same symptom on the X7SPA-HF in the 27.7.2 update

os-c-icap (Installed)
os-clamav (Installed)
os-collectd (Installed
os-dmidecode (Installed)
os-dyndns (misconfigured)
os-etpro-telemetry (Installed)
os-frr (Installed)
os-hw-probe (Installed)
os-iperf (Installed)
os-maltrail (Installed)
os-ntopng (Installed)
os-redis (Installed)
os-rspamd (Installed)
os-sensei (Installed)
os-sensei-updater (Installed)
os-smart (Installed)
os-sunnyvalley (Installed)
os-theme-tukan (Installed)
os-tinc (Installed)
os-upnp (Installed)
os-zabbix-agent (Installed)

Services do not restart on restart.

All are back in order after fitting the patch 21.7.2_1.

On the other hand the p8B-X is silent no boot and no display in shell mode, to be investigated to define what the problem would be.

Regards,

Thank you to the community for your responses to NORDVPN not working with opnsense.
Always nice to have your most relevant feedback.

Hi community,

I would like to know if you are running a NordVPN subscription without fixed IP on OPNSENSE 21.7.1 or 21.1?

We are two users who neither have arrived, by following the link
https://support.nordvpn.com/Connectivity/Router/1292598142/OPNsense-19-1-setup-with-NordVPN.htm

We bought an ASUS router with ddwrt firmware and configured nordvpn. NO PROBLEMS, it works immediately and flawlessly.

we even block with a new machine.

Looking forward to hearing from you.

Regards,

Hello everyone,

@Greelan,
Thanks for the answer and I have the same thoughts.

@KHE,
Thank you also for your relevant answer, but it is the rules of SUDO.

I am sure of my password.
After various attempts, I can only log in with the correct rights with the following instruction:

  $ su -
Password:
*** Firewall-NG.debnet: OPNsense 21.7.1 (amd64 / OpenSSL) ***
Enter an option: 8
root @ PareFeu-NG: ~ #

The malfunction appeared after reinitializing in console mode with option 4) Reset to factory defaults.

Switching to version 21.7 was tedious in many ways. But hey, you have to deal with it.

Regards,

hi guy,

cannot work in console mode

an idea ?

_________________________________________________________________________________________
FreeBSD/amd64 (PareFeu-NG.debnet) (ttyu0)

login: Stephane
Password:
Last login: Fri Aug 27 21:13:03 on ttyu0
----------------------------------------------
|      Hello, this is OPNsense 21.7          |         @@@@@@@@@@@@@@@
|                                            |        @@@@         @@@@
| Website:      https://opnsense.org/        |         @@@\\\   ///@@@
| Handbook:     https://docs.opnsense.org/   |       ))))))))   ((((((((
| Forums:       https://forum.opnsense.org/  |         @@@///   \\\@@@
| Code:         https://github.com/opnsense  |        @@@@         @@@@
| Twitter:      https://twitter.com/opnsense |         @@@@@@@@@@@@@@@
----------------------------------------------
$ sudo su
Password:
Sorry, try again.
Password:
Sorry, try again.
Password:
sudo: 3 incorrect password attempts
$ su Stephane
$ sudo Stephane
Password:
Stephane is not in the sudoers file.  This incident will be reported.
$ sudo su
Password:
Sorry, try again.
Password:
Sorry, try again.
Password:
sudo: 3 incorrect password attempts
$ sudo Stephane
Password:
Stephane is not in the sudoers file.  This incident will be reported.
$ sudo su
Password:
Sorry, try again.
Password:
Sorry, try again.
Password:
sudo: 3 incorrect password attempts
$
_________________________________________________________________________________________

regards,

Hello,
Opnsense version 21.7 has a huge gap in disk management.
This will be resolved.
patience.
Cordially,

Hello,

I answer myself.

I tried to generate an install key with the image OPNsense-21.7-OpenSSL-serial-amd64, upload to two different servers and two different USB drives.
There is a priming however the system aborts, as indicated
on the posts above.

From my software library I just regenerated the OPNsense-20.1-OpenSSL-serial-amd64 image on my key or I overwrote the OPNsense-21.7-OpenSSL-serial-amd64 image.
The usual procedure in console mode (DB9 + putty) & (In the PUTTY console in SSH on 192.168.1.1: 22 enter Login as: installer + Pssw entry: opnsense + enter) works normally.

If I understood correctly version 21.7 has been rewritten. Reading the posts, many of us have disappointments about the generation of the installation media, I let this new version mature. No one is perfect, I know something about it.

Cordially,

Hello tbird35,

I tried to generate an install key with the image OPNsense-21.7-OpenSSL-serial-amd64, upload to two different servers and two different USB drives.
There is indeed a priming, however, the system aborts.

From my software library I just regenerated the OPNsense-20.1-OpenSSL-serial-amd64 image on my key or I overwrote the OPNsense-21.7-OpenSSL-serial-amd64 image.
The usual procedure in console mode (DB9 + putty) & (In the PUTTY console in SSH on 192.168.1.1: 22 enter Login as: installer + Pssw entry: opnsense + enter) works normally.

If I understood correctly version 21.7 has been rewritten. Reading the posts, many of us have disappointments, let this new version mature. No one is perfect, I know something about it.

Cordially,

Good evening Franco,

Thank you for the answer however I do not understand its meaning, my mother tongue is French (sorry).

My APU4C is crashed on zebra.conf when I am connected in console mode (DB9 + putty) & I do not have access to the graphical interface (webgui) from a browser (edge, chrome, vivldi, brave, firefox) .

That's why I tried to generate an installation key to all overwrite with the image OPNsense-21.7-OpenSSL-serial-amd64, download on two different servers and two different USB keys.

I am in failure even if I want to start on a new hard drive, my keys do not work for an installation.

I am perplexed, either the procedure to change (In the PUTTY console in SSH on 192.168.1.1: 22 enter Login as: installer + Pssw entry: opnsense + entry), or the image has a problem, or I am incompetent.

Cordially,

Hello,

The apu3A2 successfully migrated to 21.7 after patch 21.1.8_2.
21.1.8 opnsense environment, custom ports, clamav, freshclam, maltrail, ntopng, suricata, no sensei.

The apu4C4 is picking up the passage in 21.7 before the patch 21.1.8_2.
21.1.8 opnsense environment, custom ports, lamav, freshclam, maltrail, ntopng, suricata, with sensei.
https://forum.opnsense.org/index.php?topic=24136.0

Cordially,

Salvation,

As no answer, I downloaded the OPNsense-21.7-OpenSSL-serial-amd64 file and generated my key.

I start and end of not receiving ...

Now problem with the install image.

ada0 at ahcich0 bus 0 scbus0 target 0 mon 0
ada0: <KINGSTON SUV500MS120G 003056RI> ACS-4 ATA SATA 3.x device
ada0: Serial Number 50026B7782F951FC
ada0: 600.000MB / s transfers (SATA 3.x, UDMA6, PIO 512bytes)
ada0: Command Queueing enabled
ada0: 114473MB (234441648 512 byte sectors)
Trying to mount root from ufs: / dev / ufs / OPNsense_Install [ro, noatime] ...
mountroot: waiting for device / dev / ufs / OPNsense_Install ...
Mounting from ufs: / dev / ufs / OPNsense_Install failed with error 19.

Loader variables:
  vfs.root.mountfrom = ufs: / dev / ufs / OPNsense_Install
  vfs.root.mountfrom.options = ro, noatime

Manual root filesystem specification:
  <fstype>: <device> [options]
      Mount <device> using filesystem <fstype>
      and with the specified (optional) option list.

    eg. eggs: / dev / da0s1a
        zfs: zroot / ROOT / default
        cd9660: / dev / cd0 ro
          (which is equivalent to: mount -t cd9660 -o ro / dev / cd0 /)

  ? List valid disk boot devices
  . Yield 1 second (for background tasks)
  <empty line> Abort manual input

mountroot>

When it doesn't want it, it doesn't.

Cordially,

Thanks Franco,

For information, this migration was carried out after the publication of patch 21.1.8_2 and the mirror is marked as default.

I connected in console mode, I restarted my X7SPA-HF device and it appeared in 21.7, I searched for update only sensei 1.9.3 was to update.

So far I think this device is ok.

Cordially,