[Live-devel] why am I getting "bad ports" in groupsock/GroupsockHelper.cpp:setupDatagramSocket()?
Virginia Hamm
liverwurst at owal.io
Mon Sep 26 14:13:34 PDT 2016
In trying to debug something probably unrelated to this, I made this change:
--- a/live/groupsock/GroupsockHelper.cpp
+++ b/live/groupsock/GroupsockHelper.cpp
@@@ -151,7 -151,6 +151,7 @@@ int setupDatagramSocket(UsageEnvironmen
ntohs(port.num()));
socketErr(env, tmpBuffer);
closeSocket(newSocket);
+ env << "Bad port number (@1): " << port.num() << "\n";
return -1;
}
#if defined(__WIN32__) || defined(_WIN32)
Now, whenever a client connects to the proxy, I get errors such as:
Bad port number (@1): 14875
Bad port number (@1): 15131
These two port numbers show up frequently one after the other; where are
theycoming from? For that matter, what is the purpose of that entire
multicast codepath? There are far better ways of deciding what the outgoing
IP address should be.
\/-/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20160926/7f725cc8/attachment.html>
More information about the live-devel
mailing list