Node banning internal IP "peers" | Bitcointalksearch.org

bob123

legendary

Activity: 1624

Merit: 2481

Quote from: k3tan on April 11, 2019, 01:46:03 AM

i'm experiencing this issue. all of my incoming connections are 192.168.1.1:[random port]. is there a way to configure my firewall such that I get the real IP? at the moment i've got whitelist=192.168.1.1 to stop getting 192.168.1.1 onto the banlist.

Configure your PREROUTING chain accordingly.

Depending on the interface of your firewall / router this can be either trivial or somewhat non-intuitive. Did you try out some forwarding options yet ?

k3tan

newbie

Activity: 1

Merit: 0

i'm experiencing this issue. all of my incoming connections are 192.168.1.1:[random port]. is there a way to configure my firewall such that I get the real IP? at the moment i've got whitelist=192.168.1.1 to stop getting 192.168.1.1 onto the banlist.

I'm running pfsense router and that's connected to my Netgear R7000 access point and that connects to the PC I'm running my node on.

I've looked at the Netgear R7000 access point settings and pfsense settings, but I have absolutely no idea why all my incoming peers are 192.168.1.1. Any help would be appreciated.

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Add the following line to your bitcoin.con file:

Code:

whitelist=192.168.1.1

Note that this will mean nothing will be banned if your node thinks that all connections come from your router.

What you should really do is have your router forward the connection to your computer instead of proxying it. That way your node knows that actual IP address of the node it wants to ban and bans that instead of banning your router.

aleksej996

sr. member

Activity: 490

Merit: 389

Do not trust the government

You could just use Tor and create a Tor hidden service. That way your firewall won't bother you, since all the connections will seem as outgoing and you can keep your IP hidden, so no one will know that you are the owner of that node.

It is easy to setup Tor with Bitcoin Core, as it has a default port setup in the options and more. You can search about Tor and how to create a hidden service. It is easy, you can PM me if you need any help.

jdh3

newbie

Activity: 1

Merit: 0

My node is running thru my firewall. Everything works fine but the one problem I'm having is all my incoming connections are getting an internal ip address. So when a incoming connection starts miss behaving it will get banned. Well 192.168.1.1 bans my node! Undecided

So it goes off line for 24 hours. Is there a way to lower the ban for an hour or two? Im not always around to unban the internal ip. Im just trying to find a workaround for the problem. On average my node will accept incoming connections for about 8 hours before banning an internal ip address.

Im trying to find a way to fix the firewall so I can see the external ip's but I was hoping to for a temporary fix.

Thanks!

JD

edit I just see that I posted this to the wrong discussion. Maybe a mod could move it?

Topic: Node banning internal IP "peers" (Read 511 times)