Very strange, but it suddenly worked after restarting my machine.
Even more strange, that it correctly showed up in the log.
I had a local route set from my Windows machine to the router, so that I could Wireshark packets (as Windows won't send them through the whole TCP/IP stack if both client and server run on the same interface). Windows deleted the route during the restart, so I assume this was the issue that the harvester didn't properly find the interfaces.
For me it's solved. I only wanted to comment in case somebody comes across the same issue.
From: dev [mailto:firstname.lastname@example.org] On Behalf Of Boris Grozev
Sent: Monday, October 31, 2016 08:06
To: Jitsi Developers <email@example.com>
Subject: Re: [jitsi-dev] Wrong address announced in SDP/Candidates
On 30/10/16 23:55, Oliver Hausler wrote:
Yes, but shouldn't I see the public IP as well?
Jitsi only gathers 4 candidates and these are all for the private IP, so it won't work for external clients.
Yes, you should see candidates with both addresses. Do you see anything related in the bridge's logs?
dev mailing list
Unsubscribe instructions and other list options: