Re: [pfSense] Outbound NAT rule editing in 2.4
I was literally about to upgrade one of my from 2.3.x installs and do some NAT rule editing. Whew! Thanks for pointing this out. On 10/25/2017 8:00 AM, John Kline wrote: I’m seeing the same thing adding or editing NAT rules (even after upgrading to 2.4.1). - Invalid characters detected fga9b0lcc6mv3&b=3&s=o4. Please remove invalid characters and save again. On Wednesday, October 25, 2017, 1:43 AM, Doug Lytle wrote: On 10/24/2017 10:12 PM, Travis Hansen wrote: After updating to 2.4 I see this when opening all of my outbound NAT rules: - Invalid characters detected "00". Please remove invalid characters and save again. It shows that as soon as I open the rule for editing and also prevents me from updating the rules. Anyone else seeing this? travishansentravisghan...@yahoo.com ___ I see that 2.4.1 is now available, you may want to update and try it again. Doug ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
[pfSense] 2.4.1 IPSec tunnels
I just upgraded from 2.4.0 to 2.4.1. If I view the status of my IPSec tunnels, it seems they have all been duplicated. The original tunnels all show as disconnected, while the second tunnel, which has no description, shows as connected. So all the tunnels still work, it's just that there is new duplicate entry without a description field populated. If I look in the IPSec tunnel settings however, there is only tunnel, the correct one, with the description filed populated. If I hit "connect" on one of the original tunnels, it does nothing, since of course it is already connected via the duplicate, unnamed tunnel. Has anyone else seen this? Any ideas on a way to clean it up? I don't see anything duplicated in the IPSec xml file. ed -- MADSEN, KNEPPERS & ASSOCIATES USA WARNING/CONFIDENTIALITY NOTICE: This message may be confidential and/or privileged. If you are not the intended recipient, please notify the sender immediately then delete it - you should not copy or use it for any purpose or disclose its content to any other person. Internet communications are not secure. You should scan this message and any attachments for viruses. Any unauthorized use or interception of this e-mail is illegal. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] Outbound NAT rule editing in 2.4
I’m seeing the same thing adding or editing NAT rules (even after upgrading to 2.4.1). - Invalid characters detected fga9b0lcc6mv3&b=3&s=o4. Please remove invalid characters and save again. On Wednesday, October 25, 2017, 1:43 AM, Doug Lytle wrote: On 10/24/2017 10:12 PM, Travis Hansen wrote: > After updating to 2.4 I see this when opening all of my outbound NAT rules: > - Invalid characters detected "00". Please remove >invalid characters and save again. > > It shows that as soon as I open the rule for editing and also prevents me > from updating the rules. Anyone else seeing this? > travishansentravisghan...@yahoo.com > ___ > I see that 2.4.1 is now available, you may want to update and try it again. Doug ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] Outbound NAT rule editing in 2.4
On 10/24/2017 10:12 PM, Travis Hansen wrote: After updating to 2.4 I see this when opening all of my outbound NAT rules: - Invalid characters detected "00". Please remove invalid characters and save again. It shows that as soon as I open the rule for editing and also prevents me from updating the rules. Anyone else seeing this? travishansentravisghan...@yahoo.com ___ I see that 2.4.1 is now available, you may want to update and try it again. Doug ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
