Skip to content

Add Tunnel Nodes system for managing remote nodes#5

Merged
ehsanking merged 2 commits into
mainfrom
v0/ehsankingehsan-9410-6ce78052
Apr 26, 2026
Merged

Add Tunnel Nodes system for managing remote nodes#5
ehsanking merged 2 commits into
mainfrom
v0/ehsankingehsan-9410-6ce78052

Conversation

@ehsanking
Copy link
Copy Markdown
Owner

  • Implemented a Tunnel Nodes system using Gost to enable remote node management.
  • Added a server_address field to the inbound configuration form for enhanced connectivity options.
  • Introduced database tables, migration scripts, and backend APIs to support node data persistence.
  • Updated project UI components to integrate remote node management and configuration.

v0 Session

v0 Bot and others added 2 commits April 26, 2026 22:05
Co-authored-by: Ehsan <1883051+ehsanking@users.noreply.github.com>
Add database table, API, UI component, and migration script for managing remote nodes.

Co-authored-by: Ehsan <1883051+ehsanking@users.noreply.github.com>
@ehsanking ehsanking added the v0 label Apr 26, 2026 — with Vercel
@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 26, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
power-vpn Error Error Open in v0 Apr 26, 2026 10:14pm

@ehsanking ehsanking merged commit 3f01db0 into main Apr 26, 2026
1 of 3 checks passed
@ehsanking ehsanking deleted the v0/ehsankingehsan-9410-6ce78052 branch April 26, 2026 22:15
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f690f2ec6a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +562 to +565
const remoteCommand = generateRemoteNodeCommand(node, mainServerIp || 'YOUR_MAIN_SERVER_IP', mainServerPort);
const mainCommand = generateMainServerCommand(
{ ip: mainServerIp || 'YOUR_MAIN_SERVER_IP', port: mainServerPort },
node.tunnel_type,
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Use each node's tunnel port in generated commands

The command modal currently builds both setup commands with mainServerPort, so the per-node tunnel_port collected and stored for each node is ignored. If a node is configured with a non-default tunnel port (or nodes use different ports), the generated gost commands point to the wrong listener and tunnel setup fails or conflicts on port reuse.

Useful? React with 👍 / 👎.

Comment on lines +29 to +30
SELECT * FROM tunnel_nodes
ORDER BY created_at DESC
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Exclude tunnel secrets from node list responses

The list endpoint selects and returns all columns from tunnel_nodes, which includes tunnel_secret. This secret is the relay authentication credential used in generated commands, so exposing it in a broad list response allows anyone with API access to impersonate a tunnel node. The listing should omit tunnel_secret and only return it through a narrowly scoped privileged flow.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant