Mageia forum

hello again people
i want to ask about surfing the internet problem in beta 3
i already installed it and everything is good except FN buttons
anyway
my problem is simple .....
when i try to connect with the router everything going smooth
but after surfing the internet ... i lose connection to the internet suddenly
i saw there is no problem between router and laptop wifi connection ....... but i cant connect to the internet
the most confusing thing is there is no problem with other devices that surfing the internet via that router
so .... is there any patch for such problem like that now .... or didnt anyone face it until now
my wifi adaptor name is
RTL8723BE PCIe
and sorry to bother you

As you don't provide any logs or detailed output, let me take a guess:

Maybe it's due to cosmic radiation?

doktor5000 wrote:As you don't provide any logs or detailed output, let me take a guess:

Maybe it's due to cosmic radiation?

you are right ...... maybe its a cosmatic radiation .........

.....................................

cut that out Dokto5000 .... i am dead serious

all what i know .... i already told you about it

you are the developer who knows the command line not me .....

anyway thnks and goodbye

Doktors right we are grappling around in the dark (like you are) without some intel, into the problem.

there's enough advise on this forum on how to proceed with basic diagnostics that could make Docktors reply less of a guess.

and im guessing you took no advise from my help us help you, on avoiding beta or brand new releases until you are
a bit more capable of helping yourself.

I haven't upgraded my laptop yet, to beta 3 , only my workstation as that's simpler to get going, with constantly changing and evolving beta releases, and im more than capable of helping myself.

anyone of the recent dozen or so kernel updates could be responsible for wifi issues.

wifi is notoriously troublesome on new releases, so there could be a genuine reason for your trouble or a user error.

open a command line , shell/terminal and when the connection fails run "dmesg", and see if there are any errors there relating to
network connections.

are you using kde and the netapplet or network manager to manage your connection to wifi.

what type of encryption are you using, wep, wpa, wpa2, auto , managed or adhoc

what router are you using (might seem to you that mageia should work with all routers, but routers ahave bugs and firmware versions too and could have specific trouble with some versions and one specific operating system)

anyhow as i hope ive indicated there are any number of variations in what could be behind the issue, that its impossible to guess, without having a little joke.



regards peter

almusalimalmusalimah wrote:all what i know .... i already told you about it

you are the developer who knows the command line not me .....

Well, I'm also a simple forum user who can use the search function .. showing that you already had some threads in the past with wireless issues.

viewtopic.php?f=25&t=1407
viewtopic.php?f=25&t=2774
viewtopic.php?f=25&t=7211

So you already have been given some pointers on what to look for, and Peter provided some more.
If you don't provide further information we can't offer much help.

Will Mr.peter
My road plan is so simple
Before official release i install the last version that has been released
like now when i installed B3 to see if there is any bug that hasnt been discovered yet then i report about it here And if there is no one has face it yet then i will report about it to bugs team
....
I think now you understand me ....
....
And about the kind of router .... Its the same problem with any type of router like android phone / adsl router / huawei 4g portable router all of them with wpa2 encryption
....
And about the environment then its KDE
And i am useing mageia network manager not kde netwok manager
....
Anyway thanks and sorry to bother both of you and goodbye

Please at least provide the output of the following commands as root:

Code: Select all

ifconfig -a
netstat -rn
cat /etc/hosts
cat /etc/resolv.conf
systemctl status network.service -a


here are the results

***** keep in mind these results are after the problem happend *****

Code: Select all


