Using VirtualBox 6.1 on Debian 5.4.13-1kali1 (2020-01-20) x86_64 GNU/Linux
* 64-Bit

Goal is to bridge Kali's WLAN0 with Centos distros. This bridging works fine in Mint, and Mint bridging settings appear the same in Centos distros. I have also toggled various settings, such as cable connected, etc, with no benefit.

CentOS-7-x86_64-DVD-1810 (core)
* 64-Bit
CentOS-6.10-x86_64-bin-DVD1
* 64-Bit
linuxmint-18-kde-32bit
* 32-Bit
** Adapter 1 - Bridged; Wlan0; Promiscuous Mode - Deny; Cable Connected;
CentOS-7-x86_64-DVD-1708
* 64-Bit
CentOS-8-x86_64-1905
* 64-Bit

Ideas on what I may be missing?

You are using Virtualbox ON Kali?

I'm far from an expert, as a matter of fact I just started learning this stuff 2 days ago but I just did something similar in Mint with VLANs and it works flawlessly.

Your post is missing lots of information. What is the Host OS and Guest OS? You're talking about Kali (hacking tool), Centos and Debian...

See this serverfault thread for example on what kind of info those who can help would appreciate to have https://serverfault.com/questions/40...-guest-kernels

I understand you're trying to bridge the host Wifi adapter to use as an ethernet adapter in the VM's.

How did you try this? AFAIK you need to create the bridge at the host OS level, then assign it in the VBox settings to the VM.

Works on my end with wired connections. My host OS is Mint 19.1 and I used /etc/network/interfaces to create the bridge at boot time and make sure it is up. I also use VLAN's and they are also created at boot time and up via thw same file. Works perfectly.

Post a bit more info such as the output of "ip address" on the host so we can get a better idea of what you have in your hands.

@ lpallard ... This is being a fun newbie lesson on configuring NIC's with their respective cfg files, etc..

First, I set Kali's wlan to use a static IP 192.168.0.200 & DNS 192.168.0.1; This works fine

Next, I set the Centos 7 1810 core VBox VM to use a static IP (.175) & Gateway (.1) via /etc/sysconfig/network-scripts/ifcfg-enp03
* This results in the VM being able to ping the gateway

Now I am reviewing websites which explain how to configure static DNS entries; and also how to update the modified entries upon a service or system reboot. More digging, but I am farther ahead than I was the other day. Will also be testing another RH/Centos VM to ensure its address is correctly being assigned via DHCP. This is obviously what the Linux Mint VM is doing, as I have never modified its configuration files and it can traverse outbound and resolve website names with ease. Yes, I am aware that Kali & Mint are using /etc/network/interfaces for their key network configuration scripts, and RH/Centos have its key configuration files located under /etc/sysconfig/network-scripts/ .. Goal is to (I guess) auto-update /etc/resolv.conf with DNS entries upon boot, or make them permanent.

Just trying to figure out why anyone would use virtualbox on kali...I am not that masochistic.

@ sevendogsbsd .. Key OS on my laptop is Kali. Running VBox is simply to examine and lightly test some of the other distros that I haven't seen out there. Now, were you alluding to something, or simply expressing your views? Am trying to gain an understanding for why you feel I shouldn't be doing this.

Just wondering since Kali is a pen testing distro and not meant for daily use, or rather as a desktop. You CAN, but I can drive a McLaren P1 as a daily driver and it will get me from a to b, albeit not very efficiently

If you are a pen tester, more power to you, but I answered this way because we get a ton of new users that choose Kali as a desktop and can't figure out why it doesn't work very well. They aren't. pentesters and know nada about Linux so in those cases Kali is a bad choice.

I pentest web apps as my main job and use it in a VM so always ask when people have issues with Kali.

kali is prominently known as a distribution for digital forensics and penetration testing. It was configured specifically to be that and not really an everyday distribution.

However, with the release of version 2020.1 the developers have made some changes so that you have to login as a regular user instead of root. This release is more like an everyday distribution however it isn't tested for compatibility with everyday programs so there is no guarantee of stability and no bug testing.

I've installed CentOS 7 several times (don't remember what 7.x it was) as a VirtualBox virtual machine and have not had any problems with bridged mode using a laptop with a wireless adapter. Both using Windows and linux hosts. CentOS 7 does use Network Manager so any configuration changes with the configuration scripts you need to disable network manager or configure it to use the scripts. In addition systemd complicates things a bunch with systemd-resolvd. I have not tried CentOS 8 yet but from what I have read it does not use the configuration scripts anymore.

kali and Mint are both based on debian so their configuration scripts are similar.

Backtrack and Kali have been my key OS's for ~8yrs. I originally started with these to learn the concepts of Linux, and also to learn the aircrack suite, so I could demonstrate vulnerabilities to clients at the time. I am less focused on 802.11 these days, and now primarily looking to enhance my administration skills with Linux. This is in part why seeing the NIC configuration files being in alternate locations {RH/Debian} caught my attention.