Unable to create Bridged Network on Windows 8.1 from Kali Linix

[Sreyan]

I am unable to create a bridged network from Windows 8.1 when running Kali Linux as a guest.

It fails with the error:

vbox_error.jpg (48.05 KiB) Viewed 3015 times

I have tried installing VirtualBox with the NDIS5 driver via:

Code: Select all

VirtualBox-5.0.10-104061-Win.exe -msiparams NETWORKTYPE=NDIS5

but still the same error persists.

My guest network configs are:

net_conf.jpg (86.26 KiB) Viewed 3015 times

Am I doing anything wrong ?

I don't see the NDIS6 driver anymore so what is the problem ?

wifi_conf.jpg (67.62 KiB) Viewed 3015 times

My model of wireless adapter is this:
https://zebronics.com/products/usb-devi ... b-usb150wf

Let me know if any other info is required.

[scottgus1]

I have tried installing VirtualBox with the NDIS5 driver...I don't see the NDIS6 driver anymore

Per your previous post on this subject viewtopic.php?f=6&t=98012 You apparently successfully switched to NDIS5.

Switching NDIS is extremely likely not your problem. You should switch back. If I remember right, switching from NDIS 6 to 5 was only a thing at some stages between Virtualbox and some version of Windows (possibly 7, along with Virtualbox 5.0.smallnumbers, see viewtopic.php?f=6&t=70052) due to some glitches people were getting and the downgrade fixed the problem. That issue is old and no longer needs to be implemented. You're on 8.1, switch back to NDIS6.

Next time best to ask about your problem, not your solution to the problem. We were all stuck in an "XY problem" over this NDIS# thing.

VirtualBox-5.0.10

You're using a very old outdated version of Virtualbox, which apparently did have some NDIS problems with Windows 7. But you're on 8.1. Upgrade to at least a higher last number in 5.2.x or 6.0.x, if not go up to the latest.

802.11n USB Wireless LAN Card

Bridged may not always work with a host Wifi adapter, due to strict implementation of the Wifi protocols by either the Wifi adapter driver or the access point firmware. Technically Wifi cannot Bridge, but some combinations of Wifi adapter drivers and access point firmware implement Wifi protocols in a lax fashion so Bridged can squeeze through. If it works where you are, good. If not, you need to choose one of these solutions:

1. go to wired Ethernet

2. pick another Virtualbox network type or two (NAT and Host-Only cover most situations but not where the guest must be on the host LAN)

3. use a Virtualbox USB filter to put a USB Wifi adapter directly into the guest (see USB basics and troubleshooting).

[mpack]

Cross posting is against the forum rules, because it causes irritating duplication of effort. Hence I have deleted the other topic created (in this same forum!) to discuss this problem. I was strongly tempted to delete both...

[Sreyan]

Cross posting is against the forum rules, because it causes irritating duplication of effort. Hence I have deleted the other topic created (in this same forum!) to discuss this problem. I was strongly tempted to delete both...

I made two forum posts because they had 2 different problems. One had NDIS downgrade and another one I could not create a bridged virtual network. I understand why you deleted one. I would have done the same expect I don't find any option for deleting an entire post.

[Sreyan]

Switching NDIS is extremely likely not your problem. You should switch back. If I remember right, switching from NDIS 6 to 5 was only a thing at some stages between Virtualbox and some version of Windows (possibly 7, along with Virtualbox 5.0.smallnumbers, see viewtopic.php?f=6&t=70052) due to some glitches people were getting and the downgrade fixed the problem. That issue is old and no longer needs to be implemented. You're on 8.1, switch back to NDIS6.

Yup, I already did switch back.

Next time best to ask about your problem, not your solution to the problem. We were all stuck in an "XY problem" over this NDIS# thing.

I don't understand. You mean just ask the problem without telling you what I tried ? I mentioned NDIS downgrade because that was mentioned as a possible fix somewhere.

You're using a very old outdated version of Virtualbox, which apparently did have some NDIS problems with Windows 7. But you're on 8.1. Upgrade to at least a higher last number in 5.2.x or 6.0.x, if not go up to the latest.

That is my mistake, I basically copied the command out of the gist without changing it. I am in VirtualBox 6.1.6 r137129, which I guess is the latest.

Bridged may not always work with a host Wifi adapter, due to strict implementation of the Wifi protocols by either the Wifi adapter driver or the access point firmware. Technically Wifi cannot Bridge, but some combinations of Wifi adapter drivers and access point firmware implement Wifi protocols in a lax fashion so Bridged can squeeze through. If it works where you are, good. If not, you need to choose one of these solutions:

1. go to wired Ethernet

2. pick another Virtualbox network type or two (NAT and Host-Only cover most situations but not where the guest must be on the host LAN)

3. use a Virtualbox USB filter to put a USB Wifi adapter directly into the guest (see USB basics and troubleshooting).

