Topic: [ANN] Expanse (EXP) - 1st Stable fork of Ethereum (New Algo + PirlGuard) - page 359. (Read 961474 times)

42786 UDP

Still not working for me  

I opened it at my router.

I was able to mine Ethereum with no router setup. Did you make any changes to the way it connecting to peers?

just 42786 UDP

Same here...

Windows and Linux installs. looking into router issues.

What is the port/s thats need to be open on my router?

not working for me
the nodes are not connected

Thanks for answering.

What is the port number for router forwarding? 42786?

I mined Etherum without the need for router setup.

Updated the windows builds.

https://github.com/expanse-project/go-expanse/tree/develop/BUILDS-GEXP/gexp1.1.3-go1.5.1

everything works fine here on lan without port forwarding:
will:
suffice on launch? or should i do something else?
thank you

hardcoded like 6 of them. Did you set up your router to port forward?

Also you are on the develop branch right?

Done that admin.peers   is null.

Did you hardcode nodes or we have to enter them maunaly?

I was noticing the same sort of behavior also. It is strange. Whats strange about it is, the behavior is inherited from ETH since I didnt change that stuff at all. I found though that once I forwarded all UDP traffic on my nodes, everything started working alot smoother.

this one will work 100% sure

just type admin.peers to confirm

Everyone admin.peers and see if you are connected to others now.. Also remember to portforward all UDP traffic for port 42786 for the machine hosting the node.

Also, everyone on linux


then restart your node and see if you find some more peers

I'll remake the windows binaries soon.

admin.addPeer("enode://0055fd5099543df005a13ea5bec103def47340de81a6c1b0ba20f8ef756a7fe575b362976b1a52c9f561dda95321700a1c9e769004d25278ce53d2d6aa0b65b7@80.240.138.173:42786")

The running peer (ID: "f944c6702a78a...") has an IP (74.196.59.103) in the ID peer address, all other only [::] (IPv6 broadcast?)

How should my client connect the peer in a decentralized network?

Just the one I added manually.

Now again:
> admin.peers
[{
    Caps: "exp/60, exp/61",
    ID: "f944c6702a78a0cbcd6505b76daff069dad2e45ff88896c475da2bef47091c88e5b4042211233e3 97ad958be998003a2674151e60719c5fdeeff5f8cc2c231a1",
    LocalAddress: "192.168.0.101:34810",
    Name: "Gexp/v1.1.2-74cee8c3/linux/go1.4",
    RemoteAddress: "74.196.59.103:42786"
}]


Could it be that the nodes given in the OP have not network port (42786) opened in the firewall

2 minutes later (with the same running server instance):

> admin.peers
null
> admin.peers
null
> admin.peers
null
> I0912 16:48:19.542541   29792 chain_manager.go:661] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 9.543578ms. #888 [1dd75bcd / 1dd75bcd]
> admin.peers
null
>

I'm connected to only one node, but tried all the other nodes mentioned in this thread.

> admin.peers
[{
    Caps: "exp/60, exp/61",
    ID: "f944c6702a78a0cbcd6505b76daff069dad2e45ff88896c475da2bef47091c88e5b4042211233e3 97ad958be998003a2674151e60719c5fdeeff5f8cc2c231a1",
    LocalAddress: "192.168.0.101:33095",
    Name: "Gexp/v1.1.2-74cee8c3/linux/go1.4",
    RemoteAddress: "74.196.59.103:42786"
}]

First launch clean node (without peers connected or admin.addPeer("enode:// ... or bootnodes)
launch this node with --vmodule=udp=6,server=6,downloader=6 console


 >>> then try to add 'problematic node' for ex admin.addPeer("enode://4055ec69e53df4bfecb95e3b65c28e4f2a1145a3bdc4d85d077b552248cf159951afd649f044783bebf48b902fbc0e96978c76236fd4ab3d5ef7d95d72b84ee5@[::]:42786")


I0912 10:27:40.704880    2840 server.go:624] dyn dial conn 0055fd5099543df0 [::1
]:42786 failed checkpoint posthandshake: Connected to self

>>> Now try with the working node : this one admin.addPeer("enode://f944c6702a78a0cbcd6505b76daff069dad2e45ff88896c475da2bef47091c88e5b4042211233e397ad958be998003a2674151e60719c5fdeeff5f8cc2c231a1@74.196.59.103:42786")


> I0912 10:29:05.517708    2840 server.go:475] <-posthandshake: static dial conn
 f944c6702a78a0cb 74.196.59.103:42786
I0912 10:29:05.519694    2840 server.go:481] <-addpeer: static dial conn f944c67
02a78a0cb 74.196.59.103:42786
I0912 10:29:05.520124    2840 server.go:670] Added Peer f944c6702a78a0cb 74.196.
59.103:42786
I0912 10:29:05.520515    2840 server.go:465] <-taskdone: static dial f944c6702a7
8a0cb 74.196.59.103:42786
I0912 10:29:05.624936    2840 downloader.go:215] Registering peer f944c6702a78a0
cb
I0912 10:29:08.564406    2840 server.go:465] <-taskdone: discovery lookup (1 res
ults)
I0912 10:29:08.564950    2840 server.go:431] new task: discovery lookup
I0912 10:29:11.954980    2840 downloader.go:237] Attempting synchronisation: f94
4c6702a78a0cb, head 0x6b5c6511, TD 70648672834
I0912 10:29:11.955575    2840 downloader.go:278] Block synchronisation started
I0912 10:29:11.956055    2840 downloader.go:322] Synchronizing with the network
using: f944c6702a78a0cb, exp/61


No error for this one.

So conclusion : Encryption handshake problem.

What it coulb be? lot of reasons ...

what is nodes?
how to mining with nodes?
whether the miners I've been running correctly?
if my coin will be lost at launch?