[tahoe-lafs-trac-stream] [tahoe-lafs] #2073: Wrong ports are reported for connected nodes

[tahoe-lafs]

#2073: Wrong ports are reported for connected nodes
------------------------------+--------------------------------------------
     Reporter:  genell        |      Owner:  genell
         Type:  defect        |     Status:  new
     Priority:  normal        |  Milestone:  undecided
    Component:  code-network  |    Version:  1.10.0
   Resolution:                |   Keywords:  wui tub port foolscap firewall
Launchpad Bug:                |
------------------------------+--------------------------------------------

Comment (by genell):

 Replying to [comment:1 daira]:
 > > In some occasions the node has been presented as accessible in the WUI
 and has appeared to be using a port other than 8098, while neither 8098
 nor the erroneous port has been accessible.
 > > Especially this last case is somewhat troublesome as the node appears
 online, but cannot receive data.
 >
 > Is it possible that the node made a connection at some point but the
 connectivity has changed?

 Yes, the node generally has made a connection at first, but fail to report
 broken connectivity when tub.port/tub.location is closed. We just did a
 test where port 8098 for one of the nodes were filtered in the firewall
 for about six hours. This was shown by our surveillance script testing
 8098 connectivity using nmap, but the Tahoe WUI status page just showed
 the node as connected all through the six hours.
 I'd like to suggest incorporating some recurrent data flow test, where a
 tiny data file is uploaded as mutable and recovered back again from the
 cloud and if the operation fails it should be noted on the status page.
 Would that be possible/useful?

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2073#comment:4>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage