Realtek Wifi 8822ce Kali Linux driver help

Repo1o1

New Member
Credits
169
Kali is not intended for normal desktop usage, you are better of using a distribution such as Ubuntu or Mint for desktop usage.

Share the output of the following.
Code:
apt-cache search image | grep ^linux
apt-cache search headers | grep ^linux
└─$ apt-cache search image | grep ^linux 1 ⨯
linux-base - Linux image base package
linux-headers-5.10.0-kali3-amd64 - Header files for Linux 5.10.0-kali3-amd64
linux-headers-5.10.0-kali3-cloud-amd64 - Header files for Linux 5.10.0-kali3-cloud-amd64
linux-headers-5.10.0-kali3-rt-amd64 - Header files for Linux 5.10.0-kali3-rt-amd64
linux-image-5.10.0-kali3-amd64 - Linux 5.10 for 64-bit PCs
linux-image-5.10.0-kali3-amd64-dbg - Debug symbols for linux-image-5.10.0-kali3-amd64
linux-image-5.10.0-kali3-cloud-amd64 - Linux 5.10 for x86-64 cloud
linux-image-5.10.0-kali3-cloud-amd64-dbg - Debug symbols for linux-image-5.10.0-kali3-cloud-amd64
linux-image-5.10.0-kali3-rt-amd64 - Linux 5.10 for 64-bit PCs, PREEMPT_RT
linux-image-5.10.0-kali3-rt-amd64-dbg - Debug symbols for linux-image-5.10.0-kali3-rt-amd64
linux-image-amd64 - Linux for 64-bit PCs (meta-package)
linux-image-amd64-dbg - Debugging symbols for Linux amd64 configuration (meta-package)
linux-image-cloud-amd64 - Linux for x86-64 cloud (meta-package)
linux-image-cloud-amd64-dbg - Debugging symbols for Linux cloud-amd64 configuration (meta-package)
linux-image-rt-amd64 - Linux for 64-bit PCs (meta-package)
linux-image-rt-amd64-dbg - Debugging symbols for Linux rt-amd64 configuration (meta-package)


└─$ apt-cache search headers | grep ^linux
linux-headers-5.10.0-kali3-amd64 - Header files for Linux 5.10.0-kali3-amd64
linux-headers-5.10.0-kali3-cloud-amd64 - Header files for Linux 5.10.0-kali3-cloud-amd64
linux-headers-5.10.0-kali3-common - Common header files for Linux 5.10.0-kali3
linux-headers-5.10.0-kali3-common-rt - Common header files for Linux 5.10.0-kali3-rt
linux-headers-5.10.0-kali3-rt-amd64 - Header files for Linux 5.10.0-kali3-rt-amd64
linux-headers-amd64 - Header files for Linux amd64 configuration (meta-package)
linux-headers-cloud-amd64 - Header files for Linux cloud-amd64 configuration (meta-package)
linux-headers-rt-amd64 - Header files for Linux rt-amd64 configuration (meta-package)
linux-kbuild-5.10 - Kbuild infrastructure for Linux 5.10
linux-libc-dev - Linux support headers for userspace development
linux-libc-dev-alpha-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-amd64-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-arm64-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-armel-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-armhf-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-hppa-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-i386-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-m68k-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mips-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mips64-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mips64el-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mips64r6-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mips64r6el-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mipsel-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mipsn32-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mipsn32el-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mipsn32r6-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mipsn32r6el-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mipsr6-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mipsr6el-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-powerpc-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-ppc64-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-ppc64el-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-riscv64-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-s390x-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-sh4-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-sparc64-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-x32-cross - Linux Kernel Headers for development (for cross-compiling)
s
 


f33dm3bits

Gold Member
Gold Supporter
Credits
17,920
Then do try this first.
Code:
sudo apt-get install linux-image-5.10.0-kali3-amd64 linux-headers-5.10.0-kali3-amd64 bc git
Then reboot, log back into your system and continue from step 4 in my previous post.

Maybe thats right.
I´m going into pentesting.
You should learn the basics of how to operate the system you are using before even touching any pen-testing tools.
 
Last edited:

Repo1o1

New Member
Credits
169
Then do try this first.
Code:
sudo apt-get install linux-image-5.10.0-kali3-amd64 linux-headers-5.10.0-kali3-amd64 bc git
Then reboot, log back into your system and continue from step 4 in my previous post.


You show learn the basics of how to operate the system you are using before even touching any pen-testing tools.
Did went until step 9.

"sudo: dkms: command not found"
 

f33dm3bits

Gold Member
Gold Supporter
Credits
17,920
Install dkms and then try it from step 9 again.
Code:
sudo apt-get install dkms
 

