Description of problem: I created a script to do my mageia customization on a every fresh installation . This includes networkmanager.. It used to work fine until recently. The wifi connects just fine but with no internet, I removed networkmanager and I still don't have internet on wifi. It works great on ethernet. It also works fine before running my script. I guess installing networkmanager breaks something. please help I am using mageia Cauldron 8 kernel-desktop-5.6.4
I reinstalled Mageia 8 using the Mageia 7 network installer.. I just modified the path on the mirrors to point to cauldron. Everything seems to be fine... I had ethernet connected, once I connected to wifi I rebooted and wifi seems to connect fine but still no internet.. ping google.com ping: google.com: Name or service not known My laptop is a Lenovo Thinkpad T430 lspcidrake -v lwlwofo
lspcidrake -v lwlwifi : Intel Corporation Centrino Advanced - N 6200
I reinstaslled again from network for the third time without any change and still the same problem.. Regards
Use MCC (or drakconnect from the command line) to remove the wifi interface, and then edit /etc/NetworkManager/NetworkManager.conf to remove the ifcfg clause, and reboot. The ifcfg stuff tells NM to deferto the old MGA stuff if it finds anything, and these days they frequently conflict. Removing it and the interface leaves NM in control, which may work better for you.
CC: (none) => ftg
Thanks for your learned comment, Frank.
CC: (none) => lewyssmith
Hello Frank Thanks for your help. I seached for /etc/NetworkManager/NetworkManager.conf and there isn't any. Like I mentioned earlier, I did a third reinstallation but the last one without any changes (No Networkmanager installation). Fresh Mageia 8 installation using network install via ethernet.. Once restarted I configure WIFI and it does connect.. Still no internet. NetApplet is in Green and it does display IP address, GateWay and DNS. I removed the wifi interface rebooted, added the Wifi again... still having the problem. if I ping google I still get: ping: google.com: Name or service not known. If I connect ethernet works great. Mageia Control Center Hardware show Centriono Advanced-N 6200 I have another PC connected via Wifi using Mageia and it works great. But with different hardware AFAIK... I have another same model laptop I will test later tonight to discard a hardware problem... I'll keep you posted.. ;-)
Hi Ezequiel, You miss the point. You won't find an /etc/NetworkManager/NetworkManager.conf unless NM is actually installed. Install NM and then follow the advice above.
Hello Frank I did what you recommended, edited /etc/NetworkManager/NetworkManager.conf to remove the ifcfg clause, and rebooted. Network Manager shows Wi-Fi Connected to Infini,,,, Still no internet # Ping google.com Ping: google.com: name or service not known Same problem as MGA draknet. Regards
@Frank : can I leave this with you for the present; you know what you are talking about. @Ezequie: From comment 0, comment 3, comment 6: > It also works fine before running my script > --- > I reinstaslled again from network for the third time without any change > and still the same problem.. > --- > Fresh Mageia 8 installation using network install via ethernet.. > Once restarted I configure WIFI and it does connect.. Still no internet. The first says it worked as provided, the second & third imply it did not. Can we be clear on this: - did it [Internet via WiFi] ever really work properly? - in the last two cases [no WiFi Internet], was the script run? It might be worth attaching the relevant part of the script (if it is small, all of it). Also, if the problem really does only arise after running it, try commenting out in it the relevant lines to see whether Internet then works via WiFi. If it does, it will show just what lines are causing the problem. And do you have to use Network Manager if it works without it?
Yes, Lewis, I'll take it. @Ezequie we have to separate the various use cases you have here. The point of all that stuff about NM is to compare a case with MGA netapplet and no NM to a case with NM and no net-applet. I really don't care which scenario you use, as long as they aren't both active and interfering with each other. Please fire up one or the other, and then... 1) If you believe that wifi is connecting, tell me exactly why. 2) Are you using DHCP for wifi or a static IP ? If DHCP, are you using the router's DHCP ? 3) If your wired ethernet works, is it using DHCP, and what DHCP server are you using for that ? 4) Please post the output of "route -n" when the wifi is not working. 5) Try a case where you remove the wired interface completely and then try to enable wifi.
Sorry for confusing you Guys.. Let me explain what I did.. I installed MGA using Mageia-7.1-netinstall-nonfree-x86_64 but changed repository path to install Cauldron. I chose to activate all repositories (Nonfree and Tainted as well) on the installer.. (I also tried without selecting Nonfree and Tainted before) Once MGA is installed I loaded MGA Network Center to connect to my WiFi and I got a popup notification displaying: Network is up on Interfacer (Wi-FI) (wlp3s0) Right now net_applet says my wifi is connected and it is on green.. and it displays an ip Address, DNS and GW. Network Center has a disconnect option which I guess it should be connected... I open Firefox and no internet.. ping doesn't reply... This problem happens with or without NM. I tested them both on different installations on this same Laptop. I repeated this steps with MGA 7.1 and it works fine.. MGA 8 Does not. Regards Ezequiel Partida
OK, so the answers to the questions I asked ?
I hope this helps Frank.. I appreciate your patience. 1) If you believe that wifi is connecting, tell me exactly why. Because Net_applet says it is... And it displays an IP Number. 2) Are you using DHCP for wifi or a static IP ? If DHCP, are you using the router's DHCP ? Yes I am using DHCP for wifi and using router's DHCP. 3) If your wired ethernet works, is it using DHCP, and what DHCP server are you using for that ? Yes, my wired ethernet is usind DHCP from the router, both Wifi and ethernet have the same options activated (Automatic IP )BootP/DHCP) get DNS servers from DHCP, start connection at boot) 4) Please post the output of "route -n" when the wifi is not working.` [root@localhost ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 wlp3s0 169.254.0.0 0.0.0.0 255.255.0.0 U 1003 0 0 wlp3s0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp3s0 5) Try a case where you remove the wired interface completely and then try to enable wifi. [root@localhost ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 enp0s25 169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 enp0s25 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp0s25 [root@localhost ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 wlp3s0 169.254.0.0 0.0.0.0 255.255.0.0 U 1003 0 0 wlp3s0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp3s0
So, the machine is not *directly* connected to the internet, but only through the 192.168.1.254 gateway address, which is an intranet address. So, just to be clear, the setup that gives you Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 enp0s25 169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 enp0s25 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp0s25 gets you to the internet, but the setup that gives you [root@localhost ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 wlp3s0 169.254.0.0 0.0.0.0 255.255.0.0 U 1003 0 0 wlp3s0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp3s0 does *not*, and they're both gating through the same router. This is extremely odd. The routing table is routing packets identically for both, and it shouldn't matter from which interface they originate. Can you post the contents of /etc/resolv.conf in both cases ?
Umm, also can you pick a host that you *can* find under wired, e. g. " host (hostname)" and then try to ping that IP address under wifi ?
ok. This IP addres is from Amazon.com Under Wired.. [root@localhost ~]# ping 205.251.242.103 PING 205.251.242.103 (205.251.242.103) 56(84) bytes of data. 64 bytes from 205.251.242.103: icmp_seq=1 ttl=228 time=69.1 ms 64 bytes from 205.251.242.103: icmp_seq=2 ttl=228 time=68.7 ms 64 bytes from 205.251.242.103: icmp_seq=3 ttl=228 time=68.9 ms 64 bytes from 205.251.242.103: icmp_seq=4 ttl=228 time=69.0 ms Under Wi-Fi [root@localhost ~]# ping 205.251.242.103 PING 205.251.242.103 (205.251.242.103) 56(84) bytes of data. From 192.168.1.71 icmp_seq=1 Destination Host Unreachable ping: sendmsg: Operation not permitted From 192.168.1.71 icmp_seq=2 Destination Host Unreachable ping: sendmsg: Operation not permitted From 192.168.1.71 icmp_seq=3 Destination Host Unreachable ping: sendmsg: Operation not permitted From 192.168.1.71 icmp_seq=4 Destination Host Unreachable ping: sendmsg: Operation not permitted From 192.168.1.71 icmp_seq=5 Destination Host Unreachable ping: sendmsg: Operation not permitted From 192.168.1.71 icmp_seq=6 Destination Host Unreachable ping: sendmsg: Operation not permitted From 192.168.1.71 icmp_seq=7 Destination Host Unreachable ping: sendmsg: Operation not permitted From 192.168.1.71 icmp_seq=8 Destination Host Unreachable ping: sendmsg: Operation not permitted From 192.168.1.71 icmp_seq=9 Destination Host Unreachable ping: sendmsg: Operation not permitted
CC: lewyssmith => (none)
/etc/resolv.conf ?
resolv.conf Wired: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.1.254 Wi-fi (Non Working) # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.1.254
OK, the configuration files are all correct. If the network is unreachable from wifi, then it really isn't connected. Can you post the exact messages from journalctl that show it connecting *and* scan ahead from there to ensure that it doesn't disconnect when you're not looking ?
Sorry Frank.. You you want me to post all journalctl list or is there a way for me to just log the network?.. please advice.. I'm still not a guru as you are!! ;-)
Sorry, I should have given more detail... journalctl can filter by the message-issuing component, but since I don't use net-applet, I don't know what component to tell you. So... 1) Reboot (this will limit the size of the full journalctl) 2) Let or cause the failure to occur 3) As root, issue "journalctl -b >/tmp/log" 4) Browse the /tmp/log file and search for the interface name of your wifi (wlp3s0) 5) Note the component name at the start of the messages related to the connection attempt to wifi, call it XXX 6) Now issue "journalctl -b -u XXX >/tmp/log" This should put only the messages for net-applet in the /tmp/log file. If the file is small, you can just paste the contents here, otherwise attach the file.
OK, just so I get my ducks in a row before I involve others, 1) you mention above that you installed cauldron using the MGA7 install media but using the cauldron repositories. I'm not sure that works. Can you install using the cauldron install media ? iwlwifi is a pretty well supported driver, and it may be that the version being pulled in by the MGA7 install is backlevelled. 2) Just to verify, the same install procedure using MGA 7 repos gives you working wifi ?
Hello Frank, I hope I did it correctly. -- Logs begin at Mon 2020-04-20 15:20:38 CDT, end at Wed 2020-04-22 01:08:01 CDT. -- Apr 21 14:02:51 localhost systemd[1]: Starting LSB: Bring up/down networking... Apr 21 14:02:51 localhost systemd-sysctl[1537]: Not setting net/ipv4/conf/all/rp_filter (explicit setting exists). Apr 21 14:02:51 localhost systemd-sysctl[1537]: Not setting net/ipv4/conf/default/rp_filter (explicit setting exists). Apr 21 14:02:51 localhost systemd-sysctl[1537]: Not setting net/ipv4/conf/all/accept_source_route (explicit setting exists). Apr 21 14:02:51 localhost systemd-sysctl[1537]: Not setting net/ipv4/conf/default/accept_source_route (explicit setting exists). Apr 21 14:02:51 localhost systemd-sysctl[1537]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Apr 21 14:02:51 localhost systemd-sysctl[1537]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Apr 21 14:02:52 localhost network[1079]: Bringing up loopback interface: [ OK ] Apr 21 14:02:52 localhost ifplugd(enp0s25)[2148]: ifplugd 0.28 initializing. Apr 21 14:02:52 localhost ifplugd(enp0s25)[2148]: Using interface enp0s25/F0:DE:F1:14:A2:15 with driver <e1000e> (version: 3.2.6-k) Apr 21 14:02:52 localhost ifplugd(enp0s25)[2148]: Using detection mode: SIOCETHTOOL Apr 21 14:02:52 localhost ifplugd(enp0s25)[2148]: Initialization complete, link beat not detected. Apr 21 14:02:52 localhost network[1079]: Bringing up interface enp0s25: [ OK ] Apr 21 14:02:53 localhost network[1079]: Bringing up interface wlp3s0: Apr 21 14:02:53 localhost network[2207]: Bringing up interface wlp3s0: Apr 21 14:02:53 localhost network[2207]: Apr 21 14:02:53 localhost network[2207]: rror for wireless request "Set Encode" (8B2A) : Apr 21 14:02:53 localhost network[2207]: SET failed on dev Apr 21 14:02:53 localhost network[2215]: SET failed on dev Apr 21 14:02:53 localhost network[2215]: uccessfully initiaioctl[SIOCSIWENCODEEXT]: Invalid argument Apr 21 14:02:53 localhost network[2215]: ioctl[SIOCSIWENCODEEXT]: Invalid argument Apr 21 14:02:53 localhost ifplugd(wlp3s0)[2219]: ifplugd 0.28 initializing. Apr 21 14:02:53 localhost ifplugd(wlp3s0)[2219]: Using interface wlp3s0/00:27:10:C0:03:A8 with driver <iwlwifi> (version: 5.6.5-desktop-2.mga8) Apr 21 14:02:53 localhost ifplugd(wlp3s0)[2219]: Using detection mode: SIOCETHTOOL Apr 21 14:02:53 localhost ifplugd(wlp3s0)[2219]: Initialization complete, link beat not detected. Apr 21 14:02:53 localhost network[1079]: [ OK ] Apr 21 14:02:53 localhost systemd-sysctl[2238]: Not setting net/ipv4/conf/all/rp_filter (explicit setting exists). Apr 21 14:02:53 localhost systemd-sysctl[2238]: Not setting net/ipv4/conf/default/rp_filter (explicit setting exists). Apr 21 14:02:53 localhost systemd-sysctl[2238]: Not setting net/ipv4/conf/all/accept_source_route (explicit setting exists). Apr 21 14:02:53 localhost systemd-sysctl[2238]: Not setting net/ipv4/conf/default/accept_source_route (explicit setting exists). Apr 21 14:02:53 localhost systemd-sysctl[2238]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Apr 21 14:02:53 localhost systemd-sysctl[2238]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Apr 21 14:02:53 localhost systemd[1]: Started LSB: Bring up/down networking. Apr 21 14:02:54 localhost ifplugd(enp0s25)[2148]: Link beat detected. Apr 21 14:02:55 localhost ifplugd(enp0s25)[2148]: Executing '/etc/ifplugd/ifplugd.action enp0s25 up'. Apr 21 14:02:55 localhost dhclient[2294]: DHCPREQUEST for 192.168.1.72 on enp0s25 to 255.255.255.255 port 67 Apr 21 14:02:55 localhost dhclient[2294]: DHCPACK of 192.168.1.72 from 192.168.1.254 Apr 21 14:02:55 localhost dhclient[2294]: bound to 192.168.1.72 -- renewal in 33684 seconds. Apr 21 14:02:55 localhost ifplugd(enp0s25)[2148]: client: Determining IP information for enp0s25... done. Apr 21 14:02:55 localhost ifplugd(enp0s25)[2148]: client: INFO : [ipv6_wait_tentative] Waiting for interface enp0s25 IPv6 address(es) to leave the 'tentative' state Apr 21 14:02:56 localhost ifplugd(enp0s25)[2148]: client: INFO : [ipv6_wait_tentative] Waiting for interface enp0s25 IPv6 address(es) to leave the 'tentative' state Apr 21 14:02:56 localhost ipv6_wait_tentative[2603]: Waiting for interface enp0s25 IPv6 address(es) to leave the 'tentative' state Apr 21 14:02:57 localhost ifplugd(wlp3s0)[2219]: Link beat detected. Apr 21 14:02:57 localhost ifplugd(enp0s25)[2148]: Program executed successfully. Apr 21 14:02:58 localhost ifplugd(wlp3s0)[2219]: Executing '/etc/ifplugd/ifplugd.action wlp3s0 up'. Apr 21 14:02:58 localhost dhclient[2845]: DHCPREQUEST for 192.168.1.71 on wlp3s0 to 255.255.255.255 port 67 Apr 21 14:02:58 localhost dhclient[2845]: DHCPACK of 192.168.1.71 from 192.168.1.254 Apr 21 14:02:58 localhost dhclient[2845]: bound to 192.168.1.71 -- renewal in 38003 seconds. Apr 21 14:02:58 localhost ifplugd(wlp3s0)[2219]: client: Determining IP information for wlp3s0... done. Apr 21 14:02:58 localhost ifplugd(wlp3s0)[2219]: Program executed successfully. Apr 21 14:04:03 localhost ifplugd(enp0s25)[2148]: Link beat lost. Apr 21 14:04:09 localhost ifplugd(enp0s25)[2148]: Executing '/etc/ifplugd/ifplugd.action enp0s25 down'. Apr 21 14:04:10 localhost ifplugd(enp0s25)[2148]: Program executed successfully. Apr 21 14:04:25 localhost ifplugd(wlp3s0)[2219]: Link beat lost. Apr 21 14:04:25 localhost ifplugd(wlp3s0)[2219]: Executing '/etc/ifplugd/ifplugd.action wlp3s0 down'. Apr 21 14:04:25 localhost ifplugd(wlp3s0)[2219]: Program executed successfully. Apr 21 14:04:25 localhost ifplugd(wlp3s0)[2219]: Exiting. Apr 21 14:04:52 localhost ifplugd(enp0s25)[2148]: Link beat detected. Apr 21 14:04:53 localhost ifplugd(enp0s25)[2148]: Executing '/etc/ifplugd/ifplugd.action enp0s25 up'. Apr 21 14:04:53 localhost dhclient[6294]: DHCPREQUEST for 192.168.1.72 on enp0s25 to 255.255.255.255 port 67 Apr 21 14:04:53 localhost dhclient[6294]: DHCPACK of 192.168.1.72 from 192.168.1.254 Apr 21 14:04:54 localhost dhclient[6294]: bound to 192.168.1.72 -- renewal in 35068 seconds. Apr 21 14:04:54 localhost ifplugd(enp0s25)[2148]: client: Determining IP information for enp0s25... done. Apr 21 14:04:54 localhost ifplugd(enp0s25)[2148]: Program executed successfully. Apr 21 14:05:35 localhost ifplugd(enp0s25)[2148]: Link beat lost. Apr 21 14:05:41 localhost ifplugd(enp0s25)[2148]: Executing '/etc/ifplugd/ifplugd.action enp0s25 down'. Apr 21 14:05:42 localhost ifplugd(enp0s25)[2148]: Program executed successfully.
This doesn't make sense. The log shows that your wifi actually contacted your DHCP server and got an ACK for an IP address, but then disconnected. Also, your wired did the same but then disconnected and reconnected. Just to reconfirm what you said initially, both wired and wifi work *before* you run your post-install script, but wifi breaks after ? If that's true, please post this script. Also, I thought that the parameters for the test were that you removed the interface for the wired NIC, but the log clearly shows both of them attempting to activate at the same time. They are requesting different DHCP IP addresses, so I don't see why this would be a problem ordinarily, but it complicates the test scenario. Can you use MCC to delete the wired interface, try again, and capture the same log data ? There's a possibility here that the wired and wifi interfaces don't know that they're sharing, and that whichever one activates last reconfigures the routing table to exclude the other.
Keywords: (none) => NEEDINFO
There are good enough and useful informations, (In reply to Ezequiel Partida from comment #0) > I created a script to do my mageia customization on a every fresh > installation . This includes networkmanager.. It used to work fine until > recently. > > The wifi connects just fine but with no internet, I removed networkmanager > and I still don't have internet on wifi. It works great on ethernet. > Frank Griffin asked you, Ezequiel, to post your script in order to know why this is not functioning in Mageia 8, currently in beta stage. Unless you do not so in a short period, I'm encline to close this as INVALID because you said yourself: > It also works fine before running my script. I guess installing > networkmanager breaks something. I don't think NM breaks something. Reinstalling Mageia 8 beta 1 from Classic ISO and do system upgrade, and do the following steps here: https://wiki.mageia.org/en/Switching_to_networkmanager In case you're running Plasma, it is good to install "plasma-applet-nm" package. Feel free to repoen this bug if whereas all solutions above do not give you a working WiFi connection.
Resolution: (none) => INVALIDStatus: NEW => RESOLVED