SystemCrash86 Posted August 20, 2019 Share Posted August 20, 2019 I have a fresh install of Linux mint and the WiFi works and I can use the Internet perfectly. However after installing katoolin, which I get no errors, after rebooting I can't get any Internet at all even though network manager says I am connected to my network.I can't ping anything. I think it messed up my dhcp or something but I don't know how to find out where it went wrong What happened? Link to comment Share on other sites More sharing options...
F0x3nB0x3n Posted August 20, 2019 Share Posted August 20, 2019 If you run (from the terminal): ip a What's the output? That should tell you whether or not DHCP is acquiring an address. ifconfig would also work to get that info, if you've got the older network tools installed. Not sure who runs what these days 🙂 Link to comment Share on other sites More sharing options...
SystemCrash86 Posted August 20, 2019 Author Share Posted August 20, 2019 hi thanks for the reply. i hope this helps: root@mint:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether b0:5a:da:5c:8f:2f brd ff:ff:ff:ff:ff:ff 3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether ac:b5:7d:c7:c3:06 brd ff:ff:ff:ff:ff:ff root@mint:~# ifconfig enp2s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether b0:5a:da:5c:8f:2f 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 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 3705 bytes 264858 (264.8 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 3705 bytes 264858 (264.8 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlp3s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether ac:b5:7d:c7:c3:06 txqueuelen 1000 (Ethernet) RX packets 7 bytes 1071 (1.0 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 22 bytes 4476 (4.4 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@mint:~# iwconfig lo no wireless extensions. wlp3s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=15 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off enp2s0 no wireless extensions. root@mint:~# iptables-save # Generated by iptables-save v1.6.1 on Tue Aug 20 22:14:27 2019 *filter :INPUT ACCEPT [1921:136393] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [1921:136393] COMMIT # Completed on Tue Aug 20 22:14:27 2019 root@mint Link to comment Share on other sites More sharing options...
SystemCrash86 Posted August 22, 2019 Author Share Posted August 22, 2019 root@mint:~# ps aux | grep -e 'dhclient' -e 'wpa_supplicant' | grep -v grep root 820 0.0 0.0 29332 7424 ? Ss 22:15 0:00 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant root@mint:~# root@mint:~# root@mint:~# ping 127.0.0.1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.051 ms 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.066 ms 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.064 ms ^C --- 127.0.0.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2040ms rtt min/avg/max/mdev = 0.051/0.060/0.066/0.009 ms root@mint:~# root@mint:~# ping 8.8.8.8 connect: Network is unreachable root@mint:~# ping www.google.com ping: www.google.com: Name or service not known root@mint:~# hope this helps Link to comment Share on other sites More sharing options...
SystemCrash86 Posted August 25, 2019 Author Share Posted August 25, 2019 i think i may have missed a step somewhere because i followed that and after i start the new wpa_supplicant.conf i am greeting with: "successfully initialized wpa_supplicant" but when i issue ifconfig i find that the output is the same as before with no ip. could i have missed something? Link to comment Share on other sites More sharing options...
PoSHMagiC0de Posted August 27, 2019 Share Posted August 27, 2019 Hmm, sounds like you aren't getting a dhcp address. Wpa_supplicant doesn't need manual intervention if network manager is controlling it. I have run into this when swapping on usb network adapters. After you connect, go sudo and type this. I am on a phone so no code wrap. dhclient -4 <your interface here> Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.