There are zero legal problems with what you're doing now, the objections from the seasoned users here are only practical in nature. It is counterproductive to produce yet another set of documentation that is going to be riddled with errors and inconsistencies and will lag behind the existing better quality official documentation.

No probably not. The overhead from running virtual should not be that large if the hypervisor is setup correctly. And on your hardware you shouldn't be getting even close to any limit at 180Mbps. Assuming you meant bps. Steve

It is only 5 devices :D

As impossible as it should be, I've seen 2 NICs with the same MAC. While supposedly unique, some manufactures have been known to recycle MAC addresses.  There's also the possibility of locally assigned MACs and many consumer routers can clone a MAC.  However, as long as they're not on the same local network, duplicate MACs are not a problem.

Though, for the home user, the time spent installing, configuring, tuning, and maintaining snort would probably be better spent educating the family on what not to do. That will benefit them for life on every network they encounter.

Thanks everyone this now works  :) :) :)

http://forums.kali.org/

:) :) :) :) :) :) Huraaah it works, many thanks Rafi

At the bottom of the link KOM mentioned :- Status -> System Logs -> Settings Remote Logging Options

OpenVPN? It will always allow the ping traffic out. More likely is that whatever is at the other end stopped responding to ping or you moved to a different gateway that doesn't respond. Or maybe it triggered something that blocked pings! If you set the gateway monitor to an alternative IP accessible over the VPN that should give you back link stats. Steve

@stratus: I made the following adjustment yesterday: Routing -> Edit Gateway Probe Interval: 3 Down: 60 I dont know if it is just a fluke or not, but I did not register any outages last night. I will continue to monitor and update this post as I discover things This worked for me.  Made an account just to thank you for it.  Had been troubleshooting it for 2 days.

Well, for a start I now have an AES-NI mini-pc with pfsense running as main router. :)

There are still some processes in pfSense that are thread-locked or do not scale well across cores and those benefit from faster CPU speed. If you run a number if things though, VPN, snort, squid etc, those can use separate cores so you would some benefit there. The sweet spot there depends what you're running but 4 fast cores is pretty good for a default setup. Steve

Probably not. It depends exactly what that box is doing though. For example pfSense can do ML-PPP itself: https://doc.pfsense.org/index.php/Multi-Link_PPP_(MP/MLPPP) Steve

By lying and increasing my subnet size from /29 to /24 on the LAN2 I have avoided duplicate interface addresses on LAN2 and WAN2. At least traffic is now flowing…

@Gertjan: This is the key word : Cannot allocate memory Also check drive space and disk allocations. If needed, stop en remove the "memory eaters" (packages - and I'm not talking about the cron - or note package here  ;)) Hi Gertjan, that's not a Problem of mine. The Server has a CPU Load from 3-4 Percent and a low Mem usage. I found out that the Message and the Problem happen, if a Gateway has Packetloss and it's marked as down. Than the Error is generated. Also if the GW is coming up again. I think this is a bug that has been checked. As workaround i disabled the gateway-check. Than nothing error happen.

Hi, Probably freebsd kernel hints file. See what dmesg has to say.