Ring and Eufy client behind pfSense
-
It should be passed by the existing state on WLAN. The fact it isn't implies something else is happening. Like maybe a state conflict.
-
@stephenw10 said in Ring and Eufy client behind pfSense:
It should be passed by the existing state on WLAN
Exactly - what rules on your wan mean nothing once there is a state.. The state would allow the return traffic..
-
@johnpoz Ok, extremely strange, I can see in the state table that the udp for the stun session is there, but it's definitely not appearing in an unfiltered trace of the WLAN interface on pfSense?
-
@brtech where is the state on the wan, where that was natted, you should also see that.. do all interfaces and filter on the clients IP.
example
edit: where is sniff on wan showing the response from the stun sent.. Many they are not being responded too?
-
@brtech So I got your email - what specific patch did you apply, and did you have captive portal enabled?
-
@johnpoz #12834 was the patch, yes captive portal was enabled for the guest WLAN, obviously a critical piece of info but didn't seem relevant at the time!
-
@brtech Ok its seems captive portal was enabled on this interface..
Seems this patch was applied and now working
-
@brtech said in Ring and Eufy client behind pfSense:
obviously a critical piece of info but didn't seem relevant at the time!
Yeah - that is always the issue, critical piece of the puzzle missing to complete the puzzle.
edit: note to self when asking for info, ask if captive portal is in use.. not just what packages like ips or pfblocker, etc. etc. .
-
Nice, the patch corrected it?
-
@stephenw10 Yes, all working perfectly now.
-
This post is deleted! -
S stephenw10 locked this topic on
