关于【virtualbox】的问题- 第1页

testyAndro

Asked: 2022-09-29 06:48:26 +0800 CST

多个隔离虚拟机的 VirtualBox 网络设置，其中只有一个可以访问互联网

0

所以我想用VirtualBox创建一个虚拟黑客实验室。将有两种类型的机器。

攻击机器：Kali Linux
目标机器：这可以是任何类型的操作系统；Ubuntu、CentOS 等

我希望我的攻击机器能够访问互联网，并且它应该能够与目标机器通信。但是我的目标机器不应该有任何访问互联网或主机操作系统的权限，因为大多数时候它会包含一些恶意程序。这些目标机器也需要DHCP 服务器为它们分配 IP。基本上我想使用我的攻击机器（kali）攻击这些目标机器，希望我的攻击机器能够访问互联网但不是目标机器。目标 VM 将从 Internet 下载并启用 DHCP。有时我可能不得不为这些目标机器提供 Internet 访问权限，以便它们可以自我更新，但这种情况很少见。它有点复杂，我无法弄清楚自己，所以我在这里问。

谢谢。

q0987

Asked: 2022-02-22 07:23:24 +0800 CST

如何使用 Windows 中的智能 websocket 客户端连接到 virtualbox 上正在运行的 websocket 服务器？

1

这是我的设置：

VirtuablBox 6.0 中的 Windows 8.1 和 Ubuntu 18.04
在 VirtuablBox 中的 127.0.0.1:8083 处运行 websocket 服务器
在 VirtuablBox 中，我可以连接到 websocket 服务器websocat ws://127.0.0.1:8083

为了让我通过在 Windows 主机上运行的 Chrome 扩展（即智能 Websocket 客户端）连接到 websocket 服务器，我应该使用什么设置。

我尝试在 Smart Websocket Client 中连接到“127.0.01:8083”，但显示错误：

构造“WebSocket”失败：URL“127.0.01:8083”无效。

谢谢

Marat Gainutdinov

Asked: 2021-11-12 00:48:38 +0800 CST

使用 TAP 设备在 Linux 上桥接（Virtualbox）

0

使用 TAP 设备在 Linux 上桥接

您好，我有以下架构：

为了能够 ping 远程主机，在我的情况下是分离主机 1，我启动了桥接设备 br0，它在服务器上结合了 tap0 + eth2，并将本地网络（192.168.111.0/24）与远程 openvpn 客户端（vpn2）桥接，但是仍然没有运气，请你建议我做错了什么

我可以 ping：vpn1 -> vpn2 vpn2 -> vpn1 vpn1 -> separatehost1 我无法从 vpn2（客户端）ping 单独的host1，反之亦然（目标主机无法访问）。

服务器配置文件

#Server config
proto udp
port 1194
persist-key
persist-tun
keepalive 10 60
tls-auth /etc/openvpn/movpn/ta.key 0
remote-cert-tls client
dh /etc/openvpn/movpn/dh2048.pem
ca /etc/openvpn/movpn/ca.crt
cert /etc/openvpn/movpn/server.crt
key /etc/openvpn/movpn/server.key
user nobody
group nogroup
# use ‘group nogroup’ on Debian/Ubuntu
verb 3
daemon
log-append /var/log/openvpn.log
#client-to-client
dev tap0
server-bridge 192.168.111.101 255.255.255.0 192.168.111.128 192.168.111.200

所有模式都是使用 Vagrantfile + net.ipv4.ip_forward = 1 创建的。

调出br0界面的脚本：

 #!/bin/bash
 br="br0"
 tap="tap0"
 eth="eth2"
 br_ip="192.168.111.101"
 br_netmask="255.255.255.0"
 br_broadcast="192.168.111.255"
 # Create the tap adapter
 openvpn --mktun --dev $tap
 # Create the bridge and add interfaces
 brctl addbr $br
 brctl addif $br $eth
 brctl addif $br $tap
 # Configure the bridge
 ifconfig $tap 0.0.0.0 promisc up
 ifconfig $eth 0.0.0.0 promisc up
 ifconfig $br $br_ip netmask $br_netmask broadcast $br_broadcast

根据我的故障排除，服务器没有将icmp数据包转发到separatehost1，我不知道为什么......

