@pmk_mck take the case off and let it run with a fan blowing on it, i mean..if you're blowing air in the dust is there anyways. Just dont want to electrocute or short anything during the test. I can do the same if you want to know the result.

The fan itself is standard 4 wire as far as I know so that should work if it will fit.

The actual required cooling is minimal so as long as it can be attached in some way you should have no problems.

Steve

Not really. I would say this is some WAN side connection issue except you can see much higher speeds when connecting from the device itself.

Please open a ticket with us so we can review the config and connection status: https://go.netgate.com/

Steve

You can open a ticket with is about that: https://go.netgate.com/
It is almost certainly outside any warranty though.

As far as I know running from m.2 SSD should be make that any more or less likely.

Steve

Thanks bmeeks. I need to do your second suggestion.

Open a ticket with the Netgate support: https://go.netgate.com/

-Rico

Well theres my problem...
I was caught up in configuring the port itself I forgot to add the port to the vlan group!

Communication is now working.

As always, thank you for the help!

port6:
pvid: 130
state=8<FORWARDING>
flags=0<>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
laggroup0:
members 9,10
vlangroup1:
vlan: 130
members 7,8,9t,10t

This sounds like a "Buyer Beware" warning to me. Yes, it did say on the web store page "INCLUDED USB KEY WITH PFSENSE CE 2.4.4" but one would need to be very knowledgeable about the Netgate product family to know the differences between a "factory" version of pfSense and the CE version and that additional packages came with the factory version.

Hi John,

Thanks for your reply. I only really need it primarily as a DNS black hole which it works well with as well as redundancy for 4G failover and a secondary network for guest access. I thought I'd messed up and couldn't stop NtopNG permanently from the dashboard but got that sorted.

Not really interested in traffic monitoring at the moment but it's useful to know it's there should I need it.

Thanks again!

Best regards,

Richard

My Inet got 1000/50 to, but with limiter (codel) and no negativ ping issue, i got 600-700MBit off it.

If i drop the Limiter, i got round 800MBit but no cpu Limit reached at any time.

Cabel connections are shared and if you go for max speed you depend on the segement load. If this is to high, your ping go up in the sky.

@johnpoz
Thank you. This was so obvious but because I was only looking for DHCP server V6 I did not see it listed with a slight difference as it had something else. Thanks, it worked and I am happily using my new subnet.

No problem. Let us know if you have any problems restoring that.

Steve

Maybe your rules aren't loading?

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

@ckcoder Thank you, two used cables gave me the same error which left me frustrated, and your reply drove me to open a package with a new cable which worked.

So, I turned on DHCP and low and behold, that worked. So I went back and put a static in and now that works. Rebooted a couple times to make sure it stayed working and it did.

Have no idea what was hung. But thanks for verifying I had everything above correct. Hopefully someone else can use it for configuring it themselves. The documentation out there is good, but not great for a more top to bottom of the type I needed...

Anyway, thanks for the help....

On Netgate's advice I rebooted the device and the CPU usage dropped back to less than 10% The only thing I can think of is that I leave the bandwidth monitor up all the time and that somehow created rogue processes. I guess I will not do that now.

I also updated the software to the latest version (2.4.5-RELEASE-p1) from 2.4.4p3 but I don't think that was the issue.

Thanks for everyone's help.

I think I figured it out.

Using VLAN probably is the best way to do it.
Only thing is that the firewall makes it confusing with the 4090 and 4091.

You can certainly try that.

Installing clean is a relatively quick and easy process if you have access to the serial console. I would probably go straight to that to be sure.

https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/connect-to-console.html

Steve

@Rico - Thanks for all your help and the link Rico!

Regards, Roy...