@demux
Not built-in to pfSense, but this script works. You will need to edit the config manually for the temp for which you want a warning. It polls the system at 5 minute intervals, mails on warning, mails again on warning cleared. All credit to @luckman212 .
https://github.com/luckman212/pfsense-temp-alert

@stephenw10 Thank you

@johnpoz said in Need help printing from one network to another:

https://pulsedive.com/premium?key=API_KEY&types=ip

Thanks for looking. I am not using Pulsedive, but have been digging around also to see what I can find.

Connections from the firewall itself should not need NAT. But it would be loaded by that point anyway.

Yup you can password protect the console with that option.

However if some bad actor has physical access to your firewall they could do whatever they want anyway.

Steve

I don't know about pihole specifically by adguard does much the same thing and is in the OpenWRT software repo.

https://redmine.pfsense.org/issues/15355

Has been created for this.
Thanks

Hmm, sounds like the VPN connection was taking a different route perhaps?

@SpecGlasses check https://docs.netgate.com/pfsense/en/latest/troubleshooting/disk-lifetime.html. I think I’ve seen posts that if it’s read only it can behave like this due to ZFS caching.

Also if you have a usb stick in it it can pull that file: https://docs.netgate.com/pfsense/en/latest/backup/restore-during-install.html#restore-using-the-external-configuration-locator-ecl

@milani90

Just a gateway or a default gateway. 'default' is the key word here. It would be nice if you actually show the routing table. :)

@johnpoz Actually, I have seen many routers, but they are very complicated to set up. I have never set up a site-to-site VPN in a short period of time, but with pfSense, it was so easy, and many advanced and secure methods are available. That's why I like pfSense.
Anyway, Thanks again!

Some sort of internal card reader maybe? That might be USB attached. You might be able to disable that in the BIOS.

Might be something in the UPS. Try reconnecting it after boot and see what's logged.

Make sure you're running the latest BIOS, that one has errors in the ACPI tables:

acpi0: <ALASKA A M I > Firmware Error (ACPI): Could not resolve symbol [\_SB.PC00.TXHC.RHUB.SS01], AE_NOT_FOUND (20221020/dswload2-315) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20221020/psobject-372) Firmware Error (ACPI): Could not resolve symbol [\_SB.PC00.TXHC.RHUB.SS02], AE_NOT_FOUND (20221020/dswload2-315) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20221020/psobject-372)

Most places in the GUI simply display the interfaces in the order they are parsed in the config file. So changing them there would likely change it everywhere that counts.

Ok yes it looks like one of your USB Ethernet devices disconnected itself for some reason:

ugen0.4: <Realtek USB 10/100/1000 LAN> at usbus0 (disconnected) ure1: at uhub0, port 23, addr 3 (disconnected) rgephy2: detached miibus2: detached ure1: detached Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x458 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80cc0c9c stack pointer = 0x28:0xfffffe00d93a9800 frame pointer = 0x28:0xfffffe00d93a9880 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (netlink_socket (PID) rdi: fffff8000f6382e0 rsi: 0000000000000004 rdx: 0000000000000000 rcx: 000018575745e64c r8: fffffe00dd54b8c0 r9: fffffe00d93aa000 rax: 0000000000000000 rbx: 0000000000000000 rbp: fffffe00d93a9880 r10: 0000000000001388 r11: 000000008055c23d r12: fffffe00d93a9820 r13: fffffe00dd54b3a0 r14: 0000000000000000 r15: fffff8000f6382e0 trap number = 12 panic: page fault cpuid = 0 time = 1710642139 KDB: enter: panic

And the backtrace does indeed show the issue is in the ure driver:

db:0:kdb.enter.default> bt Tracing pid 0 tid 102948 td 0xfffffe00dd54b3a0 kdb_enter() at kdb_enter+0x32/frame 0xfffffe00d93a94e0 vpanic() at vpanic+0x163/frame 0xfffffe00d93a9610 panic() at panic+0x43/frame 0xfffffe00d93a9670 trap_fatal() at trap_fatal+0x40c/frame 0xfffffe00d93a96d0 trap_pfault() at trap_pfault+0x4f/frame 0xfffffe00d93a9730 calltrap() at calltrap+0x8/frame 0xfffffe00d93a9730 --- trap 0xc, rip = 0xffffffff80cc0c9c, rsp = 0xfffffe00d93a9800, rbp = 0xfffffe00d93a9880 --- __mtx_lock_sleep() at __mtx_lock_sleep+0xbc/frame 0xfffffe00d93a9880 usbd_do_request_flags() at usbd_do_request_flags+0x75b/frame 0xfffffe00d93a9900 usbd_do_request_proc() at usbd_do_request_proc+0x5e/frame 0xfffffe00d93a9960 ure_miibus_readreg() at ure_miibus_readreg+0x185/frame 0xfffffe00d93a99d0 rgephy_status() at rgephy_status+0x7b/frame 0xfffffe00d93a9a10 rgephy_service() at rgephy_service+0x329/frame 0xfffffe00d93a9a60 mii_pollstat() at mii_pollstat+0x57/frame 0xfffffe00d93a9a90 ure_ifmedia_sts() at ure_ifmedia_sts+0x190/frame 0xfffffe00d93a9ae0 ifmedia_ioctl() at ifmedia_ioctl+0x163/frame 0xfffffe00d93a9b10 dump_iface() at dump_iface+0x145/frame 0xfffffe00d93a9bc0 rtnl_handle_getlink() at rtnl_handle_getlink+0x2a3/frame 0xfffffe00d93a9ca0 rtnl_handle_message() at rtnl_handle_message+0x195/frame 0xfffffe00d93a9d00 nl_taskqueue_handler() at nl_taskqueue_handler+0x79b/frame 0xfffffe00d93a9e40 taskqueue_run_locked() at taskqueue_run_locked+0x182/frame 0xfffffe00d93a9ec0 taskqueue_thread_loop() at taskqueue_thread_loop+0xc2/frame 0xfffffe00d93a9ef0 fork_exit() at fork_exit+0x7f/frame 0xfffffe00d93a9f30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00d93a9f30 --- trap 0xc, rip = 0x828ed73ea, rsp = 0x85dd21ca8, rbp = 0x85dd21cc0 ---

Which is expected if it did disconnect unexpectedly.

Avoid USB Ethernet if at all possible.

If a crash report exists on the other device it would be in /var/crash.

@BassT said in switch from HAProxy Manager to pfsense haproxy:

basst@Kubuntu-VM:~$ curl pfsense.home
curl: (6) Could not resolve host: pfsense.home

In that case, the pfsense is the domain (eg, pfsense.com and the home is the TLD (top level domain, eg .com). In order for that to work, you would need to set a domain of pfsense.home:
0da662dd-1610-4958-8157-d3a268ae3cf9-image.png

Don't forget to mark as solved!