root@vpn1:/etc/openvpn/movpn# ip -d link show br0
12: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 08:00:27:6c:77:40 brd ff:ff:ff:ff:ff:ff promiscuity 0 
    bridge forward_delay 1500 hello_time 200 max_age 2000 ageing_time 30000 stp_state 0 priority 32768 vlan_filtering 0 vlan_protocol 802.1Q bridge_id 8000.8:0:27:6c:77:40 designated_root 8000.8:0:27:6c:77:40 root_port 0 root_path_cost 0 topology_change 0 topology_change_detected 0 hello_timer    0.00 tcn_timer    0.00 topology_change_timer    0.00 gc_timer  150.00 vlan_default_pvid 1 vlan_stats_enabled 0 group_fwd_mask 0 group_address 01:80:c2:00:00:00 mcast_snooping 1 mcast_router 1 mcast_query_use_ifaddr 0 mcast_querier 0 mcast_hash_elasticity 4 mcast_hash_max 512 mcast_last_member_count 2 mcast_startup_query_count 2 mcast_last_member_interval 100 mcast_membership_interval 26000 mcast_querier_interval 25500 mcast_query_interval 12500 mcast_query_response_interval 1000 mcast_startup_query_interval 3124 mcast_stats_enabled 0 mcast_igmp_version 2 mcast_mld_version 1 nf_call_iptables 0 nf_call_ip6tables 0 nf_call_arptables 0 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 
root@vpn1:/etc/openvpn/movpn# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 08:00:27:b4:26:99 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 08:00:27:db:97:af brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP mode DEFAULT group default qlen 1000
    link/ether 08:00:27:6c:77:40 brd ff:ff:ff:ff:ff:ff
11: tap0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP mode DEFAULT group default qlen 100
    link/ether d6:df:32:8a:b0:5e brd ff:ff:ff:ff:ff:ff
12: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 08:00:27:6c:77:40 brd ff:ff:ff:ff:ff:ff

root@separatehosts1:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 08:00:27:b4:26:99 brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic eth0
       valid_lft 76182sec preferred_lft 76182sec
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 08:00:27:a5:4b:55 brd ff:ff:ff:ff:ff:ff
    inet 192.168.111.102/24 brd 192.168.111.255 scope global eth1
       valid_lft forever preferred_lft forever

root@vpn1:/etc/openvpn/movpn# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 08:00:27:b4:26:99 brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic eth0
       valid_lft 75325sec preferred_lft 75325sec
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 08:00:27:db:97:af brd ff:ff:ff:ff:ff:ff
    inet 192.168.33.101/24 brd 192.168.33.255 scope global eth1
       valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP group default qlen 1000
    link/ether 08:00:27:6c:77:40 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::a00:27ff:fe6c:7740/64 scope link 
       valid_lft forever preferred_lft forever
11: tap0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP group default qlen 100
    link/ether d6:df:32:8a:b0:5e brd ff:ff:ff:ff:ff:ff
12: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 08:00:27:6c:77:40 brd ff:ff:ff:ff:ff:ff
    inet 192.168.111.101/24 brd 192.168.111.255 scope global br0
       valid_lft forever preferred_lft forever
root@vpn2:/etc/openvpn/movpn# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 08:00:27:b4:26:99 brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic eth0
       valid_lft 75777sec preferred_lft 75777sec
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 08:00:27:d8:ad:47 brd ff:ff:ff:ff:ff:ff
    inet 192.168.33.102/24 brd 192.168.33.255 scope global eth1
       valid_lft forever preferred_lft forever
9: tap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 100
    link/ether 2a:2f:98:b3:34:81 brd ff:ff:ff:ff:ff:ff
    inet 192.168.111.128/24 brd 192.168.111.255 scope global tap0
       valid_lft forever preferred_lft forever

Marcell Bernát

Asked: 2021-05-12 03:15:04 +0800 CST

Dmesg 在 Ubuntu 18.04 VM 上充满了 I/O 错误，物理磁盘和主机都很好

2

