network fail after kde 3.4 upgrade

baronlynx · 06-11-2005, 03:16 PM

hi all,

i need some help because i have found myself in a situation that is kinda weired...
i'm quite new to linux (2yrs of exp. with different distros),

in short: network is not working in the newly upgraded kde,

i am running SuSE 9.2 and i have just upgraded kde to 3.4 and i have found out that after the reboot that the network was completly down.
I use ADSL router on the address 192.168.1.1 and i wasn't unable to ping even the router ...
So what i do ?
reboot
log in to the FVWM and i see the network in perfect shape ... so i wonder ... maybe kde changed some network config ... so i compare the output of ifconfig, netstat -rn and cat resolv.conf ... the output is exactly the same ...
i try to change the fixed ip into DHCP ... no change ...

the situation is more than weired ...
what i have foud out:
when i reboot directly to fvwm i have the network working ...
when i log into fvwm after login in to kde the network is down ...

what i think is that kde launches something that affects the network link or routing or i dont really know what ...

i did not find any relevant info searching google and LQ

please help since i have reached the limits of my poor linux knowledge

thanks in advance.

baronlynx

some outputs:
marc@linux:~> su -c 'ifconfig'
Password:
eth0 Lien encap:Ethernet HWaddr 08:00:46:AA:75:8E
inet adr:192.168.1.10 Bcast:192.168.1.255 Masque:255.255.255.0
adr inet6: fe80::a00:46ff:feaa:758e/64 Scope:Lien
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2499 errors:0 dropped:0 overruns:0 frame:0
TX packets:2806 errors:0 dropped:1 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:1768246 (1.6 Mb) TX bytes:448864 (438.3 Kb)
Interruption:11 Adresse de base:0x2000

lo Lien encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:92 errors:0 dropped:0 overruns:0 frame:0
TX packets:92 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:5971 (5.8 Kb) TX bytes:5971 (5.8 Kb)

marc@linux:~> su -c 'cat /etc/resolv.conf'
Password:
nameserver 192.168.1.1
search site

marc@linux:~> netstat -rn
Table de routage IP du noyau
Destination Passerelle Genmask Indic MSS Fenêtre irtt Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

baronlynx · 06-12-2005, 04:02 AM

as i am digging in deeper and deeper the answer to this question is becoming more ambitious then before ...

i took a look at the kernel messages (/var/log/messages) when starting up the kde and fvwm and i have foud out some differences:

what worries me most is the first line:

the code below are the messages that show up when starting kde that don't show up starting fvwm
i think what i see is the confirmation that whehter
a) something is being broken in the moment od startup that concerns ipv6 or
b) kde and fvwm don't have the same ip management

my questions are:
1. if my thesis b) is correct then it would be something like fvwm don't use ipv6 and that is why despite the fact that i don't have the ipv6 router present network under fvwm works ... so either i can turn of the ipv6 off (i don't know if i may and surely don't know how) or get the ipv6 router running (what i have found by google search was too confusing and scarry to try procedure...)
2. if my thesis a) is correct then what in the heck could be broken then ...

Code:

eth0: no IPv6 routers present
Jun 12 01:30:39 linux SuSEfirewall2: Firewall rules successfully set from /etc/sysconfig/SuSEfirewall2
Jun 12 01:30:45 linux kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=08:00:46:aa:75:8e:00:60:4c:05:b7:0b:08:00 SRC=82.120.248.195 DST=192.168.1.11 LEN=48 TOS=0x00 PREC=0x00 TTL=116 ID=30149 DF PROTO=TCP SPT=3020 DPT=4662 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (0204058C01010402)
Jun 12 01:30:46 linux kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=08:00:46:aa:75:8e:00:60:4c:05:b7:0b:08:00 SRC=216.27.161.5 DST=192.168.1.11 LEN=48 TOS=0x00 PREC=0x20 TTL=115 ID=2627 DF PROTO=TCP SPT=4425 DPT=4662 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (0204058C01010402)
Jun 12 01:30:47 linux kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=08:00:46:aa:75:8e:00:60:4c:05:b7:0b:08:00 SRC=216.27.161.5 DST=192.168.1.11 LEN=48 TOS=0x00 PREC=0x20 TTL=115 ID=2649 DF PROTO=TCP SPT=4425 DPT=4662 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (0204058C01010402)
Jun 12 01:30:48 linux kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=08:00:46:aa:75:8e:00:60:4c:05:b7:0b:08:00 SRC=216.27.161.5 DST=192.168.1.11 LEN=48 TOS=0x00 PREC=0x20 TTL=115 ID=2668 DF PROTO=TCP SPT=4425 DPT=4662 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (0204058C01010402)
Jun 12 01:30:48 linux kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=08:00:46:aa:75:8e:00:60:4c:05:b7:0b:08:00 SRC=67.70.78.154 DST=192.168.1.11 LEN=48 TOS=0x00 PREC=0x00 TTL=111 ID=41648 DF PROTO=TCP SPT=60334 DPT=4662 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (0204058C01010402)
...
Jun 12 01:33:51 linux kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jun 12 01:33:51 linux kernel: eth0: Transmit timeout, status 00000004 00000249
Jun 12 01:33:59 linux kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jun 12 01:33:59 linux kernel: eth0: Transmit timeout, status 00000004 00000249
Jun 12 01:34:07 linux kernel: NETDEV WATCHDOG: eth0: transmit timed out
...
Jun 12 01:34:31 linux kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jun 12 01:34:31 linux kernel: eth0: Transmit timeout, status 00000000 00000259
Jun 12 01:34:39 linux kernel: NETDEV WATCHDOG: eth0: transmit timed out