[SOLVED] Can connect to router but can't receive internet: need help with logs
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My wlo1 interface is "UP", in 192.168.1.1 i see my laptop ip as connected device, but i have no internet connection.
I can't find the answer in logs. Any help will be greatly appriciated.
My logs:
Code:
Jun 13 19:45:08 flower wpa_supplicant[1103]: Successfully initialized wpa_supplicant
Jun 13 19:45:08 flower wpa_supplicant[506]: wlo1: CTRL-EVENT-TERMINATING
Jun 13 19:45:08 flower wpa_supplicant[1107]: nl80211: Failed to open /proc/sys/net/ipv6/conf/wlo1/drop_unicast_in_l2_multicast: No such file or directory
Jun 13 19:45:08 flower wpa_supplicant[1107]: nl80211: Failed to set IPv6 unicast in multicast filter
Jun 13 19:45:08 flower wpa_supplicant[1107]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
Jun 13 19:45:08 flower wpa_supplicant[1107]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
Jun 13 19:45:08 flower dhclient[1117]: Internet Systems Consortium DHCP Client 4.4.1
Jun 13 19:45:08 flower ifup[1081]: Internet Systems Consortium DHCP Client 4.4.1
Jun 13 19:45:08 flower ifup[1081]: Copyright 2004-2018 Internet Systems Consortium.
Jun 13 19:45:08 flower ifup[1081]: All rights reserved.
Jun 13 19:45:08 flower ifup[1081]: For info, please visit https://www.isc.org/software/dhcp/
Jun 13 19:45:08 flower dhclient[1117]: Copyright 2004-2018 Internet Systems Consortium.
Jun 13 19:45:08 flower dhclient[1117]: All rights reserved.
Jun 13 19:45:08 flower dhclient[1117]: For info, please visit https://www.isc.org/software/dhcp/
Jun 13 19:45:08 flower dhclient[1117]:
Jun 13 19:45:08 flower dhclient[1117]: Listening on LPF/wlo1/b8:81:98:cb:ef:a8
Jun 13 19:45:08 flower ifup[1081]: Listening on LPF/wlo1/b8:81:98:cb:ef:a8
Jun 13 19:45:08 flower ifup[1081]: Sending on LPF/wlo1/b8:81:98:cb:ef:a8
Jun 13 19:45:08 flower ifup[1081]: Sending on Socket/fallback
Jun 13 19:45:08 flower ifup[1081]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 3
Jun 13 19:45:08 flower dhclient[1117]: Sending on LPF/wlo1/b8:81:98:cb:ef:a8
Jun 13 19:45:08 flower dhclient[1117]: Sending on Socket/fallback
Jun 13 19:45:08 flower dhclient[1117]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 3
Jun 13 19:45:11 flower dhclient[1117]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 8
Jun 13 19:45:11 flower ifup[1081]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 8
Jun 13 19:45:12 flower wpa_supplicant[1107]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=RU
Jun 13 19:45:12 flower wpa_supplicant[1107]: wlo1: SME: Trying to authenticate with 5c:77:76:6e:0d:7b (SSID='MW40V_0D7B' freq=2462 MHz)
Jun 13 19:45:12 flower kernel: [ 534.670340] wlo1: authenticate with 5c:77:76:6e:0d:7b
Jun 13 19:45:12 flower kernel: [ 534.673342] wlo1: send auth to 5c:77:76:6e:0d:7b (try 1/3)
Jun 13 19:45:12 flower wpa_supplicant[1107]: wlo1: Trying to associate with 5c:77:76:6e:0d:7b (SSID='MW40V_0D7B' freq=2462 MHz)
Jun 13 19:45:12 flower kernel: [ 534.676576] wlo1: authenticated
Jun 13 19:45:12 flower kernel: [ 534.678620] wlo1: associate with 5c:77:76:6e:0d:7b (try 1/3)
Jun 13 19:45:12 flower kernel: [ 534.698453] wlo1: RX AssocResp from 5c:77:76:6e:0d:7b (capab=0x411 status=0 aid=1)
Jun 13 19:45:12 flower wpa_supplicant[1107]: wlo1: Associated with 5c:77:76:6e:0d:7b
Jun 13 19:45:12 flower wpa_supplicant[1107]: wlo1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 13 19:45:12 flower kernel: [ 534.703233] wlo1: associated
Jun 13 19:45:12 flower wpa_supplicant[1107]: wlo1: WPA: Key negotiation completed with 5c:77:76:6e:0d:7b [PTK=CCMP GTK=TKIP]
Jun 13 19:45:12 flower wpa_supplicant[1107]: wlo1: CTRL-EVENT-CONNECTED - Connection to 5c:77:76:6e:0d:7b completed [id=0 id_str=]
Jun 13 19:45:19 flower dhclient[1117]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 19
Jun 13 19:45:19 flower ifup[1081]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 19
Jun 13 19:45:38 flower dhclient[1117]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 9
Jun 13 19:45:38 flower ifup[1081]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 9
Jun 13 19:45:38 flower dhclient[1117]: DHCPOFFER of 192.168.1.122 from 192.168.1.1
Jun 13 19:45:38 flower ifup[1081]: DHCPOFFER of 192.168.1.122 from 192.168.1.1
Jun 13 19:45:38 flower ifup[1081]: DHCPREQUEST for 192.168.1.122 on wlo1 to 255.255.255.255 port 67
Jun 13 19:45:38 flower dhclient[1117]: DHCPREQUEST for 192.168.1.122 on wlo1 to 255.255.255.255 port 67
Jun 13 19:45:38 flower dhclient[1117]: DHCPACK of 192.168.1.122 from 192.168.1.1
Jun 13 19:45:38 flower ifup[1081]: DHCPACK of 192.168.1.122 from 192.168.1.1
Jun 13 19:45:38 flower ifup[1081]: suspect value in domain_name option - discarded
Jun 13 19:45:38 flower ifup[1081]: suspect value in domain_name option - discarded
Jun 13 19:45:38 flower dhclient[1117]: suspect value in domain_name option - discarded
Jun 13 19:45:38 flower dhclient[1117]: suspect value in domain_name option - discarded
Jun 13 19:45:38 flower dhclient[1117]: bound to 192.168.1.122 -- renewal in 18374 seconds.
Jun 13 19:45:38 flower ifup[1081]: bound to 192.168.1.122 -- renewal in 18374 seconds.
Jun 13 19:45:38 flower systemd[1]: Started Raise network interfaces.
Thank you!
Last edited by OlgaM; 06-15-2020 at 08:24 PM.
Reason: addition info
Your PC has successfully created a wireless connection to the router and received an IP address from it, namely 192.168.1.122.
Now, can you access the router? For example ping 192.168.1.1, or put 192.168.1.1 into the web browser's address field? Or do whatever else is required to access that router?
Then, do you have connectivity to an IP address like 1.1.1.1? If so, you have an internet connection.
Perhaps you mean that you can't access a name like google.com. In this case, your problem is related to an ill-configured domain name service.
Let us know the results of the above tests (192.168.1.1, 1.1.1.1, google.com). Also show us the DNS configuration starting with /etc/resolv.conf, and the routing table (output of the ip route command).
berndbausch, thank you very much for information about accessing the router home page! I don't know why, but when I opened 192.168.1.1 in browser everything start working! Now i can access google.com, forum, 192.168.1.1 (my router home pages) and 1.1.1.1 (The free app that makes your Internet safer). I can also ping google.com and 192.168.1.1.
/etc/resolv.conf
Code:
nameserver 192.168.1.1
Routing table
Code:
ip route
default via 192.168.1.1 dev wlo1
192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.122
Distro and version
Code:
cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
uname -a
Linux flower 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5 (2019-06-19) x86_64 GNU/Linux
Can i ask about IPs, what is better to use: dynamic (DHCP) or static IP on laptop? And what way it's better to bring interface up: on start (automatically) or manually (ip link set wlo1 up or ifup wlo1 etc)?
Can i ask about IPs, what is better to use: dynamic (DHCP) or static IP on laptop? And what way it's better to bring interface up: on start (automatically) or manually (ip link set wlo1 up or ifup wlo1 etc)?
There is no "better" or "worse". If you have a need for a guaranteed stable IP address, you should make it static, but if not, DHCP is automatic and permits you to not worry about the network configuration.
What you call "manual" interface configuration has the huge disadvantage of not being persistent. This means that you would have to enter the ip link command each time you reboot, and that any process that needs the network while the computer is starting up won't function correctly until you enter the command. You use ip link for tests or troubleshooting, not for permanent configurations.
berndbausch, thank you a lot for helpful details! Finally, i set up static ip for my laptop. Everything is o'key. The only thing that makes me surprised is permanent dhcp address. During two days i am checking 192.168.1.1 and every day it shows me the same dhcp address for my laptop (and smartphone). I was thinking that dynamic address should changes every 24 hours. Today i changed laptop's ip from dhcp to static in etc/network/interfaces, but router's home page still shows the old dhcp address. In ip addr show i see my new static ip. I don't understand why server (router) was making my dhcp address persistent in the past and don't want to change it to static now.
Thank you for all answers! Now router shows correct static ip address. Maybe cache is refreshed, i don't know. It seems to me that when i changed ip from dhcp to static internet become faster
Internet working, i updated my debian. During update process i didn't enter 'autoremove'. I had lot's of problems because of broken dependencies when i use 'autoremove' in the past. Now i have two kernel images in boot folder. Can i ask:
- should i use 'autoremove' now for deleting duplicate kernel images etc? Is it safe?
- i made some changes in system files (truncate bluetooth and P2P configs etc). Is it possible to save these changes during the next system updates?
Internet working, i updated my debian. During update process i didn't enter 'autoremove'. I had lot's of problems because of broken dependencies when i use 'autoremove' in the past. Now i have two kernel images in boot folder. Can i ask:
- should i use 'autoremove' now for deleting duplicate kernel images etc? Is it safe?
- i made some changes in system files (truncate bluetooth and P2P configs etc). Is it possible to save these changes during the next system updates?
These questions have nothing to do with networking, your router or logs. Better ask a new question, and put it in the Debian forum.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.