Captive portal + WebRTC Discord
-
Describe your portal settings, interface settings and portal interface firewall rules.
You've kept the DNS settings on their default settings ? Or did you modify DNS ?
Discord : what doesn't work ? What device gave the error, doing what ?
If you de activate the portal, the issue goes away ?
edit : pfSense 2.7.0 ?
You've installed his package :
and 'activated' the available patches.
( I'm not sure if there are any "portal" patches right now, but having the patches active is always a good thing )
-
yes, I deactivate the captive portal and it works normally!
Basically, I have my network with around 20 users performing authentication!
Dns, I don't resolve it through PFSENSE, I have a server for that. However, Forwarde is activated on port 53.
all devices that need to go through the CAPTIVE PORTAL, discord doesn't work! Turning off the captive portal (deactivating) DISCORD works normally.
The settings are basic, the IPS of the servers are overlooked, the only thing we changed was the company logo.
-
pfSense 2.7.0 ?
Discord offer many services. You can't access the site / web server ? Something else ?
-
@Gertjan I can't get on a call with my team on the local network (where the captive portal is).
I can access everything except DISCORD! -
Like this : Captive portal blocking WEBRTC ?
That issue existed for pfSense 2.6.0. There is a patch for 2.6.0 that solves it.
pfSense 2.7.0, AFAIK, doesn't have that issue. -
@Gertjan Which patch makes this fix? My pfsense is on version 2.6.0!
-
@Gertjan Remembering that I cannot update pfsense to version 2.7.0, because it will complicate my system.
-
@wendel_gt said in Captive portal + WebRTC Discord:
My pfsense is on version 2.6.0!
Ok, thanks.
Now I understand your problem.
2.6.0 had a huge problem : the captive portal only passes TCP, no ICMP, no UDP.
That was quickly resolved, as the pfSense system patch package was introduced :
This package has patches that you can activate (apply).
One of them was : repairing the captive portal so it passes UDP .....Note : UDP is often used for "voice traffic".
@wendel_gt said in Captive portal + WebRTC Discord:
Remembering that I cannot update pfsense to version 2.7.0, because it will complicate my system.
Why ?
2.7.0 has not the issue, and is now the "latest and greatest".
I know the captive portal works on 2.7.0.What do you mean with "complicate" ?
Don't you think your current 2.6.0 isn't already complicated for you ?
-
@Gertjan Well, install and apply! Is it now necessary to restart the system? I tested it on Discord, but the same error still persists!
-
Reboot ?
Probably not needed.
Logout all connected users, and have them reconnect (?). -
@Gertjan I disconnected and reconnected, but without success! Any other options?
-
@Gertjan To update! I restarted the system and it worked. Thanks for all the support.
