Recent posts

#1
Quote from: Pavlik24rus on March 22, 2026, 11:37:18 AM
Quote from: krivik on March 22, 2026, 09:51:57 AMЗдравствуйте!
Ребят, у меня совсем не получается даже плагин установить.
Мои познания в в линуксах скудны, я только начал. Поднял свой первый шлюз. Кому не сложно дайте совет, я уже не знаю где информацию найти.
Я в /mtp закинул распакованные файлы os-amneziawg-v2 через FileZilla, но при запуске у меня ошибки:
/tmp/os-amneziawg-v2 # sh install.sh
==> Step 1: Installing AmneziaWG packages...
==> Step 2: Loading kernel module...
==> Step 3: Verifying...
install.sh: awg: not found
ERROR: awg not found!

Ты старую версию скачал, скачать через git clone с develop ветки, последнюю версию
Quote from: Pavlik24rus on March 22, 2026, 11:37:18 AM
Quote from: krivik on March 22, 2026, 09:51:57 AMЗдравствуйте!
Ребят, у меня совсем не получается даже плагин установить.
Мои познания в в линуксах скудны, я только начал. Поднял свой первый шлюз. Кому не сложно дайте совет, я уже не знаю где информацию найти.
Я в /mtp закинул распакованные файлы os-amneziawg-v2 через FileZilla, но при запуске у меня ошибки:
/tmp/os-amneziawg-v2 # sh install.sh
==> Step 1: Installing AmneziaWG packages...
==> Step 2: Loading kernel module...
==> Step 3: Verifying...
install.sh: awg: not found
ERROR: awg not found!

Ты старую версию скачал, скачать через git clone с develop ветки, последнюю версию
Спасибо!! Вышло)))))
#2
Zenarmor (Sensei) / OPNsense upgrade to 26.1 with ...
Last post by HardTack5 - Today at 04:19:33 AM
First time doing a OPNsense major upgrade running ZA.  I want to move from 25.7.11 to 26.1 , what get's upgraded first?

If I'm on the latest ZA version, do I just upgrade OPNsense and all should be well?
#3
General Discussion / opnsense-revert opnsense fails
Last post by Greelan - Today at 04:14:10 AM
Weird problem. I've been experimenting with some patches, and have routinely successfully reverted them by "opnsense-revert opnsense".

But on the latest try, it is stuck at ">>> Invoking update script 'refresh.sh'"

Previously I interrupted the script at this point and then tried again, but it complained that the OPNsense package repo conf was not available. So I copied that back from the sample, but the script still gets stuck.

Any tips how to fix this?
#4
26.1 Series / memory leak in dashboard?
Last post by am312 - Today at 03:53:04 AM
I'm running OPNsense 26.1.4-amd64.  I left the web admin open for a day and I see 2.6G memory footprint in Chrome.  Does that indicate a probelm?


#5
25.7, 25.10 Series / Re: OPNcentral Overwriting API...
Last post by amuckart - Today at 03:38:06 AM
Hi Franco,

Thanks for the reply.

Quote from: franco on March 20, 2026, 12:26:54 PMDon't sync users if you want to keep the local copies or use different usernames here.

If that is the case, I think the documentation needs to be updated to be explicit about this.

