Messages

Take the UAE as an example. VPN is allowed IF you use it for legitimate reasons.
The problem is that most hotels and mobile providers block VPNs.
I would see this as a fallback if standard WG isn't working.

I have fixed this for me with a Tampermonkey script.
Until it is fixed, you can use this.

(function()
{
    'use strict';

    GM_addStyle(`
        .tabulator .tabulator-tableholder
        {
            max-height: 2000px !important;
            height: auto !important;
            overflow-y: auto !important;
        }

        .tabulator
        {
            max-height: 2000px !important;
            height: auto !important;
        }

        .bootgrid-table-container,
        .bootgrid-body
        {
            max-height: 2000px !important;
            height: auto !important;
            overflow-y: auto !important;
        }

        .tab-content.content-box
        {
            max-height: none !important;
            overflow: visible !important;
        }
    `);
})();

I haven't upgraded yet from the old OpenVPN Server to the new configuration.
Is this required for 26.1?

what are these upgrade scripts and where can I find them?

Okay, after a second reboot, it works now with every reboot.
As I thought, when you import the config, tunables are set after the next full boot.
Then it works.

I will try a bit more.
When I boot the new installation with

set kern.vty="vt"
boot

and import the old config, the tunables are not set on next boot.
I have to try to boot it manually again set kern.vty="vt" and see if it boots up then.

At https://www.reddit.com/r/freebsd/comments/mdo0ma/following_a_tutorial/ they say that vt is standard since FreeBSD 12. This is 6 years ago.

I have the same problem like this poster had 7 years ago.
https://forum.opnsense.org/Archive/17_1_Legacy_Series/17_1_images_will_not_boot

When I go into the boot options with 3, I can do

set kern.vty="vt"
boot

and it boots.
I've edited /boot/loader.conf
like described here: https://www.reddit.com/r/freebsd/comments/mdo0ma/following_a_tutorial/
the default with a new installation is sc.
When I change it to vt, will it survive upgrades? If not, I have to send back the new router and get another one.
Any suggestion on what else I can do? Yes, I could install with CSM and without UEFI, but that shouldn't be necessary.

Thanks

I have the SMART status of my HDD on my dashboard.


It shows, okay, but the disk has many errors. I only recognized it when I updated to 25.1 and took around 1 hour to install and reboot.
Is it a bug in the SMART plugin?

Code Select Expand

Error 623 occurred at disk power-on lifetime: 23008 hours (958 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 e0 f5 18 40  Error: UNC at LBA = 0x0018f5e0 = 1635808

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 48 e0 f5 18 0a 08   1d+02:41:17.786  READ FPDMA QUEUED
  60 08 48 e0 f5 18 0a 08   1d+02:41:17.785  READ FPDMA QUEUED
  60 40 38 e8 73 01 00 08   1d+02:41:17.785  READ FPDMA QUEUED
  61 40 30 e8 73 01 00 08   1d+02:41:17.785  WRITE FPDMA QUEUED
  61 40 28 a8 0b 00 00 08   1d+02:41:17.784  WRITE FPDMA QUEUED

Error 622 occurred at disk power-on lifetime: 23008 hours (958 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 01 e0 f5 18 40  Error: UNC at LBA = 0x0018f5e0 = 1635808

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 40 e0 f5 18 0a 08   1d+02:40:41.447  READ FPDMA QUEUED
  60 08 38 c8 60 17 0a 08   1d+02:40:41.442  READ FPDMA QUEUED
  60 08 30 f8 04 1c 0a 08   1d+02:40:41.438  READ FPDMA QUEUED
  60 40 28 e8 be 16 0a 08   1d+02:40:41.433  READ FPDMA QUEUED
  60 08 20 e8 3b c3 0d 08   1d+02:40:41.423  READ FPDMA QUEUED

Error 621 occurred at disk power-on lifetime: 23008 hours (958 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 01 5f e7 2f 4a  Error: UNC 1 sectors at LBA = 0x0a2fe75f = 170911583

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 01 5f e7 2f 0a 08   1d+02:40:30.984  READ DMA
  c8 00 01 5f e7 2f 0a 08   1d+02:40:24.877  READ DMA
  c8 00 01 5f e7 2f 0a 08   1d+02:40:18.729  READ DMA
  c8 00 01 5f e7 2f 0a 08   1d+02:40:12.657  READ DMA
  c8 00 01 5f e7 2f 0a 08   1d+02:40:06.568  READ DMA

Error 620 occurred at disk power-on lifetime: 23008 hours (958 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 01 5f e7 2f 4a  Error: UNC 1 sectors at LBA = 0x0a2fe75f = 170911583

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 01 5f e7 2f 0a 08   1d+02:40:24.877  READ DMA
  c8 00 01 5f e7 2f 0a 08   1d+02:40:18.729  READ DMA
  c8 00 01 5f e7 2f 0a 08   1d+02:40:12.657  READ DMA
  c8 00 01 5f e7 2f 0a 08   1d+02:40:06.568  READ DMA
  c8 00 01 5e e7 2f 0a 08   1d+02:40:00.468  READ DMA

Error 619 occurred at disk power-on lifetime: 23008 hours (958 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 01 5f e7 2f 4a  Error: UNC 1 sectors at LBA = 0x0a2fe75f = 170911583

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 01 5f e7 2f 0a 08   1d+02:40:18.729  READ DMA
  c8 00 01 5f e7 2f 0a 08   1d+02:40:12.657  READ DMA
  c8 00 01 5f e7 2f 0a 08   1d+02:40:06.568  READ DMA
  c8 00 01 5e e7 2f 0a 08   1d+02:40:00.468  READ DMA
  c8 00 01 5e e7 2f 0a 08   1d+02:39:54.317  READ DMA


I have a problem with the widget.
It shows one temperature which is okay. But if it shows all, it's not readable. I cannot drag it longer and it doesn't autoexpand.

Got a public IPv6 and no static IPv6 on LAN so I would to NAT like you asked.
Did you get it working? I'm having the same question.

They block port and ip, and they don't care if they would block 443 for me at all.

And that was my question how multiple WG server instances work as I couldn't get it running.
My preference would be to have multiple external ports open that all route to the same port on
the OPNsense to the same WG server instance.

This wouldn't solve my problem as they would block port 443 then.
That's why I want to use ports 80, 443, 53 and some more.
If they block one port, I just use another one until the first one is released.

I'm often in Dubai, VPN is legal but often filtered in Hotels.
I have a Wireguard server running on OPNsense and it's working great but sometimes in the Hotels they start blocking this port. So as an alternative I wanted to add more ports I can use as fallbacks.

First try was to clone the whole Wireguard server with all assigned endpoints.
They get new interfaces wg1 to wg3 but don't appear in the interfaces overview.
Only when I create a new server and not clone one.
So I thought a new config makes more work and I tried to go to the firewall and
and route all ports 51821 to 52825 to the same local port 51820 so Wireguard is working.
I could get it working, so any hints if this is even possible would be helpfull.

...switch to LibreSSL (as long as it's still there) ;-)

LibreSSL ist affected by the same bug.