Networking Issue with Kali 2 Sana

[zypher1440]

Just downloaded and installed the latest version of kali and Im having problems connecting to the internet. Everything seems to be working, interfaces are up and connected, says wired 1 is connected but im not getting to the internet. Tried messing with some network files to no avail, also restarting networking services does nothing. Anyone else having similar problems?

[seClusiO]

you run on vmware, virtualbox or which ? If you install fresh kali you need to set the Network Manager follow these steps http://www.blackmoreops.com/2013/11/...managed-error/

[g0tmi1k]

you run on vmware, virtualbox or which ? If you install fresh kali you need to set the Network Manager follow these steps http://www.blackmoreops.com/2013/11/...managed-error/

This is for Kali 1.x, not Kali 2.x. The software has changed.

[0x4148]

I have the same problem
@g0tmi1k
Any help with that?!!

[0x4148]

Update : For me it was solved by changing the default "NAT" option which come by default to Custom NAT one

[mmusket33]

To zypher1440,

In response to your question is anyone else having these problems? - the answer is Yes. MTeams has spent the last 24 hours trying to figure out work-arounds - Here is what we know to date:

The problems with network manager has gotten worse not better.

Under kali-linix 1.10a network manager could override the mac spoofing setup thru the terminal window. However you still had direct control over all connections. With kali 2.0 direct control is gone or suppressed and many choices necessary to control the wifi device are not supported.

Under kali2.0 the wifi is controlled thru a manager which seems to operate between the user and Network-manager. Stations setup by the PCI/USB Wifi manager still write their data to the /etc/Networkmanager/system-connections folder.

1. The PCI manager keeps making newer and newer contact files for the same AP in the etc/Networkmanager/system-connections folder. For example after just 15 minutes of trying to connect to an AP we have five of them.

2. If you have two(2) wifi devices you cannot stop just one(1) of them thru the PCI/USB manager. We had to delete any reference to any connections listed in the etc/Networkmanager/system-connections folder before we could put one of our wifi devices to sleep.

3. The real connection status is not expressed thru the Wifi Manager drop down applete. If you loose(drop) the connection the applete shows you are connected even though iwconfig shows you are not connected and all internet response has stopped. The only real way of knowing the actual connection status is to type iwconfig in a terminal window.

4. The only way of knowing the mac spoofing status is to type ifconfig in a terminal window

The only good thing seen with all this is that Now if you spoof your mac thru the terminal window this mac will remain when network manager runs.

You could enter just below the mac-address= entry in the connection file for the connection point you are using the following:

cloned-mac-aqddress=00:11:22:33:44:55

then:

service network-manager restart

But at present we do not recommend this as the restart can confuse the pci/usb manager, and at times after restarting network-manager we had to shut the computer down and restart to get the system working again.

Unlike kali 1.10a - The best way now under kali2.0 is to spoof your mac address prior to connecting to the wifi site thru the terminal window ONLY and then check it again and again and again with ifconfig for the spoofed mac address and iwconfig for the connection status. The connection status cannot be trusted displayed cannot be trusted.
MTeams

[drewsky]

To zypher1440,

In response to your question is anyone else having these problems? - the answer is Yes. MTeams has spent the last 24 hours trying to figure out work-arounds - Here is what we know to date:

The problems with network manager has gotten worse not better.

Under kali-linix 1.10a network manager could override the mac spoofing setup thru the terminal window. However you still had direct control over all connections. With kali 2.0 direct control is gone or suppressed and many choices necessary to control the wifi device are not supported.

Under kali2.0 the wifi is controlled thru a manager which seems to operate between the user and Network-manager. Stations setup by the PCI/USB Wifi manager still write their data to the /etc/Networkmanager/system-connections folder.

1. The PCI manager keeps making newer and newer contact files for the same AP in the etc/Networkmanager/system-connections folder. For example after just 15 minutes of trying to connect to an AP we have five of them.

2. If you have two(2) wifi devices you cannot stop just one(1) of them thru the PCI/USB manager. We had to delete any reference to any connections listed in the etc/Networkmanager/system-connections folder before we could put one of our wifi devices to sleep.

3. The real connection status is not expressed thru the Wifi Manager drop down applete. If you loose(drop) the connection the applete shows you are connected even though iwconfig shows you are not connected and all internet response has stopped. The only real way of knowing the actual connection status is to type iwconfig in a terminal window.

4. The only way of knowing the mac spoofing status is to type ifconfig in a terminal window

The only good thing seen with all this is that Now if you spoof your mac thru the terminal window this mac will remain when network manager runs.

You could enter just below the mac-address= entry in the connection file for the connection point you are using the following:

cloned-mac-aqddress=00:11:22:33:44:55

then:

service network-manager restart

But at present we do not recommend this as the restart can confuse the pci/usb manager, and at times after restarting network-manager we had to shut the computer down and restart to get the system working again.

Unlike kali 1.10a - The best way now under kali2.0 is to spoof your mac address prior to connecting to the wifi site thru the terminal window ONLY and then check it again and again and again with ifconfig for the spoofed mac address and iwconfig for the connection status. The connection status cannot be trusted displayed cannot be trusted.
MTeams

Best read of the day for me,Thank you mmusket33

This read nailed it.

Appreciated

[mmusket33]

To drewsky,

There is another aspect to the network manager which is being seen by aircrack-ng users and kali2.0

We have just completed a rewite of VMR-MDK for kali2.0 and came across this problem as well. And to prove this not just an isolated case read the aircrack-ng forum thread and the solutions we provide there.

http://forum.aircrack-ng.org/index.p...ic,1062.0.html

MTeams

[drewsky]

Thanks for the Update mmusket33

That read on http://forum.aircrack-ng.org/index.p...ic,1062.0.html was excellent.