F5F Stay Refreshed Software Operating Systems The WSL2 machine isn't showing the complete ifconfig details or network adapter information.

The WSL2 machine isn't showing the complete ifconfig details or network adapter information.

The WSL2 machine isn't showing the complete ifconfig details or network adapter information.

T
Tropiko14
Member
201
06-21-2016, 02:11 AM
#1
Today I set up Kali Linux on a WSL2 device and it functions properly everywhere except for network connectivity. On a standard Linux system, when I type the ifconfig command in the terminal, it should display IP configuration details. However, on my setup, it doesn’t show any errors except for the Ethernet adapter being marked as disconnected. I need to troubleshoot why my internet isn't working despite everything else running fine.
T
Tropiko14
06-21-2016, 02:11 AM #1

Today I set up Kali Linux on a WSL2 device and it functions properly everywhere except for network connectivity. On a standard Linux system, when I type the ifconfig command in the terminal, it should display IP configuration details. However, on my setup, it doesn’t show any errors except for the Ethernet adapter being marked as disconnected. I need to troubleshoot why my internet isn't working despite everything else running fine.

P
packerfarr
Member
119
06-21-2016, 03:02 AM
#2
WSL2 operates as a virtual machine behind Hyper-V, featuring a Hyper-V network adapter attached. It's designed so you shouldn't notice these network adapters in WSL2.
P
packerfarr
06-21-2016, 03:02 AM #2

WSL2 operates as a virtual machine behind Hyper-V, featuring a Hyper-V network adapter attached. It's designed so you shouldn't notice these network adapters in WSL2.

T
TheYoanZ
Member
156
06-28-2016, 07:59 AM
#3
For Windows networking, switch to WSL1. It relies on a translator with constraints rather than a native micro-kernel in Hyper-V, making the network adapter virtual. The issue remains if you use a VPN for work or office environments. On WSL1, you can run the VPN on Windows and your Linux environment will connect normally. With WSL2, you’ll need to handle the VPN through your Linux distro, which may not work without proper support. If the company doesn’t offer Linux-compatible VPNs, using WSL2 becomes problematic.
T
TheYoanZ
06-28-2016, 07:59 AM #3

For Windows networking, switch to WSL1. It relies on a translator with constraints rather than a native micro-kernel in Hyper-V, making the network adapter virtual. The issue remains if you use a VPN for work or office environments. On WSL1, you can run the VPN on Windows and your Linux environment will connect normally. With WSL2, you’ll need to handle the VPN through your Linux distro, which may not work without proper support. If the company doesn’t offer Linux-compatible VPNs, using WSL2 becomes problematic.