SPV nodes do not listen on ports (and make themselves discoverable via DNS). So if you're the one connecting to the other node, it should be a full node.
On 05/01/2017 04:51 PM, Ramez Az wrote: > Is there any way to know about the connected node whether it is full > node or SPV node? > > Thanks, > Ramesh A > > On Friday, April 28, 2017 at 6:50:16 PM UTC+5:30, Andreas Schildbach wrote: > > Other than the port number, there is no constant that you could use for > a firewall rule. And even the port number can be changed by peers, even > if that is very rare currently. > > You could put your own full node outside of the firewall and then > connect to that node exclusively. In such a setup, you could use the IP > of your full node for the firewall rule. > > SPV nodes do not relay blocks and transactions. > > > On 04/26/2017 05:14 PM, Ramez Az wrote: > > Thanks for your clarification. > > > > For running full node, what are the steps i need to follow and Is > there > > any reliable full node is available in the internet so that i can > open > > my firewall to that fullnode and can connect. If i need to run as > full > > node, what configuration(S/W and H/W) i should have. > > > > The another thing i wanted to check is that Is the SPV node > capable of > > propagate to other nodes. So that i can use the below approach. > > > > The Machine(Within Firewall) -> SPV Node(Outside the firewall and > > connected with bitcoin network). > > > > Thanks, > > Ramesh A > > > > On Friday, April 21, 2017 at 1:53:46 PM UTC+5:30, Andreas > Schildbach wrote: > > > > Since Bitcoin is decentralized, peers can come and go without > notice. > > The DNS queries are purposefully designed to return a > different set of > > peers for each query. So yes this also applies to Mainnet. > > > > The Bitcoin P2P network cannot work unless you allow full > access to > > port > > 8333 (port 18333 for testnet). > > > > To work around that limitation, we suggest you to run your own > full > > node > > and connect to it exclusively (using the Peer API). However, > that full > > node would need to sit outside your fireware or otherwise it > could not > > connect to the P2P network either. > > > > > > On 04/21/2017 05:19 AM, Ramez Az wrote: > > > Hi, > > > > > > I am developing small client application for posting the > txns and > > > receiving the txns. I have firewall in my network and i am > able to > > allow > > > only some Peers to connect in the network. The list of peers(IP > > > addresses) are getting changed every DNS lookup at > > > testnet-seed.bitcoin.petertodd.org > <http://testnet-seed.bitcoin.petertodd.org> > > <http://testnet-seed.bitcoin.petertodd.org > <http://testnet-seed.bitcoin.petertodd.org>> domain. Can you please > > provide some > > > list of Peers through which we should be able to do connect > at any > > time. > > > Is there any other domain where we can get some consistent > Peers > > or any > > > alternatives?. If you provide some of consistent peers, i > can open my > > > firewall for those nodes. > > > > > > I am facing this issue in Testnet, Is this the same case for > > mainnet as > > > well or can we get consistent Peers in MainNet. > > > > > > As this is bit urgent, Can any one clarify as soon as possible. > > > > > > Thanks in Advance. > > > > > > Thanks, > > > Ramesh A > > > > > > -- > > > You received this message because you are subscribed to the > Google > > > Groups "bitcoinj" group. > > > To unsubscribe from this group and stop receiving emails > from it, > > send > > > an email to bitcoinj+u...@googlegroups.com > > > <mailto:bitcoinj+u...@googlegroups.com>. > > > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout> > > <https://groups.google.com/d/optout > <https://groups.google.com/d/optout>>. > > > > > > -- > > You received this message because you are subscribed to the Google > > Groups "bitcoinj" group. > > To unsubscribe from this group and stop receiving emails from it, > send > > an email to bitcoinj+u...@googlegroups.com > > <mailto:bitcoinj+u...@googlegroups.com>. > > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to the Google > Groups "bitcoinj" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to bitcoinj+unsubscr...@googlegroups.com > <mailto:bitcoinj+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "bitcoinj" group. To unsubscribe from this group and stop receiving emails from it, send an email to bitcoinj+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.