我在 Windows Server 2016 主机（Dell PowerEdge R530，Intel Xeon E5-2620 @ 2.1GHz，96GB RAM）上有一个 Ubuntu 18.04 虚拟机，在 VirtualBox 6.1.10 中运行。主机系统通过 PERC H730 Mini 控制器在 RAID 1 中有 2x2TB 硬盘驱动器。VM 运行一个 Elasticsearch 节点和一些其他用于处理传入数据的软件。它有两个连接到它的虚拟磁盘（155GB、1.5TB），但它只有第二个正在运行。几个月前它都很好，但最近它开始看似随机地抛出 I/O 错误。

这是昨天的一些 dmesg 输出：

[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:40:00:09:41/00:05:16:00:00/e0 tag 21 dma 688128 out
                                   res 41/10:40:00:09:41/00:05:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:c0:40:0e:41/00:02:16:00:00/e0 tag 15 dma 360448 out
                                   res 41/10:c0:40:0e:41/00:02:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:40:00:11:41/00:05:16:00:00/e0 tag 31 dma 688128 out
                                   res 41/10:40:00:11:41/00:05:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:40:00:09:41/00:05:16:00:00/e0 tag 7 dma 688128 out
                                   res 41/10:40:00:09:41/00:05:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:c0:40:0e:41/00:02:16:00:00/e0 tag 15 dma 360448 out
                                   res 41/10:c0:40:0e:41/00:02:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:40:00:11:41/00:05:16:00:00/e0 tag 23 dma 688128 out
                                   res 41/10:40:00:11:41/00:05:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:40:00:09:41/00:05:16:00:00/e0 tag 0 dma 688128 out
                                   res 41/10:40:00:09:41/00:05:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:c0:40:0e:41/00:02:16:00:00/e0 tag 8 dma 360448 out
                                   res 41/10:c0:40:0e:41/00:02:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:40:00:11:41/00:05:16:00:00/e0 tag 16 dma 688128 out
                                   res 41/10:40:00:11:41/00:05:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:40:00:09:41/00:05:16:00:00/e0 tag 31 dma 688128 out
                                   res 41/10:40:00:09:41/00:05:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:c0:40:0e:41/00:02:16:00:00/e0 tag 7 dma 360448 out
                                   res 41/10:c0:40:0e:41/00:02:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:40:00:11:41/00:05:16:00:00/e0 tag 17 dma 688128 out
                                   res 41/10:40:00:11:41/00:05:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:40:00:09:41/00:05:16:00:00/e0 tag 25 dma 688128 out
                                   res 41/10:40:00:09:41/00:05:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:c0:40:0e:41/00:02:16:00:00/e0 tag 2 dma 360448 out
                                   res 41/10:c0:40:0e:41/00:02:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:40:00:11:41/00:05:16:00:00/e0 tag 10 dma 688128 out
                                   res 41/10:40:00:11:41/00:05:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:40:00:09:41/00:05:16:00:00/e0 tag 18 dma 688128 out
                                   res 41/10:40:00:09:41/00:05:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] sd 3:0:0:0: [sdb] tag#18 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[Mon May 10 20:37:04 2021] sd 3:0:0:0: [sdb] tag#18 Sense Key : Illegal Request [current]
[Mon May 10 20:37:04 2021] sd 3:0:0:0: [sdb] tag#18 Add. Sense: Logical block address out of range
[Mon May 10 20:37:04 2021] sd 3:0:0:0: [sdb] tag#18 CDB: Write(10) 2a 00 16 41 09 00 00 05 40 00
[Mon May 10 20:37:04 2021] blk_update_request: I/O error, dev sdb, sector 373360896 op 0x1:(WRITE) flags 0x4000 phys_seg 168 prio class 0
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:c0:40:0e:41/00:02:16:00:00/e0 tag 1 dma 360448 out
                                   res 41/10:c0:40:0e:41/00:02:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] sd 3:0:0:0: [sdb] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[Mon May 10 20:37:04 2021] sd 3:0:0:0: [sdb] tag#1 Sense Key : Illegal Request [current]