[root@localhost mageia]# ifconfig -a
eno1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether d0:bf:9c:8d:65:02  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 0  (Local Loopback)
        RX packets 555  bytes 49510 (48.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 555  bytes 49510 (48.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlo1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.8.101  netmask 255.255.255.0  broadcast 192.168.8.255
        inet6 fe80::3668:95ff:fe6c:1f73  prefixlen 64  scopeid 0x20<link>
        ether 34:68:95:6c:1f:73  txqueuelen 1000  (Ethernet)
        RX packets 339  bytes 383486 (374.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 495  bytes 34797 (33.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
       
==============================================================================================

[root@localhost mageia]# netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         192.168.8.1     0.0.0.0         UG        0 0          0 wlo1
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 wlo1
192.168.8.0     0.0.0.0         255.255.255.0   U         0 0          0 wlo1

==============================================================================================

[root@localhost mageia]# cat /etc/hosts
127.0.0.1               localhost

==============================================================================================

[root@localhost mageia]# cat /etc/resolv.conf
# 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.8.1
search www.huaweimobilewifi.com

==============================================================================================

[root@localhost mageia]# systemctl status network.service -a
● network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network)
   Active: active (running) since Wed 2015-04-22 22:23:17 AST; 22min ago
  Process: 985 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/network.service
           ├─1724 /sbin/ifplugd -I -b -i eno1
           ├─2022 /usr/sbin/wpa_supplicant -B -i wlo1 -c /etc/wpa_supplicant....
           ├─2024 /sbin/ifplugd -I -b -i wlo1
           └─2427 dhclient -1 -q -lf /var/lib/dhclient/dhclient--wlo1.lease -...

Apr 22 22:23:17 localhost systemd-sysctl[2045]: Overwriting earlier assignment of kernel/sysrq in file '/etc/sysctl.d/51-alt-sysrq.conf'.
Apr 22 22:23:18 localhost ifplugd(wlo1)[2024]: Link beat detected.
Apr 22 22:23:19 localhost ifplugd(wlo1)[2024]: Executing '/etc/ifplugd/ifplugd.action wlo1 up'.
Apr 22 22:23:21 localhost dhclient[2166]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 7
Apr 22 22:23:24 localhost dhclient[2166]: DHCPREQUEST on wlo1 to 255.255.255.255 port 67
Apr 22 22:23:24 localhost dhclient[2166]: DHCPOFFER from 192.168.8.1
Apr 22 22:23:24 localhost dhclient[2166]: DHCPACK from 192.168.8.1
Apr 22 22:23:24 localhost dhclient[2166]: bound to 192.168.8.101 -- renewal in 34928 seconds.
Apr 22 22:23:24 localhost ifplugd(wlo1)[2024]: client: Determining IP information for wlo1... done.
Apr 22 22:23:25 localhost ifplugd(wlo1)[2024]: Program executed successfully.



OK so it looks like the wifi is still up, so ignore dns for now lets see what IP is doing

first can you ping your router 192.168.8.1

so open a terminal and type

ping 192.168.8.1

next ensure that traceroute is installed and pick a place on the internet and trace it, lets say 8.8.8.8 which i think is Google public dns

google-public-dns-a.google.com (8.8.8.8) 4.243 ms 3.986 ms 3.979 ms

can you get there

if you can then its dns that's the problem

according to your config dhcp has assigned you 192.168.8.1 as the dns , in other words your wlan is acting as a dns proxy

Ive seen situations where this fails (tiscalli for example) and end up setting peoples dns to 8.8.8.8

before you change it you can prove this by the following

install nslookup and type

nslookup forums.mageia.org 8.8.8.8


you should get something like

Code: Select all

 nslookup forums.mageia.org 8.8.8.8
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
forums.mageia.org       canonical name = alamut.mageia.org.
Name:   alamut.mageia.org
Address: 212.85.158.146



anyway if that works change your dns in resolv.conf to 8.8.8.8

it will get overwritten if you don't set it in the config, by dhcp the next time it renews but at least we will understand the problem.

regards peter

Well .......
Sorry Mr.Peter
But when the problem shown up i typed your command but it gave ma another resault ... And here it is

Code: Select all

[ root@localhost  mageia]# traceroute google.com
google.com: Name or service not known
Cannot handle "host" cmdline arg `google.com' on position 1(argc 1)

And about the first command .... Here its resaults

Code: Select all

[mageia@localhost ~]$ ping 192.168.8.1             
PING 192.168.8.1 (192.168.8.1) 56(84) bytes of data.
From 192.168.8.100 icmp_seq=1 Destination Host Unreachable
From 192.168.8.100 icmp_seq=2 Destination Host Unreachable
From 192.168.8.100 icmp_seq=3 Destination Host Unreachable
From 192.168.8.100 icmp_seq=4 Destination Host Unreachable
From 192.168.8.100 icmp_seq=5 Destination Host Unreachable
From 192.168.8.100 icmp_seq=6 Destination Host Unreachable
From 192.168.8.100 icmp_seq=7 Destination Host Unreachable
From 192.168.8.100 icmp_seq=8 Destination Host Unreachable
From 192.168.8.100 icmp_seq=9 Destination Host Unreachable
From 192.168.8.100 icmp_seq=10 Destination Host Unreachable
From 192.168.8.100 icmp_seq=11 Destination Host Unreachable
From 192.168.8.100 icmp_seq=12 Destination Host Unreachable
From 192.168.8.100 icmp_seq=13 Destination Host Unreachable
From 192.168.8.100 icmp_seq=14 Destination Host Unreachable
From 192.168.8.100 icmp_seq=15 Destination Host Unreachable
From 192.168.8.100 icmp_seq=16 Destination Host Unreachable
From 192.168.8.100 icmp_seq=17 Destination Host Unreachable
From 192.168.8.100 icmp_seq=18 Destination Host Unreachable
From 192.168.8.100 icmp_seq=19 Destination Host Unreachable
From 192.168.8.100 icmp_seq=20 Destination Host Unreachable
From 192.168.8.100 icmp_seq=21 Destination Host Unreachable
From 192.168.8.100 icmp_seq=22 Destination Host Unreachable
From 192.168.8.100 icmp_seq=23 Destination Host Unreachable
From 192.168.8.100 icmp_seq=24 Destination Host Unreachable
From 192.168.8.100 icmp_seq=25 Destination Host Unreachable
From 192.168.8.100 icmp_seq=26 Destination Host Unreachable
From 192.168.8.100 icmp_seq=27 Destination Host Unreachable
From 192.168.8.100 icmp_seq=28 Destination Host Unreachable
From 192.168.8.100 icmp_seq=29 Destination Host Unreachable
From 192.168.8.100 icmp_seq=30 Destination Host Unreachable
From 192.168.8.100 icmp_seq=31 Destination Host Unreachable
From 192.168.8.100 icmp_seq=32 Destination Host Unreachable
From 192.168.8.100 icmp_seq=33 Destination Host Unreachable
From 192.168.8.100 icmp_seq=34 Destination Host Unreachable
From 192.168.8.100 icmp_seq=35 Destination Host Unreachable
From 192.168.8.100 icmp_seq=36 Destination Host Unreachable
From 192.168.8.100 icmp_seq=37 Destination Host Unreachable
From 192.168.8.100 icmp_seq=38 Destination Host Unreachable
From 192.168.8.100 icmp_seq=39 Destination Host Unreachable
From 192.168.8.100 icmp_seq=40 Destination Host Unreachable
From 192.168.8.100 icmp_seq=41 Destination Host Unreachable
From 192.168.8.100 icmp_seq=42 Destination Host Unreachable
From 192.168.8.100 icmp_seq=43 Destination Host Unreachable
From 192.168.8.100 icmp_seq=44 Destination Host Unreachable
From 192.168.8.100 icmp_seq=45 Destination Host Unreachable
From 192.168.8.100 icmp_seq=46 Destination Host Unreachable
From 192.168.8.100 icmp_seq=47 Destination Host Unreachable
From 192.168.8.100 icmp_seq=48 Destination Host Unreachable
.
.
.
.
.
.
.
.
.
.
.
.
.
.



all the icmp_seq is Unreachable

I can verify that I have noticed the same problem in the past. Wifi connects with excellent signal quality but can't ping even local network. Connection show excellent signal, but no data gets through What is stranger is that another wifi adapter on the same machine may work OK.

So far I had attributed this behavior to compatibility issues with the wifi spot, but I am curious whether some other explanation exists.

I should add that I have noticed this with the previous 4 version as well. Can't remember if I had noticed on Mageia 3 though.

Without more information it's pretty hard to say that your situtation was the same problem. It might look like that to you, but the underlying issue might be totally different.
Sounds more like an issue with the wifi AP, which does not seem to hand out an IP adress via DHCP or something the like.

So together with a ping to your router IP and to 8.8.8.8 at least provide the following information as mentioned in previous post:
viewtopic.php?p=56185#p56185

something weird going on in your network

i would not take to much of the ping not responding your router might be rejecting pings.

do any of your other devices have ping if so try pinging the router from them.

also try putting 192.168.8.1 in your web browser does anything come up.

i said dont use dns, use ipaddresses only so you tracerouted google.com, not 8.8.8.8 as asked.

if its not clear to you, then ill spell it out

when diagnosing an ipaddress problem, using names is useless as you connectivity problems rely on dns, and if there's a connectivity issue
using google.com is the same as using icanttype.com, useless.
whenever you use ping/traceroute/webbrowser, and put in a name the first thing that happens is the NSS stack goes out to your configured resolver, to find the nearest dns server, and asks it to translate that to an IP. If that's not working because ip is stuffed, then its hiding the real symptom, and not much help.

use ipaddesses only, until the problem is resolved, i picked 8.8.8.8 as its a well known external address.

does your laptop have a wired ethernet port.

it would be worth checking that mageia is working correctly with a hardwired connection and your router first reliably, again as a method of eliminating
items from the problem.

also try clearing out you current wireless configs, and starting a fresh.
the wireless configs are stored in /etc/sysconfig/network-scripts/wireless.d

each of the contents is a mac address named file or hostname named file that stores the wireless configuration.

if this is stored wrong, it can give frustratingly annoying problems, until a good config is chosen, and so its sometimes better to clear it out
and start again.

back those files up somewhere in case you need one of them, for a hotel, or coffeeshop setting you have previously stored.

and then clear out the directory.

lets see how far trying the above helps.

regards peter

Hi,

Can you try the following?
1. If you connect this machine via Ethernet (wired connection), does ping 8.8.8.8 work? How about if you ping 192.168.8.1?
2. Try setting up static IP address using network manager something like 192.168.1.110 and DNS Server being 8.8.8.8 then try to ping google.com, 8.8.8.8 and 192.168.8.1.
3. Check your router settings, there could be some WiFi-specific configuration that you might have missed in allowing your computer proper access to its WiFi network.

doktor5000
==========

i already gave you all the results in
viewtopic.php?f=15&t=9718#p56264
or ... do you mean give you the results while pinging the ipaddress

***********************************

Mr.Peter
==========

other devices that using the same router has no any problem surfing the internet while in the same time i cant unless i cut the wireless connection then reconnect again
or using bots4ever method and set IP and DNS address manually but this method will not solve it
so Im in a loop ..... if the problem appear i need to set my connection manually and if it appear again i returned it to automaticlly

and about tracingout here is the result

Code: Select all

 [root@localhost mageia]# traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * localhost (192.168.8.100)  3005.937 ms !H


thats all i have now

and about wired ..... sorry i dont have
sorry .... bothring you all

I meant provide all the necessary information when the problem occurs. It doesn't help when you post it when connectivity is working fine.

E.g. in the previous posts you only provide the ping or traceroute output. Without more information, that alone is nearly useless.
In the traceroute output after 11 hops your own box answers that the target host is unreachable, that usually means you're missing a route to the target network/host in the routing table, or a default route or your router is borked.

Next time it happens please, in addition to previously requested output also add the output as root of

Code: Select all

ip route get 8.8.8.8
ip route get 192.168.8.1

(if 192.168.8.1 is the IP of your router)


Remember, we can only help you as far as you provide sufficient information. If you don't, we can only help you as far as you provide the input.

To add my own reply , but in line with Doktors above reply

ive asked you to do several things to help me have a clear understanding of whats going on.

im in the dark, trying to guess,

and you dismiss things i ask you to do because you think they are irrelevant and that
does not help me help you or me at all.

If you are so sure they are irrelevant, then why are you asking for help, you clearly know more about this problem than i do.

No one is going to just simply know what your problem is and give you an answer, it sounds like it could be mageia, it could be your router, it could be your network, it could even be a faulty wireless card in your PC, just cant tell unless i have your PC in my hands to play with, otherwise i have to use you as a remote control, to do this things i would try, and right now that remote is not working.

im going to install mageia 5 RC1 on my asus zenbook this weekend, as part of helping the team with feedback, ill let you know how it goes.


regards peter

Mr.doktor5000 & Mr.peter
Both of you i really appreciate your helps
But let me rest for a while and provide both of you what you are need later
Sorry to bother both of you

OK ive just installed M5RC 1 on my asus zenbook prime

connected to wifi instantly

steams video over youtube permanently, no interrupts.

works perfectly

regards peter

Does it also sport a Realtek RTL8723BE chipset? Doesn't it use an Intel chipset supported by iwlwifi?
But as a general comparison that's fine, granted I also don't have any issues with mine, which is a Broadcom ac device only supported by the wl driver.

Yes Doktor this was a general observation not an exact comparison

no it uses

http://www.intel.co.uk/content/www/uk/e ... -6235.html

so this at least narrows down the problem to a possible driver issue with that realtek, or something external to mageia.

the simplest next step of course would be disable the realtek in the bios, and try a run of the mill, mageia supported usb wifi dongle.

regards peter

Another user reported that realtek trl8723be works on mga5 beta1: viewtopic.php?p=53713#p53713