GDP

Router goes in a pretty useless state, not allowing any clients to do useful operations. Here are the symptoms:

• Clients are able to establish a TCP connection, but they can't get any messages through. Here's a short log (see attached file for a more verbose log)

$ ./gdp-reader -D *=10 -s MerBLVlMI8-syn_mtadS2eLkAxCsjVvSsZAoo1SMWOw 
_gdp_lib_init(NULL)
    @(#)libgdp 0.6.1 (2016-08-09 22:03) 8dd74a73dcdd29d9e8e06dfae01dd43cce502277
My GDP routing name = zwKgqZG80_V_gHOkx_HRQWGk2Mku3_5JEdcO_7JZzZY
gdp_lib_init: OK
_gdp_chan_open(gdp-01.eecs.berkeley.edu; gdp-02.eecs.berkeley.edu; gdp-03.eecs.berkeley.edu; gdp-04.eecs.berkeley.edu)
Trying gdp-01.eecs.berkeley.edu
Talking to router at gdp-01.eecs.berkeley.edu:8007
_gdp_advertise => OK
gdp_init: OK
Reading GCL MerBLVlMI8-syn_mtadS2eLkAxCsjVvSsZAoo1SMWOw
_gdp_req_unsend: req 0xa64b70 has NULL GCL
_gdp_req_unsend: req 0xa64b70 has NULL GCL
Couldn't open GCL MerBLVlMI8-syn_mtadS2eLkAxCsjVvSsZAoo1SMWOw:
    ERROR: Connection timed out [EPLIB:errno:110]
[ERROR] gdp-reader: Cannot open GCL:
    ERROR: Connection timed out [EPLIB:errno:110]
exiting after 0 records with status ERROR: Connection timed out [EPLIB:errno:110]

• Connecting to port 15000 on the router for checking advertisements stays stuck after establishing a TCP connection:

$ wget http://gdp-01.eecs.berkeley.edu:15000
--2016-08-09 22:12:11--  http://gdp-01.eecs.berkeley.edu:15000/
Resolving gdp-01.eecs.berkeley.edu (gdp-01.eecs.berkeley.edu)... 128.32.33.233
Connecting to gdp-01.eecs.berkeley.edu (gdp-01.eecs.berkeley.edu)|128.32.33.233|:15000... connected.
HTTP request sent, awaiting response... 

• The log for the router has repeated messages of the type (multiple messages per second):

Recvied packet of length: 140
Received NEW_SECONDARY from node (128.32.33.232, 8007) 
I am a Primary node and the NEW SECONDARY node is (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Recvied packet of length: 140
Received NEW_SECONDARY from node (128.32.33.232, 8007) 
I am a Primary node and the NEW SECONDARY node is (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)
Forwarding NEW SECONDARY to node (10.142.33.243, 136.152.142.33, 8007)