You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there! Thanks for creating broadcast-box -- it's immediately solved an issue I've been stuck on for months and I am elated!
It seems I've found a bug though with how UDP_MUX_PORT applies.
With srflx set, the ANSWER includes the LAN IP, WAN IP (and a second WAN IP?). In that case, only the LAN IP answers with the UDP_MUX_PORT; the two WAN IPs include randomised UDP ports.
Without srflx set, the ANSWER includes the WAN IP twice -- where the first WAN IP is listening on the UDP_MUX_PORT set in .env.production.
(I'm using 111.222.3.444 as a placeholder for my home public IP)
Hi there! Thanks for creating broadcast-box -- it's immediately solved an issue I've been stuck on for months and I am elated!
It seems I've found a bug though with how
UDP_MUX_PORT
applies.With
srflx
set, theANSWER
includes the LAN IP, WAN IP (and a second WAN IP?). In that case, only the LAN IP answers with theUDP_MUX_PORT
; the two WAN IPs include randomised UDP ports.Without
srflx
set, theANSWER
includes the WAN IP twice -- where the first WAN IP is listening on theUDP_MUX_PORT
set in.env.production
.(I'm using
111.222.3.444
as a placeholder for my home public IP).env.production
ANSWER
withNAT_ICE_CANDIDATE_TYPE=srflx
setANSWER
withoutNAT_ICE_CANDIDATE_TYPE=srflx
setThe text was updated successfully, but these errors were encountered: