Saltar al contenido
Underc0de /foro

[SOLVED] Kali Linux doesn't detect wireless or wired network

🌐 This is an automatic translation of a topic from Underc0de, the largest Spanish-speaking hacking and IT community. Read the original (Spanish) and reply →
Cuervo ·
Today I tried to change my IP address to make it static. I did it graphically from the network settings. When I finished configuring everything I saved the changes and exited. After that I decided to restart the computer's network and when I did, in the network section the wireless or wired option no longer appeared, only proxy appeared, and since then I haven't been able to connect to the Internet. I've searched for information but it happened to other people when updating their operating systems, which isn't the same as my case.<br /><br />If anyone can help me I'd really appreciate it
davidhs ·
Hi cuervo, I could try to help you, but I need you to give me more information, such as which virtualizer you use, the version of kali linux you're currently using, whether you're running kali linux natively on a pc, etc. I'd appreciate it, since the more information you give us, the sooner we could find the solution.
Cuervo ·
Hi davidhs!<br />Well, I have Kali Linux installed on my hard drive, which shares space with Windows 7 (partition). It's version 2.0<br />As I said, I tried to change my IP address to make it static but when I restarted the laptop and turned it on I realized I no longer had the option to connect wirelessly or by cable, only by proxy
UpecBlack ·
xD , do you have dhcp on your modem?
xianur0n ·
We understand you tried to do it automatically but if you want help you need to give more information. run ifconfig, iwconfig and post them so we can see what that looks like. how do you usually connect, wireless or by cable. This sounds like when you did it through the gui, it changed some data in the configuration files and disabled dhcp, just speculating. I need to see what information ifconfig or iwconfig gives you, what the networkmanager configuration says, which is in /etc/NetworkManager/NetworkManager.conf, and the interfaces configuration, which is in /etc/network/interfaces.
Cuervo ·
Yes my modem has dhcp. What I wanted to do was convert my IP, which was already dynamic, into a static IP <br />Here's the data:<br /> <br /><br />------------------------------------------------------------------<br />ifconfig<br />eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500<br />        ether 00:22:68:12:17:53  txqueuelen 1000  (Ethernet)<br />        RX packets 0  bytes 0 (0.0 B)<br />        RX errors 0  dropped 0  overruns 0  frame 0<br />        TX packets 0  bytes 0 (0.0 B)<br />        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0<br />        device interrupt 20  memory 0xfc000000-fc020000  <br /><br />lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536<br />        inet 127.0.0.1  netmask 255.0.0.0<br />        inet6 ::1  prefixlen 128  scopeid 0x10<host><br />        loop  txqueuelen 0  (Local Loopback)<br />        RX packets 20  bytes 1200 (1.1 KiB)<br />        RX errors 0  dropped 0  overruns 0  frame 0<br />        TX packets 20  bytes 1200 (1.1 KiB)<br />        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0<br /><br />wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500<br />        inet6 fe80::21e:65ff:fe37:b14e  prefixlen 64  scopeid 0x20<link><br />        ether 00:1e:65:37:b1:4e  txqueuelen 1000  (Ethernet)<br />        RX packets 46  bytes 13346 (13.0 KiB)<br />        RX errors 0  dropped 0  overruns 0  frame 0<br />        TX packets 44  bytes 7075 (6.9 KiB)<br />        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0<br /><br /><br />----------------------------------------------------------<br />iwconfig<br />eth0      no wireless extensions.<br /><br />wlan0     IEEE 802.11abgn  ESSID:"INFINITUM8844"  <br />          Mode:Managed  Frequency:2.432 GHz  Access Point: 7C:A2:3E:1D:4A:98   <br />          Bit Rate=1 Mb/s   Tx-Power=15 dBm   <br />          Retry short limit:7   RTS thr:off   Fragment thr:off<br />          Encryption key:off<br />          Power Management:off<br />          Link Quality=55/70  Signal level=-55 dBm  <br />          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0<br />          Tx excessive retries:0  Invalid misc:28   Missed beacon:0<br /><br />lo        no wireless extensions.<br /><br /><br />---------------------------------------------------------------------------<br />/etc/NetworkManager/NetworkManager.conf<br />bash: /etc/NetworkManager/NetworkManager.conf: Permiso denegado<br /><br /><br />--------------------------------------------------------------------------<br />/etc/network/interfaces<br />bash: /etc/network/interfaces: Permiso denegado<br /><br /><br /><br /><br />
Stiuvert ·
Hi @Cuervo, you should configure the "interfaces" file and access it as root, since in your previous post I saw the following:<br /><br />
Citarbash: /etc/network/interfaces: Permiso denegado
<br /><br />To access it you have to do it as follows<br /><br />
Código: bash
sudo nano /etc/network/interfaces
<br /><br />And configure your static IP following this example:<br /><br />Los enlaces son solo para miembros. Registrate o iniciá sesión<br /><br />Then do a restart<br /><br />
Código: bash
/etc/init.d/networking restart
<br /><br />Regards
Cuervo ·
I already did what you told me and reconfigured it but it still doesn't work.<br />I also did this, look: <br /><br /># This file describes the network interfaces available on your system<br /># and how to activate them. For more information, see interfaces(5).<br /><br />source /etc/network/interfaces.d/*<br /><br /># The loopback network interface<br />auto lo<br />iface lo inet loopback<br /><br />auto wlan0<br />iface wlan0 inet dhcp<br /><br />As you can see I set wlan0 to receive its IP address automatically, meaning I tried to leave everything as it was from the beginning. I restarted and applied the command <br /><br />sudo reboot <br /><br />When it turned on I noticed I could connect to the internet but only by cable, not wirelessly.<br /><br />Any advice on how to get the network configuration back to how it was from the beginning?
xianur0n ·
Ok I have the solution to your problem. I've been using Debian for a while now. well this is what's going on, kali is derived from debian so most of the configurations are the same. well let's get to the point. I'll refer to Debian a bit, you know there's debian 7 (Whezzy) and debian's latest stable version 8 (jessie). since whezzy or debian 7 came out, the debian documentation says wireless interfaces could be in /etc/network/interfaces if you wanted but it wasn't necessary, and I verified it myself. the same configuration you have, if you leave it like this you'll be able to communicate with the wlan0 interface, and this is due to the kernel's UDEV which allows detecting the hardware and loading the necessary modules. Thanks Linus Trovals.. <br />
Citar# This file describes the network interfaces available on your system<br /># and how to activate them. For more information, see interfaces(5).<br /><br />source /etc/network/interfaces.d/*<br /><br /># The loopback network interface<br />auto lo<br />iface lo inet loopbacak<br />
<br /><br />But I'm not done, I imagine you're wondering what if I have to configure my wlan0 interface, how the heck do I do it, ok it's easy, if you do a man wireless it's more detailed, but if you want to have the dhcp configuration of wlan0 in the /etc/network/interfaces file you have to have it this way. <br />
Citar# This file describes the network interfaces available on your system<br /># and how to activate them. For more information, see interfaces(5).<br /><br />source /etc/network/interfaces.d/*<br /><br /># The loopback network interface<br />auto lo<br />iface lo inet loopbacak<br /><br />auto wlan0 inet dhcp<br />        wireless-essid 4B14F6<br />        wireless-mode Managed<br />
<br /><br />Either way will work. I work on debian 8 stable on my machine :) I'm sure it'll work on kali too. now if you want to configure your wlan0 interface with a static ip follow these steps. stiuvert already explained how to do it with a wired connection. the configuration for a wireless interface is COMPLETELY DIFFERENT. while I was researching the topic I saw many tutorials for setting a static ip on a wireless interface that are wrong. first, according to the debian documentation /etc/network/interfaces SHOULD NOT BE THE PLACE FOR A WIRELESS CONFIGURATION. I'M SURE IN A SERVER EDITION THIS WOULDN'T BE THE CASE BUT ANYWAY. since according to the documentation wireless configurations shouldn't go in /etc/network/interfaces, we know /etc/network/interfaces holds the configuration for network-manager. well the debian documentation, WHICH I'M SURE WILL BE THE SAME IN KALI, RECOMMENDS THAT WE DON'T USE NETWORK-MANAGER, WHICH IS THE default tool the operating system uses. so let's do a<br />Service network-manager stop. this way we'll stop the daemon<br />now we'll install Wicd. it's an alternative to network-manager. it's perfect for desktops. as I said before I imagine for servers it won't be like that. but just saying. it would be pretty stupid to set up a server with a wireless connection and on top of that a static address. I imagine that's why the developers didn't burn the midnight oil so much on making a wireless interface have a static address through network-manager. but anyway we install Wicd<br />you know apt install wicd or apt-get install wicd. we install it. very important, if we're going to use wicd and not network-manager we must leave /etc/network/interfaces like this <br /><br />
Código: text
# The loopback network interface<br />auto lo<br />iface lo inet loopbacak
<br /><br />nothing more, nothing less. <br />if you were already using network manager you most likely already belong to the netdev group. if not you can check with the id command. if not you must add yourself to that group, it's easy, you just have to do adduser "tuusername" netdev. then you start the daemon like this /etc/init.d/dbus reload and then the other daemon /etc/init.d/wicd start.<br />and everything will be ready, remember for the network manager<br />now just type in the console wicd-client -n and a graphical utility will open where all the wireless connections will appear. if you go to the network you want to connect to, click on properties and configure your static address and your dns server. remember, where the dns fields are, put your dnsserver in all of them. if you don't know which it is just do cat /etc/resolvconf and there you'll see it, most likely you only have one, which is your router. AFTER RESEARCHING FOR TWO HOURS WHY I COULDN'T CONFIGURE A STATIC IP THROUGH NETWORK-MANAGER OR /ETC/NETWORK/INTERFACES, THIS WAS THE SOLUTION THAT WORKED FOR ME. I'M USING DEBIAN 8 (JESSIE).
Cuervo ·
It didn't work bro, I tried both ways you gave me to receive the IP automatically, or rather for the configuration to be as it was from the start. But only the Proxy option still appears and it won't let me connect to the internet :( <br />Any other solution? UnU Or should I just format and reinstall Kali?
xianur0n ·
sorry it didn't work on your machine. well, you don't have to wipe the whole system and install it again. usually when deb packages are misbehaving  ;) it's a good idea to reinstall them. this will reinstall all the configurations and leave it brand new.<br />
Citarapt-get install --reinstall network-manager
Grupo de WhatsApp