Questions and Answers :
Macintosh :
Open port 31416
Message board moderation
Author | Message |
---|---|
Rodney Send message Joined: 6 Sep 06 Posts: 1 Credit: 3,270 RAC: 0 |
Why does Boinc constantly beg to open port 31416 on my computer? I have a firewall and that port is closed. |
Odysseus Send message Joined: 26 Jul 99 Posts: 1808 Credit: 6,701,347 RAC: 6 |
Why does Boinc constantly beg to open port 31416 on my computer? I have a firewall and that port is closed. I’m not sureâ€â€don’t know much about networkingâ€â€but I believe the BOINC GUI and core client communicate with each other using TCP/IP. The related “network traffic†doesn’t actually go outside the system unless the Manager on one host is being used to control others over a network. |
mr.kjellen Send message Joined: 4 Jan 01 Posts: 195 Credit: 71,324,196 RAC: 0 |
That is the default port for remote managing boinc via gui_rpc. The boinc client is constantly listening on that port. On a windows install it can be port 1043 as well. If you have windows machines in your network you can install boincview and control all your machines from there. /Anton |
WillL Send message Joined: 9 Oct 02 Posts: 6 Credit: 19,862 RAC: 0 |
That is the default port for remote managing boinc via gui_rpc. The boinc client is constantly listening on that port. On a windows install it can be port 1043 as well. What if I don't want to control the boinc client from another machine. How do I shutdown the port and still use boinc? Regards, Bill |
Jeffrey Send message Joined: 21 Nov 03 Posts: 4793 Credit: 26,029 RAC: 0 |
How do I shutdown the port and still use boinc? Apparently, Boinc Manager is talking to the boinc client... If you execute boinc from the command line shown below you won't get the continual localhost connections... You can still use Boinc Manager to manage the project because Boinc Manager will simply connect and disconnect from the already running client... ;) /Applications/BOINCManager.app/Contents/resources/boinc -redirectio -dir /Library/Application\\ Support/BOINC\\ Data/ & It may not be 1984 but George Orwell sure did see the future . . . |
WillL Send message Joined: 9 Oct 02 Posts: 6 Credit: 19,862 RAC: 0 |
/Applications/BOINCManager.app/Contents/resources/boinc -redirectio -dir /Library/Application\\ Support/BOINC\\ Data/ &[/quote] I am not a UNIX person. What does this do. Does it close the port. Or do I need to worry about the port. From other readings it seems that this port is a local port, similar to the printer port. |
Jeffrey Send message Joined: 21 Nov 03 Posts: 4793 Credit: 26,029 RAC: 0 |
I am not a UNIX person. What does this do. Boinc Manager is just an application to run and control the boinc command line application, which is no different than the UNIX command line version on the downloads page... /Applications/BOINCManager.app Path to the BOINC Manager application found in your applications folder... /Contents/resources/boinc Path to the UNIX command line version of boinc embedded in the BOINC Manager application... -redirectio -dir /Library/Application\\ Support/BOINC\\ Data/ This redirects the boinc messages to the log files found in the BOINC Data folder... & This lets boinc run in the background so you can close the terminal window without killing boinc... It also lets you run boinc as a service so you can log out or log in as a different user without shutting down boinc... Does it close the port. The port would only be open when the BOINC Manager application is running... do I need to worry about the port. No... ;) It may not be 1984 but George Orwell sure did see the future . . . |
WillL Send message Joined: 9 Oct 02 Posts: 6 Credit: 19,862 RAC: 0 |
So the steps I would follow would be to shutdown the manager.app, remove it from my login file, restart my machine, enter the command in Terminal, then quit Terminal and go my merry way. Does this mean I can no longer look at messages or see my statistics? By the way, I am running the OSX firewall, so how is it that the Manager.app can open a port in the firewall? The only thing I have turned on is print sharing and Network time. |
Jeffrey Send message Joined: 21 Nov 03 Posts: 4793 Credit: 26,029 RAC: 0 |
So the steps I would follow would be [snip] Yes... But the reboot is not necessary... Does this mean I can no longer look at messages or see my statistics? You can still use the Boinc Manager application to view messages and make changes to the running boinc client... how is it that the Manager.app can open a port in the firewall? The open port is from localhost to localhost (Boinc Manager to boinc), it never leaves your computer: Proto___Recv-Q_Send-Q_____Local Address_______Foreign Address_____(state) tcp4_____0______0_______localhost.xqosd______localhost.51537___ESTABLISHED tcp4_____0______0_______localhost.51537_____localhost.xqosd____ESTABLISHED The default OSX firewall settings don't block outbound connections anyway, only inbound... Unless of course, you modify it... ;) It may not be 1984 but George Orwell sure did see the future . . . |
WillL Send message Joined: 9 Oct 02 Posts: 6 Credit: 19,862 RAC: 0 |
Thanks for all the help. I guess I was making something out of nothing. how is it that the Manager.app can open a port in the firewall? The open port is from localhost to localhost (Boinc Manager to boinc), it never leaves your computer: Proto___Recv-Q_Send-Q_____Local Address_______Foreign Address_____(state) tcp4_____0______0_______localhost.xqosd______localhost.51537___ESTABLISHED tcp4_____0______0_______localhost.51537_____localhost.xqosd____ESTABLISHED The default OSX firewall settings don't block outbound connections anyway, only inbound... Unless of course, you modify it... ;)[/quote] localhost.xqosd is port 31416 which showed open but port 51537 never did? Any thoughts. |
Jeffrey Send message Joined: 21 Nov 03 Posts: 4793 Credit: 26,029 RAC: 0 |
localhost.xqosd is port 31416 which showed open but port 51537 never did? Any thoughts. If you restart Boinc Manager, the port number will change... Port 31416 didn't show open for me, but neither did port 51537... I changed the number... ;) It may not be 1984 but George Orwell sure did see the future . . . |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.