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 :(
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
@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.
@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.
@jvamos
Don't confuse Bytes (B) with bits (b). Bytes generally refer to an amount of data, such as with disk space, but bits refer to a transmission rate. A byte = 8 bits.
@stephenw10
The strange thing is that i used this kind of configuration on an other host PC, with fewer VMs and this problem did not occur. Then the version of the pfSense was older.
