Messages

1

21.1 Legacy Series / Re: Upgrade to 21.1 may take *very* long time (>1h)

« on: January 29, 2021, 06:32:47 pm »

Upgrade went super smooth as always.

Good job guys and thanks for all the hard work!

2

General Discussion / Re: Announce: new OPNsense community repository

« on: January 22, 2021, 04:18:58 pm »

Beer & Boobies for mimugmail

3

General Discussion / Re: Announce: new OPNsense community repository

« on: January 22, 2021, 07:48:08 am »

If anyone would like to test if AGH works with LibreSSL tool, I'd be very thankful

I'm running it on LibreSSL

4

20.7 Legacy Series / Re: Resize OPNSense Partition

« on: January 21, 2021, 08:14:10 pm »

Today I did the following:
Peter

Good howto. I've just used your steps to resize my root partition. Worked flawlessly. Maybe with a little doc-fu it can be added to the docs or pinned?

5

General Discussion / Re: Announce: new OPNsense community repository

« on: January 21, 2021, 07:36:46 pm »

Please check for updates again. I updated to 1.3 with full service control

I can confirm that both the service status and starting on boot is solved with this new release.

Your quick response and action is very much appreciated!

6

General Discussion / Re: Announce: new OPNsense community repository

« on: January 20, 2021, 08:00:30 pm »

I finally got AdGuardHome working as an opnsense plugin. Grab it from here: https://www.routerperformance.net/opnsense-repo/

It's still lacking status view, but after install and enabling it's available via port 3000 (if no other service listens to it).

Good work. Been running it as first-in-chain dns on client subnet for a couple of days now.

Not sure if you're aware but the plugin does not seem to run on boot. I presume this is related to the service status which is not working as well.

Could you propose a workaround or do you suspect it might be caused by my environment?

Code: [Select]

dmesg.boot:

---<>---
Copyright (c) 2013-2019 The HardenedBSD Project.
Copyright (c) 1992-2019 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.1-RELEASE-p12-HBSD #0  0857355c1c2(stable/20.7)-dirty: Mon Jan 18 18:12:55 CET 2021
    root@sensey:/usr/obj/usr/src/amd64.amd64/sys/SMP amd64
FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1)
VT(vga): text 80x25
HardenedBSD: initialize and check features (__HardenedBSD_version 1200059 __FreeBSD_version 1201000).
CPU: Intel(R) Celeron(R) CPU 3865U @ 1.80GHz (1799.99-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x806e9  Family=0x6  Model=0x8e  Stepping=9
  Features=0x1f83fbff
  Features2=0xcffaa223
  AMD Features=0x2c100800
  AMD Features2=0x121
  Structured Extended Features=0x944683
  Structured Extended Features2=0x4
  Structured Extended Features3=0xac000400
  XSAVE Features=0xf
  IA32_ARCH_CAPS=0x48
  AMD Extended Feature Extensions ID EBX=0x1001000
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
Hypervisor: Origin = "KVMKVMKVM"
real memory  = 3264217088 (3113 MB)
avail memory = 3125776384 (2980 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table:
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
random: unblocking device.
ioapic0  irqs 0-23 on motherboard
Launching APs: 1
wlan: mac acl policy registered
random: entropy device external interface
kbd1 at kbdmux0
module_register_init: MOD_LOAD (vesa, 0xffffffff8128e7c0, 0) error 19
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
000.000052 [4336] netmap_init               netmap: loaded module
[ath_hal] loaded
nexus0
vtvga0:  on motherboard
cryptosoft0:  on motherboard
acpi0:  on motherboard
acpi0: Power Button (fixed)
cpu0:  on acpi0
atrtc0:  port 0x70-0x71,0x72-0x77 irq 8 on acpi0
atrtc0: registered as a time-of-day clock, resolution 1.000000s
Event timer "RTC" frequency 32768 Hz quality 0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x608-0x60b on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
isab0:  at device 1.0 on pci0
isa0:  on isab0
atapci0:  port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc1e0-0xc1ef at device 1.1 on pci0
ata0:  at channel 0 on atapci0
ata1:  at channel 1 on atapci0
pci0:  at device 1.3 (no driver attached)
vgapci0:  mem 0xfd000000-0xfdffffff,0xfebd0000-0xfebd0fff at device 2.0 on pci0
vgapci0: Boot video device
virtio_pci0:  port 0xc0c0-0xc0df mem 0xfebd1000-0xfebd1fff,0xfe000000-0xfe003fff irq 11 at device 3.0 on pci0
vtnet0:  on virtio_pci0
vtnet0: Ethernet address: 52:54:00:a7:1b:68
vtnet0: netmap queues/slots: TX 1/256, RX 1/128
000.000760 [ 447] vtnet_netmap_attach       vtnet attached txq=1, txd=256 rxq=1, rxd=128
uhci0:  port 0xc0e0-0xc0ff irq 11 at device 4.0 on pci0
usbus0 on uhci0
usbus0: 12Mbps Full Speed USB v1.0
uhci1:  port 0xc100-0xc11f irq 10 at device 4.1 on pci0
usbus1 on uhci1
usbus1: 12Mbps Full Speed USB v1.0
uhci2:  port 0xc120-0xc13f irq 10 at device 4.2 on pci0
usbus2 on uhci2
usbus2: 12Mbps Full Speed USB v1.0
ehci0:  mem 0xfebd2000-0xfebd2fff irq 11 at device 4.7 on pci0
usbus3: EHCI version 1.0
usbus3 on ehci0
usbus3: 480Mbps High Speed USB v2.0
virtio_pci1:  port 0xc080-0xc0bf mem 0xfebd3000-0xfebd3fff,0xfe004000-0xfe007fff irq 10 at device 5.0 on pci0
virtio_pci2:  port 0xc000-0xc07f mem 0xfebd4000-0xfebd4fff,0xfe008000-0xfe00bfff irq 10 at device 6.0 on pci0
vtblk0:  on virtio_pci2
vtblk0: 16384MB (33554432 512 byte sectors)
virtio_pci3:  port 0xc140-0xc15f mem 0xfe00c000-0xfe00ffff irq 11 at device 7.0 on pci0
vtballoon0:  on virtio_pci3
virtio_pci4:  port 0xc160-0xc17f mem 0xfebd5000-0xfebd5fff,0xfe010000-0xfe013fff irq 11 at device 8.0 on pci0
vtnet1:  on virtio_pci4
vtnet1: Ethernet address: 52:54:00:43:a3:2f
vtnet1: netmap queues/slots: TX 1/256, RX 1/128
000.001313 [ 447] vtnet_netmap_attach       vtnet attached txq=1, txd=256 rxq=1, rxd=128
virtio_pci5:  port 0xc180-0xc19f mem 0xfebd6000-0xfebd6fff,0xfe014000-0xfe017fff irq 10 at device 9.0 on pci0
vtnet2:  on virtio_pci5
vtnet2: Ethernet address: 52:54:00:f0:0d:26
vtnet2: netmap queues/slots: TX 1/256, RX 1/128
000.001314 [ 447] vtnet_netmap_attach       vtnet attached txq=1, txd=256 rxq=1, rxd=128
virtio_pci6:  port 0xc1a0-0xc1bf mem 0xfebd7000-0xfebd7fff,0xfe018000-0xfe01bfff irq 10 at device 10.0 on pci0
vtnet3:  on virtio_pci6
vtnet3: Ethernet address: 52:54:00:54:7f:5f
vtnet3: netmap queues/slots: TX 1/256, RX 1/128
000.001315 [ 447] vtnet_netmap_attach       vtnet attached txq=1, txd=256 rxq=1, rxd=128
ahci0:  port 0xc1c0-0xc1df mem 0xfebd8000-0xfebd8fff irq 11 at device 11.0 on pci0
ahci0: AHCI v1.00 with 6 1.5Gbps ports, Port Multiplier not supported
ahcich0:  at channel 0 on ahci0
ahcich1:  at channel 1 on ahci0
ahcich2:  at channel 2 on ahci0
ahcich3:  at channel 3 on ahci0
ahcich4:  at channel 4 on ahci0
ahcich5:  at channel 5 on ahci0
acpi_syscontainer0:  on acpi0
acpi_syscontainer1:  port 0xaf00-0xaf0b on acpi0
acpi_syscontainer2:  port 0xafe0-0xafe3 on acpi0
acpi_syscontainer3:  port 0xae00-0xae13 on acpi0
atkbdc0:  port 0x60,0x64 irq 1 on acpi0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0:  irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse Explorer, device ID 4
fdc0:  port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: does not respond
device_attach: fdc0 attach returned 6
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart0: console (9600,n,8,1)
orm0:  at iomem 0xe8000-0xeffff pnpid ORM0000 on isa0
vga0:  at port 0x3c0-0x3df iomem 0xa0000-0xbffff pnpid PNP0900 on isa0
attimer0:  at port 0x40 on isa0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
fdc0: No FDOUT register!
Timecounters tick every 10.000 msec
ugen2.1:  at usbus2
ugen3.1:  at usbus3
uhub0:  on usbus2
ugen0.1:  at usbus0
uhub1:  on usbus3
ugen1.1:  at usbus1
uhub2:  on usbus0
uhub3:  on usbus1
Trying to mount root from ufs:/dev/ufs/OPNsense [rw,noatime]...
uhub0: 2 ports with 2 removable, self powered
uhub2: 2 ports with 2 removable, self powered
uhub3: 2 ports with 2 removable, self powered

7

General Discussion / Re: Announce: new OPNsense community repository

« on: January 09, 2021, 02:31:49 pm »

Good job mimugmail.

This community repo idea has great potential imho.

8

20.7 Legacy Series / Re: OpenVPN multiple server issues

« on: January 05, 2021, 09:42:00 pm »

did you assign the 2 ovpn interfaces manually and configured fw rules per interface?

9

General Discussion / Re: Remote Syslog

« on: January 05, 2021, 08:35:10 pm »

As long as you're not flooding your local syslog with default block firewall logs, squid, resolver, etc you should be g2g to log all facility's to your remote syslog.

But as always it all depends on what logs you find important enough to keep in your environment and what resources (network/disk io) you can "spare" .

I would suggest logging over TCP unless you are looking into "physically" seperating your log server by disabling Tx on hardware level.

Hope this helps.

10

20.7 Legacy Series / Re: Unbound service routinely stopping/crashing following 20.7.7 update

« on: January 04, 2021, 08:41:38 pm »

Because it's part of the official 20.7.7 now.

Nice!

11

20.7 Legacy Series / Re: 20.7.7 upgrade made unbound unstable

« on: December 24, 2020, 02:36:30 pm »

This issue (or related) has been covered already in >> https://forum.opnsense.org/index.php?topic=20516.0

You should test with the provided upgrade of unbound to 1.13.1 in this thread and report back if it solved your issue.

12

20.7 Legacy Series / Re: Unbound service routinely stopping/crashing following 20.7.7 update

« on: December 23, 2020, 10:48:42 am »

Here's the latest Unbound revision 1 from FreeBSD ports to try:

# pkg add -f https://pkg.opnsense.org/FreeBSD:12:amd64/20.7/misc/unbound-1.13.0_1.txz

Cheers,
Franco

Updated unbound on my system to the provided revision. Will report back with feedback.

Unbound has been running stable for 24 hours now on the new revision. Issue appears resolved on my end.

13

20.7 Legacy Series / Re: Unbound service routinely stopping/crashing following 20.7.7 update

« on: December 22, 2020, 10:40:36 am »

Here's the latest Unbound revision 1 from FreeBSD ports to try:

# pkg add -f https://pkg.opnsense.org/FreeBSD:12:amd64/20.7/misc/unbound-1.13.0_1.txz

Cheers,
Franco

Updated unbound on my system to the provided revision. Will report back with feedback.

14

20.7 Legacy Series / Re: Unbound service routinely stopping/crashing following 20.7.7 update

« on: December 18, 2020, 05:04:01 pm »

Setting the interfaces manually appears to have stabilized the issue. Will report back if the situation changes.

Spoke too soon It just crashed again.

Reverted to unbound 20.7.6 as suggested by Franco

15

20.7 Legacy Series / Re: Unbound service routinely stopping/crashing following 20.7.7 update

« on: December 18, 2020, 04:24:05 pm »

Setting the interfaces manually appears to have stabilized the issue. Will report back if the situation changes.