Messages

1

High availability / Re: CARP awareness for Wireguard 2.0 & follow a single interface - 23.7.3

« on: July 30, 2024, 03:41:43 pm »

Hi, does Your script still works without problems or something changed? I'm on 24.1.10, Your script is reacting to CARP (I see messages like "due to master/backup wireguard turn on/off), but on both nodes they are still running and their handshakes break connections Manually executing  /usr/local/sbin/pluginctl -s wireguard stop is successfull but just after that /usr/local/sbin/pluginctl -s wireguard status is showing, that it is still running.

2

Hardware and Performance / Re: usb ethernet ASIX AX88179A

« on: June 25, 2023, 02:12:31 pm »

For recommendations ( I tested both):
Dell Wyse 5070 Extended
Fujitsu Futro S940

3

Tutorials and FAQs / Re: HOWTO - Update AdGuard Home automatically with cron

« on: March 30, 2023, 01:09:20 pm »

Thanks for HOWTO, I used Your example for auto-updates. But in my case, I also have command for syncing YAML file between 2 nodes, I simply modified my additional file agh_sync.d and added update there with command:

/usr/local/AdGuardHome/./AdGuardHome --update;(sleep 15 && /usr/local/etc/rc.d/adguardhome stop && sleep 5 && /usr/local/etc/rc.d/adguardhome start)

No need to modify plugin files, not so clean about restart but works

4

22.1 Legacy Series / Re: [AdGuardHome] DNS not working on VIP interface

« on: May 06, 2022, 03:06:32 pm »

Thanks, workaround is working well

5

22.1 Legacy Series / [AdGuardHome] DNS not working on VIP interface

« on: May 05, 2022, 12:16:15 pm »

Hello,
I have strange problem and i can't find what can be the root of it. I set up AdGuardHome (mimugmail repository). It works very well, with AGH working on port 53 and Unbound on 5353 (for registering in AGH DHCP leases). However, after setting VIP addresses for HA (HA is working perfectly), AGH is not working on VIP interface (but it is normally listed in AGH setup). When i try to nslookup different domains via VIP interface address, nslookup times out and OPNSense nor AGH don't even show anything in logs (Firewall, general, backend and AGH log). Unbound works well on VIP via 5353 port so it is clearly not entirely VIP interface fault but rather AGH using VIP interface bug.

I know this is community repository and not directly related to OPNSense, but maybe someone has any idea how to try to debug this?

6

20.1 Legacy Series / Trying to build for Raspberry Pi 4

« on: March 15, 2020, 11:31:06 am »

Hello,
Anyone tried to build OPNSense for RPI4? I saw that there is already uboot for rpi4 and FreeBSD is also supposed to work on it. I tried to build it myself with opnsense tools but after adding new device config (copy paste RPI2) and replacing arch to arm64:aarch64 and paths to uboot and firmware, building still failed.

I'm not well versed in build with opnsense tools, maybe someone had more luck?

7

19.7 Legacy Series / [ACME][Let's Encrypt] Location of generated certificates for export purposes

« on: December 27, 2019, 09:37:13 pm »

Hello,
I have problem with finding the path where are stored generated by acme certificates in OPNSense (using 19.7.8
 AMD64 right now). I'm using os-acme-client for generating wildcard SSL, which i would like later to distribute to other home servers.

My first attempt for that was to use Automation part of acme client with Upload to SFTP but somehow it doesn't work. I enabled it and added in automation section when defining certificate generation procedure. Test connection is ok, but i didn't see for it to be triggered when renewing certs, logs don't show anything.

Second attempt is then manually copy certs. I followed tips from this topic:
https://forum.opnsense.org/index.php?topic=8865.msg39661#msg39661
but as far as specified there path exist ("/var/etc/acme-client/home/"), those are always empty.

Any idea how to tackle it?

8

Hardware and Performance / Re: [Work In Progress] OPNsense Ported into ARM Devices

« on: November 30, 2019, 11:07:55 am »

Which version of RPI2 You have? I know, that there are 2 revisions, 2 different SOCs. I have first version with older CPU (V1.1), newer has the same as RPI3 but underclocked (V1.2).

I tried to use image from the first post of this topic. Resulted with black screen after initial booting, last msg was:
Booting [/boot/kernel/kernel]...
/boot/dtb/bcm2836-rpi-2-b.dtb size=0x385e
Loaded DTB from file 'bcm2836-rpi-2-b.dtb'.
Kernel entry at 0x200180...
Kernel args: (null)

After this message screen goes black, and both LEDs on RPI turn off. Ethernet port also is inactive (both LEDs are turned off).

Lately i successfully compiled new IMG from latest OPNSESNSE tools (19.7 on 11.2 FreeBSD). But the result after putting it on SD card is the same. Still black screen. I have now no idea how to tackle it.

EDIT. Can You share Your latest img? Either 19.7 or 20.1, maybe i'm doing something wrong.

9

Hardware and Performance / Re: [Work In Progress] OPNsense Ported into ARM Devices

« on: November 23, 2019, 11:44:26 am »

Hello, i have problem with running OPNsense on RPI2. Somehow, after installing img from opening post on SD card, RPI2 boots, but after loading kernel screen goes black and device is unresponsive, ETH not working too.
Last msg before black screen is something like:
Booting [/boot/kernel/kernel]...
/boot/dtb/bcm2836-rpi-2-b.dtb size=0x385e
Loaded DTB from file 'bcm2836-rpi-2-b.dtb'.
Kernel entry at 0x200180...
Kernel args: (null)

I tried 2 different SD cards (which both work normally on raspbian).
After that tried to compile myself but on FreeBSD 11.2 amd64 i get errors when # make base DEVICE=RPI2 so compiling is unsuccessful... Something about [clang], already removed VM so can't check. Any idea?