Can Not connect to any peer in segnet4, Could I use other block chain?

[feeling4t]

2016-07-07 12:07:22 dnsseed thread start
2016-07-07 12:07:22 Loading addresses from DNS seeds (could take a while)
2016-07-07 12:07:22 0 addresses found from DNS seeds
2016-07-07 12:07:22 dnsseed thread exit
.......
2016-07-07 12:08:23 Adding fixed seed nodes as DNS doesn't seem to be available.
2016-07-07 12:08:23 connect() to 37.34.48.17:28901 failed after select(): Connection refused (111)
2016-07-07 12:08:24 connect() to 37.34.48.17:28901 failed after select(): Connection refused (111)
2016-07-07 12:08:25 connect() to 37.34.48.17:28901 failed after select(): Connection refused (111)

and keep refused

so Could I use other blockchain instead of segnet4?

[Roasbeef]

My local btcd node is still able to successfully connect to the segnet4 DNS seed. It has also been around since segnet was created, so its addrman is well populated. As a result I have no problem connecting to other nodes on segnet.

You might need to find/locate the address of an existing segnet node in order to bootstrap your bitcoind node.

Alternatively, you can use testnet as you suggested in the issue title.

[feeling4t]

@Roasbeef thank you, cound you give the ip address of some segnet node, or your peers.dat to feeling4t@gmail.com ?

[andrewshvv]

@Roasbeef me too, andrew.shvv@gmail.com

[Roasbeef]

For the most part, segnet is pretty much dead at this point. I've switched over primarily to using a local instance of simnet instead.

Now that Bitcoin Core has released version 0.13, there should be more segwit enabled peers on testnet now, so I'd recommend running the daemon in testnet mode for now. The daemon can be switched over to testnet mode by passing the --testnet flag on the command line, or setting testnet=1 in your lnd.conf.

[Roasbeef]

Closing this issue as testing has now primarily moved onto Testnet3.