[Mon May 10 20:37:04 2021] sd 3:0:0:0: [sdb] tag#1 Add. Sense: Logical block address out of range
[Mon May 10 20:37:04 2021] sd 3:0:0:0: [sdb] tag#1 CDB: Write(10) 2a 00 16 41 0e 40 00 02 c0 00
[Mon May 10 20:37:04 2021] blk_update_request: I/O error, dev sdb, sector 373362240 op 0x1:(WRITE) flags 0x0 phys_seg 88 prio class 0
[Mon May 10 20:37:04 2021] EXT4-fs warning (device sdb1): ext4_end_bio:315: I/O error 10 writing to inode 10095089 (offset 8388608 size 1871872 starting block 46670368)
[Mon May 10 20:37:04 2021] Buffer I/O error on device sdb1, logical block 46669856
[Mon May 10 20:37:04 2021] Buffer I/O error on device sdb1, logical block 46669857
[Mon May 10 20:37:04 2021] Buffer I/O error on device sdb1, logical block 46669858
[Mon May 10 20:37:04 2021] Buffer I/O error on device sdb1, logical block 46669859
[Mon May 10 20:37:04 2021] Buffer I/O error on device sdb1, logical block 46669860
[Mon May 10 20:37:04 2021] Buffer I/O error on device sdb1, logical block 46669861
[Mon May 10 20:37:04 2021] Buffer I/O error on device sdb1, logical block 46669862
[Mon May 10 20:37:04 2021] Buffer I/O error on device sdb1, logical block 46669863
[Mon May 10 20:37:04 2021] Buffer I/O error on device sdb1, logical block 46669864
[Mon May 10 20:37:04 2021] Buffer I/O error on device sdb1, logical block 46669865
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:40:00:11:41/00:05:16:00:00/e0 tag 7 dma 688128 out
                                   res 41/10:40:00:11:41/00:05:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] sd 3:0:0:0: [sdb] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[Mon May 10 20:37:04 2021] sd 3:0:0:0: [sdb] tag#7 Sense Key : Illegal Request [current]
[Mon May 10 20:37:04 2021] sd 3:0:0:0: [sdb] tag#7 Add. Sense: Logical block address out of range
[Mon May 10 20:37:04 2021] sd 3:0:0:0: [sdb] tag#7 CDB: Write(10) 2a 00 16 41 11 00 00 05 40 00
[Mon May 10 20:37:04 2021] blk_update_request: I/O error, dev sdb, sector 373362944 op 0x1:(WRITE) flags 0x4000 phys_seg 168 prio class 0
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:04 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:04 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:04 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:04 2021] ata4.00: cmd 35/00:08:40:16:41/00:01:16:00:00/e0 tag 13 dma 135168 out
                                   res 41/10:08:40:16:41/00:01:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:04 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:04 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:04 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:04 2021] ata4: EH complete
[Mon May 10 20:37:05 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:05 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:05 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:05 2021] ata4.00: cmd 35/00:08:40:16:41/00:01:16:00:00/e0 tag 30 dma 135168 out
                                   res 41/10:08:40:16:41/00:01:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:05 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:05 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:05 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:05 2021] ata4: EH complete
[Mon May 10 20:37:05 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:05 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:05 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:05 2021] ata4.00: cmd 35/00:08:40:16:41/00:01:16:00:00/e0 tag 5 dma 135168 out
                                   res 41/10:08:40:16:41/00:01:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:05 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:05 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:05 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:05 2021] ata4: EH complete
[Mon May 10 20:37:05 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:05 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:05 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:05 2021] ata4.00: cmd 35/00:08:40:16:41/00:01:16:00:00/e0 tag 28 dma 135168 out
                                   res 41/10:08:40:16:41/00:01:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:05 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:05 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:05 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:05 2021] ata4: EH complete
[Mon May 10 20:37:05 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:05 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:05 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:05 2021] ata4.00: cmd 35/00:08:40:16:41/00:01:16:00:00/e0 tag 19 dma 135168 out
                                   res 41/10:08:40:16:41/00:01:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:05 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:05 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:05 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:05 2021] ata4: EH complete
[Mon May 10 20:37:05 2021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Mon May 10 20:37:05 2021] ata4.00: irq_stat 0x40000000
[Mon May 10 20:37:05 2021] ata4.00: failed command: WRITE DMA EXT
[Mon May 10 20:37:05 2021] ata4.00: cmd 35/00:08:40:16:41/00:01:16:00:00/e0 tag 11 dma 135168 out
                                   res 41/10:08:40:16:41/00:01:16:00:00/e0 Emask 0x81 (invalid argument)
