Strange Internet Connection - Konsole ok, KDE not ok

schimpfj · 2007-10-29 08:56:59

Hello All,

Please apologize my cross posting but since I did not get any reply on my issue yet I want to try it here:

I face the following issue (using kdemod):
In KDE using Konsole I open an Internet connection as a user and can ping addresses in this console - see below. Opening another Konsole instance the ping does no longer work. More important, KDE browser does not work either ("Unknown host www.google.de").

[guest@archlinux ~]$ sudo pon
Passwort:
Plugin rp-pppoe.so loaded.
RP-PPPoE plugin version 3.3 compiled against pppd 2.4.4
[guest@archlinux ~]$ ping www.google.de
PING www.l.google.com (209.85.135.147) 56(84) bytes of data.
64 bytes from mu-in-f147.google.com (209.85.135.147): icmp_seq=1 ttl=248 time=23.6 ms
64 bytes from mu-in-f147.google.com (209.85.135.147): icmp_seq=2 ttl=248 time=22.5 ms

Anyone an idea what config I missed?

Thanks in advance for any response!
Jochen

(Original post: http://bbs.archlinux.org/viewtopic.php?id=38911)

schimpfj · 2007-12-03 19:19:57

Hello,

I am (still) having trouble accessing the Internet via KDE. I have installed latest Arch packages and KDE (full). I am connecting to the internet via DSL. It works fine on the console, i.e. lynx and pacman. Also ping.

In KDE I am starting the DSL interface via Konsole as a user. The first connection to an URL works fine, whether I do a ping or use Konquerer. However, any subsequent URL, whether link or another ping, fail. Strange enough, traceroute still works. What also confuses me, is that /etc/ppp/resolv.conf get a new timestamp after the ping. I believe no one/nothing should touch the file, shouldn't it? resolv.conf content is unchanged, however. I use the same resolv.conf with my (soon to be) old Suse installation without issues.

Example
[guest@archlinux ~]$ sudo pon
Plugin rp-pppoe.so loaded.
RP-PPPoE plugin version 3.3 compiled against pppd 2.4.4

[guest@archlinux ~]$ ls -l /etc/ppp/resolv.conf
-rw-r--r-- 1 root root 51 3. Dez 19:40 /etc/ppp/resolv.conf

[guest@archlinux ~]$ ping www.archlinux.org
PING archlinux.org (66.211.213.17) 56(84) bytes of data.
64 bytes from 66-211-213-17.velocity.net (66.211.213.17): icmp_seq=1 ttl=46 time=265 ms
64 bytes from 66-211-213-17.velocity.net (66.211.213.17): icmp_seq=2 ttl=46 time=259 ms
64 bytes from 66-211-213-17.velocity.net (66.211.213.17): icmp_seq=3 ttl=46 time=261 ms
64 bytes from 66-211-213-17.velocity.net (66.211.213.17): icmp_seq=4 ttl=46 time=255 ms
64 bytes from 66-211-213-17.velocity.net (66.211.213.17): icmp_seq=5 ttl=46 time=244 ms

--- archlinux.org ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 244.935/257.126/265.395/6.963 ms

[guest@archlinux ~]$ ping www.archlinux.org
ping: unknown host www.archlinux.org

[guest@archlinux ~]$ traceroute www.archlinux.org
traceroute to archlinux.org (66.211.213.17), 30 hops max, 40 byte packets
1 * * *
2 * * ge-3-0-0-101.pr01.fra.de.hansenet.net (62.109.109.176) 16.173 ms
3 decix-hansenet-3-de.fra.seabone.net (89.221.34.25) 99.501 ms 37.734 ms 15.825 ms
4 decix.mpd01.fra03.atlas.cogentco.com (80.81.192.63) 17.623 ms 17.890 ms 15.948 ms
5 gi9-0-0.core01.fra03.atlas.cogentco.com (130.117.0.1) 15.975 ms 17.884 ms 15.947 ms
6 po15-0.core01.par02.atlas.cogentco.com (130.117.0.18) 162.052 ms 174.003 ms 165.945 ms
7 po13-0.core01.par01.atlas.cogentco.com (130.117.1.137) 163.929 ms 163.985 ms 165.967 ms
8 te2-3.mpd02.par01.atlas.cogentco.com (130.117.2.50) 163.957 ms 183.999 ms 169.945 ms
9 te3-4.mpd01.dca01.atlas.cogentco.com (130.117.2.102) 177.935 ms 168.011 ms 161.956 ms
10 te8-1.ccr02.dca01.atlas.cogentco.com (154.54.2.194) 177.948 ms 168.021 ms 169.951 ms
11 gi1-0-0.core01.dca01.atlas.cogentco.com (154.54.3.157) 161.946 ms 169.996 ms 165.918 ms
12 po15-0.core02.dca01.atlas.cogentco.com (66.28.4.22) 167.878 ms 163.880 ms 163.954 ms
13 te3-1.mpd01.dca01.atlas.cogentco.com (154.54.5.50) 167.945 ms 167.919 ms 169.954 ms
14 te8-1.mpd01.dca02.atlas.cogentco.com (154.54.1.70) 125.953 ms 123.932 ms 135.948 ms
15 vl3495.mpd01.iad01.atlas.cogentco.com (154.54.5.62) 121.947 ms 127.862 ms 233.939 ms
16 gi9-0-0.core01.iad01.atlas.cogentco.com (154.54.3.221) 123.953 ms 139.903 ms 125.953 ms
17 po6-0.core01.pit02.atlas.cogentco.com (154.54.3.26) 171.953 ms 167.902 ms 163.940 ms
18 vl105.na01.b016102-1.pit02.atlas.cogentco.com (38.112.37.162) 163.958 ms 165.892 ms 167.955 ms
19 Velocity_dot_net.demarc.cogentco.com (38.112.28.14) 127.950 ms 127.908 ms 125.973 ms
20 core01-ge-0-1.eri.velocity.net (66.211.254.1) 137.948 ms 151.900 ms 137.964 ms
21 cust02-ge-0-0.eri.velocity.net (66.211.250.2) 183.931 ms 183.888 ms 183.950 ms
22 66-211-213-17.velocity.net (66.211.213.17) 141.956 ms 143.927 ms 137.951 ms

[guest@archlinux ~]$ ping www.archlinux.org
ping: unknown host www.archlinux.org

[guest@archlinux ~]$ ls -l /etc/ppp/resolv.conf
-rw-r--r-- 1 root root 51 3. Dez 19:49 /etc/ppp/resolv.conf
[guest@archlinux ~]$ cat /etc/ppp/resolv.conf
nameserver 62.109.123.197
nameserver 213.191.74.19

[guest@archlinux ~]$ sudo poff

I am not having such trouble as root. Does someone understand what's going on here?

Jochen

XGremlinX · 2007-12-03 19:50:05

hi! Dunno if it is anywhere related, but in some distros at least, if I setup my connection through the console/scripts, to some apps like Konqueror, all that matters is KNetworkManager.

Since you set it up through console, KNetworkManager doesn't detects this, and if it is open it will report has not being connected, so Konqueror doesn't even try to connect to anything. Shutting down KNetworkManager does the trick and Konqueror can access the web in that case.

lilsirecho · 2007-12-03 19:56:55

This probably coms from requiring a selection of wired ethernet due to the inclusion of wireless options. Thus with each instance of Kde, the selection is probably needed.

schimpfj · 2007-12-03 20:02:12

Thank you for your suggestions, but why would it work on the first attempt. Shouldn't it fail on any attempt by what you are saying?

lilsirecho · 2007-12-03 21:51:36

Strange things are happening.......probably the first was already enabled and the second trial required a re-established wired ethernet.

I am in FaunOS based on archlinux and must restart ethernet each time I reboot. I may use /etc/rc.local to change that ...perhaps that will also work for you.

Arch Linux

#1 2007-10-29 08:56:59

Strange Internet Connection - Konsole ok, KDE not ok

#2 2007-12-03 19:19:57

Re: Strange Internet Connection - Konsole ok, KDE not ok

#3 2007-12-03 19:50:05

Re: Strange Internet Connection - Konsole ok, KDE not ok

#4 2007-12-03 19:56:55

Re: Strange Internet Connection - Konsole ok, KDE not ok

#5 2007-12-03 20:02:12

Re: Strange Internet Connection - Konsole ok, KDE not ok

#6 2007-12-03 21:51:36

Re: Strange Internet Connection - Konsole ok, KDE not ok

Board footer