Network issue

[jamichelli76]

I've been using a Kali machine on VB (hosted on Windows 10) for quite a while now.

For the network settings:

Enable Network Adapter (checked)
Attached to: NAT
Adapter Type: Intel PRO/1000 MT Desktop ((8254OEM)

This morning, I was doing a search on a website that only allows a certain number of requests from a single MAC/IP combination, so I've been switching between different VPN servers and changing the MAC address each time the server for this site kicks me off. It's been working well for me...up until about an hour ago. Suddenly, I had no network connection. I've tried switching the MAC address randomly in the settings, switching the MAC address manually to match what my host says the virtual MAC address should be for my virtual adapter...all to no avail.

Any help on how to get my network connection back up and running?

[scottgus1]

I've seen Linux in a VM not notice the change to the Virtualbox network. I don't know how to fix it though, without rebooting.

[jamichelli76]

I've seen Linux in a VM not notice the change to the Virtualbox network. I don't know how to fix it though, without rebooting.

I have rebooted...I've rebooted the VM numerous times, as well as rebooting the host machine, all without any change in the network connection.

Any other thoughts?

[scottgus1]

1. Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
   
   Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. In the "Logs" subfolder, zip the VM's "vbox.log", and post the zip file, using the forum's Upload Attachment tab.
2. Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. Zip the VM's .vbox file (not the .vbox-prev file), and post the zip file, using the forum's Upload Attachment tab. (Configure your host OS to show all extensions if the folder that opens does not show a .vbox file.)
3. In the Windows OS, open a Command Prompt and run ipconfig /all. Post the command output.
4. In the Linux OS, open a Terminal and run ifconfig or ip address. Post the command output.

[jamichelli76]

1. Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
   
   Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. In the "Logs" subfolder, zip the VM's "vbox.log", and post the zip file, using the forum's Upload Attachment tab.
2. Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. Zip the VM's .vbox file (not the .vbox-prev file), and post the zip file, using the forum's Upload Attachment tab. (Configure your host OS to show all extensions if the folder that opens does not show a .vbox file.)
3. In the Windows OS, open a Command Prompt and run ipconfig /all. Post the command output.
4. In the Linux OS, open a Terminal and run ifconfig or ip address. Post the command output.

From the Windows OS:

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-SK269S6
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Unknown adapter ProtonVPN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WireGuard Tunnel
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.2.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 0.0.0.0
DNS Servers . . . . . . . . . . . : 10.2.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Unknown adapter ProtonVPN TUN:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : ProtonVPN Tunnel
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) I211 Gigabit Network Connection
Physical Address. . . . . . . . . : 70-85-C2-A1-BA-25
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet 4:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 0A-00-27-00-00-18
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.214.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VirtualBox Host-Only Network #2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter #2
Physical Address. . . . . . . . . : 0A-00-27-00-00-19
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.220.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled

Unknown adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-ProtonVPN Windows Adapter V9
Physical Address. . . . . . . . . : 00-FF-DD-6B-65-B5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 30-24-32-8E-DB-E6
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 13:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physical Address. . . . . . . . . : 32-24-32-8E-DB-E5
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TeamViewer VPN Adapter
Physical Address. . . . . . . . . : 00-FF-0E-8A-E6-4B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 3168
Physical Address. . . . . . . . . : 30-24-32-8E-DB-E5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.0.208(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, November 27, 2022 10:20:54 AM
Lease Expires . . . . . . . . . . : Tuesday, November 29, 2022 1:14:47 PM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 68.105.28.11
68.105.29.11
68.105.28.12
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 30-24-32-8E-DB-E9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

From the Kali OS:

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.0.2.15 netmask 255.255.255.0 broadcast 10.0.2.255
inet6 fe80::a00fea9:aebf prefixlen 64 scopeid 0x20<link>
ether 08:00:27:a9:ae:bf txqueuelen 1000 (Ethernet)
RX packets 1 bytes 590 (590.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 13 bytes 1208 (1.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

ipv6leakintrf0: flags=195<UP,BROADCAST,RUNNING,NOARP> mtu 1500
inet6 fe80:1aa9:5318:84ef prefixlen 64 scopeid 0x20<link>
inet6 fdeb:446c:912d:8da:: prefixlen 64 scopeid 0x0<global>
ether b2:e2:bd:fb:47:c9 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 1048 bytes 114440 (111.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1048 bytes 114440 (111.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[scottgus1]

Your VM is on NAT and the Virtualbox 'cable' is connected.

The only thing I see that might be unusual is:

<Adapter slot="0" enabled="true" MACAddress="080027A9AEBF" type="82540EM">

inet6 fe80::a00:27ff:fea9:aebf prefixlen 64 scopeid 0x20<link>
ether 08:00:27:a9:ae:bf txqueuelen 1000 (Ethernet)

I don't know if the Linux IPv6 address is supposed to draw from the MAC address. Was this an intentional setting? If so it could be a problem. Typically, NAT-based networking sets the IP in the VM OS via DHCP. Changing from what DHCP sets may break network connectivity.

[fth0]

This morning, I was doing a search on a website that only allows a certain number of requests from a single MAC/IP combination, so I've been switching between different VPN servers and changing the MAC address each time the server for this site kicks me off.

Please elaborate on "the website", and on why you think that the website would see any IP or MAC address from within the VM or the PC. If you switch the VPN service, in effect you're changing the exit node of the VPN service that the website sees.

---

I don't know if the Linux IPv6 address is supposed to draw from the MAC address.

What you're seeing here is a standard link-local IPv6 address (fe80::/64) that an IPv6 endpoint gives itself, comparable to an IPv4 APIPA address. It is built from the MAC address using Modified EUI-64. Written in full, the IPv6 address corresponding to the MAC address 08:00:27:a9:ae:bf is fe80:0000:0000:0000:0a00:27ff:fea9:aebf.

[scottgus1]

What you're seeing here is a standard link-local IPv6 address

Thanks, fth0! I appreciate knowing this is normal. I have a lot more to learn about IPv6....