Messages

1

Hardware and Performance / Re: DEC750 issues on startup from Serial Console

« on: January 31, 2023, 05:20:25 pm »

The resolution was some PuTTY settings, specifically setting the Terminal | Keyboard seetings for Backspace to CTRL-H, and the Function Keys to VT100+. Screenshot attached.

2

Hardware and Performance / Re: DEC750 issues on startup from Serial Console

« on: January 30, 2023, 03:21:43 pm »

Would love to! However, I cannot select any boot devices on the appliance at all. I even thought about swapping the NVMe module (on the DEC750) but no joy.

3

Hardware and Performance / Re: DEC750 issues on startup from Serial Console

« on: January 29, 2023, 03:18:01 pm »

Understood. I did directly connect via a machine on Ubuntu yesterday, but no change in results. Thankfully I had some spare equipment to put into service for the weekend, and I have a support request in to Deciso, but wanted to see if I could get this resolved on my own.

The worst part is this setup was able to get into the UEFI boot menu over the last year without an issue. Now the device doesn’t respond at all via anything I connect to it.

4

Hardware and Performance / Re: DEC750 issues on startup from Serial Console

« on: January 28, 2023, 05:40:49 pm »

I did try a connection from a RasPi using https://github.com/Pack3tL0ss/ConsolePi which has worked on this device in the past, but doesn't seem to work now.

And I tried the same command but using the USB serial interface on the RasPi, but the same result. I think the UEFI is corrupted in some way, but cannot confirm.

5

Hardware and Performance / Re: DEC750 issues on startup from Serial Console

« on: January 28, 2023, 03:47:42 am »

Yep. I am connected to the serial interface on the DEC750, and using PuTTY to communicate via the virtual COM port created when connecting to the USB interface.

6

Hardware and Performance / DEC750 issues on startup from Serial Console

« on: January 27, 2023, 07:31:00 pm »

I am having issues getting into the Setup menu on my existing DEC750. When using PuTTY, and connected to the serial interface, I am getting the following prompt:

Code: [Select]

BIOS Version : 05.32.50.0012-A10.20
BIOS Build Date : 11/15/2021
Processor Type : AMD Ryzen Embedded V1500B
System Memory Speed : 2400 MHz
Press Esc to go to Setup
However, the system does not respond to the Esc key, nor does it respond to any keyboard input. I have tried this from an existing serial console, and 2 other machines with no change.

The additional output is as follows:

Code: [Select]

