LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   kali linx from live USB its not detecting any WIFI signals (https://www.linuxquestions.org/questions/linux-newbie-8/kali-linx-from-live-usb-its-not-detecting-any-wifi-signals-4175583103/)

Roshan619 06-25-2016 04:44 PM

kali linx from live USB its not detecting any WIFI signals
 
I Just brought a new laptop LENOVO G50 AMD A8. the problem is when I boot kali linx from live USB its not detecting any WIFI signals. actually we have a router of TP LINK in our room. but kali linux coilden't detect it i tried every possible solutions but its wot worked.so ineed help from you. please help me to sort out this issue.

onebuck 06-26-2016 11:02 AM

Member response
 
Hi,

You should consider reading http://www.linuxquestions.org/questi...#faq_lqwelcome so you can compose queries to help you to help us to diagnose issues.

You can look at Troubleshooting Wireless Drivers - Kali Linux to get some help diagnosing issues.

Or use some of the following.
You can look at 'dmesg' for your wireless device to see if the device has been sensed & activated
Code:

# dmesg |grep -i wireless
[    7.303760] Intel(R) Wireless WiFi driver for Linux, in-tree:

Check to see if the wireless is enabled;
Code:

# rfkill list
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
3: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

Some wireless devices can be controlled via the keyboard Fn keys. The above code block will show you if the device is enabled or blocked.

You can look at the device module/driver that is recognized via;
Code:

# lspci -kk |grep -iA3 network
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6230 [Rainbow Peak] (rev 34)
        Subsystem: Intel Corporation Centrino Advanced-N 6230 AGN
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi

You may need to check that proper firmware is installed for your device. You can look at the /lib/firmware with information for the example above for Intel 6230;
Code:

# ls /lib/firmware/iwl*
/lib/firmware/iwlwifi-100-5.ucode  /lib/firmware/iwlwifi-3160-7.ucode  /lib/firmware/iwlwifi-5000-5.ucode    /lib/firmware/iwlwifi-6050-4.ucode
/lib/firmware/iwlwifi-1000-3.ucode  /lib/firmware/iwlwifi-3160-8.ucode  /lib/firmware/iwlwifi-5150-2.ucode    /lib/firmware/iwlwifi-6050-5.ucode
/lib/firmware/iwlwifi-1000-5.ucode  /lib/firmware/iwlwifi-3160-9.ucode  /lib/firmware/iwlwifi-6000-4.ucode    /lib/firmware/iwlwifi-7260-7.ucode
/lib/firmware/iwlwifi-105-6.ucode  /lib/firmware/iwlwifi-3945-2.ucode  /lib/firmware/iwlwifi-6000g2a-5.ucode  /lib/firmware/iwlwifi-7260-8.ucode
/lib/firmware/iwlwifi-135-6.ucode  /lib/firmware/iwlwifi-4965-2.ucode  /lib/firmware/iwlwifi-6000g2a-6.ucode  /lib/firmware/iwlwifi-7260-9.ucode
/lib/firmware/iwlwifi-2000-6.ucode  /lib/firmware/iwlwifi-5000-1.ucode  /lib/firmware/iwlwifi-6000g2b-5.ucode  /lib/firmware/iwlwifi-7265-8.ucode
/lib/firmware/iwlwifi-2030-6.ucode  /lib/firmware/iwlwifi-5000-2.ucode  /lib/firmware/iwlwifi-6000g2b-6.ucode  /lib/firmware/iwlwifi-7265-9.ucode

Checking the Intel site for the 6000 firmware shows the /lib/firmware/iwlwifi-6000g2b-6.ucode is the proper firmware for the 6230 device. The kali kernel firmware should provide that firmware for such device.

Please realize that I have been using my wireless to show by example what can be done. To do the above commands you must be root or superuser. I usually open a terminal or console and use 'su -' & password to get root rights.

If the device is recognized and uses proper firmware you can check for LAN configurations by;
Code:

# ifconfig -a
eth0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 84:8f:69:c4:6a:e2  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 0  (Local Loopback)
        RX packets 1471  bytes 118994 (116.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1471  bytes 118994 (116.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.254.14  netmask 255.255.255.0  broadcast 192.168.254.255
        ether 00:db:df:3d:dd:a3  txqueuelen 1000  (Ethernet)
        RX packets 15208148  bytes 11071901603 (10.3 GiB)
        RX errors 0  dropped 1090583  overruns 0  frame 0
        TX packets 5349482  bytes 911015518 (868.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Note that my wlan0 does have a IP address.
My kernel route table;
Code:

# route -n
Kernel IP routing table
Destination    Gateway        Genmask        Flags Metric Ref    Use Iface
0.0.0.0        192.168.254.254 0.0.0.0        UG    1      0        0 wlan0
127.0.0.0      0.0.0.0        255.0.0.0      U    0      0        0 lo
192.168.254.0  0.0.0.0        255.255.255.0  U    0      0        0 wlan0

I do suggest that you 'man command' to understand what is being done.

You can check your DNS via;
Code:

# cat /etc/resolv.conf
#search workgroup
#nameserver 208.67.222.222
nameserver 8.8.4.4
nameserver 4.2.2.2
nameserver 208.67.220.220
nameserver 4.2.2.1
#inameserver 208.67.220.220
nameserver 8.8.8.8

I use a mix of DNS, OpenDNS (208.67.220.220) plus google(8.8.8.8 & 8.8.4.4) and Verizon 3rd level (4.2.2.1 & 4.2.2.2) nameservers. The way I have group within my /etc/resolv.conf seems to work for me. I commented out other nameservers, you do not need more than six nameservers with '/etc/resolv.conf'.

If things check out OK after the above then you can test via;
Code:

To test LAN ;
# ping 216.58.192.174             
PING 216.58.192.174 (216.58.192.174) 56(84) bytes of data.
64 bytes from 216.58.192.174: icmp_seq=1 ttl=55 time=9.98 ms
64 bytes from 216.58.192.174: icmp_seq=2 ttl=55 time=10.2 ms
64 bytes from 216.58.192.174: icmp_seq=3 ttl=55 time=10.4 ms
^C
--- 216.58.192.174 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 9.984/10.229/10.494/0.239 ms

To test that DNS is functioning then;
Code:

# ping google.com
PING google.com (216.58.192.142) 56(84) bytes of data.
64 bytes from ord36s01-in-f14.1e100.net (216.58.192.142): icmp_seq=1 ttl=55 time=14.1 ms
64 bytes from ord36s01-in-f14.1e100.net (216.58.192.142): icmp_seq=2 ttl=55 time=10.4 ms
64 bytes from ord36s01-in-f14.1e100.net (216.58.192.142): icmp_seq=3 ttl=55 time=12.0 ms
64 bytes from ord36s01-in-f14.1e100.net (216.58.192.142): icmp_seq=4 ttl=55 time=10.0 ms
^C
--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 10.027/11.654/14.110/1.614 ms

If these steps are successful then your LAN configuration is working
You can use 'man command' to understand the above commands.

You should look at the bottom of this thread for similar threads that may provide additional help. A LQ Search will provide you answers as to how to do a Static IP configuration as this has been done many times here at LQ.

Hope this helps.
Have fun & enjoy!
:hattip:

ardvark71 06-26-2016 11:09 AM

Quote:

Originally Posted by Roshan619 (Post 5566269)
I Just brought a new laptop LENOVO G50 AMD A8. the problem is when I boot kali linx from live USB its not detecting any WIFI signals. actually we have a router of TP LINK in our room. but kali linux coilden't detect it i tried every possible solutions but its wot worked.so ineed help from you. please help me to sort out this issue.

Hi...

First, are you new to Linux? If so, perhaps you should read here first. Kali is not meant for folks just starting out or for everyday use. ;)

Does the information here help at all? :)

EDIT: Looks like onebuck beat me to it with a much more detailed reply. ;)

Regards...

AwesomeMachine 06-26-2016 04:36 PM

Type:

$ lspci -vvv | grep -i -A 10 ethernet
google dns
and see which adapter you have in the laptop. Then, look at which driver it requires. Try to load the driver:

$ modprobe driver

If you need help along the way, just come back and ask.


All times are GMT -5. The time now is 12:32 AM.