Hi Andreas,
Thanks for your reply.
I checked address range of my environment, but my env did not have 169.254/16
in ICE candidates.
I tested this issue again. Then, I found that behavior got different after FF58.
With 57.0.4 (64 bit), it worked well with TURN since remote-candidates of Janus
Admin log included ``relay`` candidates as follows,
```
"local-candidates": [
"1 1 udp 2013266431 10.0.2.15 52855 typ host",
"2 1 udp 167772671 52.41.145.197 59022 typ relay raddr
10.0.2.15 rport 0",
"3 1 udp 1677722111 165.254.239.194 24786 typ srflx
raddr 10.0.2.15 rport 52855"
],
"remote-candidates": [
"0 1 UDP 2122187007 10.49.52.222 64179 typ host",
"4 1 UDP 2122252543
2001:418:149f:1052:9d6d:7332:3369:7126 64180 typ host",
"9 1 UDP 8265727 52.41.145.197 50133 typ relay raddr
52.41.145.197 rport 50133",
"1 1 UDP 1685987327 165.254.239.194 17963 typ srflx
raddr 10.49.52.222 rport 64179"
],
```
But 58.0b14 (64-bit) and 59.0a1 (2018-01-08) (64 bit), it failed with skipping
``relay`` candidate from remote-candidates.
```
"local-candidates": [
"1 1 udp 2013266431 10.0.2.15 54551 typ host",
"2 1 udp 167772671 52.41.145.197 54316 typ relay raddr
10.0.2.15 rport 0",
"3 1 udp 1677722111 165.254.239.194 21385 typ srflx
raddr 10.0.2.15 rport 54551"
],
"remote-candidates": [
"0 1 UDP 2122252543 10.49.52.222 56774 typ host",
"4 1 UDP 2122187007
2001:418:149f:1052:9d6d:7332:3369:7126 54378 typ host",
"1 1 UDP 1686052863 165.254.239.194 15475 typ srflx
raddr 10.49.52.222 rport 56774"
],
```
Also, I saw "Skipping TURN server because of link local mis-match" in
about:webrtc.
2018年1月5日金曜日 5時36分43秒 UTC-8 Andreas Pehrson:
> Hi Kensaku,
>
> Looking at our code, the error originates at one of the two checks in [1].
>
> "link local" seems to refer to an address in the 169.254/16 range. There's
> a similar check for ipv6. Does your server sit in this range?
>
> We also raise the same error in case of a mismatch between your local
> interface's and the turn server's ip address version (4 vs 6).
>
> I suppose there is a chance of false positives during enumeration of all
> interfaces re the version check. Does the server show up in the table on
> about:webrtc?
>
>
>
> Best regards,
>
> Andreas
>
>
> [1]
> https://searchfox.org/mozilla-central/source/media/mtransport/third_party/nICEr/src/net/transport_addr.c#488-497
>
> On Fri, Jan 5, 2018 at 2:45 AM, <[email protected]> wrote:
>
> > Hi,
> >
> > I am trying to make webrtc connection between Janus in vagrant and FF (=<
> > 57) on host machine. But it make an ice failed error (Chrome works fine).
> >
> > As mentioned by Lorenzo in another topic, https://groups.google.com/
> > forum/#!topic/mozilla.dev.media/rQUhtfBNRgU, I guess it is because of ICE
> > state machine behavior difference or so.
> >
> > Then, I also tested with my custom TURN server. But FF still made an error
> > as "ICE failed, your TURN server appears to be broken, see about:webrtc for
> > more details". And, I found error message in ``about:webrtc`` as
> >
> > "Skipping TURN server because of link local mis-match"
> >
> > So, what condition does above error message happen? In other words, what
> > does 'local mis-match' mean?
> >
> > --- Kensaku Komatsu
> > _______________________________________________
> > dev-media mailing list
> > [email protected]
> > https://lists.mozilla.org/listinfo/dev-media
> >
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
