@abit same results after the last instruction - rescan blockchain and all
@cube - yes I see connections to several seed nodes... on and off
104.236.144.84:1777, -> 104.236.144.84:1777 last seen 2016-01-26T18:37:49
here are data from 3 different times later on... mostly non-seed nodes as far as I can tell.
TCP xxx.154.1.146:58678 23-95-43-126-host:50696 ESTABLISHED
TCP xxx.154.1.146:58678 45:1779 ESTABLISHED
TCP xxx.154.1.146:58678 cpe-70-114-143-108:48173 SYN_SENT
TCP xxx.154.1.146:58678 104.236.144.84:1777 TIME_WAIT
TCP xxx.154.1.146:58678 114.92.254.159:62015 LAST_ACK
TCP xxx.154.1.146:58678 115.29.36.189:35897 ESTABLISHED
TCP xxx.154.1.146:58678 178.62.88.151:60335 TIME_WAIT
TCP xxx.154.1.146:58678 witness:35718 LAST_ACK
TCP xxx.154.1.146:58718 a23-72-60-161:https CLOSE_WAIT
TCP xxx.154.1.146:58678 162.243.138.215:40124 ESTABLISHED
TCP xxx.154.1.146:58678 178.62.88.151:60335 ESTABLISHED
TCP xxx.154.1.146:58678 li699-30:44223 ESTABLISHED
TCP xxx.154.1.146:58678 69.30.232.146:52002 ESTABLISHED
TCP xxx.154.1.146:58678 84.200.17.129:1779 ESTABLISHED
TCP xxx.154.1.146:58678 104.236.144.84:1777 ESTABLISHED
TCP xxx.154.1.146:58678 li611-150:42665 TIME_WAIT
TCP xxx.154.1.146:58678 115.29.36.189:35897 ESTABLISHED
This one 84.200.17.129 from above is a seed node. The communication went something like...
active: 84.200.17.129:1779 with 97ea3e6a4056decd6d44868e43cb444d883f875cebedfd00a48159a23a95c0b67f [outbound]
eer 84.200.17.129:1779 because they didn't respond to my request for sync item ids after ["002b0e5966422ef475e20ef2c96acdaec7d51127","002b21e06bbd170a778f9cbc8891fa73f51764b1...
nnection.cpp:202
2016-01-26T19:00:36 p2p:message read_loop on_connection_closed ] Remote peer 84.200.17.129:1779 closed their connection to us
node.cpp:985
2016-01-26T19:00:36 p2p:message read_loop schedule_peer_for_de ] scheduling peer for deletion: 84.200.17.129:1779 (this will not block)
handshaking: 84.200.17.129:1779 with 000000000000000000000000000000000000000000000000000000000000000000 [unknown]
handshaking: 84.200.17.129:1779 with 97ea3e6a4056decd6d44868e43cb444d883f875cebedfd00a48159a23a95c0b67f [outbound]
84.200.17.129:1779 last seen 2016-01-26T19:00:50
some active communications with some non-seed nodes
from p2p.log2016012T1800000
node.cpp:2522
2016-01-26T18:37:51 p2p:message read_loop fetch_next_batch_of_ ] sync: sending a request for the next items after 002b2d966b7cf344032b787762760e770e22c90d to peer 159.203.101.247:54765, (full request is ["002b0e5966422ef475e2...
node.cpp:2424
2016-01-26T18:37:51 p2p:message read_loop on_message ] handling message blockchain_item_ids_inventory_message_type 57179945df4926db3b90931eafa6834ba1213ce8 size 40010 from peer 159.203.101.247:5
node.cpp:1754
2016-01-26T18:37:51 p2p:message read_loop on_blockchain_item_i ] sync: received a list of 2000 available items from 159.203.101.247:54765
node.cpp:1754
2016-01-26T18:37:51 p2p:message read_loop on_blockchain_item_i ] sync: received a list of 2000 available items from 159.203.101.247:54765
PS
and the witness node spit a new line (for the first time) after 2h or so later:
2095358ms ntp ntp.cpp:177 read_loop ] ntp_de
lta_time updated to 950002 us