[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 摘要。