Recent posts

#1
General Discussion / Re: DEC850 problem
Last post by borealis67 - Today at 05:20:12 AM
I managed to get in by manually setting my PCs IP to 192.168.1.101, the gateway to 192.168.1.1 and subnet to 255.255.255.0. I was then able to get to the web gui.

Now I have a new problem. I have connected the DEC850 to the internet through my existing ISP provided gateway and tried to update the firmware but I receive the following error: No address record found for the selected mirror

The dashboard states that I am running 25.7.3_7-amd64

I am also finding the this error in the log:

 PHP Errors:

[01-Jan-2017 03:33:51 Etc/UTC] [gateway_item.7d114b3e-298b-40e4-b984-a2a0ec7a3345.name] A value is required.

dmesg.boot:

---<<BOOT>>---
Copyright (c) 1992-2023 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 14.3-RELEASE-p2 stable/25.7-n271676-ab2281de1853 SMP amd64
FreeBSD clang version 19.1.7 (https://github.com/llvm/llvm-project.git llvmorg-19.1.7-0-gcd708029e0b2)
[1] VT(vga): resolution 640x480
[1] CPU: AMD EPYC 3201 8-Core Processor                  (1497.26-MHz K8-class CPU)
[1]   Origin="AuthenticAMD"  Id=0x800f12  Family=0x17  Model=0x1  Stepping=2
[1]   Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
[1]   Features2=0x7ed8320b<SSE3,PCLMULQDQ,MON,SSSE3,FMA,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
[1]   AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM>
[1]   AMD Features2=0x35c233ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,SKINIT,WDT,TCE,Topology,PCXC,PNXC,DBE,PL2I,MWAITX>
[1]   Structured Extended Features=0x209c01a9<FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA>
[1]   XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
[1]   AMD Extended Feature Extensions ID EBX=0x1007<CLZERO,IRPerf,XSaveErPtr,IBPB>
[1]   SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=32768
[1]   TSC: P-state invariant, performance statistics
[1] real memory  = 17179869184 (16384 MB)
[1] avail memory = 16464011264 (15701 MB)
[1] Event timer "LAPIC" quality 600
[1] ACPI APIC Table: <INSYDE WALLABY>
[1] FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
[1] FreeBSD/SMP: 1 package(s) x 2 cache groups x 4 core(s)
[1] random: registering fast source Intel Secure Key RNG
[1] random: fast provider: "Intel Secure Key RNG"
[1] random: unblocking device.
[1] ioapic0: MADT APIC ID 128 != hw id 0
[1] ioapic1: MADT APIC ID 129 != hw id 0
[1] ioapic0 <Version 2.1> irqs 0-23
[1] ioapic1 <Version 2.1> irqs 24-55
[1] Launching APs: 7 5 6 4 3 1 2
[1] random: entropy device external interface
[1] wlan: mac acl policy registered
[1] kbd0 at kbdmux0
[1] WARNING: Device "spkr" is Giant locked and may be deleted before FreeBSD 15.0.
[1] efirtc0: <EFI Realtime Clock>
[1] efirtc0: registered as a time-of-day clock, resolution 1.000000s
[1] vtvga0: <VT VGA driver>
[1] smbios0: <System Management BIOS> at iomem 0x7945c000-0x7945c017
[1] smbios0: Entry point: v3 (64-bit), Version: 3.0
[1] aesni0: <AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS,SHA1,SHA256>
[1] acpi0: <INSYDE WALLABY>
[1] acpi0: Power Button (fixed)
[1] cpu0: <ACPI CPU> on acpi0
[1] hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff irq 0,8 on acpi0
[1] Timecounter "HPET" frequency 14318180 Hz quality 950
[1] Event timer "HPET" frequency 14318180 Hz quality 350
[1] Event timer "HPET1" frequency 14318180 Hz quality 350
[1] Event timer "HPET2" frequency 14318180 Hz quality 350
[1] atrtc0: <AT realtime clock> port 0x70-0x71 on acpi0
[1] atrtc0: registered as a time-of-day clock, resolution 1.000000s
[1] Event timer "RTC" frequency 32768 Hz quality 0
[1] attimer0: <AT timer> port 0x40-0x43 on acpi0
[1] Timecounter "i8254" frequency 1193182 Hz quality 0
[1] Event timer "i8254" frequency 1193182 Hz quality 100
[1] apei0: <ACPI Platform Error Interface> on acpi0
[1] Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
[1] acpi_timer0: <32-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
[1] acpi_button0: <Power Button> on acpi0
[1] pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
[1] pci0: <ACPI PCI bus> on pcib0
[1] pci0: <base peripheral, IOMMU> at device 0.2 (no driver attached)
[1] pcib1: <ACPI PCI-PCI bridge> at device 1.3 on pci0
[1] pci1: <ACPI PCI bus> on pcib1
[1] igb0: <Intel(R) I210 Flashless (Copper)> port 0x5000-0x501f mem 0x80800000-0x8081ffff,0x80820000-0x80823fff at device 0.0 on pci1
[1] igb0: NVM V0.6 imgtype6
[1] igb0: Using 1024 TX descriptors and 1024 RX descriptors
[1] igb0: Using 4 RX queues 4 TX queues
[1] igb0: Using MSI-X interrupts with 5 vectors
[1] igb0: Ethernet address: f4:90:ea:00:61:27
[1] igb0: netmap queues/slots: TX 4/1024, RX 4/1024
[1] pcib2: <ACPI PCI-PCI bridge> at device 1.4 on pci0
[1] pci2: <ACPI PCI bus> on pcib2
[1] igb1: <Intel(R) I210 Flashless (Copper)> port 0x4000-0x401f mem 0x80700000-0x8071ffff,0x80720000-0x80723fff at device 0.0 on pci2
[1] igb1: NVM V0.6 imgtype6
[1] igb1: Using 1024 TX descriptors and 1024 RX descriptors
[1] igb1: Using 4 RX queues 4 TX queues
[1] igb1: Using MSI-X interrupts with 5 vectors
[1] igb1: Ethernet address: f4:90:ea:00:61:28
[1] igb1: netmap queues/slots: TX 4/1024, RX 4/1024
[1] pcib3: <ACPI PCI-PCI bridge> at device 1.5 on pci0
[1] pci3: <ACPI PCI bus> on pcib3
[1] igb2: <Intel(R) I210 Flashless (Copper)> port 0x3000-0x301f mem 0x80600000-0x8061ffff,0x80620000-0x80623fff at device 0.0 on pci3
[1] igb2: NVM V0.6 imgtype6
[1] igb2: Using 1024 TX descriptors and 1024 RX descriptors
[1] igb2: Using 4 RX queues 4 TX queues
[1] igb2: Using MSI-X interrupts with 5 vectors
[1] igb2: Ethernet address: f4:90:ea:00:61:29
[1] igb2: netmap queues/slots: TX 4/1024, RX 4/1024
[1] pcib4: <ACPI PCI-PCI bridge> at device 1.6 on pci0
[1] pci4: <ACPI PCI bus> on pcib4
[1] igb3: <Intel(R) I210 Flashless (Copper)> port 0x2000-0x201f mem 0x80500000-0x8051ffff,0x80520000-0x80523fff at device 0.0 on pci4
[1] igb3: NVM V0.6 imgtype6
[1] igb3: Using 1024 TX descriptors and 1024 RX descriptors
[1] igb3: Using 4 RX queues 4 TX queues
[1] igb3: Using MSI-X interrupts with 5 vectors
[1] igb3: Ethernet address: f4:90:ea:00:61:2a
[1] igb3: netmap queues/slots: TX 4/1024, RX 4/1024
[1] pcib5: <ACPI PCI-PCI bridge> at device 7.1 on pci0
[1] pci5: <ACPI PCI bus> on pcib5
[1] pci5: <encrypt/decrypt> at device 0.2 (no driver attached)
[1] xhci0: <XHCI (generic) USB 3.0 controller> mem 0x80200000-0x802fffff at device 0.3 on pci5
[1] xhci0: 64 bytes context size, 64-bit DMA
[1] usbus0: waiting for BIOS to give up control
[1] usbus0 on xhci0
[1] usbus0: 5.0Gbps Super Speed USB v3.0
[1] pcib6: <ACPI PCI-PCI bridge> at device 8.1 on pci0
[1] pci6: <ACPI PCI bus> on pcib6
[1] pci6: <encrypt/decrypt> at device 0.1 (no driver attached)
[1] ahci0: <AMD KERNCZ AHCI SATA controller> mem 0x8018e000-0x8018efff at device 0.2 on pci6
[1] ahci0: AHCI v1.31 with 1 6Gbps ports, Port Multiplier supported with FBS
[1] ahcich0: <AHCI channel> at channel 0 on ahci0
[1] hdac0: <AMD X370 HDA Controller> mem 0x80180000-0x80187fff at device 0.3 on pci6
[1] ax0: <AMD 10 Gigabit Ethernet Driver> mem 0x80160000-0x8017ffff,0x80140000-0x8015ffff,0x80188000-0x80189fff at device 0.4 on pci6
[1] ax0: Using 512 TX descriptors and 512 RX descriptors
[1] ax0: Using 8 RX queues 8 TX queues
[1] ax0: Using MSI-X interrupts with 12 vectors
[1] ax0: Ethernet address: f4:90:ea:00:61:2b
[1] ax0: xgbe_config_sph_mode: SPH disabled in channel 0
[1] ax0: xgbe_config_sph_mode: SPH disabled in channel 1
[1] ax0: xgbe_config_sph_mode: SPH disabled in channel 2
[1] ax0: xgbe_config_sph_mode: SPH disabled in channel 3
[1] ax0: xgbe_config_sph_mode: SPH disabled in channel 4
[1] ax0: xgbe_config_sph_mode: SPH disabled in channel 5
[1] ax0: xgbe_config_sph_mode: SPH disabled in channel 6
[1] ax0: xgbe_config_sph_mode: SPH disabled in channel 7
[1] ax0: RSS Enabled
[1] ax0: Receive checksum offload Enabled
[1] ax0: VLAN filtering Enabled
[1] ax0: VLAN Stripping Enabled
[1] ax0: Checking GPIO expander validity
[1] ax0: GPIO configuration valid
[1] ax0: xgbe_phy_sfp_signals: port_sfp_inputs: 0x7
[1] ax0: xgbe_phy_sfp_detect: mod absent
[1] ax0: netmap queues/slots: TX 8/512, RX 8/512
[1] ax1: <AMD 10 Gigabit Ethernet Driver> mem 0x80120000-0x8013ffff,0x80100000-0x8011ffff,0x8018a000-0x8018bfff at device 0.5 on pci6
[1] ax1: Using 512 TX descriptors and 512 RX descriptors
[1] ax1: Using 8 RX queues 8 TX queues
[1] ax1: Using MSI-X interrupts with 12 vectors
[1] ax1: Ethernet address: f4:90:ea:00:61:2c
[1] ax1: xgbe_config_sph_mode: SPH disabled in channel 0
[1] ax1: xgbe_config_sph_mode: SPH disabled in channel 1
[1] ax1: xgbe_config_sph_mode: SPH disabled in channel 2
[1] ax1: xgbe_config_sph_mode: SPH disabled in channel 3
[1] ax1: xgbe_config_sph_mode: SPH disabled in channel 4
[1] ax1: xgbe_config_sph_mode: SPH disabled in channel 5
[1] ax1: xgbe_config_sph_mode: SPH disabled in channel 6
[1] ax1: xgbe_config_sph_mode: SPH disabled in channel 7
[1] ax1: RSS Enabled
[1] ax1: Receive checksum offload Enabled
[1] ax1: VLAN filtering Enabled
[1] ax1: VLAN Stripping Enabled
[1] ax1: Checking GPIO expander validity
[1] ax1: GPIO configuration valid
[1] ax1: xgbe_phy_sfp_signals: port_sfp_inputs: 0x7
[1] ax1: xgbe_phy_sfp_detect: mod absent
[1] ax1: netmap queues/slots: TX 8/512, RX 8/512
[1] isab0: <PCI-ISA bridge> at device 20.3 on pci0
[1] isa0: <ISA bus> on isab0
[1] uart0: <8250 or 16450 or compatible> port 0x3f8-0x3ff irq 3 flags 0x10 on acpi0
[1] hwpstate0: <Cool`n'Quiet 2.0> on cpu0
[1] cpufreq0: <CPU frequency control> on cpu0
[1] Timecounter "TSC" frequency 1497186677 Hz quality 1000
[1] Timecounters tick every 1.000 msec
[1] ugen0.1: <AMD XHCI root HUB> at usbus0
[1] uhub0 on usbus0
[1] uhub0: <AMD XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
[1] Trying to mount root from ufs:/dev/gpt/rootfs [rw]...
[1] ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <TS256GMTS952T2 02J0T4GB> ACS-2 ATA SATA 3.x device
ada0: Serial Number G219190013
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 1024bytes)
ada0: Command Queueing enabled
ada0: 244198MB (500118192 512 byte sectors)
[1] uhub0: 8 ports with 8 removable, self powered
[3] ZFS filesystem version: 5
[3] ZFS storage pool version: features support (5000)

Please help. Thanks for the response.
#2
General Discussion / Re: Idea for next version's co...
Last post by drosophila - Today at 04:58:27 AM
Yes, I've seen these two-word names, but they don't function well for this purpose, and "X-rays" would be cheating IMO. ;)
#3
General Discussion / Re: DEC850 problem
Last post by drosophila - Today at 04:54:51 AM
After a reset the interfaces might not even be assigned and thus have no IP address to connect to, so you'd need to configure these things using the console.

The 850 should have shipped with a mini USB to USB cable. If you find one of these you should look at this guide:
https://docs.opnsense.org/hardware/serial_connectivity.html

For the terminal program you would likely use PuTTY
https://www.chiark.greenend.org.uk/~sgtatham/putty/
(if you're on Windows)
#4
26.1 Series / Re: Rule or alias not matching
Last post by clarknova - Today at 03:45:26 AM
Yeah the alias was disabled :P I'm a little disappointed in how long it took me to figure that one out.
#5
26.1 Series / Re: CALL FOR TESTING: Multi-dh...
Last post by Maurice - Today at 03:09:52 AM
As promised, I tested again, performed packet captures and looked at the dhcp6c log.

WAN 2 works fine.

For WAN 1
- with Rapid Commit disabled, there is a Solicit from OPNsense and an Advertise from the DHCPv6 server, but OPNsense then doesn't send a Request.
- with Rapid Commit enabled, there is a Solicit from OPNsense and a Reply from the DHCPv6 server, but OPNsense doesn't seem to process the reply.

In both cases, the dhcp6c process for WAN 2(!) logs "skipping unrelated packet (interface 1)".

So it seems that messages received on both interfaces are all delivered to the same dhcp6c process (WAN 2 in my case), which then of course can't find a matching interface in its config for messages received on WAN 1.

How do you deliver inbound DHCPv6 messages to the correct process in the first place? Do the dhcp6c processes bind to distinct sockets?

Cheers
Maurice
#6
General Discussion / DEC850 problem
Last post by borealis67 - Today at 02:31:48 AM
I am new here so hi. I have a problem with my DEC850. I have never been an expert at networking. Far from it. I am a total beginner. So please have patience with me.

I bought this DEC850 years ago to mess around with and to try and learn, as I learn by doing. It worked fine for years with no problems. I moved to a new location and am trying to set this device up and it also worked fine up until today. I plugged it into my PC to try and access the web interface and it will not fully connect to my PC well enough to bring up the web interface. It's making a hardware connection but the PC will not get an IP address. I tried all ports and nothing.

The DEC850 was reset to factory defaults during last use so there are no weird configurations going on. I am directly connecting to the 850 from my laptop with an ethernet cable on port 0. I tried all ports but I cannot get anything to load. What can I try? I would try the usb console but I don't know where to begin. What software to use, etc. Please help me get this thing working again. Thank you.
#7
German - Deutsch / Re: "Lahmes" Internet seit Upd...
Last post by drosophila - Today at 01:57:09 AM
Ja, IPv4 ist generell langsamer als IPv6, aber das sollte nicht so extrem sein, dass es das Originalproblem wäre. Und weil letztlich IPv4 irgendwann abgedreht werden wird, sollte man sich schon irgendwann mit IPv6 anfreunden, besonders, weil viele Provider nur noch DS-Lite ausspucken und wer sich da was hosten will, tut sich mit IPv6 auf Dauer wohl eher einen Gefallen, als mit Tunneln herumzubasteln. Das mit dem schwatzhaften IPv6 stimmt zwar auch, aber vermutlich wäre das bei IPv4 auch so, wenn das mit DHCP und dem ganzen anderen Autokonfigurationszirkus aufgezogen wird. Mich stören hauptsächlich die autogenerierten Adressen, da sehe ich nicht an der IP, welcher Rechner das war, was bei Logs IMO extrem wichtig ist.
Deine Pingzeiten sind zwar langsam, aber nicht so grottig, dass das allein das Problem sein sollte. Kannst Du den traceroute mal vom Client aus machen? So sieht man ja Deine OPNsense nicht. Die sollte deutlich unter 1ms liegen.

iperf3 bietet AFAIK keiner an, also falls Du nicht selber irgendwo einen Server laufen lassen kannst geht das nur im eigenen Netz. Also z.b. zwischen Client und Deiner Sensebox. Deshalb eher die Bandbreitenmessung machen und sehen, ob zumindest der Rohdurchsatz paßt.
#8
Like this diff for /usr/local/sbin/opnsense-shell, only conditionally applied when the plugin is installed / reversed if removed?
25a26
> CMD_IPERF3="/usr/local/bin/iperf3 -s"
105a107,110
> iperf3)
>     shift
>     exec ${CMD_IPERF3} "${@}"
>     ;;
128c133
< echo
---
> echo "                                        14) iperf3 server"
177a183,185
>     ;;
> 14)
>     ${CMD_IPERF3}
Is this possible, or don't the installers for these plugins have access to the systems innards?
#9
General Discussion / Re: internal DNS issues
Last post by donee - Today at 01:17:02 AM
I believe the default behavior is a combo of 
Services: Dnsmasq DNS & DHCP and Services: Unbound DNS
which is what I am trying to get working.  My external DNS works but I want it so that when a new machine is added to the network via DHCP, its hostname is automatically gets added to DNS and it can be resolved anywhere internally.  I have never had so much trouble getting this working in the past.   Sorry about not being as cear as possible. Hopefully this works better. 


PDF print out of Services: Unbound DNS: General
screenshot of Services: Unbound DNS: General

and a screenshot from Services: Dnsmasq DNS & DHCP: Leases



#10
25.1, 25.4 Legacy Series / Re: Prevent OPNsense from shut...
Last post by vizi0n - Today at 01:04:34 AM
Hey that's my reddit post !

Sorry to bring this back from the dead, but I did in fact solve my issue. It was not done in the most elegant way, but it does what I need so, I guess that's good !

My home's setup is a 120v powered Proxmox server (on the UPS) and a 12v powered Proxmox server (on a car battery / home made UPS).

My problem was getting to run NUT server on the 12v Proxmox server OPNsense VM so that it monitors the UPS that is powering the 120v Proxmox server which hosts my primary OPNsense. The 12v OPNsense would always shut down when the 120v UPS would kick in even though it is on a different power source.

The 120v Proxmox server is the main server, which hosts many different VMs and LXC such as my primary OPNsense, FreePBX, Pihole, etc, and the 12v server is the "power outage backup router" that runs the backup OPNsense as well as the Omada controller to keep the APs running, Pihole and others light things, including NUT server.

My not-so-elegant solution :

- I have instealled the NUT server on a Debian VM on the 12v Proxmox server, with a USB passthrough of the port that goes to the UPS
- I have installed the client NUT package ONLY on the primary OPNsense so that it can shut down when there is a power outage, but not on the backup OPNsense.
- I have also created a very basic script that I have added to the crontab. It runs every minute to validate if the UPS is back on power because the "FSD OL" status would always kill my primary OPNsense when it was booting and can only be reset back to "OL" by restarting the daemon.

Here is the cron job script if you are interested. Simply adjust the UPS' name

#!/bin/bash
upsstatus=$(upsc CP1500AVRLCD3@localhost 2>&1 | grep "ups.status:" | sed 's/^.*: //g')

echo "UPS Status : $upsstatus"
if [ "$upsstatus" = "FSD OL" ]; then
#       echo "Restarting NUT daemon"
        /etc/init.d/nut-server restart
else
        echo "Doing nothing"
fi

I understand that this is not a real real solution to running the NUT server on OPNsense, but that is how I ended up doing it.