Opened 7 years ago

Last modified 5 years ago

#1259 open defect

Recognize transition to completely blocked UDP

Reported by: zzz Owned by: zzz
Priority: minor Milestone: 0.9.28
Component: router/transport Version: 0.9.12
Keywords: Cc:
Parent Tickets: #1835 Sensitive: no


For unknown reasons, after 3 days of uptime, my UDP completely stopped working. Zero SSU peers.

Maybe a firewall glitch, maybe a router bug.

But SSU continued to advertised its address and claim "OK", because there were no SSU peers for peer testing ("UDPTransport: Unable to run a periodic test, as there are no peers with the capacity required"). SSU continued to bid for messages. CPU usage very high, presumably due to tunnel building. Known peer count went down to ~150. Still had participating tunnels. NTCP out and in was still working.

Router restart fixed it.

Version: 0.9.12-14

I think if it had been blocked at the beginning, net status would have stayed at "testing"?

Anyway, there may be a couple bugs here. But at the least, SSU should give up after some number of failed connections, or some time stuck at zero peers, or something. Where "give up" means disabling itself (mostly? completely?) and not bidding for messages. And not publishing an address.


Change History (4)

comment:1 Changed 7 years ago by zzz

Of course, if we implement a transition to some sort of "hosed" state, we also have to implement a transition back out of it, which could be even harder. So we couldn't completely shut off SSU, but just reject bids maybe 90% of the time.

comment:2 Changed 7 years ago by zzz


comment:3 Changed 6 years ago by str4d

Status: newopen

comment:4 Changed 5 years ago by zzz

Parent Tickets: 1835
Note: See TracTickets for help on using tickets.