[Mon May 10 20:37:05 2021] ata4.00: status: { DRDY ERR }
[Mon May 10 20:37:05 2021] ata4.00: error: { IDNF }
[Mon May 10 20:37:05 2021] ata4.00: configured for UDMA/133
[Mon May 10 20:37:05 2021] sd 3:0:0:0: [sdb] tag#11 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[Mon May 10 20:37:05 2021] sd 3:0:0:0: [sdb] tag#11 Sense Key : Illegal Request [current]
[Mon May 10 20:37:05 2021] sd 3:0:0:0: [sdb] tag#11 Add. Sense: Logical block address out of range
[Mon May 10 20:37:05 2021] sd 3:0:0:0: [sdb] tag#11 CDB: Write(10) 2a 00 16 41 16 40 00 01 08 00
[Mon May 10 20:37:05 2021] blk_update_request: I/O error, dev sdb, sector 373364288 op 0x1:(WRITE) flags 0x0 phys_seg 33 prio class 0
[Mon May 10 20:37:05 2021] EXT4-fs warning (device sdb1): ext4_end_bio:315: I/O error 10 writing to inode 10095089 (offset 8388608 size 1871872 starting block 46670569)
[Mon May 10 20:37:05 2021] ata4: EH complete
[Mon May 10 20:37:05 2021] JBD2: Detected IO errors while flushing file data on sdb1-8

HD Sentinel 报告说两个磁盘都很好，我在 SMART 数据中看不到任何问题。通过 iDRAC 进行的诊断没有发现任何东西，RAID 控制器及其电池都很好。

谷歌提出的所有问题都指向物理硬盘故障或 Hyper-V 问题，但这是一个虚拟磁盘，Hyper-V 已禁用。也许它与VirtualBox的设置有关？它在相同的设置下运行了几个月。毕竟，也许它是控制器？

一些关于如何继续追查这个问题的根源的指示将不胜感激。

fared

Asked: 2021-04-04 12:22:24 +0800 CST

Apache SSL 代理通行证不起作用，但它与 VirtualBox NAT 端口转发有关

1

我在端口 80 和 443 上配置了 Apache 代理传递。端口 80 有效，但对于 443，我似乎没有得到任何响应。从我的公共 ip 我没有得到服务器的响应。这是我在文件中获得的虚拟主机配置httpd-vhost.conf

这按预期工作

<VirtualHost *:80>
    ServerName subdomain.example.com
    ServerAlias subdomain.example.com

    SSLProxyCheckPeerName Off

    ProxyPreserveHost On
    ProxyRequests Off
    ProxyPass / http://{LOCAL_IP}/
    ProxyPassReverse / http://{LOCAL_IP}/    
</VirtualHost>

这不起作用。

<VirtualHost *:443>
    ServerName subdomain.example.com
    ServerAlias subdomain.example.com
    SSLEngine On
    SSLProxyEngine On
    SSLProxyCheckPeerCN On    
    SSLProxyCheckPeerName Off

    SSLCertificateFile C:\{PATH_TO_CERTS}\cert.pem
    SSLCertificateKeyFile C:\{PATH_TO_KEY}\key.pem
    ProxyPreserveHost On
    ProxyRequests Off
    ProxyPass / https://{LOCAL_IP}/
    ProxyPassReverse / https://{LOCAL_IP}/
</VirtualHost>

但出于测试目的，我设置了一个 VirtualBox 环境 NAT 用于端口转发。并从本机443端口转发到虚拟机443端口；并且站点确实在端口 443 中工作。

我错过了我没有配置的东西吗？

Pedro L.

Asked: 2021-03-15 08:29:22 +0800 CST

在 `VBoxManage guestcontrol run` 中设置工作目录

1

我在用着：

VBoxManage guestcontrol "Windows 10" --username "john" run "Z:\\path\\to\\bin.exe"

该命令被执行，但我需要在指定目录中运行它。

有没有办法设置工作目录VBoxManage guestcontrol run？

Wolf

Asked: 2021-03-10 05:23:24 +0800 CST

vboxmanage dhcpserver 添加但客户端无法获取 DHCP ip

0

这是我在主机操作系统中使用的命令，不幸的是客户操作系统仍然无法获取 DHCP ip。

