-
Notifications
You must be signed in to change notification settings - Fork 944
Open
Labels
Description
I use Frigate 0.17-Beta2 (native go2rtc 1.9.10) and had #1890 issue.
Successfully updated to 1.9.14 via standard Frigate process https://docs-dev.frigate.video/configuration/advanced/#custom-go2rtc-version without any issues. For external access I would like to try IPv6 ( 0 nat, I have working stack end-2-end) and my Frigate has routable IPv6 address.
When do
webrtc:
listen: ":8555" #:8555 #192.168.50.154:8555 Using :8555 usually binds to both IPv4 (0.0.0.0) and IPv6 ([::]) if available.
filters:
network: [udp4, tcp4, udp6, tcp6] # Ensure all are enabled
#candidates:
# - 192.168.50.154:8555 # Internal IPv4
# - "[2001:9b1:4296:d700::5]:8555" # Direct IPv6
I get
root@nanopc:/opt# docker exec frigate lsof -iUDP -P -n | grep go2rtc
go2rtc 128 root 8u IPv4 21837513 0t0 UDP 192.168.50.154:8555
go2rtc 128 root 9u IPv4 21837519 0t0 UDP 192.168.50.154:5353
go2rtc 128 root 10u IPv4 21837520 0t0 UDP *:5353
root@nanopc:/opt# docker exec frigate lsof -iTCP -P -n | grep go2rtc
go2rtc 128 root 5u IPv6 21838439 0t0 TCP *:8554 (LISTEN)
go2rtc 128 root 6u IPv6 21839462 0t0 TCP *:1984 (LISTEN)
go2rtc 128 root 7u IPv6 21837510 0t0 TCP *:8555 (LISTEN)
go2rtc 128 root 11u IPv6 21837735 0t0 TCP 127.0.0.1:8554->127.0.0.1:53272 (ESTABLISHED)
go2rtc 128 root 12u IPv6 21843079 0t0 TCP 127.0.0.1:8554->127.0.0.1:53282 (ESTABLISHED)
go2rtc 128 root 13u IPv6 21842378 0t0 TCP 127.0.0.1:8554->127.0.0.1:53288 (ESTABLISHED)
go2rtc 128 root 15u IPv6 21841712 0t0 TCP 127.0.0.1:8554->127.0.0.1:53290 (ESTABLISHED)
go2rtc 128 root 17u IPv6 21882591 0t0 TCP 192.168.50.154:1984->192.168.50.3:49200 (ESTABLISHED)
So UDP is v4 and TCP is v6. Why? Am I missing anything?
Reactions are currently unavailable