Opened 9 months ago

Last modified 9 months ago

#2803 new enhancement

Tunnel Manager index page improvement

Reported by: Reportage Owned by:
Priority: minor Milestone: undecided
Component: apps/i2ptunnel Version: 0.9.48
Keywords: i2ptunnel Cc: idk
Parent Tickets: Sensitive: no


  • Add button to restart individual tunnels in addition to start and stop buttons
  • Add button to delete individual tunnels to obviate the need to browse to the tunnel config page


Change History (2)

comment:1 Changed 9 months ago by zzz

Cc: idk added

Not in favor of restart, in fact I think we should remove the "restart all" button:

  • not clear why you would ever need to restart a tunnel
  • after changes over last few releases, almost all config changes either a) take effect immediately, or b) cannot be changed unless the tunnel is stopped, or c) are prevented after tunnel creation. In theory there shouldn't be any changes that can be made while a tunnel is running that don't take effect until after a restart. That's the goal anyway
  • if there's some state that can only be fixed by a tunnel restart, thats a bug we should fix, not add a restart button as a workaround

re: delete, that should be very rare, and one extra click isn't so bad. Seems like a delete button on the index page would lead to accidental deletions which could be really catastrophic… i.e. add more problems than it solves.

so neither one of these sounds like a good idea to me

comment:2 Changed 9 months ago by Reportage

A restart button would be useful in various contexts:

  • to immediately generate a new destination for a client tunnel
  • to activate configuration changes to a remote console, where stopping the server tunnel would sever the link to the console, preventing the tunnel from being restarted

I agree the 'restart all' button as is serves no useful purpose, given that it doesn't take into account the currently active tunnels. Perhaps this could be swapped out with a "restart all active" button which might arguably be marginally more useful, though maybe removal is a better bet, given the likelihood it's vary rarely used in practice.

As for a 'delete tunnel' button, without a confirmation prompt it could potentially be dangerous in the hands of the wrong person, I agree there. To ensure that the prompt is displayed, it would be conditional on javascript being active, and the button would be hidden in the event that it's not.

Note: See TracTickets for help on using tickets.