Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Mattps

#1
I know, I deliberately didn't go into details in case someone shouted out something "MTU size". Both VLANs were tagged by the way.

Anyway I've decide  to move this to a physical interface and see how that goes.
#2
Hi,

I have created two vlan interfaces on a physical interface, using the guide. The first VLAN interface I created works really well. However, the second VLAN interface I added is experiencing odd behavior. Traffic is passing through from the LAN side - I can ping/trace route/and open a Google page. But if I try and pull any larger amounts of data - speedcheck, Azure Portal login page, the connections time out (even thought the pings stay constant).

Any suggestions here? Both VLANs have the same (Best, 0) priority settings. I've tried elevating this to but it doesn't make a difference.

Cheers,
Matt


#3
General Discussion / Re: GUI/Shell crashing
November 25, 2025, 12:36:36 PM
Thank you,

I did try the tuneable (point 23) as you suggested previous - as indicated in post #3. Sorry, only just spotted Patrick's reply - this was installed before creating this post.
#4
General Discussion / Re: GUI/Shell crashing
November 25, 2025, 08:37:05 AM
Thanks Meyergru,

I've looked and couldn't find any microcode updates AMD only deliver these for this CPU via bios updates and the bios update for this model is only delivered by HP.

I'm going to put Proxmox on it today and try and run OPNsense as a VM and see if it's stable. The goal here to was to get it running natively on separate hardware from my larger Proxmox servers, so although this would be a compromise, I can live with for now.
#5
General Discussion / Re: GUI/Shell crashing
November 24, 2025, 09:32:15 PM
Microcode updates are applied via a BIOS update, there aren't any separate updates. It's running the lasted BIOS L43 1.16.

I would try the Realtek plugin but this requires to upgrade the opnsense fw first and I can't get the device to stay up long enough.

It's just strange that it seems to die under load.
#6
General Discussion / Re: GUI/Shell crashing
November 24, 2025, 09:00:30 PM
Well, no closer to getting this working. I reimaged the T730 with Windows 11 IoT today and ran non-stop speed tests for 6 hours and it didn't skip a beat. Then I re-imaged with opnsnese and just left the LAN connection in ping a host. This worked for 2.5 hours and stayed up. I then connected the LAN and tried to run a bandwdidth speed test and bang it locks up. I thought it may have been the onboard Realtek nic so changed interfaces to just use the Intel pro/1000 but tis made no difference.
I can't even do an opnsense fw update before it dies, it gets about 10 secs in the locks up.

Could this be a compatibility issues with FreeBSD and an HP T730 think client? I'm sure I read other people using this device with opnsense.

Not sure where to go from here.
#7
General Discussion / Re: GUI/Shell crashing
November 23, 2025, 08:12:20 PM
I believe the microcode update is in the latest BIOS update, which I have installed. I'll have a look at the other posts. Do you think this is an issue with the HP T730 or the PCIe NIC?
#8
General Discussion / Re: GUI/Shell crashing
November 23, 2025, 07:46:26 PM
It stayed up for about 20 mins and then died again unfortunately.
#9
General Discussion / Re: GUI/Shell crashing
November 23, 2025, 06:43:58 PM
Thanks Meyergru, I'll try that. I managed to get the Firmware > Report output before it crashed, I've attached in case that's helpful.
#10
General Discussion / GUI/Shell crashing
November 23, 2025, 06:17:38 PM
Hi Forum,

I need a some troubleshooting an unstable OPNSense installation. I've moved from a virtualised OPNSense instances to running of dedicated hardware:

HP T730 Mini PC 8GB RAM, 64GB NVMe, Intel Pro/1000 ET 82576 Quad NIC

I'm using the latest VGA image with no additional plugins. OPNSense will suddenly lock up, GUI/Shell become unresponsive and the NIC ports link lights stop. Rebooting the PC resolves the issue. Yesterday with just 1 LAN and WAN interface configured it would crash after about 20 mins. I installed Windows 11 IoT over the top, updated the BIOS, ran hardware diagnostics - all passed. With Windows it ran without issue. Confident that it was fixed I reinstalled OPNSense and it seemed to work - ran for over 90 mins without issue.

Today I have configured 3 additional LAN interfaces and the problem is back, except now it will stay on for about 2 mins before dying. Any had any experience of this or where I can check logs to see what is going on?

Thanks in advance,
Matt
#11
General Discussion / Re: Basic firewall rule help
November 01, 2025, 03:10:05 PM
I think I have found the issue. It seems that the interface address mask is defaulting to /32 when I shutdown and restart the OPNSense vm.

I have spun up another instance on a different host and it seems to retain the correct /24 mask. Not sure why this is doing this but I will continue to monitor. For now it appears to be working and I have my isolated network accessing the internet only.

Thanks for your help forum.

Matt
#12
General Discussion / Re: Basic firewall rule help
November 01, 2025, 02:54:22 PM
Quote from: Patrick M. Hausen on November 01, 2025, 02:41:26 PMI block image hosting. Please attach directly to your post. Embedding image hosting URLs is a rude violation of other people's privacy, IMHO.

Hi Patrick,

I don't seem to have the option to attach/embed, only inserting an image or link with a URL.

Kind regards,
Matt
#13
General Discussion / Re: Basic firewall rule help
November 01, 2025, 02:36:19 PM
Hi Patrick,

Apologies not sure what happened then, image posting is always a bit hit and miss here for some reason.

https://ibb.co/RkHV2ShS
#14
General Discussion / Re: Basic firewall rule help
October 31, 2025, 03:23:07 PM
Quote from: Patrick M. Hausen on October 30, 2025, 01:59:22 PMPlease add a screen shot of the rule.

Hi Patrick, sure here is the rule (I have added another interface to block as well (LAN111):



Kind regards,
Matt
#15
General Discussion / Re: Basic firewall rule help
October 30, 2025, 01:41:56 PM
Quote from: Patrick M. Hausen on October 27, 2025, 12:42:48 PMYou need a rule on LAN2:

Source: any
Destination: LAN110 net
Action: deny

and place that before the rule allowing Internet access.

Nope that didn't work I'm afraid, I now I am not able to get to the internet from any interface - I can't even PING the upstream gateway from the diagnostics section.

Can you suggest anything?

That's one way to do it. There are more. ;-)