mirror of
https://github.com/ConvoyPanel/panel.git
synced 2026-04-25 20:55:50 +03:00
[GH-ISSUE #57] NAT VM Deployment #40
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/panel#40
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Hostrdp on GitHub (Dec 5, 2023).
Original GitHub issue: https://github.com/ConvoyPanel/panel/issues/57
Is there an existing feature request for this?
Describe the feature you would like to see.
Ability to auto deploy NAT VM using NAT IP that assigned on the node
Ability to auto configure port forwarding (SSH if Linux, RDP if Windows + HTTP and HTTPS ports) and assigns 20 ports for usages
Describe the solution you'd like.
Maybe using combinations Proxmox API and Iptables scripts
Additional context to this request.
No response
@ericwang401 commented on GitHub (Dec 5, 2023):
How will port forwarding work exactly if a port that is needed among all the VMs can only be allocated to a single VM?
@TeYroXOfficial commented on GitHub (Dec 5, 2023):
For example VM will get 20 ports, let's say from 59200->59220, so first port of this range will be set to 22/3389 of vm internal
For example:
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 59200 -j DNAT --to 192.168.100.1:22
Where 192.168.100.1 is a local IP's are assigned from NAT IP block
@ericwang401 commented on GitHub (Dec 5, 2023):
There seems to be a load of work cut out for this to be implemented, which is something above my pay grade.