Jump to content

Linux mint Internet issues


Recommended Posts

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 post
Share on other sites

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 post
Share on other sites

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 post
Share on other sites

It's not a firewall issue. Are you connecting just through wifi, or do you have an Ethernet cable connected?

One other thing to check, to see if dhcp client is still running (dhclient) and also if the wifi's client is running (wpa_supplicant):

$ ps aux | grep -e 'dhclient' -e 'wpa_supplicant' | grep -v grep

 

Edited by kdodge
afterthought
Link to post
Share on other sites
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 post
Share on other sites

so from:

ps aux | grep -e 'dhclient' -e 'wpa_supplicant' | grep -v grep

wpa_supplicant is running, but from

iwconfig

Access Point: Not-Associated means that you are not connected to the access point. You could try manually connecting to the AP from the command line. 

you should do a google for wpa_supplicant.conf cause there's a lot of different formats for that file depending on how the security is setup on your wifi.

A quick search I found this from here, https://coderwall.com/p/v290ta/raspberry-pi-wifi-setup-with-wpa2-psk-aes (it might or might not work)

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
  ssid="replace_with_your_ssid"
  psk="replace_with_your_password"
  proto=RSN
  key_mgmt=WPA-PSK
  pairwise=CCMP
  group=CCMP
  auth_alg=OPEN
}

Then save that in a file called wpa_supplicant.conf. Kill the old wpa service and start a new one with the new file

$ sudo killall wpa_supplicant 
$ sudo /sbin/wpa_supplicant -i wlp3s0 -c /path/to/wpa_supplicant.conf

I'm hoping the dhcp client will start after you connect to the AP. If you still don't get an ip addr after you successfully connect to the AP, then you need to run dhclient to get an ip address.

$ sudo /sbin/dhclient wlp3s0

you can check to see if the ip got assigned with this command

$ ifconfig wlp3s0

You should see a line that says "inet' with your new assigned ip address.

Link to post
Share on other sites

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 post
Share on other sites

if you are getting "successfully initialized wpa_supplicant", check that you have an associated Access Point to that adapter

$ iwconfig wlp3s0

it should state some info about the AP. If you are connected to the AP, then you can run the DHCP client:

$ sudo dhclient wlp3s0

this will start the DHCP client and automagically assign the ip addr to the adapter. the next thing to do after that is assign the correct DNS server address. "If" you trust google, you can use their dns servers:

$ cat << EOF | sudo tee /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4
EOF

or you can replace those ip's with your chosen dns serevrs.

You should be ready to surf the interwebs after that 😊

  • Like 1
Link to post
Share on other sites

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>

 

Edited by PoSHMagiC0de
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...