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

[tahoe-lafs]

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

 * keywords:  WUI port => wui tub port foolscap
 * component:  unknown => code-network


Old description:

> In our friendnet all nodes are configured to use port 8098 as tub.port
> and in tub.location. This port is being forwarded through the firewalls
> of each node owner. Connectivity has been confirmed using nmap from the
> introducer node computer. In the WUI under "Address" some nodes appear to
> use 8098 as expected, but some appear to use random high port numbers
> such as 173.194.32.55:51265. These apparent port numbers also differ
> between the WUI:s of the different nodes. 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.

New description:

 In our friendnet all nodes are configured to use port 8098 as tub.port and
 in tub.location. This port is being forwarded through the firewalls of
 each node owner. Connectivity has been confirmed using nmap from the
 introducer node computer. In the WUI under "Address" some nodes appear to
 use 8098 as expected, but some appear to use random high port numbers such
 as 173.194.32.55:51265. These apparent port numbers also differ between
 the WUI:s of the different nodes. 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.

--

Comment:

 > 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?

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