[opensuse] Connection doesn't work with some wifi networks
Hello, I'm on Tumbleweed with network manager and KDE. With some wifi networks (now 2), network manager can connect but it has no data flux and the ping doesn't work. I haven't connection issue with another wifi networks. I can use these wifi networks with an Ubuntu live USB. Thanks for your helping. Charles -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On May 28, 2018 3:40:15 PM PDT, Charles Robert <crobert@afribec.com> wrote:
Hello,
I'm on Tumbleweed with network manager and KDE.
With some wifi networks (now 2), network manager can connect but it has no data flux and the ping doesn't work. I haven't connection issue with another wifi networks. I can use these wifi networks with an Ubuntu live USB.
Thanks for your helping.
Charles
Maybe it's something to do with routes? Does ping to an IP work? -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi, Yes, ping IP adress working. So, how I can fix it ? 2018-05-28 22:59 GMT-04:00 John Andersen <jsamyth@gmail.com>:
On May 28, 2018 3:40:15 PM PDT, Charles Robert <crobert@afribec.com> wrote:
Hello,
I'm on Tumbleweed with network manager and KDE.
With some wifi networks (now 2), network manager can connect but it has no data flux and the ping doesn't work. I haven't connection issue with another wifi networks. I can use these wifi networks with an Ubuntu live USB.
Thanks for your helping.
Charles
Maybe it's something to do with routes? Does ping to an IP work?
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On May 28, 2018 8:20:30 PM PDT, Charles Robert <crobert@afribec.com> wrote:
Hi,
Yes, ping IP adress working.
So, how I can fix it ?
Sounds like you aren't getting DNA servers provided by the Wi-Fi router or perhaps when you set up this particular connection you set it not to ask for DNA servers. After connection, look at /etc/resolv.conf and see nameservers are listed.
2018-05-28 22:59 GMT-04:00 John Andersen <jsamyth@gmail.com>:
On May 28, 2018 3:40:15 PM PDT, Charles Robert <crobert@afribec.com> wrote:
Hello,
I'm on Tumbleweed with network manager and KDE.
With some wifi networks (now 2), network manager can connect but it has no data flux and the ping doesn't work. I haven't connection issue with another wifi networks. I can use these wifi networks with an Ubuntu live USB.
Thanks for your helping.
Charles
Maybe it's something to do with routes? Does ping to an IP work?
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
the list is nameserver 192.168.100.1 2018-05-28 23:28 GMT-04:00 John Andersen <jsamyth@gmail.com>:
On May 28, 2018 8:20:30 PM PDT, Charles Robert <crobert@afribec.com> wrote:
Hi,
Yes, ping IP adress working.
So, how I can fix it ?
Sounds like you aren't getting DNA servers provided by the Wi-Fi router or perhaps when you set up this particular connection you set it not to ask for DNA servers.
After connection, look at /etc/resolv.conf and see nameservers are listed.
2018-05-28 22:59 GMT-04:00 John Andersen <jsamyth@gmail.com>:
On May 28, 2018 3:40:15 PM PDT, Charles Robert <crobert@afribec.com> wrote:
Hello,
I'm on Tumbleweed with network manager and KDE.
With some wifi networks (now 2), network manager can connect but it has no data flux and the ping doesn't work. I haven't connection issue with another wifi networks. I can use these wifi networks with an Ubuntu live USB.
Thanks for your helping.
Charles
Maybe it's something to do with routes? Does ping to an IP work?
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On May 28, 2018 8:38:59 PM PDT, Charles Robert <crobert@afribec.com> wrote:
the list is nameserver 192.168.100.1
Try adding another line ahead of the exiting nameserver line with 8.8.8.8 as the number. If that works, then the problem lies with the Wi-Fi router. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I added this 1.1.1.1 and 1.0.0.1 from https://1.1.1.1/ and it's working very well. Thank you for your help ! Charles 2018-05-29 0:38 GMT-04:00 John Andersen <jsamyth@gmail.com>:
On May 28, 2018 8:38:59 PM PDT, Charles Robert <crobert@afribec.com> wrote:
the list is nameserver 192.168.100.1
Try adding another line ahead of the exiting nameserver line with 8.8.8.8 as the number.
If that works, then the problem lies with the Wi-Fi router.
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On May 28, 2018 10:46:24 PM PDT, Charles Robert <crobert@afribec.com> wrote:
I added this 1.1.1.1 and 1.0.0.1 from https://1.1.1.1/ and it's working very well.
Thank you for your help !
Charles
Almost certainly a wifi router configuration problem. If that wifi is under your control, you should probably look into it's settings. It sounds like it's internal DNS server is not operating or misconfigured. Fixing the router is preferable to tweeking each device that uses it. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Unfortunately, it's a public hotspot, and another customers haven't issue with it. 2018-05-29 2:07 GMT-04:00 John Andersen <jsamyth@gmail.com>:
On May 28, 2018 10:46:24 PM PDT, Charles Robert <crobert@afribec.com> wrote:
I added this 1.1.1.1 and 1.0.0.1 from https://1.1.1.1/ and it's working very well.
Thank you for your help !
Charles
Almost certainly a wifi router configuration problem. If that wifi is under your control, you should probably look into it's settings. It sounds like it's internal DNS server is not operating or misconfigured. Fixing the router is preferable to tweeking each device that uses it.
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On May 28, 2018 11:12:41 PM PDT, Charles Robert <crobert@afribec.com> wrote:
Unfortunately, it's a public hotspot, and another customers haven't issue with it.
That's not the first report of this exact same situation I've seen in the last week. I can't remember if the other event was here on this list or the Manjaro forum. Maybe you should ask the owner to reboot it as the FBI suggests. (I kid you not, there's one bit of malware currently affecting routers that has the FBI's attention. Google it.)
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Den 2018-05-29 kl. 08:29, skrev John Andersen:
Maybe you should ask the owner to reboot it as the FBI suggests. (I kid you not, there's one bit of malware currently affecting routers that has the FBI's attention. Google it.)
Correct. Although I would ad that reboot only solves the stage2 and stage3 of this malware. Stage1 is persistent. The malware is unfortunately very robust. FBI want everyone to reboot so that stage1 tries to download stage2 again so they can find the source. Several manufactures recommend factory reset instead. If you need to google, the name of the malware is VPNFilter. PS. Have had my eyes on this for a while due to building our own OS routers. DS. Cheers, -- /bengan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello back, Tonight, the hotpot with issue it very slow. The google.com's ping result is: --- google.com ping statistics --- 37 packets transmitted, 14 received, 62% packet loss, time 36503ms rtt min/avg/max/mdev = 11.004/18.954/33.702/6.762 ms But when I use an Ubuntu Live USB, everything working very well. So, I don't know where is an issue... Charles 2018-05-29 2:29 GMT-04:00 John Andersen <jsamyth@gmail.com>:
On May 28, 2018 11:12:41 PM PDT, Charles Robert <crobert@afribec.com> wrote:
Unfortunately, it's a public hotspot, and another customers haven't issue with it.
That's not the first report of this exact same situation I've seen in the last week. I can't remember if the other event was here on this list or the Manjaro forum.
Maybe you should ask the owner to reboot it as the FBI suggests. (I kid you not, there's one bit of malware currently affecting routers that has the FBI's attention. Google it.)
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 30.05.2018 02:59, Charles Robert wrote:
Hello back,
Tonight, the hotpot with issue it very slow. The google.com's ping result is: --- google.com ping statistics --- 37 packets transmitted, 14 received, 62% packet loss, time 36503ms rtt min/avg/max/mdev = 11.004/18.954/33.702/6.762 ms
But when I use an Ubuntu Live USB, everything working very well.
So, I don't know where is an issue...
Charles
I can't really help you, just tell you that I had the same problem on my laptop recently. Sometimes it worked, sometimes not, with some wifi's it did, with others not, sometimes it was /extremely/ slow, sometimes nothing at all... Then there was an update with the nvidia drivers that caused the creation of a new initrd and right after that wifi worked (and still works, fingers crossed) on all wifis I can reach here. It's magic. No idea if something in my initrd was wrong, if the nvidia driver has something to do with it (wouldn't know why)...? But it still works even after an update of the kernel. This is on 42.3 on an asus laptop. Maybe making a fresh initrd would help you, too? -- Daniel Bauer photographer Basel Barcelona https://www.patreon.com/danielbauer http://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/29/2018 08:59 PM, Charles Robert wrote:
Tonight, the hotpot with issue it very slow. The google.com's ping result is: --- google.com ping statistics --- 37 packets transmitted, 14 received, 62% packet loss, time 36503ms rtt min/avg/max/mdev = 11.004/18.954/33.702/6.762 ms
But when I use an Ubuntu Live USB, everything working very well.
So, I don't know where is an issue...
Dude, first thing: use traceroute to get the IP for the next hop after your wifi card, i.e., that of the access point/hotspot. This will give you more reliable test results than pinging all the way to google. If you're using the ubuntu flashdrive on the same machine (?), that's great... it eliminates hardware differences. Compare the routing tables between the two Linuxes. The problems you're having could be a lot of things, but a messed up routing table can be one of them. Don't overlook a wrong netmask. That can bounce packets all over until they time out. If you want, copy-n-paste the output of "route" on both systems into an email to us. hth -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, Here a traceroute on same computer for tumbleweed, leap and ubuntu: Tumbleweed traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 192.168.0.1 (192.168.0.1) 3.890 ms 6.022 ms 6.285 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 16.574 ms 16.888 ms 16.886 ms 5 216.113.124.54 (216.113.124.54) 40.368 ms 216.113.123.174 (216.113.123.174) 37.985 ms 216.113.124.54 (216.113.124.54) 38.872 ms 6 216.113.123.174 (216.113.123.174) 37.451 ms 34.201 ms 36.927 ms 7 209.63.99.246 (209.63.99.246) 62.816 ms 66.504 ms br01.chcgildt.integra.net (208.115.136.101) 37.747 ms 8 209.63.99.246 (209.63.99.246) 65.073 ms 70.103.180.172 (70.103.180.172) 70.718 ms 209.63.99.246 (209.63.99.246) 65.516 ms 9 70.103.180.172 (70.103.180.172) 75.548 ms 192.94.118.230 (192.94.118.230) 66.490 ms 64.149 ms 10 intra.attachmategroup.com (130.57.66.19) 83.162 ms 86.558 ms 78.261 ms Bowen:/home/charles # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Bowen:/home/charles # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 intra.attachmategroup.com (130.57.66.19) 85.850 ms 85.685 ms 85.741 ms Bowen:/home/charles # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 192.168.0.1 (192.168.0.1) 10.117 ms 10.112 ms 10.646 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 25.130 ms 24.126 ms 25.288 ms 5 216.113.123.174 (216.113.123.174) 48.312 ms 48.551 ms 49.083 ms 6 216.113.123.174 (216.113.123.174) 47.998 ms 39.507 ms br01.chcgildt.integra.net (208.115.136.101) 162.131 ms 7 209.63.99.246 (209.63.99.246) 162.061 ms 149.183 ms br01.chcgildt.integra.net (208.115.136.101) 147.072 ms 8 70.103.180.172 (70.103.180.172) 148.104 ms 125.161 ms 125.070 ms 9 192.94.118.230 (192.94.118.230) 124.697 ms 70.103.180.172 (70.103.180.172) 124.073 ms 124.018 ms 10 intra.attachmategroup.com (130.57.66.19) 143.811 ms 192.94.118.230 (192.94.118.230) 143.618 ms intra.attachmategroup.com (130.57.66.19) 145.267 ms Bowen:/home/charles # traceroute opensuse.org opensuse.org: Temporary failure in name resolution Cannot handle "host" cmdline arg `opensuse.org' on position 1 (argc 1) Leap localhost:/home/linux # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 192.168.100.1 (192.168.100.1) 10.771 ms 11.643 ms 13.197 ms 2 192.168.0.1 (192.168.0.1) 15.760 ms 15.776 ms 15.770 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 770.151 ms 770.150 ms 770.143 ms 5 216.113.123.174 (216.113.123.174) 865.626 ms 865.619 ms 865.610 ms 6 br01.chcgildt.integra.net (208.115.136.101) 865.560 ms 700.622 ms 216.113.123.174 (216.113.123.174) 2125.989 ms 7 209.63.99.246 (209.63.99.246) 2125.985 ms 2125.991 ms br01.chcgildt.integra.net (208.115.136.101) 2125.944 ms 8 209.63.99.246 (209.63.99.246) 2125.947 ms 2125.939 ms 2125.932 ms 9 70.103.180.172 (70.103.180.172) 2125.938 ms 192.94.118.230 (192.94.118.230) 2125.918 ms 2125.897 ms 10 partnerweb.attachmate.com (130.57.66.19) 2125.898 ms 2125.888 ms 192.94.118.230 (192.94.118.230) 2125.831 ms Ubuntu traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 192.168.100.1 (192.168.100.1) 4.120 ms 7.240 ms 9.994 ms 2 192.168.0.1 (192.168.0.1) 19.330 ms 21.521 ms 26.724 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 299.650 ms 299.659 ms 299.648 ms 5 216.113.123.174 (216.113.123.174) 299.647 ms 216.113.124.54 (216.113.124.54) 299.643 ms 299.639 ms 6 br01.chcgildt.integra.net (208.115.136.101) 299.635 ms 200.903 ms 216.113.123.174 (216.113.123.174) 209.061 ms 7 br01.chcgildt.integra.net (208.115.136.101) 209.008 ms 209.021 ms 209.019 ms 8 209.63.99.246 (209.63.99.246) 209.018 ms * 209.008 ms 9 * * 192.94.118.230 (192.94.118.230) 208.994 ms 10 * * 192.94.118.230 (192.94.118.230) 208.960 ms 11 reflection.com (130.57.66.19) 207.760 ms 207.761 ms 207.747 ms Charles 2018-05-30 11:39 GMT-04:00 ken <gebser@mousecar.com>:
On 05/29/2018 08:59 PM, Charles Robert wrote:
Tonight, the hotpot with issue it very slow. The google.com's ping result is: --- google.com ping statistics --- 37 packets transmitted, 14 received, 62% packet loss, time 36503ms rtt min/avg/max/mdev = 11.004/18.954/33.702/6.762 ms
But when I use an Ubuntu Live USB, everything working very well.
So, I don't know where is an issue...
Dude, first thing: use traceroute to get the IP for the next hop after your wifi card, i.e., that of the access point/hotspot. This will give you more reliable test results than pinging all the way to google.
If you're using the ubuntu flashdrive on the same machine (?), that's great... it eliminates hardware differences.
Compare the routing tables between the two Linuxes. The problems you're having could be a lot of things, but a messed up routing table can be one of them. Don't overlook a wrong netmask. That can bounce packets all over until they time out.
If you want, copy-n-paste the output of "route" on both systems into an email to us.
hth
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-30 23:08, Charles Robert wrote:
Hello,
Here a traceroute on same computer for tumbleweed, leap and ubuntu:
Tumbleweed
traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 192.168.0.1 (192.168.0.1) 3.890 ms 6.022 ms 6.285 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 16.574 ms 16.888 ms 16.886 ms 5 216.113.124.54 (216.113.124.54) 40.368 ms 216.113.123.174 (216.113.123.174) 37.985 ms 216.113.124.54 (216.113.124.54) 38.872 ms
Bowen:/home/charles # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 * * *
And this machine is...?
Bowen:/home/charles # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 * * * 3 * * *
And this machine is...?
17 intra.attachmategroup.com (130.57.66.19) 85.850 ms 85.685 ms 85.741 ms
Bowen:/home/charles # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 192.168.0.1 (192.168.0.1) 10.117 ms 10.112 ms 10.646 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 25.130 ms 24.126 ms 25.288 ms 5 216.113.123.174 (216.113.123.174) 48.312 ms 48.551 ms 49.083 ms
You have to explain how each test is different from the others. Different machine, different network, something changed, what?
Bowen:/home/charles # traceroute opensuse.org opensuse.org: Temporary failure in name resolution Cannot handle "host" cmdline arg `opensuse.org' on position 1 (argc 1)
And this one? Same machine and conditions as the previous one, but it just failed? In that case it simply means you got no DNS connection.
Leap
localhost:/home/linux # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 192.168.100.1 (192.168.100.1) 10.771 ms 11.643 ms 13.197 ms 2 192.168.0.1 (192.168.0.1) 15.760 ms 15.776 ms 15.770 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 770.151 ms 770.150 ms 770.143 ms 5 216.113.123.174 (216.113.123.174) 865.626 ms 865.619 ms 865.610 ms
Ubuntu
traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 192.168.100.1 (192.168.100.1) 4.120 ms 7.240 ms 9.994 ms 2 192.168.0.1 (192.168.0.1) 19.330 ms 21.521 ms 26.724 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 299.650 ms 299.659 ms 299.648 ms 5 216.113.123.174 (216.113.123.174) 299.647 ms 216.113.124.54 (216.113.124.54) 299.643 ms 299.639 ms
Leap and Ubuntu behave the same. But what Ken said was «use traceroute to get the IP for the next hop after your wifi card, i.e., that of the access point/hotspot. This will give you more reliable test results than pinging all the way to google.» Well, you have to ping 192.168.100.1 and 192.168.0.1, perhaps 10.170.183.61. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 05/31/2018 06:25 AM, Carlos E. R. wrote:
But what Ken said was «use traceroute to get the IP for the next hop after your wifi card, i.e., that of the access point/hotspot. This will give you more reliable test results than pinging all the way to google.»
Well, you have to ping 192.168.100.1 and 192.168.0.1, perhaps 10.170.183.61.
Yes, exactly. 192.168.100.1 is in all likelihood the home router. 10.170.183.61 is the next hop, the first one encountered on the internet, and in your current situation the one your ping tests should be done against. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
2018-05-31 6:25 GMT-04:00 Carlos E. R. <robin.listas@telefonica.net>:
On 2018-05-30 23:08, Charles Robert wrote:
Hello,
Here a traceroute on same computer for tumbleweed, leap and ubuntu:
Tumbleweed
traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 192.168.0.1 (192.168.0.1) 3.890 ms 6.022 ms 6.285 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 16.574 ms 16.888 ms 16.886 ms 5 216.113.124.54 (216.113.124.54) 40.368 ms 216.113.123.174 (216.113.123.174) 37.985 ms 216.113.124.54 (216.113.124.54) 38.872 ms
Bowen:/home/charles # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 * * *
And this machine is...?
Same machine.
Bowen:/home/charles # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 * * * 3 * * *
And this machine is...?
Same machine.
17 intra.attachmategroup.com (130.57.66.19) 85.850 ms 85.685 ms 85.741 ms
Bowen:/home/charles # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 192.168.0.1 (192.168.0.1) 10.117 ms 10.112 ms 10.646 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 25.130 ms 24.126 ms 25.288 ms 5 216.113.123.174 (216.113.123.174) 48.312 ms 48.551 ms 49.083 ms
You have to explain how each test is different from the others. Different machine, different network, something changed, what?
Same machine, same network. Did back to back with just 1-2 seconds between each.
Bowen:/home/charles # traceroute opensuse.org opensuse.org: Temporary failure in name resolution Cannot handle "host" cmdline arg `opensuse.org' on position 1 (argc 1)
And this one?
Same machine, same network...
Same machine and conditions as the previous one, but it just failed? In that case it simply means you got no DNS connection.
Did just 1-2 seconds after a previous one.
Leap
localhost:/home/linux # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 192.168.100.1 (192.168.100.1) 10.771 ms 11.643 ms 13.197 ms 2 192.168.0.1 (192.168.0.1) 15.760 ms 15.776 ms 15.770 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 770.151 ms 770.150 ms 770.143 ms 5 216.113.123.174 (216.113.123.174) 865.626 ms 865.619 ms 865.610 ms
Ubuntu
traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 192.168.100.1 (192.168.100.1) 4.120 ms 7.240 ms 9.994 ms 2 192.168.0.1 (192.168.0.1) 19.330 ms 21.521 ms 26.724 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 299.650 ms 299.659 ms 299.648 ms 5 216.113.123.174 (216.113.123.174) 299.647 ms 216.113.124.54 (216.113.124.54) 299.643 ms 299.639 ms
Leap and Ubuntu behave the same.
But what Ken said was «use traceroute to get the IP for the next hop after your wifi card, i.e., that of the access point/hotspot. This will give you more reliable test results than pinging all the way to google.»
Well, you have to ping 192.168.100.1 and 192.168.0.1, perhaps 10.170.183.61.
ping 192.168.100.1 PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data. 64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.060 ms 64 bytes from 192.168.100.1: icmp_seq=2 ttl=64 time=0.046 ms 64 bytes from 192.168.100.1: icmp_seq=3 ttl=64 time=0.047 ms 64 bytes from 192.168.100.1: icmp_seq=4 ttl=64 time=0.052 ms 64 bytes from 192.168.100.1: icmp_seq=5 ttl=64 time=0.048 ms 64 bytes from 192.168.100.1: icmp_seq=6 ttl=64 time=0.047 ms ^C --- 192.168.100.1 ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5084ms rtt min/avg/max/mdev = 0.046/0.050/0.060/0.004 ms ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. 64 bytes from 192.168.0.1: icmp_seq=1 ttl=63 time=27.3 ms ^C --- 192.168.0.1 ping statistics --- 23 packets transmitted, 1 received, 95% packet loss, time 22485ms rtt min/avg/max/mdev = 27.352/27.352/27.352/0.000 ms ping 10.170.183.61 PING 10.170.183.61 (10.170.183.61) 56(84) bytes of data. ^C --- 10.170.183.61 ping statistics --- 44 packets transmitted, 0 received, 100% packet loss, time 44024ms
-- Cheers / Saludos,
Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-31 20:51, Charles Robert wrote:
2018-05-31 6:25 GMT-04:00 Carlos E. R. <robin.listas@telefonica.net>:
On 2018-05-30 23:08, Charles Robert wrote:
Hello,
Here a traceroute on same computer for tumbleweed, leap and ubuntu:
Tumbleweed
traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 192.168.0.1 (192.168.0.1) 3.890 ms 6.022 ms 6.285 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 16.574 ms 16.888 ms 16.886 ms 5 216.113.124.54 (216.113.124.54) 40.368 ms 216.113.123.174 (216.113.123.174) 37.985 ms 216.113.124.54 (216.113.124.54) 38.872 ms
Bowen:/home/charles # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 * * *
And this machine is...?
Same machine.
Bowen:/home/charles # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 * * * 3 * * *
And this machine is...?
Same machine.
17 intra.attachmategroup.com (130.57.66.19) 85.850 ms 85.685 ms 85.741 ms
Bowen:/home/charles # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 192.168.0.1 (192.168.0.1) 10.117 ms 10.112 ms 10.646 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 25.130 ms 24.126 ms 25.288 ms 5 216.113.123.174 (216.113.123.174) 48.312 ms 48.551 ms 49.083 ms
You have to explain how each test is different from the others. Different machine, different network, something changed, what?
Same machine, same network. Did back to back with just 1-2 seconds between each.
Ok, so you were testing the same machine with no changes, yet the results are different? I don't then understand this:
1 * * * 2 192.168.0.1 (192.168.0.1) 10.117 ms 10.112 ms 10.646 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 25.130 ms 24.126 ms 25.288 ms 5 216.113.123.174 (216.113.123.174) 48.312 ms 48.551 ms 49.083 ms
1 * * * 2 * * * 3 * * *
At least, you should get a response from your own router.
But what Ken said was «use traceroute to get the IP for the next hop after your wifi card, i.e., that of the access point/hotspot. This will give you more reliable test results than pinging all the way to google.»
Well, you have to ping 192.168.100.1 and 192.168.0.1, perhaps 10.170.183.61.
ping 192.168.100.1 PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data. 64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.060 ms 64 bytes from 192.168.100.1: icmp_seq=2 ttl=64 time=0.046 ms 64 bytes from 192.168.100.1: icmp_seq=3 ttl=64 time=0.047 ms 64 bytes from 192.168.100.1: icmp_seq=4 ttl=64 time=0.052 ms 64 bytes from 192.168.100.1: icmp_seq=5 ttl=64 time=0.048 ms 64 bytes from 192.168.100.1: icmp_seq=6 ttl=64 time=0.047 ms ^C --- 192.168.100.1 ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5084ms rtt min/avg/max/mdev = 0.046/0.050/0.060/0.004 ms
ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. 64 bytes from 192.168.0.1: icmp_seq=1 ttl=63 time=27.3 ms ^C --- 192.168.0.1 ping statistics --- 23 packets transmitted, 1 received, 95% packet loss, time 22485ms rtt min/avg/max/mdev = 27.352/27.352/27.352/0.000 ms
I would ping for a long time, like 15 minutes, and collect the stats. There are other ping variants best suited for this, I would have to read the man pages to see which and what options.
ping 10.170.183.61 PING 10.170.183.61 (10.170.183.61) 56(84) bytes of data. ^C --- 10.170.183.61 ping statistics --- 44 packets transmitted, 0 received, 100% packet loss, time 44024ms
It is possible that this host does not respond to ping, you would have to try perhaps tcp on some port. Try this one: nping -c 10 --tcp -p 80 SomeMachine. you may have to install nping. -c is the number of pings, one per second roughly. nping -c 900 --tcp 192.168.0.1 10.170.183.61 -p 80,433 I try it: Telcontar:~ # nping -c 10 --tcp 192.168.0.1 10.170.183.61 -p 80,433 Starting Nping 0.6.47 ( http://nmap.org/nping ) at 2018-05-31 21:12 CEST SENT (0.0565s) TCP 192.168.1.14:5881 > 192.168.0.1:80 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 SENT (1.0566s) TCP 192.168.1.14:5881 > 10.170.183.61:80 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 SENT (2.0578s) TCP 192.168.1.14:5881 > 192.168.0.1:433 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 SENT (3.0589s) TCP 192.168.1.14:5881 > 10.170.183.61:433 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 SENT (4.0591s) TCP 192.168.1.14:5881 > 192.168.0.1:80 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 RCVD (4.2351s) ICMP [10.195.97.231 > 192.168.1.14 Host 10.170.183.61 unreachable (type=3/code=1) ] IP [ttl=64 id=61496 iplen=72 ] RCVD (4.2351s) ICMP [10.195.97.231 > 192.168.1.14 Host 10.170.183.61 unreachable (type=3/code=1) ] IP [ttl=64 id=61497 iplen=72 ] SENT (5.0593s) TCP 192.168.1.14:5881 > 10.170.183.61:80 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 SENT (6.0604s) TCP 192.168.1.14:5881 > 192.168.0.1:433 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 ... Statistics for host 192.168.0.1: | Probes Sent: 20 | Rcvd: 0 | Lost: 20 (100.00%) |_ Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A Statistics for host 10.170.183.61: | Probes Sent: 20 | Rcvd: 18 | Lost: 2 (10.00%) |_ Max rtt: 1176.185ms | Min rtt: 1149.732ms | Avg rtt: 1162.072ms Raw packets sent: 40 (1.600KB) | Rcvd: 18 (1.296KB) | Lost: 22 (55.00%) Nping done: 2 IP addresses pinged in 40.12 seconds Telcontar:~ # Funny. I do have some 10.*** network nearby. The standard ping fails completely on that host (which is not the same 10.170.183.61 as you see). -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
2018-05-31 15:17 GMT-04:00 Carlos E. R. <robin.listas@telefonica.net>:
On 2018-05-31 20:51, Charles Robert wrote:
2018-05-31 6:25 GMT-04:00 Carlos E. R. <robin.listas@telefonica.net>:
On 2018-05-30 23:08, Charles Robert wrote:
Hello,
Here a traceroute on same computer for tumbleweed, leap and ubuntu:
Tumbleweed
traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 192.168.0.1 (192.168.0.1) 3.890 ms 6.022 ms 6.285 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 16.574 ms 16.888 ms 16.886 ms 5 216.113.124.54 (216.113.124.54) 40.368 ms 216.113.123.174 (216.113.123.174) 37.985 ms 216.113.124.54 (216.113.124.54) 38.872 ms
Bowen:/home/charles # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 * * *
And this machine is...?
Same machine.
Bowen:/home/charles # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 * * * 3 * * *
And this machine is...?
Same machine.
17 intra.attachmategroup.com (130.57.66.19) 85.850 ms 85.685 ms 85.741 ms
Bowen:/home/charles # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 192.168.0.1 (192.168.0.1) 10.117 ms 10.112 ms 10.646 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 25.130 ms 24.126 ms 25.288 ms 5 216.113.123.174 (216.113.123.174) 48.312 ms 48.551 ms 49.083 ms
You have to explain how each test is different from the others. Different machine, different network, something changed, what?
Same machine, same network. Did back to back with just 1-2 seconds between each.
Ok, so you were testing the same machine with no changes, yet the results are different?
I don't then understand this:
1 * * * 2 192.168.0.1 (192.168.0.1) 10.117 ms 10.112 ms 10.646 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 25.130 ms 24.126 ms 25.288 ms 5 216.113.123.174 (216.113.123.174) 48.312 ms 48.551 ms 49.083 ms
1 * * * 2 * * * 3 * * *
At least, you should get a response from your own router.
But what Ken said was «use traceroute to get the IP for the next hop after your wifi card, i.e., that of the access point/hotspot. This will give you more reliable test results than pinging all the way to google.»
Well, you have to ping 192.168.100.1 and 192.168.0.1, perhaps 10.170.183.61.
ping 192.168.100.1 PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data. 64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.060 ms 64 bytes from 192.168.100.1: icmp_seq=2 ttl=64 time=0.046 ms 64 bytes from 192.168.100.1: icmp_seq=3 ttl=64 time=0.047 ms 64 bytes from 192.168.100.1: icmp_seq=4 ttl=64 time=0.052 ms 64 bytes from 192.168.100.1: icmp_seq=5 ttl=64 time=0.048 ms 64 bytes from 192.168.100.1: icmp_seq=6 ttl=64 time=0.047 ms ^C --- 192.168.100.1 ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5084ms rtt min/avg/max/mdev = 0.046/0.050/0.060/0.004 ms
ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. 64 bytes from 192.168.0.1: icmp_seq=1 ttl=63 time=27.3 ms ^C --- 192.168.0.1 ping statistics --- 23 packets transmitted, 1 received, 95% packet loss, time 22485ms rtt min/avg/max/mdev = 27.352/27.352/27.352/0.000 ms
I would ping for a long time, like 15 minutes, and collect the stats. There are other ping variants best suited for this, I would have to read the man pages to see which and what options.
ping 10.170.183.61 PING 10.170.183.61 (10.170.183.61) 56(84) bytes of data. ^C --- 10.170.183.61 ping statistics --- 44 packets transmitted, 0 received, 100% packet loss, time 44024ms
It is possible that this host does not respond to ping, you would have to try perhaps tcp on some port. Try this one:
nping -c 10 --tcp -p 80 SomeMachine.
you may have to install nping.
-c is the number of pings, one per second roughly.
nping -c 900 --tcp 192.168.0.1 10.170.183.61 -p 80,433
I try it:
Telcontar:~ # nping -c 10 --tcp 192.168.0.1 10.170.183.61 -p 80,433
Starting Nping 0.6.47 ( http://nmap.org/nping ) at 2018-05-31 21:12 CEST SENT (0.0565s) TCP 192.168.1.14:5881 > 192.168.0.1:80 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 SENT (1.0566s) TCP 192.168.1.14:5881 > 10.170.183.61:80 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 SENT (2.0578s) TCP 192.168.1.14:5881 > 192.168.0.1:433 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 SENT (3.0589s) TCP 192.168.1.14:5881 > 10.170.183.61:433 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 SENT (4.0591s) TCP 192.168.1.14:5881 > 192.168.0.1:80 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 RCVD (4.2351s) ICMP [10.195.97.231 > 192.168.1.14 Host 10.170.183.61 unreachable (type=3/code=1) ] IP [ttl=64 id=61496 iplen=72 ] RCVD (4.2351s) ICMP [10.195.97.231 > 192.168.1.14 Host 10.170.183.61 unreachable (type=3/code=1) ] IP [ttl=64 id=61497 iplen=72 ] SENT (5.0593s) TCP 192.168.1.14:5881 > 10.170.183.61:80 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 SENT (6.0604s) TCP 192.168.1.14:5881 > 192.168.0.1:433 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480
...
Statistics for host 192.168.0.1: | Probes Sent: 20 | Rcvd: 0 | Lost: 20 (100.00%) |_ Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A Statistics for host 10.170.183.61: | Probes Sent: 20 | Rcvd: 18 | Lost: 2 (10.00%) |_ Max rtt: 1176.185ms | Min rtt: 1149.732ms | Avg rtt: 1162.072ms Raw packets sent: 40 (1.600KB) | Rcvd: 18 (1.296KB) | Lost: 22 (55.00%) Nping done: 2 IP addresses pinged in 40.12 seconds Telcontar:~ #
Funny. I do have some 10.*** network nearby. The standard ping fails completely on that host (which is not the same 10.170.183.61 as you see).
Statistics for host 192.168.0.1: | Probes Sent: 1800 | Rcvd: 309 | Lost: 1491 (82.83%) |_ Max rtt: 3739.069ms | Min rtt: 2.792ms | Avg rtt: 591.496ms Statistics for host 10.170.183.61: | Probes Sent: 1800 | Rcvd: 0 | Lost: 1800 (100.00%) |_ Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A Raw packets sent: 3600 (144.000KB) | Rcvd: 309 (13.016KB) | Lost: 3291 (91.42%) Nping done: 2 IP addresses pinged in 3604.45 seconds
-- Cheers / Saludos,
Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-31 22:46, Charles Robert wrote:
2018-05-31 15:17 GMT-04:00 Carlos E. R. <>:
...
It is possible that this host does not respond to ping, you would have to try perhaps tcp on some port. Try this one:
nping -c 10 --tcp -p 80 SomeMachine.
you may have to install nping.
-c is the number of pings, one per second roughly.
nping -c 900 --tcp 192.168.0.1 10.170.183.61 -p 80,433
I try it:
Telcontar:~ # nping -c 10 --tcp 192.168.0.1 10.170.183.61 -p 80,433
Statistics for host 192.168.0.1: | Probes Sent: 1800 | Rcvd: 309 | Lost: 1491 (82.83%) |_ Max rtt: 3739.069ms | Min rtt: 2.792ms | Avg rtt: 591.496ms Statistics for host 10.170.183.61: | Probes Sent: 1800 | Rcvd: 0 | Lost: 1800 (100.00%) |_ Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A Raw packets sent: 3600 (144.000KB) | Rcvd: 309 (13.016KB) | Lost: 3291 (91.42%) Nping done: 2 IP addresses pinged in 3604.45 seconds
I forgot to mention that you can try probing with different ports till one responds. It is possible that the 10.170.183.61 machine (if it is still that address, I told you to verify this before pinging it) doesn't respond on the ports I wrote. Anyway, even your own gateway has problems, 80% failure. That's pretty bad. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
2018-05-31 17:47 GMT-04:00 Carlos E. R. <robin.listas@telefonica.net>:
On 2018-05-31 22:46, Charles Robert wrote:
2018-05-31 15:17 GMT-04:00 Carlos E. R. <>:
...
It is possible that this host does not respond to ping, you would have to try perhaps tcp on some port. Try this one:
nping -c 10 --tcp -p 80 SomeMachine.
you may have to install nping.
-c is the number of pings, one per second roughly.
nping -c 900 --tcp 192.168.0.1 10.170.183.61 -p 80,433
I try it:
Telcontar:~ # nping -c 10 --tcp 192.168.0.1 10.170.183.61 -p 80,433
Statistics for host 192.168.0.1: | Probes Sent: 1800 | Rcvd: 309 | Lost: 1491 (82.83%) |_ Max rtt: 3739.069ms | Min rtt: 2.792ms | Avg rtt: 591.496ms Statistics for host 10.170.183.61: | Probes Sent: 1800 | Rcvd: 0 | Lost: 1800 (100.00%) |_ Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A Raw packets sent: 3600 (144.000KB) | Rcvd: 309 (13.016KB) | Lost: 3291 (91.42%) Nping done: 2 IP addresses pinged in 3604.45 seconds
I forgot to mention that you can try probing with different ports till one responds. It is possible that the 10.170.183.61 machine (if it is still that address, I told you to verify this before pinging it) doesn't respond on the ports I wrote.
Anyway, even your own gateway has problems, 80% failure. That's pretty bad.
I don't know why with a computer with Tumbleweed on this network, I have an issue, and with a same computer, with Leap 15 or Ubuntu 16.04 on Live USB, I haven't an issue on the same network, and with a same computer with tumbleweed on another network, I haven't an issue.
-- Cheers / Saludos,
Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Charles Robert <crobert@afribec.com> [05-31-18 23:17]: [...]
I don't know why with a computer with Tumbleweed on this network, I have an issue, and with a same computer, with Leap 15 or Ubuntu 16.04 on Live USB, I haven't an issue on the same network, and with a same computer with tumbleweed on another network, I haven't an issue.
you undoubtedly have different setting for each distro. compare the /etc/resolv.conf on each. or show them to us. the statement above gives no one any hint as to your problem, only guesses. and please, trim your quotes. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-01 05:47, Patrick Shanahan wrote:
* Charles Robert <crobert@afribec.com> [05-31-18 23:17]:
[...]
I don't know why with a computer with Tumbleweed on this network, I have an issue, and with a same computer, with Leap 15 or Ubuntu 16.04 on Live USB, I haven't an issue on the same network, and with a same computer with tumbleweed on another network, I haven't an issue.
you undoubtedly have different setting for each distro. compare the /etc/resolv.conf on each. or show them to us. the statement above gives no one any hint as to your problem, only guesses.
Well, tell him what commands to issue to get precise information. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
you undoubtedly have different setting for each distro. compare the /etc/resolv.conf on each. or show them to us. the statement above gives no one any hint as to your problem, only guesses.
Here resolv.conf content for Ubuntu, Leap and Tumbleweed. It's working in Leap and Ubuntu, didn't in Tumbleweed. Also, I renamed resolv.conf and restarted Network Manager and no change with new resolv.conf file. Ubuntu nameserver 127.0.1.1 Leap nameserver 192.168.100.1 Tumbleweed nameserver 192.168.100.1 Charles -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-02 06:07, Charles Robert wrote:
you undoubtedly have different setting for each distro. compare the /etc/resolv.conf on each. or show them to us. the statement above gives no one any hint as to your problem, only guesses.
Here resolv.conf content for Ubuntu, Leap and Tumbleweed. It's working in Leap and Ubuntu, didn't in Tumbleweed. Also, I renamed resolv.conf and restarted Network Manager and no change with new resolv.conf file.
Ubuntu nameserver 127.0.1.1 Leap nameserver 192.168.100.1 Tumbleweed nameserver 192.168.100.1
Charles
Wait. This: nameserver 127.0.1.1 only works *IF* you are running a domain server in your own machine; typically it would be dnsmasq, and the real outside DNS would be configured in /etc/dnsmasq.conf. The other configuration: nameserver 192.168.100.1 is strange and may not work, because you said your Gateway is 192.168.0.1, as shown in the traceroutes. Otherwise, show ping to 192.168.100.1, then find out what this machine is. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 2018-06-01 05:15, Charles Robert wrote:
2018-05-31 17:47 GMT-04:00 Carlos E. R. <>:
Anyway, even your own gateway has problems, 80% failure. That's pretty bad.
I don't know why with a computer with Tumbleweed on this network, I have an issue, and with a same computer, with Leap 15 or Ubuntu 16.04 on Live USB, I haven't an issue on the same network, and with a same computer with tumbleweed on another network, I haven't an issue.
I don't know. It is something related to this particular network. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Guys, trim your posts please. If the same machine running a different distro works, then we can dispense with diagnosing the network. The hardware clearly works, other than the possibility of Wi-Fi chipset firmware. So that leaves drivers and configuration. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/28/2018 10:59 PM, John Andersen wrote:
On May 28, 2018 3:40:15 PM PDT, Charles Robert <crobert@afribec.com> wrote:
Hello,
I'm on Tumbleweed with network manager and KDE.
With some wifi networks (now 2), network manager can connect but it has no data flux and the ping doesn't work. I haven't connection issue with another wifi networks. I can use these wifi networks with an Ubuntu live USB.
Thanks for your helping.
Charles
Maybe it's something to do with routes? Does ping to an IP work?
Specifically, to the router or something else on the local LAN. Start with the device and work out from there. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/29/2018 12:40 AM, Charles Robert wrote:
Hello,
I'm on Tumbleweed with network manager and KDE.
With some wifi networks (now 2), network manager can connect but it has no data flux and the ping doesn't work. I haven't connection issue with another wifi networks. I can use these wifi networks with an Ubuntu live USB.
Thanks for your helping.
Charles
It looks similar to the issue that I had after upgrade. I solved mine by deleting (renaming) /etc/resolv.conf and restarting NetworkManager.service. HTH, R. Soskic
Am 01.06.2018 um 11:48 schrieb Radule Šoškić:
It looks similar to the issue that I had after upgrade. I solved mine by deleting (renaming) /etc/resolv.conf and restarting NetworkManager.service.
I had the same issue and the same solution. -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (10)
-
Bengt Gördén -
Carlos E. R. -
Charles Robert -
Daniel Bauer -
James Knott -
Johannes Weberhofer -
John Andersen -
ken -
Patrick Shanahan -
Radule Šoškić