Check the Networksection on Virtual box. It creates one virtual NIC by default.
That would be in your case enp0s3.
Yes of course, sorry I was being stupid. Sorry.
]]>I forget to mention that it is a USB wifi dongle (Tplink TL-WN722N). And I'm also running within virtualbox - I hope that does not complicate matters?
It changes matters - please mention such things in the original post.
Is the usb device being handed through into the virtual machine (ctrl+home -> usb devices)? You need it to show up in lsusb, then load the kernel modules if needed. <-- stupidity.. see the reply below.
]]>hokasch wrote:Check your chipset (lspci), see if the corresponding kernel module got loaded. Look for dmesg errors. Another way to check device names (from the wiki):
$ ls /sys/class/net
How do I check if the kernal module got loaded?
lspci | grep net
> only shows my ethernet controllerlsusb
> does not show it ethierI forget to mention that it is a USB wifi dongle (Tplink TL-WN722N). And I'm also running within virtualbox - I hope that does not complicate matters?
Probably. You'll need to make sure that VB guest can see your USB ports. You'll need the VB wiki pages for that though.
I don't use it, so can't help, sorry.
Check your chipset (lspci), see if the corresponding kernel module got loaded. Look for dmesg errors. Another way to check device names (from the wiki):
$ ls /sys/class/net
How do I check if the kernal module got loaded?
lspci | grep net
> only shows my ethernet controller
lsusb
> does not show it ethier
I forget to mention that it is a USB wifi dongle (Tplink TL-WN722N). And I'm also running within virtualbox - I hope that does not complicate matters?
]]>$ ls /sys/class/net
Am I missing something?
]]>ip link
It should be the one starting with "w".
]]>So the wiki says:
"After finishing the rest of this installation and rebooting, you can connect to the network with wifi-menu interface_name (where interface_name is the interface of your wireless chipset). "
How do I find out the name of my interface?
]]>