Opened at 2013-09-01T05:38:12Z

Last modified at 2013-09-09T20:40:26Z

#2073 new defect

Wrong ports are reported for connected nodes — at Version 1

Reported by: genell Owned by: daira
Priority: normal Milestone: undecided
Component: code-network Version: 1.10.0
Keywords: wui tub port foolscap firewall Cc:
Launchpad Bug:

Description (last modified by daira)

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.

Change History (1)

comment:1 Changed at 2013-09-01T15:51:42Z by daira

  • Component changed from unknown to code-network
  • Description modified (diff)
  • Keywords wui tub foolscap added; WUI removed
  • Summary changed from WUI: Wrong ports are reported for connected nodes to Wrong ports are reported for connected 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.

Is it possible that the node made a connection at some point but the connectivity has changed?

Note: See TracTickets for help on using tickets.