On Tue, Jul 18, 2017 at 08:33:37AM -0700, Max wrote: > Hi, > > I have installed the Bitcoin Core client and wish to allow inbound > connections. Has anyone tried doing this? I am able to connect to the network > with outbound connections but have had no success when trying to get inbound > connections > > I have taken these steps: > > 1) Installed Bitcoin GUI in the template VM > 2) Run it in a dedicated AppVM, downloaded the entire blockchain and am in > sync > 3) Configured port forwarding on the router, removed the firewall > 4) Followed the port forwarding steps > (https://www.qubes-os.org/doc/firewall/#port-forwarding-to-a-qube-from-the-outside-world) > but replaced the port 443 in the instructions with 8333 > 5) Tried to Telnet the IP address on the sys-net (appears to be 192.168.1.18 > on the wlp0s1 and do check node on bitnodes.21.co but it is unable to connect > to host / says my IP is unreachable > > Any advice > > Thanks, > > Max >
I'm always worried when I see comments like "removed the firewall", or global changes to firewall rules. This is almost never the right thing to do.You should be able to put new permissive rules in the firewall and retain other protections. Anyway, 192.168.. is a private address, not routable on the internet. What you want to provide is the EXTERNAL IP address on your router. If you don't know this you can check it using nwtools.com, unless you're using Tor or a VPN, in which case just log in to the router and check. unman -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20170718154508.ttlrp3zds373qhyz%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
