In case you haven't seen it: Application for port-number (1043-Assigned)

Framework for separate GUIs

---

Time to revisit my firewall policy...

> In case you haven't seen it: <a> href="http://www.ssl.berkeley.edu/pipermail/boinc_dev/2004-November/000772.html">Application
> for port-number (1043-Assigned)[/url]
>
> Framework for separate
> GUIs
>
>

They can't use 1043. Sorry.

Sorry, but how does this work, should i do nothing or is there something i have to configure?

---

Regards

> Sorry, but how does this work, should i do nothing or is there something i
> have to configure?
>

No, you don't have to do anything unless your firewall is blocking BOINC's connection. If it is, then you'll need to open up the port BOINC is using to allow the connection.

Ned

---

*** My Guide to Compiling Optimised BOINC and SETI Clients ***
*** Download Optimised BOINC and SETI Clients for Linux Here ***

For which purposes will BOINC use such a port number? Do they want to stop using port 80 (http)??? Then I will be diconnected, it's one and only port I can connect from here.

---

ALL GLORY TO THE HYPNOTOAD!
Potrebujete pomoc?
My Stats

> For which purposes will BOINC use such a port number? Do they want to stop
> using port 80 (http)??? Then I will be diconnected, it's one and only port I
> can connect from here.

The current rpc port is 31416 which will change to 1043.

The port is used to remotely talk to the Boinc client via rpc.

The new boinc series 4.5x uses a two aprt boinc, the core client and Boinc Manager, these talk ove the RPC port to communciate.

Normally the port is only enabled for the lcoal client, you have to enable remote rpc to talk to the boinc client from other clients.

Boinc client to projects over http on port 80 is not affected.

73 de Peter VK3AVE

---

73 de Peter VK3AVE

Thanks a lot, so in other words, if I want use for example BoincView to control remotely some boxes it will use new 1043 port number. So if I want to control my home box from here I have to open another port on my home firewall to connect. For example.

> > For which purposes will BOINC use such a port number? Do they want to
> stop
> > using port 80 (http)??? Then I will be diconnected, it's one and only
> port I
> > can connect from here.
>
> The current rpc port is 31416 which will change to 1043.

---

ALL GLORY TO THE HYPNOTOAD!
Potrebujete pomoc?
My Stats

open port and used protocoll (upd or tcp)

Like (CB) radio, changing the frequency.

The use of port numbers for tcp/ip programming/communication is a technical Thing.
It nearly doesn't matter, which frequency/port number is used, IF the port is free and open.

The IANA organisation is a kind of central registration area, "Adresses" are assigned for world wide use.

The stage before aproovement is RFC (Request for comment)a de facto standard.

Now it looks like, for BOINC, a world wide unique port number is officilaly assigned and reserved.

Still open 4e, will it be a common change to the new port number(now registered) or will this number used additionally ?
like mentioned above, for commnunication between Management station (for exp. BoncView) and core client?
Internet Assigned Numbers Authority (IANA)

> Still open 4e, will it be a common change to the new port number(now
> registered) or will this number used additionally ?
> like mentioned above, for commnunication between Management station (for exp.
> BoncView) and core client?
> Internet Assigned Numbers Authority (IANA)
I think they (in Berkeley) would like use that port in general and have it registered. One reason what I see is for example that when I'm configuring some router or firewall in the same way like for SMTP, POP3 I will build in BOINC Client port enable/disable. Other tink is, just some kind of my personal philosophy, it goes to be more official. Since port is registered it is going to be a standard. Which sounds pretty good.
And probably they will offer possibility to swith form port 80 (http) if user want to own port number. So also client - server communication will be possible on that different port number.

---

ALL GLORY TO THE HYPNOTOAD!
Potrebujete pomoc?
My Stats

U right.
> want to own port number. So also client - server communication will be
> possible on that different port number.


quota
BOINC's GUI RPC now has an official port number (see below)
so we're going to switch to it (from the pi-inspired 31416).
-- David

rereading the statement, I interprete, they will change.

This will be an adventure, to change "world wide" the ports used.
The only, less hard way might be, to allow both numbers at the same time for a
announced time frame.

Whats good with the entry at iana also is, the people running at work and had some restrictions due traffic filtering/shapper, they can now go and say, look, the port adress is an official adress, there is no reason to keep it close.

Til now the admins could say, is there something official?

using several (open) ports together, could give "Boinc management apps"
more speed, in point of view midrange/large farms and could bundle the local traffic more.

Does port change affect me?

This port change will only affect people who use 3rd party programs to help manage their boinc systems. If you don't use one, this does not affect you.
Examples: boincview, boinclogX, CPDN spy, etc.

When will it happen?
This port will probably only go into affect when the version 4.50 BOINC client is released. There is a possibility it might be used on an earlier release.

What is port change
For WU upload/download, updating, etc. BOINC uses the standard web page port for all communications (Port 80, like when you type http://).

For special client control and status requests a different port is used (called the RPC port).

Apparently David Anderson and the development group applied for an official port number, from the port management group.

They were just granted one -- 1043.

Until this time they had been using 31416 (see definition of PI)

---

@Benger: Nice summary.

---

ALL GLORY TO THE HYPNOTOAD!
Potrebujete pomoc?
My Stats

> And probably they will offer possibility to swith form port 80 (http) if user
> want to own port number. So also client - server communication will be
> possible on that different port number.

I highly doubt that. As far as I know, this is only going to affect RPC access to the client.

trane

---

> When will it happen?
> This port will probably only go into affect when the version 4.50 BOINC client
> is released. There is a possibility it might be used on an earlier release.

Looks like it's going to be in the next Core Client after v4.54.

BOINC Checkin Notes (Long load time)
"David 12 Nov 2004
- bug fixes for admin web interface (from Bruce Allen)
- change GUI RPC port number from 31416 to 1043
- remove Mac files from Makefile"

---