Avatar
BlessedBovine
c566aa07755e1982f2bceefedd3d1b1470c7b094600a02a36267d6b09c9ba4a2
Husband of npub12wk0tlwr5wa39l6slw8rskwsvkatcll6zjrx8d909ltkvu7lsalsveyvqf Father Brother Catholic Bitcoiner (Class of 2023) American Dreamer Bitcoin Full Node Runner on Tor On Nostr Since 850200; Verified 852712

Suggestions:

It looks like you're dealing with the limitations of Carrier-Grade NAT (CGNAT) from your ISP, which restricts your ability to receive inbound connections directly. Here are a few potential solutions to work around this:

1. **VPN with Dedicated IP:**

- **VPN Service with Port Forwarding:** Some VPN providers offer dedicated IP addresses and port forwarding options. By using a VPN with a dedicated IP, you can route inbound traffic through the VPN, bypassing the CGNAT limitations.

- **Steps:**

1. Subscribe to a VPN service that offers dedicated IP addresses and port forwarding (e.g., NordVPN, PureVPN).

2. Configure your device to use the VPN and set up port forwarding as per the VPN provider's instructions.

3. Use the dedicated IP provided by the VPN for inbound connections.

2. **Dynamic DNS with VPN:**

- If your VPN service supports Dynamic DNS (DDNS), you can use a DDNS service to map a domain name to your changing IP address. This is useful if you don't have a static IP.

- **Steps:**

1. Set up a DDNS service (e.g., No-IP, DynDNS).

2. Configure the DDNS to update with your VPN-assigned IP.

3. Set up port forwarding on the VPN.

4. Use the DDNS hostname for inbound connections.

3. **Tor Network:**

- Tor can provide inbound connections without needing a public IP address, but it's more complex and may introduce latency.

- **Steps:**

1. Set up a Tor hidden service on your device.

2. Configure your application to use the .onion address provided by the Tor network for inbound connections.

3. This method is more suitable for use cases where privacy and anonymity are prioritized.

4. **Remote Access Services:**

- Use remote access services that work over the internet without requiring a public IP (e.g., TeamViewer, AnyDesk).

- **Steps:**

1. Install and configure the remote access software on your device.

2. Access your device remotely using the softwareโ€™s service.

5. **Reverse SSH Tunnel:**

- Create a reverse SSH tunnel from your device to a remote server with a public IP.

- **Steps:**

1. Set up an SSH server on a remote host with a public IP.

2. Create an SSH reverse tunnel from your local machine to the remote server: `ssh -R [remote_port]:localhost:[local_port] user@remote_host`.

3. Connect to the remote host on the specified port, which will forward traffic to your local machine.

6. **Cloud-based Solutions:**

- Host the service in a cloud environment (e.g., AWS, Google Cloud, Azure) where you can get a public IP address.

- **Steps:**

1. Set up a VM or container in the cloud.

2. Configure your service on the cloud instance.

3. Use the cloud instanceโ€™s public IP for inbound connections.

### Additional Considerations:

- **Security:** Ensure that any solution you implement is secured properly to avoid unauthorized access.

- **ISP Contact:** If possible, contact your ISP to see if they offer an option for a static public IP or a business account with different NAT policies.

By using one of these methods, you can effectively bypass the limitations imposed by CGNAT and allow for inbound connections to your device.

I was able to set up my Bitcoin Core Node to use the Tor network on Windows. (No previous networking/programming experience, just good guides and a good deal of time messing with it.) It's been running since 2:50ish PDT. I have logged inbound peers at an average of 15 minute intervals according to the debug.log. "New Inbound" peer connected at:

3:13PM PDT

3:22PM PDT

3:57PM PDT

4:17PM PDT

4:31PM PDT

Hope that means I'm up and running, I still don't show up on Bitnodes.io, but everything seems to be working otherwise.

Current node address is:

t5fj3j25sj6kheyqwbgji4wcrkjwsa75kwgz2gswejdxsjypxyxku4qd.onion

If anyone can ping that, I'd appreciate it.

It looks like CGNat is my hang up. The ISP is pooling us with other traffic. So I don't have an inboud IP to be pinged. Which is why my port shows open when I check the local network, but Nmap says I have 0 IP addresses.

Now I've gotta figure a way around that without having access to the account for the ISP. I'm thinking of potentially running a VPN with a dedicated IP and porting options. Or really going down a rabbit hole and learning about Tor.

Given your setup, there are several areas to investigate to resolve the issue of your Bitcoin Core node not receiving inbound connections. Here are some suggestions:

1. **Double-Check Port Forwarding:**

- Ensure that your router's port forwarding rules are correctly set up for port 8333 on both TCP and UDP. Sometimes, port forwarding settings can be tricky, and a small mistake can cause issues.

- Verify that the internal IP address specified in the port forwarding rule is the correct IP address of the machine running the Bitcoin Core node.

2. **Router Configuration:**

- Make sure your router is not using Carrier-Grade NAT (CGNAT), which can sometimes interfere with port forwarding.

- Ensure that there are no additional firewall settings on the router that might be blocking incoming connections.

3. **Local Firewall:**

- Verify that Windows Defender Firewall has the correct inbound rules for both Bitcoin Core and port 8333. Sometimes, the rules might need to be more specific or duplicated for different network profiles (Private, Public, Domain).

4. **ISP Blocking:**

- Although less common, some ISPs might block certain ports or traffic types. Since you mentioned youโ€™re on a shared office building wifi, the network administrator might have certain ports blocked.

- If possible, contact the network administrator or ISP to confirm if port 8333 is being blocked.

5. **Testing Connectivity:**

- Use a port checking tool like [canyouseeme.org](https://canyouseeme.org) to see if port 8333 is accessible from the internet. This will help determine if the port forwarding is working correctly.

- You can also use tools like `telnet` or `nc` (netcat) from an external machine to test if port 8333 is open.

6. **Bitcoin Core Configuration:**

- Ensure that your Bitcoin Core node is configured to accept incoming connections. Check your `bitcoin.conf` file for the following settings:

```plaintext

listen=1

port=8333

bind=:8333

```

- Also, ensure that the `maxconnections` setting allows for a reasonable number of inbound connections.

7. **Alternative Network Setup:**

- Since you're running off a shared office building wifi, consider testing with a different network (e.g., a home network or mobile hotspot) to rule out any network-specific issues.

8. **UPnP and NAT-PMP:**

- Ensure that Universal Plug and Play (UPnP) and NAT Port Mapping Protocol (NAT-PMP) are enabled on your router. Bitcoin Core can use these protocols to automatically configure port forwarding.

By systematically checking each of these areas, you should be able to pinpoint the issue preventing inbound connections to your Bitcoin Core node.

Thanks, I'm going to work my way through each of those. I should try another network to see. I don't have internet at my house, we live in the boons. I'll have to bumb usage off a friend or family member around here to rule out the network.

I cannot for the life of me track down why my Bitcoin Core Node isn't receiving any inbound connections. Number of connections 10 (In: 0 / Out: 10). Port forwarding for TCP and UDP for port 8333 external and internal. Windows Defender Firewall exemption for Bitcoin Core GUI. Two separate rules to exempt Port 8333 through the Firewall. Can ping it from my local network, but not over the internet.

It's possible my ISP is blocking it, but I can't confirm that since I'm not the account holder. Just running a separate router off the shared office building wifi. In the USA, so I that should rule out any government restrictions.

Any ideas? nostr:nprofile1qqsy4ytpp8ln830va364awxjut6h679ksjcx0f9p9dfsrfpdkrpxlpspzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgjwaehxw309ac82unsd3jhqct89ejhxqgdwaehxw309ahx7uewd3hkczzdxj8 nostr:nprofile1qqsfev65tsmfgrv69mux65x4c7504wgrzrxgnrzrgj70cnyz9l68hjspp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujumn0wvh8xmmrd9skcqgcwaehxw309aex2mrp0yhx6mmddaehgu3wwp5ku6cnr2xg3

#AskNostr #Bitcoin #BTCNodes #BitcoinNodes #Nodes #Relays

Thank you, it's been fun coming up with my own algo. :)

Wrong timezone for me, but I think we may need to be friends my fellow Bovine! I'm off for the night. Have a wonderful morning :)

A portion of this is a repost. As I didn't know about #introductions originally.

I'm excited to be on Nostr. Which is neat, because I've never been excited about nor felt like jumping into a social media community. I've never felt like being active on social media platforms, because I've always felt there's no ownership to what you post. I love that there is no way for someone to clone my account, because those who know me and follow me will always know my npub is nostr:nprofile1qqsv2e42qa64uxvz727walka85d3gux8kz2xqzsz5d3x044snjd6fgspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsctplg0. Thank you, #Nostr for giving me a place online where I can feel in control of my persona. Thank you to the #Bitcoin community for bringing me here. I look forward to seeing the world of hope and optimism spread!

USA for me. I suppose I'm blessed, because the worst I deal with is 48-72hr hold on our paychecks when my wife and I deposit them. An irritating experience after seeing #Bitcoin in action. Both via on chain and Lightning.

Additionally, I'll add the entirety of my interactions with #Coinbase whom froze our account and funds for "Suspicious Activity" for four month, after we started a mad dash to save as much of our time and energy as possible in #Bitcoin. I'm trying to close my account, which I haven't used in probably ten months now, and they just put a 72hr hold on transfering 32000 Sats to a LN address.

So happy we found nostr:nprofile1qqsza56ed667de7q6mu6uxspetg7gzadqtkeug3plserzcj2nz6vc7qpz9mhxue69uhkummnw3ezuamfdejj7txdgdu for future stacking.

I do disagree with his final statement that #Bitcoin is not an instrument for hope.

#Bitcoin is hope. Hope for a fair economic policy for all the people of earth. Hope for a future for us and our heirs, and their heirs. Hope that my value today, will be as valuable as in the future. The hope we can protect ourselves from the time theft perpetuated on us by the elites, and our government. #Bitcoin gives me hope for myself, my wife, my children, my family, and my friends. We can opt out of our broken financial system that steals and devalues our time, to a system that protects and adds value to our time https://video.nostr.build/26d52fa84986528a70dc6d8df59397746250dc7267916c009889e2f09518f8fb.mp4

I think that the final reward block to be mined will be viewed similarly to Y2K. People will think there's no reason that #Bitcoin time chain will keep running with no block reward. As we draw closer to that in a hundred plus years, the miner fees on transactions will balance it out. I wonder if people will even know about Y2K at that point...

I really like that concept. I just started learning about Lightning, and it's going to take me a while to get comfortable enough to set up and run a LN node. I really like your new implementation for Zaps, and look forward to being able to use it. The only reason I set up my non-custodial LN with Speed was for use with Nostr, since I don't know any Bitcoiners.

You are incapable of fathoming my disdain for Coinbase. Trying to close out my account, that hasn't been used in nine months as I've moved on to nostr:nprofile1qqsza56ed667de7q6mu6uxspetg7gzadqtkeug3plserzcj2nz6vc7qpz9mhxue69uhkummnw3ezuamfdejj7txdgdu. Evidently, I still had about 3200 Sats. Tried to transfer it out via Lightning and they put a 72hr hold on it.

nostr:nprofile1qqst0dgucffpd4xpp0y94cns2hy6j307wl90633u7gajpyt7888xs9spzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcgfhdj7