If you only use 2 or 3 interfaces this should be fine. For more you need to deal with VLANs first because LAN 1-4 is switched on the SG-3100

-Rico

@bmeeks said in Installtion on a laptop with Ethernet and USB:

SG-1100

Yes, looks like a better option. Thanks

@rks I am not sure what you're doing when I see that extraction on the screen. I can tell you that, having installed both pfSense 2.4.4 and 2.5 on a 2011 Mac Mini server, it is possible. You should download the pfSense for flash drive, then get balenaEtcher for Mac and use that to flash the pfSense onto your jump drive ... you'll find that easy than trying to use Terminal which creates issues.

Once you have your jump drive with pfSense, connect it to your Mac Mini and boot it by holding down the option key while you're startup ... it will take a few minutes to boot fully. Once the installer appears, you can let the installer do the work; for example, format the hard-drive and install pfSense. Those thunderbolt adapter uses Broadcom NIC ... I ended up getting a used thunderbolt PCI enclosure and put in an Intel i350 NIC for IDS/IPS.

@moelharrak said in PPPoE Goes Down Frequenctly:

what to do

Use another non-Realtek NIC or try another driver.

-Rico

The team create rules, to Tenable access and execute scanning.

But the "external Scan" follow architecture of banking.
Not is open for world, is segmented.

The Team have fear the application PFSense not work e lost access to server.

@jimp

Thank you, i will work on option #2

@fnarq

Check if you run block bogons on the interfaces when filter reloads. uncheck them.

It destroys the box completely....

That ^.

What are you installing on? Exactly what image are you using?

Steve

A wise decision. ☺

I just wanted to post my resolution to the issue I was having here. It turns out the Quagga_OSPF package was missing and that was causing the routing problems. I was finally able to figure this out due to another firewall failing and having to replace it. Going through that troubleshooting led me to realize the missing package was the root of all the problems. Hopefully this helps someone else who may have a similar issue.

Ok, so after troubleshooting and not finding it, I've caved and purchased an Intel X520-DA2 SFP+ card.
Installed it, booted up and worked immediately after assigning it to the LAG.

So for future readers, abandon hope and purchase Intel NICs...

PS: If one should ask it works out-of-the-box without a LAG as well.
PPS: If someone would ever find the solution, always welcome to share.

No idea. But doubtful. If the docker-hypervisor relationship is completely ignorant of the guest OS then maybe, but I wouldn't hold my breath.

@Gertjan

Thus : for the moment : both should have a minimal static IP setup. Just IP and mask, DNS and gateway are not relevant.

Good point, but I would expect that having a gateway listed in your network config doesn't hurt even though you don't need it.

As soon as you have access :
set :

Indeed, I have changed all remaining devices to DHCP now and will avoid fixed IP's as much as possible. Had some Wifi AP's with fixed IP's, but there's no real need for that. It's very easy to have the FRITZ!Box always assign the same IP address to devices. I noticed that it's a bit more complicated with pfSense, but also quite straightforward.

Btw : if you used one of those "how do I protect my Syno NAS" video's on Youtube, it's time to remember that. For example : auto lock out after x login failures ? ;)

Didn't look at those yet, I just wanted to have a separate network for IoT devices. Next to that I also want to have more monitoring capabilities, so Snort is high on my wish list.

What is that ? The thing that came with Syno on a CD ?

Indeed. I forgot all about that utility until I couldn't access my Synology anymore. Should not be necessary anymore, since I will only use DHCP from now on :-).

pfSense 2.4.5 Release notes and at Netgate.

@dotsch said in Panic + hung after 2.5 upgrade:

The system ran about 10 days without any issues after the upgrade.

Aha !
That closes in on a hardware failure.
Swap out the SD.