两个操作系统都在 Linux 中运行。

wolf@linux:~$ vboxmanage dhcpserver add --network=malfoy --server-ip=10.38.1.1 --lower-ip=10.38.1.110 --upper-ip=10.38.1.120 --netmask=255.255.255.0 --enable
wolf@linux:~$

确认

wolf@linux:~$ vboxmanage list dhcpservers
NetworkName:    malfoy
Dhcpd IP:       10.38.1.1
LowerIPAddress: 10.38.1.110
UpperIPAddress: 10.38.1.120
NetworkMask:    255.255.255.0
Enabled:        Yes
Global Configuration:
    minLeaseTime:     default
    defaultLeaseTime: default
    maxLeaseTime:     default
    Forced options:   None
    Suppressed opts.: None
        1/legacy: 255.255.255.0
Groups:               None
Individual Configs:   None
wolf@linux:~$

来宾操作系统

guestOS$ ip a s enp0s3
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 08:00:27:aa:aa:aa brd ff:ff:ff:ff:ff:ff
guestOS$ 

guestOS$ sudo dhclient enp0s3 -v
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/enp0s3/08:00:27:aa:aa:aa
Sending on   LPF/enp0s3/08:00:27:aa:aa:aa
Sending on   Socket/fallback
DHCPDISCOVER on enp0s3 to 255.255.255.255 port 67 interval 3 (xid=0xc1337)
DHCPDISCOVER on enp0s3 to 255.255.255.255 port 67 interval 7 (xid=0xc1337)
DHCPDISCOVER on enp0s3 to 255.255.255.255 port 67 interval 10 (xid=0xc1337)
...
DHCPDISCOVER on enp0s3 to 255.255.255.255 port 67 interval 8 (xid=0xc1337)
DHCPDISCOVER on enp0s3 to 255.255.255.255 port 67 interval 11 (xid=0xc1337)
DHCPDISCOVER on enp0s3 to 255.255.255.255 port 67 interval 14 (xid=0xc1337)
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
guestOS$

参考：

https://progmar.net.pl/en/knowledge-base/virtualbox-adding-dhcp-server

https://www.youtube.com/watch?v=mvsiuLzpx2E

如何解决此问题？

Rajiv

Asked: 2020-12-13 19:33:12 +0800 CST

通过 Windows 10 客户端通过 Windows Server 2012 ping 8.8.8.8 会出现请求超时错误

-1

这是我在 virtualbox 中的设置。

范围为 112.123.1.100 到 112.123.3.188 的 DHCP 范围，长度 = 16，路由器 IP 为 112.123.2.2（这也是配置 DHCP 的服务器的 IP）。

在此之后，我将 Windows Server 2012 的 IP 手动设置为 IP：112.123.2.2。子网：255.255.0.0 网关 = 10.0.2.2 DNS1：10.0.2.2 DNS2：8.8.8.8

运行服务器的这个 virtualbox VM 位于内部 NAT 网络类型上。为了访问互联网，我按照本指南将第二个适配器配置为 NAT 类型：https ://www.nakivo.com/blog/virtualbox-network-setting-guide/

服务器可以 Ping google.com，因此它可以访问 Internet。

客户端：

我将 VM 配置为内部 NAT 类型。现在我将我的 IP 地址设置为： IP：112.123.3.95 子网：255.255.0.0 网关：112.123.2.2

DNS1：112.123.2.2 DNS2：8.8.8.8

之后，在 Windows 10 Pro 的 VM 中，我加入了服务器域（工作组）。

当我从客户端 ping 服务器时，我在 CMD 中得到响应，但是当我 ping 8.8.8.8 时，我在 CMD 中收到“请求超时”消息。

有谁知道我做错了什么？同样，所有这些都发生在 VM 的关闭 virtualBox 内。

编辑：忘了提到客户端确实可以ping服务器但服务器由于某种原因无法ping客户端，但客户端能够加入服务器工作组/域。所以我不知道那里发生了什么。

Tabz

Asked: 2020-12-13 00:25:02 +0800 CST

无法访问在 VirtualBox 和远程机器上运行的 Ubuntu Server

-1