Any way to access the host from the VM ?

I am using Kali Linux as my guest and I will be running various scans on my host, any way to do that ?

That is my main requirement. I thought bridged mode would allow me that.

[scottgus1]

Any way to access the host from the VM ?....I will be running various scans on my host, any way to do that ?

That is my main requirement. I thought bridged mode would allow me that.

Bridged would work for that, if Bridged was working. You are trying to Bridge to a Wi-Fi adapter, which does not work sometimes.

To let your Kali guest monitor/exploit your host, try item 1 or 3 suggested above.

You mean just ask the problem without telling you what I tried ?

The other thread that got deleted was the XY problem thread. That one just asked about changing NDIS without explaining why, or what caused you to feel that changing NDIS was necessary. Much discussion could develop without getting to the root of the problem.

The way you started this post was really good. Your problem and what you tried were stated, a good start for a topic.

[Sreyan]

Bridged would work for that, if Bridged was working. You are trying to Bridge to a Wi-Fi adapter, which does not work sometimes.

To let your Kali guest monitor/exploit your host, try item 1 or 3 suggested above.

I did not understand what you meant by putting an USB filter on the Virtualbox itself. How does that help in this case ? Does my VM get an IP from the router as my PC, I will need them to be on the same LAN.

[scottgus1]

A USB filter allows a plug-in USB device to be pumped into the guest instead of the host. See https://www.virtualbox.org/manual/ch03.html#usb-support. With a USB filter you can put a USB wi-fi adapter directly into the guest. No Virtualbox network at all required. The guest OS uses the USB wi-fi adapter directly to access your wi-fi access point same as the host is doing, and the guest looks to your network and host OS like another new PC on the network. Whatever Kali can do when connected with wifi, your guest can do with the USB filter and USB wi-fi adapter. This method will satisfy this requirement:

Does my VM get an IP from the router as my PC, I will need them to be on the same LAN

Be sure to get a USB wi-fi adapter that Kali has built-in drivers for.

I see from your fist post above that you already have a USB wi-fi adapter. If this is the adapter your host was already using to access the wi-fi network, then you will need another one, try to get a different manufacturer/chipset (compatible with Kali) for the guest to use, it will help setting up the USB filter. If you were planning to use this adapter with the guest via Bridged and the host already had another network connection, then you might be able to use this device through a USB filter in the guest as mentioned above, just need to check if Kali supports that device.

[Sreyan]

If this is the adapter your host was already using to access the wi-fi network, then you will need another one

So just to be crystal clear. There is no way to use the WIFI adapter that the host uses. There is no way to do this with the hardware I have, and will absolutely require another WIFI adapter. Right ?

[scottgus1]

If you must keep the host on Wi-Fi then that is correct.

[Sreyan]

If you must keep the host on Wi-Fi then that is correct.

How else would I access the host from the guest ?

[facboy]

is this getting a bit xy problem again?

do you need Bridged mode or do you just need to access the host from the guest? If the latter I just add a second Network Adapter to the VM and set it to Host-only Adapter. You can configure the host network from Host Network Manager under the File menu.

[scottgus1]

facboy, Sreyan wants to hack/pen-test the host PC from the guest. The host and guest must be on the same LAN to do this. Host-Only would put the guest on a LAN with the host, but no internet. Bridged would be the most optimum situation. But Bridged does not always work over wi-fi, and Sreyan connects the host PC to the network via wi-fi, and so needs another wi-fi adapter to put in the guest. Then the guest would access wi-fi directly along with the host all in the same internet-connected LAN.

Sreyan, if you can connect your PC with wired Ethernet, then the guest will Bridge to the wired Ethernet card just fine.

[Sreyan]

facboy, Sreyan wants to hack/pen-test the host PC from the guest. The host and guest must be on the same LAN to do this. Host-Only would put the guest on a LAN with the host, but no internet. Bridged would be the most optimum situation. But Bridged does not always work over wi-fi, and Sreyan connects the host PC to the network via wi-fi, and so needs another wi-fi adapter to put in the guest. Then the guest would access wi-fi directly along with the host all in the same internet-connected LAN.

Sreyan, if you can connect your PC with wired Ethernet, then the guest will Bridge to the wired Ethernet card just fine.

You mean I can ping the host from the guest using Host-only adapter ?

Does it mean there will no internet on any of the machines in this case ? Internet should remain for the host right ?

[facboy]

You mean I can ping the host from the guest using Host-only adapter ?

Does it mean there will no internet on any of the machines in this case ? Internet should remain for the host right ?

I must admit I don't really understand what you're trying to do. I can tell you that I can ping (ssh, whatever) my VMs from the host, and they have internet (as does the host).

I just put two adapters on the VM, one NAT and one host-only adapter. This might not be optimal but it does what I need it to.