I created a bug report for the case mentioned above when renewing in the GUI: https://redmine.pfsense.org/issues/11514

@stephenw10 said in LACP LAGG in Silicom NICs: Completely different NIC type though. Yep, I think I'll wait a bit and test again under 2.5.(?) although, if I read it correctly (somewhere), only "ixl" got a brand new driver under FB12

This turned out to be hardware issue. Had to replace the SSD card. I worked with the freebsd forum. https://forums.freebsd.org/threads/cannot-boot-via-ssd-gptboot-no-boot-loader-on-0-ad-0p2.78994/

I don't recall exactly when, I thought it was in 2.4.x, but we disabled X11 forwarding in the SSH daemon on the firewall for security reasons. The error is harmless though, you can ignore it, or like you've done, disable it on the client side.

To ensure you have all of the current known and fixed IPsec issues corrected, You can install the System Patches package and then create entries for the following commit IDs to apply the fixes: ead6515637a34ce6e170e2d2b0802e4fa1e63a00 #11435 57beb9ad8ca11703778fc483c7cba0f6770657ac #11435 10eb04259fd139c62e08df8de877b71fdd0eedc8 #11442 ded7970ba57a99767e08243103e55d8a58edfc35 #11486 afffe759c4fd19fe6b8311196f4b6d5e288ea4fb #11487 2fe5cc52bd881ed26723a81e0eed848fd505fba6 #11488

ok. I have a 1GB WAN from Comcast. it runs at about 750MB, its never a Gig. anyway, I am in the process of aggregating 2 nic's into my switch from my docs 3.1 modem and 2 WAN ports into pfsense (if thats possible), and added a 2nd virtual and physical nic to the storj node. Now I'm trying to do some traffic shaping to prioritize traffic from the node in both the switch, esxi and pfsense. This is new to me as i said so its going to take me a minute to figure out how to do it. Also, it seems the storj node is working much better already and the satellite online % has increased significantly overnight. I am having loss and lag on the WAN port still between 8% and 22% I have an appointment scheduled for a tech to come out but of course they will say. "everything looks fine..." because unfortunately Comcast field techs get paid poorly and thus are minimally knowledgeable which is a corporate decision and is a bad one to say the least, for both the field techs and the customer but good for the share holders and board members. Right? Anyway, thank you to everyone for the help identifying my issues. So far pfsense and the community has been great! EDIT: I just wanted to say, that so far everything open source and Linux related is just awesome. I have been on several forums, this one is the latest and its just great how everyone helps out and i dunno. its just a great way to do things... Thanks everyone.

After read another topic, I notice that this was the result of pfsense repos changed to the latest branch, 21.02.x (at System/Update/Update Settings). After changing to previous 2.4.5, it happear again.

@stephenw10 They are in tunnel mode. I have not seen then going down before the crash, but will look into it in more detail if this happens again. Thanks

@johnpoz said in Edit File how to save ?: see my edit.. posted pic of where Got that, thx! However it did not fix my issue https://forum.netgate.com/topic/161275/x11-forwarding-request-failed-on-channel-0-after-2-5-0 :(

You're welcome. Always set that if you are not on the latest so the package system doesn't download code for the later version.

@matty-ct said in VoIP issue SIP ALG detected...?: As you suspected, You welcome. Somehow I felt this

Permission denied like that is almost always blocked outbound traffic and there is not much that can do that. But Snort is something that can. Are running it? Steve

@mohkhalifa Couldn't you just use this one ? https://forum.netgate.com/topic/161025/to-2-5-0-or-not-that-is-the-question/69

@cdbrown2018 You will have to find a way to connect pfSense to the wireless network. pfSense itself doesn't support wireless hardware like wifi ac sticks well. But depending on your hardware, you may run for instance a Linux on bare metal and virtualize pfSenes on it. So you can abstract the hardware layer for pfSense.

@gertjan Thank you very much

@shjfliejfasel Now you done it. You forced me to do an archaeological dig through my "Junque" box to find a 9 pin - 9 pin null modem cable, so I could try it with my firewall. BTW, it works.