Still no info on the "hang" problem, but I'm betting on the issue where you need to disable SMP in the BIOS for install and then reenable it later.  That seems to hit a decent number of Dell servers.

No problem mate :) Glad to help because this community helped me a lot :)

@denask: Any security gains are from having additional devices on a separate subnet anyway, I guess. If you have two interfaces bridged into one subnet you can still apply firewall rules at those interfaces to filter traffic to some extent. So there some security gains if you need them. I would also just attach it to the switch though unless you really need filtering. Steve

Thank you !!

@marcelloc: sip phones are on lan too? If so try to configure a heartbit on your sip servers. Depends on what kind of SIP servers he has on the network. Not all have heartbeat feature. I recommend using DNS server for load balancing. Use round robin feature.. you can add both SIP servers in DNS and the request goes in a round robin fashion. You can have multiple SIP servers in load balancing this way.

Errors are gone now, transfer speeds up to: 70 Mbytes/s. PCIe ASPM was to blame, hope it helps some one :) Thanks stephenw10, I really appreciate it!

I suspect this is fixed by this commit from jimp a couple of hours ago: https://github.com/pfsense/pfsense/commit/c1e48e9b40cb08884a6b4848ef95ec27b6311549

thanks, now it works

It's not quite the same as accessing a modem where the PPPoE interface doesn't use the actual ethernet interface. In this case the interface connecting to the ubnt device is already in use so a virtual IP must be used. Steve

@NOYB: I think the difference between the two ways that would be most likely to impact would be the NAT/Firewall settings I use to restrict WoL begin accepted from only a few static source IP addresses.  Guessing your mobile device wouldn't have a static IP address.  So the NAT/Firewall rule would have to accept any, or at least a much larger range, of IP addresses.  But I think your NAT/Firewall rule already allows any address to accommodate the mobile device.  Both ways should work with mobile device so long as the NAT/Firewall is configured to accommodate it. It makes sense. I will start to monitor my cell phone IP just to see if its going to change. Thank you!

Thanks for giving me some interesting things to think about and to look at. I will tinker around a bit, never considered looking at power settings because all cores showed 50c. Which now that i think about it is prob on the low side for 100%.

No problem - Just a lucky guess.

Not so far, there is another topic on this where the poster is going to look into making the changes needed. You might be interested in assisting them or even doing it yourself if they aren't going to be able to do it. https://forum.pfsense.org/index.php/topic,66985.msg366187.html#msg366187

The keyboard-interactive method is more secure flexible, but not all SSH servers support it or have it enabled. It allows for things like multiple prompts to implement multi-factor auth and so on.

Not that I'm aware of. HAproxy can do it by a cookie or session ID of some sort, which is probably the most flexible.

I delete the vlan in confg.xml and save it. Then i just created the vlan again and everything seems to be ok now.

I would say that you don't need VLANs. You already have several spare ports that you bridged together so the only other reason you might want them is to segregate sections of your network that span switches, you haven't mentioned anything like that. If you need (or want  ;)) a managed switch then define what features you need on it. The low end HP switches always get a good write up here as do the Netgear managed switches, the GS108T for example. Steve