f33dm3bits

Gold Member
Gold Supporter
Credits
17,920
I didn't read your first post because I only jumped in half way into the topic, I just read your first post and saw that you have Kali installed in a virtual machine. From your virtualization software you are going to have to assign the wireless network interface to your virtual machine before your virtual machine can see it and it can't be in use by your host machine.
Checked again with "ip addr" but still no eth1 Realtek device
ethX are only used for ethernet interfaces not for wireless interfaces, wireless interfaces will usually have a name like wlan0, wlp1s0 or wlp2s0..etc.
 
Last edited:

Repo1o1

New Member
Credits
169
I didn't read your first post because I only jumped in half way into the topic, I just read your first post and saw that you have Kali installed in a virtual machine. From your virtualization software you are going to have to assign the wireless network interface to your virtual machine before your virtual machine can see it and it can't be in use by your host machine.

ethX are only used for ethernet interfaces not for wireless interfaces, wireless interfaces will usually have a name like wlan0, wlp1s0 or wlp2s0..etc.
So using a wireless network card will be not possible in a vm?

Therefore I need to get a second usb plug in wireless network adapter to get to run it in a vm?

But how does the vm get internet connecntion?
 

wizardfromoz

Super Moderator
Staff member
Gold Supporter
Credits
15,484

f33dm3bits

Gold Member
Gold Supporter
Credits
17,920
So using a wireless network card will be not possible in a vm?

Therefore I need to get a second usb plug in wireless network adapter to get to run it in a vm?

But how does the vm get internet connecntion?
The vm currently has an internet connection because it has a virtual network adapter which NAT's the traffic, you can't use that virtual network adapter for what you are wanting to do with Kali. You can buy a usb wifi adapter for your system and assign that to your vm for Kali and it needs to support monitor mode for what you are probably wanting to do: link1 link2
 
Last edited:

Repo1o1

New Member
Credits
169
The vm currently has an internet connection because it has a virtual network adapter which NAT's the traffic, you can't use that virtual network adapter for what you are wanting to do with Kali. You can buy a usb wifi adapter for your system and assign that to your vm for Kali and it needs to support monitor mode for what you are probably wanting to do: link1 link2
Yes thats what I wanted.

I thought I could connect my realtek wireless card to my kali linux vm to try/check if it got monitor mode and use it without buying a second wireless adapter.
 

f33dm3bits

Gold Member
Gold Supporter
Credits
17,920
Yes, I checked it. Still want to got directly to kali linux. I just do not have so much time to learn everything from the beginning :)
I´m pretty sure I will do it.
 

Repo1o1

New Member
Credits
169
The vm currently has an internet connection because it has a virtual network adapter which NAT's the traffic, you can't use that virtual network adapter for what you are wanting to do with Kali. You can buy a usb wifi adapter for your system and assign that to your vm for Kali and it needs to support monitor mode for what you are probably wanting to do: link1 link2
I tried to select in the vm´s interface my realtek network card, but there is no such option.
Only:

"NAT
Network Bridge
Intern negtwork
Host Only Adapter
Generic Driver
Nat network
Cloud Network"
 
Last edited:

f33dm3bits

Gold Member
Gold Supporter
Credits
17,920
I don't use Virtualbox so no idea how it works there. I think @KGIII runs Virtualbox will be able to answer that question better than me.
 

Repo1o1

New Member
Credits
169
You'll need to look into what's called "VirtualBox USB passthrough". That's something I've never needed to learn, but there are a ton of search results. Just search for that exact phrase.
Its not about USB.

its about using the hosts network card on the VM.
 

f33dm3bits

Gold Member
Gold Supporter
Credits
17,920
Its not about USB.

its about using the hosts network card on the VM.
You can't do this if you want to use the use the wireless interface for scanning or monitoring with Kali tools you need it to show up as a wireless interface on your vm. The only way to do this is to assign a dedicated wireless interface to the vm and this wireless interface can't be in use by the host. The way to do this is through "VirtualBox USB Pass through" as @KGIII already said.
 
Last edited:

Repo1o1

New Member
Credits
169
You can't do this if you want to use the use the wireless interface for scanning or monitoring with Kali tools you need it to show up as a wireless interface on your vm. The only way to do this is to assign a dedicated wireless interface to the vm and this wireless interface can't be in use by the host. The way to do this is through "VirtualBox USB Pass through" as @KGIII already said.

ok thank you for your patience guys, I do realy appreciate that.

I bought one of these.
I will read a bit more about everything and will get back to you if its ok.
 
Last edited:
$100 Digital Ocean Credit
Get a free VM to test out Linux!

Members online


Latest posts

Top