uart0: <8250 or 16450 or compatible> port 0x3f8-0x3ff irq 3 flags 0x10 on acpi0
hwpstate0: <Cool`n'Quiet 2.0> on cpu0
Timecounter "TSC-low" frequency 1097937965 Hz quality 1000
Timecounters tick every 1.000 msec
nvd0: <TS256GMTE652T2> NVMe namespace
nvd0: 244198MB (500118192 512 byte sectors)
Trying to mount root from ufs:/dev/gpt/rootfs [rw]...
ugen0.1: <AMD XHCI root HUB> at usbus0
ugen1.1: <AMD XHCI root HUB> at usbus1
uhub0 on usbus0
WARNING: /mnt was not properly dismounted
uhub1WARNING: /mnt: mount pending error: blocks 16 files 1
on usbus1
uhub1: <AMD XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus1
uhub0: <AMD XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
uhub1: 3 ports with 3 removable, self powered
panic: ufs_dirbad: /: bad dir ino 18429440 at offset 512: mangled entry
cpuid = 4
time = 1514767363
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe008fa13890
vpanic() at vpanic+0x17f/frame 0xfffffe008fa138e0
panic() at panic+0x43/frame 0xfffffe008fa13940
ufs_lookup_ino() at ufs_lookup_ino+0xc75/frame 0xfffffe008fa13a20
vfs_cache_lookup() at vfs_cache_lookup+0xad/frame 0xfffffe008fa13a70
lookup() at lookup+0x45c/frame 0xfffffe008fa13b10
namei() at namei+0x259/frame 0xfffffe008fa13bc0
kern_statat() at kern_statat+0xf3/frame 0xfffffe008fa13d00
sys_fstatat() at sys_fstatat+0x2f/frame 0xfffffe008fa13e00
amd64_syscall() at amd64_syscall+0x10c/frame 0xfffffe008fa13f30
fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe008fa13f30
--- syscall (552, FreeBSD ELF64, sys_fstatat), rip = 0x8011f019a, rsp = 0x7fffffffd328, rbp = 0x7fffffffd440 ---
KDB: enter: panic
[ thread pid 67 tid 100147 ]
Stopped at      kdb_enter+0x37: movq    $0,0x11f821e(%rip)
db>
From this, I would assume the media was corrupted in some way, hence my desire to boot from a USB device and reimage the device. However, if I cannot get into the Boot menu, I cannot choose the boot device. Any assistance anyone can provide would be welcome.

7

Hardware and Performance / Issues with opnsense-business 22.10 on DEC850

« on: November 21, 2022, 04:29:48 pm »

Greetings all!

I have a DEC850 that I have had for about a year. When I updated the unit to 22.10, there were some issues with the device not updating correctly. After getting access to the console, I was able to complete the update, but I have had a number of issues since, including:

• unable to allocate swap
• redis, ntopng, Zenarmor/Sensi, and unbound terminating with signal 6
• sporadic reboots

I think this may be related to issues with the upgrade. I would love to just redeploy the software on this, but I have some questions before I go about wiping the device, and reinstalling OPNsense-business:

• Is there a 'correct' way to replace the version that shipped?
• Do I need to reapply any settings that are unique to the Deciso hardware?
• Can you restore a backup config without carrying over the issues I am seeing?
• Is this even necessary, and is anyone else experiencing these issues?

I am also contacting the folks at Deciso, and if I get a response, I will post it. Any assistance that you can provide would be appreciated!

8

22.1 Legacy Series / Re: Running native ipv6 but I get no ipv6 default route

« on: April 21, 2022, 04:20:37 pm »

I do not. I have a few Netgear switches, and checked all of them, and IGMP snooping is disabled, as well as anything related to multicast routing. For the moment, the configuration is a flat network, with no VLANS, so the need for those services is minimal.

It's bad enough that I am having to bounce the WAN interfaces and switch ports daily to get a working IPv6 route. Some devices are able to get a route via RA, all of them are receiving the announcement, but it is garbled on some devices through this switch.

9

22.1 Legacy Series / Re: Running native ipv6 but I get no ipv6 default route

« on: April 13, 2022, 08:21:13 pm »

Quick update: this one has me scratching my head. After I did a Wireshark capture, I was able to determine that the RA was not being carried across a particular switch. Once I power cycled that switch, I was able to get the Windows machines to see the RA, and update their routes.

I am at a bit of a loss to figure out why this switch (a Netgear GS716T on 6.3.1.39 firmware) would start filtering RA...

10

22.1 Legacy Series / Re: Running native ipv6 but I get no ipv6 default route

« on: April 13, 2022, 06:46:07 pm »

I seem to be getting a similar, but slightly different issue. From what I can tell, my device is generating a IPv6 RA, which seems to be correctly formatted. Linux hosts are receiving it, and it seems to be correctly formed:

Code: [Select]

#
# radvd configuration generated by radvdump 2.17
# based on Router Advertisement from fe80::f690:eaff:fe00:72c0
# received by interface eth0
#

interface eth0
{
        AdvSendAdvert on;
        # Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump
        AdvManagedFlag on;
        AdvOtherConfigFlag on;
        AdvReachableTime 0;
        AdvRetransTimer 0;
        AdvCurHopLimit 64;
        AdvDefaultLifetime 1800;
        AdvHomeAgentFlag off;
        AdvDefaultPreference medium;
        AdvLinkMTU 1500;
        AdvSourceLLAddress on;

        prefix {ISP ASSIGNED BLOCK}::/64
        {
                AdvValidLifetime 86400;
                AdvPreferredLifetime 14400;
                AdvOnLink on;
                AdvAutonomous off;
                AdvRouterAddr off;
        }; # End of prefix definition


        RDNSS {DNS SERVERS IPv6 ADDRESSES}
        {
                AdvRDNSSLifetime 600;
        }; # End of RDNSS definition


        DNSSL {LOCAL SEARCH DOMAIN}
        {
                AdvDNSSLLifetime 600;
        }; # End of DNSSL definition

}; # End of interface definition
For some reason, as of about 1 day ago, the Windows machines on my network are not processing the RA and adding the OPNsense LAN interface to the IPv6 route table. If I add it manually, they are able to send and receive traffic, but this doesn't seem to work via the RA process, as it does for the Linux and BSD hosts.