Enable configuration of listen address/interface

[julian1]

I'm running:

• Which Parity version?:

Parity/v1.7.12-unstable-f96d15254-20180109/x86_64-linux-gnu/rustc1.21.0

• Which operating system?:

Linux 4.9.0-5-amd64 #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) x86_64 GNU/Linux

• How installed?:

from source

• Are you fully synchronized?: no / yes
• Which network are you connected to?: ethereum / ropsten / kovan / ...
• Did you try to restart the node?: no / yes

netstat shows parity listens on 0.0.0.0

$ netstat -tnlp | grep parity
tcp        0      0 0.0.0.0:30303           0.0.0.0:*               LISTEN      898/parity          
tcp        0      0 127.0.0.1:8545          0.0.0.0:*               LISTEN      898/parity     

I have a box with numerous interfaces and want ot restrict the p2p listen address. One can change the port using the --port flag, but how do I specify the listen address which defaults to 0.0.0.0 ?

Looking through the parity --help options I can't see anything relevant.

For example for rpc one just uses --jsonrpc-interface IP, but what about p2p?

[julian1]

As a follow up, why does parity p2p connect to itself? Granted it looks like it can be limited with --allow-ips=public, but it's a bit weird.

netstat -tnp | grep parity | grep 127.0
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 127.0.0.1:30303         127.0.0.1:60572         ESTABLISHED 1016/parity         
tcp        0      0 127.0.0.1:30303         127.0.0.1:60570         ESTABLISHED 1016/parity         
tcp        0      0 127.0.0.1:60572         127.0.0.1:30303         ESTABLISHED 1016/parity         
tcp        0      0 127.0.0.1:60570         127.0.0.1:30303         ESTABLISHED 1016/parity  

If one could specify the listen address, then this could be avoided.

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

This issue now has a funding of 0.16 ETH (92.13 USD @ $575.79/ETH) attached to it.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $9,068.61 more funded OSS Work available on the Gitcoin Issue Explorer

[pfilippi24]

@folsen
Looks like this ticket was already solved by #8699
Or is there something else to work on?

[julian1]

As the original issue submitter, this looks right to me. Nice one!

[folsen]

@pfilippi24 That's right, but since the PR is still open this isn't closed yet.

[5chdn]

@gnunicorn you can claim that bounty, I guess ;)

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work has been started.

These users each claimed they can complete the work by 8 months, 2 weeks ago.
Please review their action plans below:

1) gnunicorn has started work.

Hey, I am trying out this gitcoin as you suggested. Is this how I'd have to do it?

Learn more on the Gitcoin Issue Details page.

[folsen]

@vs77bb what should @gnunicorn do here, since the issue is already closed?

[vs77bb]

@gnunicorn Feel free to now submit work on Gitcoin, linking to your PR. This will allow us to pay you out for the bounty!

@folsen Issue being closed will not hold up @gnunicorn from collecting his bounty, it actually is helpful as a validation mechanism 🙂

[gitcoinbot]

@gnunicorn Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• warning (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[5chdn]

@gitcoinbot 🙄 🤣

[gitcoinbot]

@5chdn. 👋 thanks for the atMention, but you need to install @gitcoinbot on this repo for me to be able to respond. More details in the documentation.

✌️
@gitcoinbot

[vs77bb]

@5chdn Sorry about Gitcoin Bot, we're still training it over here 🤖 😂 appreciate any feedback.

Also @gnunicorn - we haven't seen a submission from you yet here, this is necessary for us to pay out the bounty. If interested in collecting, please do so at your convenience 🙂

[gnunicorn]

@vs77bb I have trouble claiming them as the faucet didn't give me ether and now I am stuck in some loop. I tried to email you about it, but the gmail-addr of your github profile bounces with Quota Limit reached...

[vs77bb]

Ah @gnunicorn Can you DM me your MetaMask account details on Gitcoin Slack? I'll send you over a bit more ETH so you can make the submission.

[vs77bb]

Hi @gnunicorn bumping to get your MetaMask details. Would love to pay this one out this week 🙂

[spm32]

Hey @gnunicorn! Just wanted to bump this once more, did you get a chance to connect with @vs77bb for payout?

[gitcoinbot]

⚡️ A tip worth 0.16000 ETH (44.1 USD @ $275.62/ETH) has been granted to @gnunicorn for this issue from @vs77bb. ⚡️

Nice work @gnunicorn! Your tip has automatically been deposited in the ETH address we have on file.

• $17556.48 in Funded OSS Work Available at: https://gitcoin.co/explorer
• Incentivize contributions to your repo: Send a Tip or Fund a PR
• No Email? Get help on the Gitcoin Slack

[vs77bb]

Bump... @gnunicorn we have sent you your funds for this bounty. @Tbaut this was completed as we close out any open issues on Parity-Ethereum, FYI 🙂

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

The funding of 0.16 ETH (42.52 USD @ $265.77/ETH) attached to this issue has been approved & issued.

• Learn more on the Gitcoin Issue Details page
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $17,292.53 more funded OSS Work available on the Gitcoin Issue Explorer