search

threefoldfoundation / tfchain

Official implementation of the ThreeFold blockchain
https://explorer.threefoldtoken.com
Apache License 2.0
13 stars 7 forks source link

Clients don't sync with ropsten on the fruit #277

Closed LeeSmet closed 5 years ago

LeeSmet commented 5 years ago

Running in the network namespace in the fruit, a node running an eth light client is refusing to sync. If run without the network namespace, it does sync eventually (though starts from 0)

LeeSmet commented 5 years ago

Log msg from the bridge if run in a network namespace:

msg="seed node (age 429876h43m19.737756073s): enode://6332792c4a00e3e4ee0926ed89e0d27ef985424d97b6a45bf0f23e51f0dcb5e66b875777506458aea7af6f9e4ffb69f43f3778ee73c81ed9d34c51c4b16b0b0f@52.232.243.152:30303"

LeeSmet commented 5 years ago

Running a slightly modified build with trace logging reveals that every node it tries to connect to results in a ping timeout, so this does make me believe it has something to do with the network setup

LeeSmet commented 5 years ago

Ping (UDP) Packets do leave, but the replies are sent to the host address instead of the network namespace address (i.e. leave from 185.69.166.13 and replies go to 185.69.166.26). Need to look into the eth network code to figure out why

LeeSmet commented 5 years ago

Docker contiainer running a daemon with ethvalidation module on macvlan also does not work, for the same reasons

LeeSmet commented 5 years ago

This setup does work on my laptop, possibly an issue in the fruit setup

LeeSmet commented 5 years ago

After rebooting the node, the syncing now works properly on the fruit as well on both rinkeby and ropsten, so this is a non issue