[Bug]: localhostreachable1 toggle option should be added to Settings

未關閉
#952 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 6 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
25/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
c, cpp

研究方向

The payload names only the VBoxManage option --nat-localhostreachable1 as the existing switch for this behaviour, so start by finding where that option is parsed and stored for a VM's NAT settings. Then check whether the VirtualBox GUI settings panel already has a NAT network section where a checkbox could go. Done means the toggle is visible in VM settings, persists, and matches the VBoxManage behaviour. The issue has no maintainer reply yet, so confirm the approach before writing code.

由索引模型根據 Issue 內容生成。

描述

enhancement
Component

Network

What problem are you facing?

I wasted my work hours trying to understand why my Guest(10.0.2.15) cannot connect to Host(10.0.2.2)'s webserver:

  • ping 10.0.2.2 works,
  • but http://10.0.2.2/ does not.

Even AI could NOT help me - until I read tons of codes...

After running "<path/to/VBoxManage>" modifyvm "vmname" --nat-localhostreachable1 on I was able to reach host again.

WHY did you break Virtualbox behavior anyway!?

How can we fix this?

By adding "Allow connection to Host" in VM's Settings panel!

What alternatives or workarounds exist?

"<path/to/VBoxManage>" modifyvm "vmname" --nat-localhostreachable1 on

Anything else we should know?

No response

主要語言
C
星號
1.4k
分支
219
PR 合併指標
30 天內沒有已合併 PR

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

VirtualBox/virtualbox 的其他 Issue

查看 VirtualBox/virtualbox 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。