Activity
From 03/18/2021 to 04/16/2021
04/16/2021
-
03:42 PM Bug #11807 (Rejected): HA setup restarts all OpenVPN instances on the secondary after making any change on the primary
- This patch was applied to both pfSense Plus and CE. If you believe there is a regression or the issue is not fully fi...
-
10:18 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- DRago_Angel [InV@DER] wrote:
> Updated to 21.02.2-RELEASE and NPt still not works on non-primary WAN so issue resolv... -
04:18 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- Updated to 21.02.2-RELEASE and NPt still not works on non-primary WAN so issue resolved not fully.
04/15/2021
-
10:37 AM Bug #11807 (Rejected): HA setup restarts all OpenVPN instances on the secondary after making any change on the primary
- This Plus project does not contemplate the issue reported in:
https://redmine.pfsense.org/issues/11082
We simpl...
04/14/2021
-
07:36 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- Some reports that this is happening on CE now, but not Plus. See #11805
Keeping this one closed since it was speci...
04/08/2021
-
05:49 PM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- Working fine for me now after update to 21.02.2.r.20210406.1302
Now once again able to connect to the network from t... -
07:21 AM Bug #11466: PHP exits with signal 11 on SG-3100 when calling PCRE functions
- Bill Meeks wrote:
> One of the issues identified in this ticket, the logging of "blank" interface names and the disp...
04/07/2021
-
08:03 AM Regression #11436 (Resolved): State matching problem with reponses to packets arriving on non-default WANs
-
05:10 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- @Rick Strangman
> Updated by Renato Botelho 1 day ago
>...
>Fix was pushed to FreeBSD and cherry-picked to FreeBSD... -
05:07 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- I can confirm the issue has been resolved. Explanation please.
04/06/2021
-
05:30 PM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- I tested it on RC update channel
currently running 21.02.2.r.20210406.1302
and port forward works as expected. on b... -
05:24 PM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- So is this build different that what shows up in System->Updates?
-
05:17 PM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- to be more precise tested on build 21.02.2.r.20210405.1121
on booth wans port forward works now as expected.
Good... -
05:05 PM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- Renato Botelho wrote:
> Fix was pushed to FreeBSD and cherry-picked to FreeBSD-src on commit 4fd4e2b70189
works o...
04/05/2021
-
01:31 PM Regression #11436 (Feedback): State matching problem with reponses to packets arriving on non-default WANs
- Fix was pushed to FreeBSD and cherry-picked to FreeBSD-src on commit 4fd4e2b70189
04/04/2021
04/03/2021
-
06:16 PM Feature #10804: Interface Status page information for switch uplinks may be replaced by switch port data when media state monitoring is set
- Status>Interfaces shows tagged ports
Netgate XG-7100
21.02.2-RC (amd64)
built on Sat Apr 03 03:04:06 EDT 2021... -
07:24 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- I've reproduced the issue, and believe I have a fix.
I'm still trying to work out why it didn't happen on CE though.
04/02/2021
-
11:57 AM Bug #11466: PHP exits with signal 11 on SG-3100 when calling PCRE functions
- One of the issues identified in this ticket, the logging of "blank" interface names and the display of "Unknown" as t...
04/01/2021
-
04:26 PM Feature #11772: Layer 2 Tunnel Bonding Capability
- Bonus points on this one: A "wizard" which can be run on the "central office" end PF to create the configuration for...
-
04:22 PM Feature #11772 (New): Layer 2 Tunnel Bonding Capability
- Ability to tunnel traffic over multiple WAN connections back to another PF appliance at a central location in order t...
-
11:28 AM Bug #11770 (New): Pantech UML295 USB Modem No Longer Functional
- The Pantech UML295 modem in the USB port is caused pfSense to hang on reboot when upgrading to version 21.02 of the s...
03/31/2021
-
12:47 PM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- I am trying to reproduce with CE my scenario in a virtual environment and was having issues, good to know it doesn't ...
03/30/2021
-
05:10 PM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- I can confirm that it does not occur in CE v5.0. I had the config operational before I migrated to Netgate x7100 with...
-
04:10 PM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- Jordan Bradley wrote:
> I'm using community edition and this bug is affecting me.
Based on your description above... -
04:08 PM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- I'm using community edition and this bug is affecting me.
-
04:00 PM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- A few notes:
* This only appears to affect pfSense Plus, not CE, which explains why some people cannot reproduce t...
03/29/2021
-
10:12 AM Bug #11726 (Rejected): Network traffic stops with latest RC build.
- Unable to reproduce and not enough information to determine if there is a bug, or anything which can be done.
If y... -
03:16 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- Rick Strangman wrote:
> I attach a pfsense packet capture on the LAN side from the bad WAN2. You can see that the in...
03/28/2021
-
02:41 AM Bug #11741 (Closed): VLAN 1 description displays as "Default System VLANDefault System VLAN"
- internal issue NG 5952 created
-
12:23 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- I believe I'm also encountering this issue, at least a google for "pfsense rdr not working after upgrade" brought me ...
03/27/2021
-
11:30 PM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- I attach a pfsense packet capture on the LAN side from the bad WAN2. You can see that the initial SMTP request comes ...
-
04:28 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- Just wanted to add that this issue also impact IPv6 NPt with multiwan, please check this as well when fix will be at ...
-
03:33 PM Bug #11726: Network traffic stops with latest RC build.
- This may be a dup of ticket 11540.
-
11:42 AM Bug #11741: VLAN 1 description displays as "Default System VLANDefault System VLAN"
- Screenshot didn't make it. Here
!https://dsc.cloud/b854da/pb-A0SwdJGmBR/pb-A0SwdJGmBR.png! -
11:37 AM Bug #11741 (Closed): VLAN 1 description displays as "Default System VLANDefault System VLAN"
- In the GUI, the description for the default VLAN is printed twice:
!https://cln.sh/dd93kN!
I made a simple fix ...
03/26/2021
-
11:23 AM Feature #11732 (New): Add VXLAN Support to pfSense Plus
- VXLAN Support would be useful for scalable cloud deployments of pfSense Plus
03/25/2021
-
09:19 PM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- The issue is:
1. 2 x WAN, WAN1 & WAN 2, both DHCP
2. WAN1 set as default gateway
3. Both WANs have identical NAT r... -
08:10 PM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- Kris Phillips wrote:
> Testing with the following on amd64:
>
> 1. Created Port Forward from WAN address to inter... -
07:08 PM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- Kris,
I can reliably reproduce this bug on my systems. We are running 2 C2758s in a MultiWAN / HA config. We set... -
05:11 PM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- My setup is that I'm trying to do port forwarding on an openvpn client interface in order to forward a reserved port ...
-
05:01 PM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- Testing with the following on amd64:
1. Created Port Forward from WAN address to internal and WAN2 set as default ...
03/24/2021
-
09:17 PM Bug #11726 (Rejected): Network traffic stops with latest RC build.
- After updating to the RC build 21.02.2.r.20210324.0300 network traffic ceased. No NAT traffic was passing, each inter...
-
01:59 PM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- Svein Wisnaes wrote:
> Grzegorz Krzystek wrote:
> > last known working version is 2.4.5p1
> >
> > No ETA on this... -
07:32 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- Grzegorz Krzystek wrote:
> last known working version is 2.4.5p1
>
> No ETA on this, nor known workaround yet.
...
03/23/2021
-
11:15 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- I can concur that with 2 Wan Interfaces (different subnet in our case), with DMZ and LAN networks that traffic coming...
-
09:57 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- Thanks for that.
The only progress I can report so far is that this demonstrates that the initial SYN arrives and ... -
08:38 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- last known working version is 2.4.5p1
No ETA on this, nor known workaround yet.
-
08:34 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- Netgate XG-1537
21.02-RELEASE-p1 (amd64)
built on Mon Feb 22 09:39:51 EST 2021
FreeBSD 12.2-STABLE
2 x WAN wi... -
07:49 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- please check your mailbox ;)
-
07:44 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- Yes, that's the setup I have, and I'm unable to reproduce the problem. The port forwarding just work on both WAN and ...
-
05:44 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- What is funny is it need to be related with routing.
reflection nat works. this is impacting only when connection ca... -
05:33 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- Kristof Provost wrote:
> With a PPPoE setup I still can't reproduce the problem. Along with the latest report that's... -
05:22 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- With a PPPoE setup I still can't reproduce the problem. Along with the latest report that's fairly strong evidence th...
03/22/2021
-
04:43 PM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- I am not using PPPOE. Both WANs are DHCP. My config attached.
-
11:45 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- Thanks. I've not immediately spotted anything suspect in there.
However, it appears that all reports of this issue... -
08:48 AM Regression #11436: State matching problem with reponses to packets arriving on non-default WANs
- I've so far been unable to reproduce this problem.
It's possible that I'm missing some relevant factor in my setup. ... -
09:58 AM Regression #11689 (Resolved): LEDs do not indicate available upgrade status
- Confirmed working on latest snapshot
03/20/2021
-
09:18 PM Bug #11630: WireGuard MultiWAN Not Failing Back to Tier 1
- Since Wireguard is being removed from the next release, this bug report should be closed out as Rejected.
-
09:14 PM Bug #11673: Thermal Sensors Non-functional on SG-3100
- Important to note that this seemed to work fine in the 2.4.5p1 images. Its just the newer release that has issues.
Also available in: Atom