Currenty it says the existing API key+secret (I assume this means the one on the machine, but that's ambiguous as the docs are written) will be merged - which is the correct and sensible behaviour - but that isn't happening and access breaks as soon as you sync users.

This is a major flaw for something billed as a central management solution.
#6
26.1 Series / Re: MiniUPNPD
Last post by bntyhunter - Today at 02:16:15 AM
Fresh install of 26.1 in February.  Upgraded to 26.1.4 after it had been out a week.  Installed MiniUPNPD a couple of days ago.  It has not worked correctly since it was installed. Log is full of this:

2026-03-22T18:50:59-05:00Errorminiupnpdpfctl_get_rules_info: Invalid argument
2026-03-22T18:50:57-05:00Errorminiupnpdpfctl_get_rules_info: Invalid argument
2026-03-22T18:50:57-05:00Errorminiupnpdioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Invalid argument
2026-03-22T18:50:57-05:00Errorminiupnpdpfctl_get_rules_info: Invalid argument
2026-03-22T18:50:57-05:00Errorminiupnpdpfctl_get_rules_info: Invalid argument
2026-03-22T18:50:57-05:00Errorminiupnpdpfctl_get_rules_info: Invalid argument
2026-03-22T18:50:57-05:00Errorminiupnpdioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Invalid argument
2026-03-22T18:50:57-05:00Errorminiupnpdpfctl_get_rules_info: Invalid argument
2026-03-22T18:50:57-05:00Errorminiupnpdpfctl_get_rules_info: Invalid argument
2026-03-22T18:50:57-05:00Errorminiupnpdpfctl_get_rules_info: Invalid argument
2026-03-22T18:50:57-05:00Errorminiupnpdioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Invalid argument
2026-03-22T18:50:57-05:00Errorminiupnpdpfctl_get_rules_info: Invalid argument
2026-03-22T18:50:57-05:00Errorminiupnpdpfctl_get_rules_info: Invalid argument
2026-03-22T18:50:57-05:00Errorminiupnpdpfctl_get_rules_info: Invalid argument
#7
Quote from: GorillaP on Today at 01:48:59 AMHey I'm riding the struggle bus here. I'm tinkering with a new box to familiarize myself with the upgrade process as Im sure this would be helpful for others.
I'm running this on a 4-port Topton box.
I'm currently running Windows on this. I believe I have everything correct.
I have the binaries and config files in the same directory.
Running the updater results in the following. Ive tried the 1mb and 2mb bin. I think it might be an issue with the config file. I'm not sure what the "replaces" line is used for how to get the proper parameter.
c:\intel\i226-1mb>nvmupdatew64e.exe -u -f nvmupdate.cfg -l update_log.txt

Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.41.3.1
Copyright(C) 2013 - 2024 Intel Corporation.

Bad command line parameter 'nvmupdate.cfg'.

Here is the current config.
CURRENT FAMILY: 1.0.0
CONFIG VERSION: 1.20.0

; NIC device
BEGIN DEVICE
DEVICENAME: Intel(R) Ethernet Controller I226-V
VENDOR: 8086
DEVICE: 125C
SUBVENDOR: 8086
SUBDEVICE: 0000
NVM IMAGE: FXVL_125C_V_2MB_2.32.bin
EEPID: 80000290
RESET TYPE: REBOOT
REPLACES:
END DEVICE

Here is the inventory result
Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.41.3.1
Copyright(C) 2013 - 2024 Intel Corporation.

nvmupdatew64e.exe -i -l inventory.txt

Config file will not be read.
Inventory
[00:002:00:00]: Intel(R) Ethernet Controller I226-V
Alternate MAC address is not set.
Flash inventory started.
Shadow RAM inventory started.
Shadow RAM inventory finished.
Flash inventory finished.
[00:003:00:00]: Intel(R) Ethernet Controller I226-V
Alternate MAC address is not set.
Flash inventory started.
Shadow RAM inventory started.
Shadow RAM inventory finished.
Flash inventory finished.
[00:004:00:00]: Intel(R) Ethernet Controller I226-V
Alternate MAC address is not set.
Flash inventory started.
Shadow RAM inventory started.
Shadow RAM inventory finished.
Flash inventory finished.
[00:005:00:00]: Intel(R) Ethernet Controller I226-V
Alternate MAC address is not set.
Flash inventory started.
Shadow RAM inventory started.
Shadow RAM inventory finished.
Flash inventory finished.
[00:002:00:00]: Intel(R) Ethernet Controller I226-V
Vendor                 : 8086
Device                 : 125C
Subvendor              : 8086
Subdevice              : 0000
Revision               : 4
LAN MAC                : 60BEB40D8560
Alt MAC                : 000000000000
SAN MAC                : 000000000000
ETrackId               : 80000290
SerialNumber           : 60BEB4FFFF0D8560
NVM Version            : 2.20(2.14)
PBA                    : G23456-000
VPD status             : Not set
VPD size               : 0
NVM update             : No config file entry
  checksum             : Valid
[00:003:00:00]: Intel(R) Ethernet Controller I226-V
Vendor                 : 8086
Device                 : 125C
Subvendor              : 8086
Subdevice              : 0000
Revision               : 4
LAN MAC                : 60BEB40D8561
Alt MAC                : 000000000000
SAN MAC                : 000000000000
ETrackId               : 80000290
SerialNumber           : 60BEB4FFFF0D8561
NVM Version            : 2.20(2.14)
PBA                    : G23456-000
VPD status             : Not set
VPD size               : 0
NVM update             : No config file entry
  checksum             : Valid
[00:004:00:00]: Intel(R) Ethernet Controller I226-V
Vendor                 : 8086
Device                 : 125C
Subvendor              : 8086
Subdevice              : 0000
Revision               : 4
LAN MAC                : 60BEB40D8562
Alt MAC                : 000000000000
SAN MAC                : 000000000000
ETrackId               : 80000290
SerialNumber           : 60BEB4FFFF0D8562
NVM Version            : 2.20(2.14)
PBA                    : G23456-000
VPD status             : Not set
VPD size               : 0
NVM update             : No config file entry
  checksum             : Valid
[00:005:00:00]: Intel(R) Ethernet Controller I226-V
Vendor                 : 8086
Device                 : 125C
Subvendor              : 8086
Subdevice              : 0000
Revision               : 4
LAN MAC                : 60BEB40D8563
Alt MAC                : 000000000000
SAN MAC                : 000000000000
ETrackId               : 80000290
SerialNumber           : 60BEB4FFFF0D8563
NVM Version            : 2.20(2.14)
PBA                    : G23456-000
VPD status             : Not set
VPD size               : 0
NVM update             : No config file entry
  checksum             : Valid


Post #39 in the thread has all the instructions.   

The correct name of the file is nvm.cfg as per post #39 of this thread. 
#8
26.1 Series / Re: IPv6 from Android devices ...
Last post by OPNenthu - Today at 02:02:45 AM
https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2021q1/014753.html

Does this mean it's tied to the DHCPv6 lease time rather than the RA lifetime?  I'm not sure how to interpret it.
#9
Hey I'm riding the struggle bus here. I'm tinkering with a new box to familiarize myself with the upgrade process as Im sure this would be helpful for others.
I'm running this on a 4-port Topton box.
I'm currently running Windows on this. I believe I have everything correct.
I have the binaries and config files in the same directory.
Running the updater results in the following. Ive tried the 1mb and 2mb bin. I think it might be an issue with the config file. I'm not sure what the "replaces" line is used for how to get the proper parameter.
c:\intel\i226-1mb>nvmupdatew64e.exe -u -f nvmupdate.cfg -l update_log.txt

Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.41.3.1
Copyright(C) 2013 - 2024 Intel Corporation.

Bad command line parameter 'nvmupdate.cfg'.

Here is the current config.
CURRENT FAMILY: 1.0.0
CONFIG VERSION: 1.20.0

; NIC device
BEGIN DEVICE
DEVICENAME: Intel(R) Ethernet Controller I226-V
VENDOR: 8086
DEVICE: 125C
SUBVENDOR: 8086
SUBDEVICE: 0000
NVM IMAGE: FXVL_125C_V_2MB_2.32.bin
EEPID: 80000290
RESET TYPE: REBOOT
REPLACES:
END DEVICE

Here is the inventory result
Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.41.3.1
Copyright(C) 2013 - 2024 Intel Corporation.

nvmupdatew64e.exe -i -l inventory.txt

Config file will not be read.
Inventory
[00:002:00:00]: Intel(R) Ethernet Controller I226-V
Alternate MAC address is not set.
Flash inventory started.
Shadow RAM inventory started.
Shadow RAM inventory finished.
Flash inventory finished.
[00:003:00:00]: Intel(R) Ethernet Controller I226-V
Alternate MAC address is not set.
Flash inventory started.
Shadow RAM inventory started.
Shadow RAM inventory finished.
Flash inventory finished.
[00:004:00:00]: Intel(R) Ethernet Controller I226-V
Alternate MAC address is not set.
Flash inventory started.
Shadow RAM inventory started.
Shadow RAM inventory finished.
Flash inventory finished.
[00:005:00:00]: Intel(R) Ethernet Controller I226-V
Alternate MAC address is not set.
Flash inventory started.
Shadow RAM inventory started.
Shadow RAM inventory finished.
Flash inventory finished.
[00:002:00:00]: Intel(R) Ethernet Controller I226-V
Vendor                 : 8086
Device                 : 125C
Subvendor              : 8086
Subdevice              : 0000
Revision               : 4
LAN MAC                : 60BEB40D8560
Alt MAC                : 000000000000
SAN MAC                : 000000000000
ETrackId               : 80000290
SerialNumber           : 60BEB4FFFF0D8560
NVM Version            : 2.20(2.14)
PBA                    : G23456-000
VPD status             : Not set
VPD size               : 0
NVM update             : No config file entry
  checksum             : Valid
[00:003:00:00]: Intel(R) Ethernet Controller I226-V
Vendor                 : 8086
Device                 : 125C
Subvendor              : 8086
Subdevice              : 0000
Revision               : 4
LAN MAC                : 60BEB40D8561
Alt MAC                : 000000000000
SAN MAC                : 000000000000
ETrackId               : 80000290
SerialNumber           : 60BEB4FFFF0D8561
NVM Version            : 2.20(2.14)
PBA                    : G23456-000
VPD status             : Not set
VPD size               : 0
NVM update             : No config file entry
  checksum             : Valid
[00:004:00:00]: Intel(R) Ethernet Controller I226-V
Vendor                 : 8086
Device                 : 125C
Subvendor              : 8086
Subdevice              : 0000
Revision               : 4
LAN MAC                : 60BEB40D8562
Alt MAC                : 000000000000
SAN MAC                : 000000000000
ETrackId               : 80000290
SerialNumber           : 60BEB4FFFF0D8562
NVM Version            : 2.20(2.14)
PBA                    : G23456-000
VPD status             : Not set
VPD size               : 0
NVM update             : No config file entry
  checksum             : Valid
[00:005:00:00]: Intel(R) Ethernet Controller I226-V
Vendor                 : 8086
Device                 : 125C
Subvendor              : 8086
Subdevice              : 0000
Revision               : 4
LAN MAC                : 60BEB40D8563
Alt MAC                : 000000000000
SAN MAC                : 000000000000
ETrackId               : 80000290
SerialNumber           : 60BEB4FFFF0D8563
NVM Version            : 2.20(2.14)
PBA                    : G23456-000
VPD status             : Not set
VPD size               : 0
NVM update             : No config file entry
  checksum             : Valid
#10
26.1 Series / Re: IPv6 from Android devices ...
Last post by Javier® - Today at 01:39:24 AM
I don't know if it can be changed, can it be done manual

Recursive DNS Server (RDNSS) lifetime in Router Advertisements (RAs) is automatically managed based on the shortest lifetime of the preferred address on the interface. While RDNSS support adheres to RFC 8106, Dnsmasq does not provide a direct configuration option to set an explicit RDNSS lifetime value.