我在 VirtualBox 上安装了一个 Ubuntu 20.04.1 服务器作为 VM，这个 VirtualBox 在我学校的远程服务器上运行并安装GNS3在这个 VM（Ubuntu 服务器）上。到目前为止，一切都很好。但是当我尝试使用我的本地机器（MacOS Catalina）并TunnelBlick连接到这个远程服务器时，我得到了错误：TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity).

到目前为止，在阅读了几个答案之后，已经尝试过：

从本地 Macnc -uvz <remote server IP/also VM IP> 1194成功！
检查client.ovpn，正确的远程IP在那里。
可以scp使用公共 IP 在主机和 VM 之间进行 - 这意味着 VM 的 IP 是正确的并且可以访问。
卸载并安装GNS3了几次并更新了配置文件。

请帮我解决一下这个。

Cipher

Asked: 2020-11-06 02:23:24 +0800 CST

仅主机适配器虚拟框

0

我的主机是arch linux。我和客人有相同的arch linux。仅使用主机适配器和 nat 连接。在主机适配器设置中，为客人手动分配 IP。

从客人我可以访问主机，但从主机我不能访问客人。

主持人 - -

ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 20:1a:06:1f:b7:ad brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether f8:2f:a8:ed:d7:a5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.6/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp2s0
       valid_lft 83103sec preferred_lft 83103sec
    inet6 fe80::b2d9:237f:aec4:181/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
10: vboxnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
    inet 192.168.56.1/24 brd 192.168.56.255 scope global vboxnet0
       valid_lft forever preferred_lft forever
    inet6 fe80::800:27ff:fe00:0/64 scope link 
       valid_lft forever preferred_lft forever

ping 192.168.56.8                                                                                                                           3s
PING 192.168.56.8 (192.168.56.8) 56(84) bytes of data.
From 192.168.56.1 icmp_seq=1 Destination Host Unreachable
From 192.168.56.1 icmp_seq=2 Destination Host Unreachable
From 192.168.56.1 icmp_seq=3 Destination Host Unreachable
^C
--- 192.168.56.8 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4123ms

来宾 - -

ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 08:00:27:04:81:09 brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic noprefixroute enp0s3
       valid_lft 83209sec preferred_lft 83209sec
    inet6 fe80::ebdc:629a:ea5:dc7a/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: enp0s8: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 08:00:27:ed:d3:c9 brd ff:ff:ff:ff:ff:ff
    inet 192.168.56.8/24 brd 192.168.56.255 scope global enp0s8
       valid_lft forever preferred_lft forever

ping 192.168.56.1

PING 192.168.56.1 (192.168.56.1) 56(84) bytes of data.
64 bytes from 192.168.56.1: icmp_seq=1 ttl=63 time=0.512 ms
64 bytes from 192.168.56.1: icmp_seq=2 ttl=63 time=0.560 ms
64 bytes from 192.168.56.1: icmp_seq=3 ttl=63 time=0.474 ms
^C
--- 192.168.56.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2032ms
rtt min/avg/max/mdev = 0.474/0.515/0.560/0.035 ms

多个隔离虚拟机的 VirtualBox 网络设置，其中只有一个可以访问互联网

如何使用 Windows 中的智能 websocket 客户端连接到 virtualbox 上正在运行的 websocket 服务器？

使用 TAP 设备在 Linux 上桥接（Virtualbox）

Dmesg 在 Ubuntu 18.04 VM 上充满了 I/O 错误，物理磁盘和主机都很好

Apache SSL 代理通行证不起作用，但它与 VirtualBox NAT 端口转发有关

在 `VBoxManage guestcontrol run` 中设置工作目录

vboxmanage dhcpserver 添加但客户端无法获取 DHCP ip

通过 Windows 10 客户端通过 Windows Server 2012 ping 8.8.8.8 会出现请求超时错误

无法访问在 VirtualBox 和远程机器上运行的 Ubuntu Server

仅主机适配器虚拟框

新安装后 postgres 的默认超级用户用户名/密码是什么？

SFTP 使用什么端口？

命令行列出 Windows Active Directory 组中的用户？

什么是 Pem 文件，它与其他 OpenSSL 生成的密钥文件格式有何不同？

如何确定bash变量是否为空？

问题[virtualbox](server)