Changes between Initial Version and Version 1 of Ticket #2073


Ignore:
Timestamp:
2013-09-01T15:51:42Z (11 years ago)
Author:
daira
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?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2073

    • Property Keywords wui tub foolscap added; WUI removed
    • Property Component changed from unknown to code-network
    • Property Summary changed from WUI: Wrong ports are reported for connected nodes to Wrong ports are reported for connected nodes

  • Ticket #2073 – Description

    initial v1  
    11In 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.
    2 Especially this last case is somewhat troublesome as the node appears online, but cannot receive data. 
     2Especially this last case is somewhat troublesome as the node appears online, but cannot receive data.