-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I’m going to join in here as a person needing help; perhaps my issue is
the same but if not I’ll start a new thread.
First, this is a new laptop with the following as seen from /sbin/lspci:
Code:
04:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE
802.11b/g/n WiFi Adapter (rev 01)
The following is my wireless setup at home:
Code:
ab@ablaptop0:~/Desktop> ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
state DOWN qlen 1000
link/ether 00:90:f5:d3:b1:43 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
qlen 1000
link/ether 94:db:c9:50:6b:fb brd ff:ff:ff:ff:ff:ff
inet 192.168.1.2/24 brd 192.168.1.255 scope global wlan0
16: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN
link/ether 52:54:00:5f:b8:0d brd ff:ff:ff:ff:ff:ff
inet 192.168.200.1/24 brd 192.168.200.255 scope global virbr0
17: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc noop master virbr0
state DOWN qlen 500
link/ether 52:54:00:5f:b8:0d brd ff:ff:ff:ff:ff:ff
Code:
ab@ablaptop0:~/Desktop> ip route
default via 192.168.1.1 dev wlan0 proto static
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.2
192.168.200.0/24 dev virbr0 proto kernel scope link src 192.168.200.1
My /etc/resolv.conf has one uncommented line:
nameserver 192.168.1.1
This, as you can see, is also my gateway, and it’s a little NetGear
router/switch/WAP that I’ve had forever. In my home I also have two
other laptops, both on OpenSUSE 12.1 with various types of NICs, the
same routes and resolv.conf files, but (of course) different IPs. Both
have been running for the better part of this calendar year without
related issues.
After installing 12.2 RC2 on my new box last week, and then using the
update channels early last week to get to whatever was current in them,
I started to notice odd things at home. I have only been able to narrow
down this ‘flakiness’ to my home connection when I am upstairs doing a
lot of something over wireless. My favorite way to cause myself
problems is to fire up Pidgin and login to a network. If I do so from
the downstairs next to the access point, no problems. If I used wired,
no problems. If I use my older laptop anywhere at all, no problems. If
I use the other laptop in the house from anywhere, no problems. It is
only this laptop (which happens to be the only one on 12.2 right now)
when doing things that seem to cause a load from a decent distance that
otherwise works for every other box. When the problem manifests itself
I lose the ability to get responses (per a LAN trace) from the
router/WAP box; ICMP echo requests show up in my laptops LAN trace, but
they never get any responses. ARP requests (which eventually get sent
out) go unanswered. ‘ping’ shows a lot of ‘destination host
unreachable’; of course pings to the outside world also fail when done
by IP address.
This box has all current patches and as such is on the
3.4.6-2.10-desktop kernel.
This really seems like an inability of the new system to handle some
dropped packets or something; I haven’t been able to get a LAN trace
from the router (no idea if it can even do that) and haven’t tried from
another system (not sure if they can be that promiscuous) but I am
assuming my packets are making it out of my box to the router. I have a
wired server I’ll see if I can use for verification of that assumption
the next time I cause the problem. Unfortunately for testing I am not
willing to revert installations to 12.1 on this box, I do not have time
to push the 12.1 box up to 12.2 (going away tomorrow), and the other
12.1 box probably won’t be upgraded for a bit, but who knows if it will
even duplicate due to different NICs and drivers. I would also really
prefer to try a custom compiled kernel since this box is used almost
every single day for work and if I somehow lost access to it it would be
very painful to recover (full disk encryption makes me a little more
careful than I would be otherwise because recovering takes a little more
work).
So there you go; any ideas for troubleshooting?
Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQIcBAEBAgAGBQJQSBMMAAoJEF+XTK08PnB5nlsP/jXz3+toc4iAGmhTgb88/pcg
uSgbG355YSOjipn0vY9jYBdGgBzWvLQtxaVjYetER0Yz8Mq6TuBQp29dQ9l2loOt
iXAZ3tnqtAkB/LBQgjTnCuWk6A85tvghtRAbpwApr9ItAncTLNZkwpfUJPo63wQY
5wLYR2lLpOXRD14ZtKQRjZ4vvRJL4uaA2fDcbZD85a1Y6dUhM/RTug6hfuLMF5Kr
2sSsxA6e61V9qcoXrjr2Cfs5jmgz0v2r/0Sw39pm5MF9IXO59NpoXzNjJWnOubI0
XqSxZGeXj36IZB+YaPc1GWpsqYs+drHuj9TguggTO9ybqHgSWO4pJuP2N5Mj6edm
6rS1El+BPln14cAjJO52zXWpv1QydOefegBiNHWjK9QILbDfkZPhrMyZNC52NS+f
4b1MnrXkArzyofvgzS1w0mY7yjU1whuALTLQqniu4BqIGd2nCjVfFtX3UiSJy2Cq
IT72wJ/tRnAHtjIAUhzR4GlRcMnmXwVrsBU5WiCUoM3iB1nh1WVj+ruVZZaPf5Jt
nji4yCR4itwaSOyurTWWGHUCNYt3B/SuCkDmS1Du5mORNHHho7pAMnLIl90ZT2gU
ajV/1tk88y3zZ4p831IJXgE5rN5sqy5dKkcN0G9n3tg7c3qTc8smDWm5Tunt6DZK
XcyFXSt54DmnsZbCVUYk
=rTjj
-----END PGP SIGNATURE-----