Bug 716637 - F15 network manager segfaults with signal 11 after obtaining wlan ip then KDE becomes erratic (downgrade requiered)
Summary: F15 network manager segfaults with signal 11 after obtaining wlan ip then KDE...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 15
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-25 21:13 UTC by Reartes Guillermo
Modified: 2011-10-21 11:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-21 11:57:46 UTC
Type: ---

Attachments (Terms of Use)
messages [msi wind u100] (2.02 MB, application/octet-stream)
2011-06-25 21:13 UTC, Reartes Guillermo 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Reartes Guillermo 2011-06-25 21:13:16 UTC 
Created attachment 509927 [details]
messages [msi wind u100]

Description of problem: 
When i try to connect to wireless, it connects but then plasma starts to crash, programs cannot be opened or crashes. 
Firefox does resolve dns.
command line: yum update works, dns works, ping works. (but sometimes the conection gets dropped). It happened with my sisters laptop, a MSI u100. Recently i tried with my dell e4300 and found that i do experience similar issues, will update later.
KDE becomes erratic after the problem manifests, random plasma crashes or applications crashing uppon launching or randomly.

I started to use openwag for my wag200g, but still the software should not crash.

Version-Release number of selected component (if applicable):

NetworkManager.i686  1:0.8.9997-4.git20110620.fc15 @updates                    
NetworkManager-glib.i686 1:0.8.9997-4.git20110620.fc15 @updates                    
NetworkManager-openvpn.i686  1:0.8.999-1.fc15 @koji-override-0/$releasever
NetworkManager-pptp.i686     1:0.8.999-1.fc15 @koji-override-0/$releasever
NetworkManager-vpnc.i686     1:0.8.999-2.fc15 @koji-override-0/$releasever

kernel 2.6.38.8-32.fc15.i686

kdebase.i686                   6:4.6.3-1.fc15     @updates
kdebase-libs.i686              6:4.6.3-1.fc15     @updates
kdebase-runtime.i686             4.6.3-1.fc15     @updates
kdebase-runtime-flags.noarch     4.6.3-1.fc15     @updates
kdebase-runtime-libs.i686        4.6.3-1.fc15     @updates
kdebase-workspace.i686           4.6.3-5.fc15     @updates
kdebase-workspace-libs.i686      4.6.3-5.fc15     @updates


How reproducible:
allways

Steps to Reproduce:
1. try to conect to the wireless conection
2.
3.
  
Actual results:
crash, and also plasma crashes if using the applet after the first crash.

Expected results:
no crash or an error at least.

Additional info:

Using staging kernel drivers from rpmfusion:
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8187SE Wireless LAN Controller (rev 22)
Comment 1 Reartes Guillermo 2011-06-26 03:49:04 UTC 
Well, i updated the dell e4310 (x86_64) and with the new network manager (the same from the wind u100) and it has the same problem, segfault and plasma crashes... (with the previous one, it worked)

downgrading network-manager fixed the issue on the dell.

downgrading network-manager pseudo-fixed the issue on the wind u100.
pseudo-fixed because (using wlan):
 * ping works (ipv4, dns)
 * yum works (installed lynx and links)
 * firefox and konqueror could not open sites. (it also fails to open an ip which was obtained with ping)
 * lynx also cannot open sites.
 * links CAN open sites (!)


-----

the package: 
 NetworkManager.XXXX  1:0.8.9997-4.git20110620.fc15
is broken (horribly broken) for both 32 and 64 bit.
failed with a wind u100 and a dell e4310. downgrading both machines fixed the issue. (the wind seems to have an extra issue, maybe unrelated or not).
Comment 2 Reartes Guillermo 2011-06-26 03:50:58 UTC 
i was unable to find how-to disable the packagekit notification, set it to never but it is there. also i was unable to find any systemd or sysv service to disable the auto-update notification.
Comment 3 Jacek Pawlyta 2011-06-26 10:57:59 UTC 
Confirming the same problem, F15 64bit KDE. However nm-applet for Gnome works OK.
Comment 4 Patrick Dubois 2011-06-26 14:40:13 UTC 
Using F15 X86_64 here, same issue.

Discovered from bug : https://bugzilla.redhat.com/show_bug.cgi?id=716527

That packages in updates-testing might fix the issue.
--
yum update kde-plasma-networkmanagement --enablerepo updates-testing
--

Reboot after package upgrade and the problem would appear to be fixed.

Enjoy!
Comment 5 Reartes Guillermo 2011-06-26 15:19:34 UTC 
@Patrik

Thanks, it fixes the issue of network manager. First, i updated again. Then i updated kde-plasma-networkmanagement from updates-testing and the crash is gone. it connects wlan correctly.

---

However, with the wind u100 i do still experience the bizarre issue:
* ping works (ipv4, dns)
* yum works (installed lynx and links)
* firefox and konqueror could not open sites.
  (it also fails to open an ip which was obtained with ping)
 * lynx also cannot open sites.
 * links CAN open sites (!) 

why only links works? or why does firefox, konqueror and lynx fail to open sites or an ip. (no proxy)

Tried to test with opera, but i cannot download it with links because of the get.pl part of the site seems to not support links.
Comment 6 Patrick Dubois 2011-06-26 18:13:22 UTC 
Glad it helped at least 50%. 

For the other problems, could you provide the logs from a connection attempt(post crash fix) and the output of nm-tool ? 



(In reply to comment #5)
> @Patrik
> 
> Thanks, it fixes the issue of network manager. First, i updated again. Then i
> updated kde-plasma-networkmanagement from updates-testing and the crash is
> gone. it connects wlan correctly.
> 
> ---
>
Comment 7 André Johansen 2011-06-26 18:53:52 UTC 
Same crash seen on Eee 901 running KDE net-book workspace; not able to connect to the LAN with WiFi.  Downgrade of the NetworkManager RPMs solved the issue.
Comment 8 Reartes Guillermo 2011-06-26 21:21:30 UTC 
from the affected machine:

# nm-tool 

NetworkManager Tool

State: connected (global)

- Device: em1 ------------------------------------------------------------------
  Type:              Wired
  Driver:            r8169
  State:             unavailable
  Default:           no
  HW Address:        00:21:85:47:01:08

  Capabilities:
    Carrier Detect:  yes
    Speed:           10 Mb/s

  Wired Properties
    Carrier:         off


- Device: wlan0  [cubesphere] --------------------------------------------------
  Type:              802.11 WiFi
  Driver:            r8180
  State:             connected
  Default:           yes
  HW Address:        00:1D:92:C8:BA:86

  Capabilities:
    Speed:           54 Mb/s

  Wireless Properties
    WEP Encryption:  yes
    WPA Encryption:  yes
    WPA2 Encryption: yes

  Wireless Access Points (* = current AP)
    speedywifi1:     Infra, 40:4A:03:D0:A9:D3, Freq 2462 MHz, Rate 54 Mb/s, Strength 62
    *cubesphere:     Infra, 00:1E:E5:92:1B:AE, Freq 2447 MHz, Rate 54 Mb/s, Strength 89 WPA2

  IPv4 Settings:
    Address:         192.168.1.111
    Prefix:          24 (255.255.255.0)
    Gateway:         192.168.1.1

    DNS:             192.168.1.1

-----

I am logged in via ssh over wlan, so the wlan does indeed work ok.

-----

FF: www.redhat.com (cannot open page)
-------------------------------------
18:06:29.997316 EAPOL key (3) v1, len 95
18:06:30.993752 EAPOL key (3) v1, len 95
18:06:30.994217 EAPOL key (3) v1, len 117
18:06:30.997604 EAPOL key (3) v1, len 151
18:06:30.998001 EAPOL key (3) v1, len 95
18:06:32.774210 ARP, Request who-has 192.168.1.1 tell rukia, length 28
18:06:32.775704 ARP, Request who-has 192.168.1.1 tell rukia, length 28
18:06:32.775846 ARP, Reply 192.168.1.1 is-at 00:1e:e5:92:1b:ae (oui Unknown), length 28
18:06:32.775872 IP rukia.43158 > 192.168.1.1.domain: 35979+ A? www.redhat.com. (32)
18:06:32.775975 IP rukia.50549 > 192.168.1.1.domain: 31144+ PTR? 1.1.168.192.in-addr.arpa. (42)
18:06:32.776104 IP rukia.43158 > 192.168.1.1.domain: 7359+ AAAA? www.redhat.com. (32)
18:06:32.780237 IP 192.168.1.1.domain > rukia.50549: 31144 NXDomain 0/0/0 (42)
18:06:32.780871 IP rukia.34359 > 192.168.1.1.domain: 57642+ PTR? 111.1.168.192.in-addr.arpa. (44)
18:06:32.783709 IP 192.168.1.1.domain > rukia.34359: 57642* 1/0/0 PTR rukia. (63)
18:06:32.803360 IP 192.168.1.1.domain > rukia.43158: 35979 4/0/0 CNAME www.redhat.com.edgekey.net., CNAME www.redhat.com.edgekey.net.globalredir.akadns.net., CNAME e86.b.akamaiedge.net., A 23.1.128.112 (179)
18:06:32.990167 IP 192.168.1.1.domain > rukia.43158: [|domain]
18:06:32.990527 IP rukia.53252 > 192.168.1.1.domain: 35979+ A? www.redhat.com. (32)
18:06:32.990675 IP rukia.53252 > 192.168.1.1.domain: 7359+ AAAA? www.redhat.com. (32)
18:06:32.993161 IP 192.168.1.1.domain > rukia.53252: 35979 4/0/0 CNAME www.redhat.com.edgekey.net., CNAME www.redhat.com.edgekey.net.globalredir.akadns.net., CNAME e86.b.akamaiedge.net., A 23.1.128.112 (185)
18:06:33.194366 IP 192.168.1.1.domain > rukia.53252: [|domain]
18:06:33.194738 IP rukia.33574 > 192.168.1.1.domain: 21604+ A? www.redhat.com.espada. (39)
18:06:33.194888 IP rukia.33574 > 192.168.1.1.domain: 29726+ AAAA? www.redhat.com.espada. (39)
18:06:33.212168 IP 192.168.1.1.domain > rukia.33574: [|domain]
18:06:33.212607 IP rukia.45512 > 192.168.1.1.domain: 21604+ A? www.redhat.com.espada. (39)
18:06:33.212993 IP rukia.45512 > 192.168.1.1.domain: 29726+ AAAA? www.redhat.com.espada. (39)
18:06:33.228359 IP 192.168.1.1.domain > rukia.45512: 21604 1/0/0 A 208.70.188.15 (76)
18:06:33.230842 IP 192.168.1.1.domain > rukia.45512: [|domain]
18:06:33.231930 IP rukia.49401 > 192.168.1.1.domain: 43263+ A? www.redhat.com. (32)
18:06:33.232330 IP rukia.49401 > 192.168.1.1.domain: 49179+ AAAA? www.redhat.com. (32)
18:06:33.234712 IP 192.168.1.1.domain > rukia.49401: 43263 4/0/0 CNAME www.redhat.com.edgekey.net., CNAME www.redhat.com.edgekey.net.globalredir.akadns.net., CNAME e86.b.akamaiedge.net., A 23.1.128.112 (185)
18:06:33.249778 IP 192.168.1.1.domain > rukia.49401: [|domain]
18:06:33.250234 IP rukia.47684 > 192.168.1.1.domain: 43263+ A? www.redhat.com. (32)
18:06:33.250588 IP rukia.47684 > 192.168.1.1.domain: 49179+ AAAA? www.redhat.com. (32)
18:06:33.252869 IP 192.168.1.1.domain > rukia.47684: 43263 4/0/0 CNAME www.redhat.com.edgekey.net., CNAME www.redhat.com.edgekey.net.globalredir.akadns.net., CNAME e86.b.akamaiedge.net., A 23.1.128.112 (185)
18:06:33.270439 IP 192.168.1.1.domain > rukia.47684: [|domain]
18:06:33.270879 IP rukia.40645 > 192.168.1.1.domain: 15404+ A? www.redhat.com.espada. (39)
18:06:33.271328 IP rukia.40645 > 192.168.1.1.domain: 43096+ AAAA? www.redhat.com.espada. (39)
18:06:33.273343 IP 192.168.1.1.domain > rukia.40645: 15404 1/0/0 A 208.70.188.15 (55)
18:06:33.292642 IP 192.168.1.1.domain > rukia.40645: [|domain]
18:06:33.293374 IP rukia.43128 > 192.168.1.1.domain: 15404+ A? www.redhat.com.espada. (39)
18:06:33.294569 IP rukia.43128 > 192.168.1.1.domain: 43096+ AAAA? www.redhat.com.espada. (39)
18:06:33.295523 IP 192.168.1.1.domain > rukia.43128: 15404 1/0/0 A 208.70.188.15 (55)
18:06:33.310440 IP 192.168.1.1.domain > rukia.43128: [|domain]
18:06:33.436475 IP 192.168.1.1.domain > rukia.33574: 21604 1/0/0 A 208.70.188.15 (76)
18:06:33.436635 IP rukia > 192.168.1.1: ICMP rukia udp port 33574 unreachable, length 112
18:06:35.591605 IP rukia.36777 > 192.168.1.1.domain: 10322+ A? www.stopbadware.org. (37)
18:06:35.591849 IP rukia.36777 > 192.168.1.1.domain: 18578+ AAAA? www.stopbadware.org. (37)
18:06:35.594329 IP 192.168.1.1.domain > rukia.36777: 10322 2/0/0 CNAME stopbadware.org., A 128.103.64.79 (82)
18:06:35.609582 IP 192.168.1.1.domain > rukia.36777: [|domain]
18:06:35.610295 IP rukia.50123 > 192.168.1.1.domain: 10322+ A? www.stopbadware.org. (37)
18:06:35.610517 IP rukia.50123 > 192.168.1.1.domain: 18578+ AAAA? www.stopbadware.org. (37)
18:06:35.612621 IP 192.168.1.1.domain > rukia.50123: 10322 2/0/0 CNAME stopbadware.org., A 128.103.64.79 (82)
18:06:35.626038 IP 192.168.1.1.domain > rukia.50123: [|domain]
18:06:35.626379 IP rukia.50034 > 192.168.1.1.domain: 56412+ A? www.stopbadware.org.espada. (44)
18:06:35.626531 IP rukia.50034 > 192.168.1.1.domain: 34879+ AAAA? www.stopbadware.org.espada. (44)
18:06:35.643176 IP 192.168.1.1.domain > rukia.50034: [|domain]
18:06:35.643561 IP rukia.36276 > 192.168.1.1.domain: 56412+ A? www.stopbadware.org.espada. (44)
18:06:35.643732 IP rukia.36276 > 192.168.1.1.domain: 34879+ AAAA? www.stopbadware.org.espada. (44)
18:06:35.645937 IP 192.168.1.1.domain > rukia.50034: 56412 1/0/0 A 208.70.188.15 (86)
18:06:35.646054 IP rukia > 192.168.1.1: ICMP rukia udp port 50034 unreachable, length 122
18:06:35.647023 IP 192.168.1.1.domain > rukia.36276: 56412 1/0/0 A 208.70.188.15 (60)
18:06:35.660360 IP 192.168.1.1.domain > rukia.36276: [|domain]
18:06:35.661093 IP rukia.48827 > 192.168.1.1.domain: 3293+ A? www.stopbadware.org. (37)
18:06:35.661308 IP rukia.48827 > 192.168.1.1.domain: 38090+ AAAA? www.stopbadware.org. (37)
18:06:35.663590 IP 192.168.1.1.domain > rukia.48827: 3293 2/0/0 CNAME stopbadware.org., A 128.103.64.79 (82)
18:06:35.677777 IP 192.168.1.1.domain > rukia.48827: [|domain]
18:06:35.678310 IP rukia.41997 > 192.168.1.1.domain: 3293+ A? www.stopbadware.org. (37)
18:06:35.678515 IP rukia.41997 > 192.168.1.1.domain: 38090+ AAAA? www.stopbadware.org. (37)
18:06:35.680709 IP 192.168.1.1.domain > rukia.41997: 3293 2/0/0 CNAME stopbadware.org., A 128.103.64.79 (82)
18:06:35.694834 IP 192.168.1.1.domain > rukia.41997: [|domain]
18:06:35.695097 IP rukia.52147 > 192.168.1.1.domain: 35+ A? www.stopbadware.org.espada. (44)
18:06:35.695281 IP rukia.52147 > 192.168.1.1.domain: 55446+ AAAA? www.stopbadware.org.espada. (44)
18:06:35.697328 IP 192.168.1.1.domain > rukia.52147: 35 1/0/0 A 208.70.188.15 (60)
18:06:35.711251 IP 192.168.1.1.domain > rukia.52147: [|domain]
18:06:35.711635 IP rukia.53632 > 192.168.1.1.domain: 35+ A? www.stopbadware.org.espada. (44)
18:06:35.711805 IP rukia.53632 > 192.168.1.1.domain: 55446+ AAAA? www.stopbadware.org.espada. (44)
18:06:35.714183 IP 192.168.1.1.domain > rukia.53632: 35 1/0/0 A 208.70.188.15 (60)
18:06:35.730469 IP 192.168.1.1.domain > rukia.53632: [|domain]
18:06:29.997316 EAPOL key (3) v1, len 95
18:06:30.993752 EAPOL key (3) v1, len 95
18:06:30.994217 EAPOL key (3) v1, len 117
18:06:30.997604 EAPOL key (3) v1, len 151
18:06:30.998001 EAPOL key (3) v1, len 95
18:06:32.774210 ARP, Request who-has 192.168.1.1 tell rukia, length 28
18:06:32.775704 ARP, Request who-has 192.168.1.1 tell rukia, length 28
18:06:32.775846 ARP, Reply 192.168.1.1 is-at 00:1e:e5:92:1b:ae (oui Unknown), length 28
18:06:32.775872 IP rukia.43158 > 192.168.1.1.domain: 35979+ A? www.redhat.com. (32)
18:06:32.775975 IP rukia.50549 > 192.168.1.1.domain: 31144+ PTR? 1.1.168.192.in-addr.arpa. (42)
18:06:32.776104 IP rukia.43158 > 192.168.1.1.domain: 7359+ AAAA? www.redhat.com. (32)
18:06:32.780237 IP 192.168.1.1.domain > rukia.50549: 31144 NXDomain 0/0/0 (42)
18:06:32.780871 IP rukia.34359 > 192.168.1.1.domain: 57642+ PTR? 111.1.168.192.in-addr.arpa. (44)
18:06:32.783709 IP 192.168.1.1.domain > rukia.34359: 57642* 1/0/0 PTR rukia. (63)
18:06:32.803360 IP 192.168.1.1.domain > rukia.43158: 35979 4/0/0 CNAME www.redhat.com.edgekey.net., CNAME www.redhat.com.edgekey.net.globalredir.akadns.net., CNAME e86.b.akamaiedge.net., A 23.1.128.112 (179)
18:06:32.990167 IP 192.168.1.1.domain > rukia.43158: [|domain]
18:06:32.990527 IP rukia.53252 > 192.168.1.1.domain: 35979+ A? www.redhat.com. (32)
18:06:32.990675 IP rukia.53252 > 192.168.1.1.domain: 7359+ AAAA? www.redhat.com. (32)
18:06:32.993161 IP 192.168.1.1.domain > rukia.53252: 35979 4/0/0 CNAME www.redhat.com.edgekey.net., CNAME www.redhat.com.edgekey.net.globalredir.akadns.net., CNAME e86.b.akamaiedge.net., A 23.1.128.112 (185)
18:06:33.194366 IP 192.168.1.1.domain > rukia.53252: [|domain]
18:06:33.194738 IP rukia.33574 > 192.168.1.1.domain: 21604+ A? www.redhat.com.espada. (39)
18:06:33.194888 IP rukia.33574 > 192.168.1.1.domain: 29726+ AAAA? www.redhat.com.espada. (39)
18:06:33.212168 IP 192.168.1.1.domain > rukia.33574: [|domain]
18:06:33.212607 IP rukia.45512 > 192.168.1.1.domain: 21604+ A? www.redhat.com.espada. (39)
18:06:33.212993 IP rukia.45512 > 192.168.1.1.domain: 29726+ AAAA? www.redhat.com.espada. (39)
18:06:33.228359 IP 192.168.1.1.domain > rukia.45512: 21604 1/0/0 A 208.70.188.15 (76)
18:06:33.230842 IP 192.168.1.1.domain > rukia.45512: [|domain]
18:06:33.231930 IP rukia.49401 > 192.168.1.1.domain: 43263+ A? www.redhat.com. (32)
18:06:33.232330 IP rukia.49401 > 192.168.1.1.domain: 49179+ AAAA? www.redhat.com. (32)
18:06:33.234712 IP 192.168.1.1.domain > rukia.49401: 43263 4/0/0 CNAME www.redhat.com.edgekey.net., CNAME www.redhat.com.edgekey.net.globalredir.akadns.net., CNAME e86.b.akamaiedge.net., A 23.1.128.112 (185)
18:06:33.249778 IP 192.168.1.1.domain > rukia.49401: [|domain]
18:06:33.250234 IP rukia.47684 > 192.168.1.1.domain: 43263+ A? www.redhat.com. (32)
18:06:33.250588 IP rukia.47684 > 192.168.1.1.domain: 49179+ AAAA? www.redhat.com. (32)
18:06:33.252869 IP 192.168.1.1.domain > rukia.47684: 43263 4/0/0 CNAME www.redhat.com.edgekey.net., CNAME www.redhat.com.edgekey.net.globalredir.akadns.net., CNAME e86.b.akamaiedge.net., A 23.1.128.112 (185)
18:06:33.270439 IP 192.168.1.1.domain > rukia.47684: [|domain]
18:06:33.270879 IP rukia.40645 > 192.168.1.1.domain: 15404+ A? www.redhat.com.espada. (39)
18:06:33.271328 IP rukia.40645 > 192.168.1.1.domain: 43096+ AAAA? www.redhat.com.espada. (39)
18:06:33.273343 IP 192.168.1.1.domain > rukia.40645: 15404 1/0/0 A 208.70.188.15 (55)
18:06:33.292642 IP 192.168.1.1.domain > rukia.40645: [|domain]
18:06:33.293374 IP rukia.43128 > 192.168.1.1.domain: 15404+ A? www.redhat.com.espada. (39)
18:06:33.294569 IP rukia.43128 > 192.168.1.1.domain: 43096+ AAAA? www.redhat.com.espada. (39)
18:06:33.295523 IP 192.168.1.1.domain > rukia.43128: 15404 1/0/0 A 208.70.188.15 (55)
18:06:33.310440 IP 192.168.1.1.domain > rukia.43128: [|domain]
18:06:33.436475 IP 192.168.1.1.domain > rukia.33574: 21604 1/0/0 A 208.70.188.15 (76)
18:06:33.436635 IP rukia > 192.168.1.1: ICMP rukia udp port 33574 unreachable, length 112
18:06:35.591605 IP rukia.36777 > 192.168.1.1.domain: 10322+ A? www.stopbadware.org. (37)
18:06:35.591849 IP rukia.36777 > 192.168.1.1.domain: 18578+ AAAA? www.stopbadware.org. (37)
18:06:35.594329 IP 192.168.1.1.domain > rukia.36777: 10322 2/0/0 CNAME stopbadware.org., A 128.103.64.79 (82)
18:06:35.609582 IP 192.168.1.1.domain > rukia.36777: [|domain]
18:06:35.610295 IP rukia.50123 > 192.168.1.1.domain: 10322+ A? www.stopbadware.org. (37)
18:06:35.610517 IP rukia.50123 > 192.168.1.1.domain: 18578+ AAAA? www.stopbadware.org. (37)
18:06:35.612621 IP 192.168.1.1.domain > rukia.50123: 10322 2/0/0 CNAME stopbadware.org., A 128.103.64.79 (82)
18:06:35.626038 IP 192.168.1.1.domain > rukia.50123: [|domain]
18:06:35.626379 IP rukia.50034 > 192.168.1.1.domain: 56412+ A? www.stopbadware.org.espada. (44)
18:06:35.626531 IP rukia.50034 > 192.168.1.1.domain: 34879+ AAAA? www.stopbadware.org.espada. (44)
18:06:35.643176 IP 192.168.1.1.domain > rukia.50034: [|domain]
18:06:35.643561 IP rukia.36276 > 192.168.1.1.domain: 56412+ A? www.stopbadware.org.espada. (44)
18:06:35.643732 IP rukia.36276 > 192.168.1.1.domain: 34879+ AAAA? www.stopbadware.org.espada. (44)
18:06:35.645937 IP 192.168.1.1.domain > rukia.50034: 56412 1/0/0 A 208.70.188.15 (86)
18:06:35.646054 IP rukia > 192.168.1.1: ICMP rukia udp port 50034 unreachable, length 122
18:06:35.647023 IP 192.168.1.1.domain > rukia.36276: 56412 1/0/0 A 208.70.188.15 (60)
18:06:35.660360 IP 192.168.1.1.domain > rukia.36276: [|domain]
18:06:35.661093 IP rukia.48827 > 192.168.1.1.domain: 3293+ A? www.stopbadware.org. (37)
18:06:35.661308 IP rukia.48827 > 192.168.1.1.domain: 38090+ AAAA? www.stopbadware.org. (37)
18:06:35.663590 IP 192.168.1.1.domain > rukia.48827: 3293 2/0/0 CNAME stopbadware.org., A 128.103.64.79 (82)
18:06:35.677777 IP 192.168.1.1.domain > rukia.48827: [|domain]
18:06:35.678310 IP rukia.41997 > 192.168.1.1.domain: 3293+ A? www.stopbadware.org. (37)
18:06:35.678515 IP rukia.41997 > 192.168.1.1.domain: 38090+ AAAA? www.stopbadware.org. (37)
18:06:35.680709 IP 192.168.1.1.domain > rukia.41997: 3293 2/0/0 CNAME stopbadware.org., A 128.103.64.79 (82)
18:06:35.694834 IP 192.168.1.1.domain > rukia.41997: [|domain]
18:06:35.695097 IP rukia.52147 > 192.168.1.1.domain: 35+ A? www.stopbadware.org.espada. (44)
18:06:35.695281 IP rukia.52147 > 192.168.1.1.domain: 55446+ AAAA? www.stopbadware.org.espada. (44)
18:06:35.697328 IP 192.168.1.1.domain > rukia.52147: 35 1/0/0 A 208.70.188.15 (60)
18:06:35.711251 IP 192.168.1.1.domain > rukia.52147: [|domain]
18:06:35.711635 IP rukia.53632 > 192.168.1.1.domain: 35+ A? www.stopbadware.org.espada. (44)
18:06:35.711805 IP rukia.53632 > 192.168.1.1.domain: 55446+ AAAA? www.stopbadware.org.espada. (44)
18:06:35.714183 IP 192.168.1.1.domain > rukia.53632: 35 1/0/0 A 208.70.188.15 (60)
18:06:35.730469 IP 192.168.1.1.domain > rukia.53632: [|domain]


Links: www.redhat.com (Page is loaded, ok)
------------------------------------------
18:11:14.943101 IP rukia.59712 > 192.168.1.1.domain: 18459+ A? www.redhat.com. (32)
18:11:15.184886 IP 192.168.1.1.domain > rukia.59712: 18459 4/0/0 CNAME www.redhat.com.edgekey.net., CNAME www.redhat.com.edgekey.net.globalredir.akadns.net., CNAME e86.b.akamaiedge.net., A 23.1.48.112 (179)
18:11:15.186001 IP rukia.40894 > a23-1-48-112.deploy.akamaitechnologies.com.http: Flags [S], seq 2412926196, win 14600, options [mss 1460,sackOK,TS val 857375 ecr 0,nop,wscale 6], length 0
18:11:15.354520 IP a23-1-48-112.deploy.akamaitechnologies.com.http > rukia.40894: Flags [S.], seq 2818929567, ack 2412926197, win 5792, options [mss 1460,sackOK,TS val 3349367590 ecr 857375,nop,wscale 5], length 0
18:11:15.354682 IP rukia.40894 > a23-1-48-112.deploy.akamaitechnologies.com.http: Flags [.], ack 1, win 229, options [nop,nop,TS val 857544 ecr 3349367590], length 0
18:11:15.355471 IP rukia.40894 > a23-1-48-112.deploy.akamaitechnologies.com.http: Flags [P.], seq 1:607, ack 1, win 229, options [nop,nop,TS val 857545 ecr 3349367590], length 606
18:11:15.531381 IP a23-1-48-112.deploy.akamaitechnologies.com.http > rukia.40894: Flags [.], ack 607, win 219, options [nop,nop,TS val 3349367768 ecr 857545], length 0
18:11:15.694646 IP a23-1-48-112.deploy.akamaitechnologies.com.http > rukia.40894: Flags [.], seq 1:1373, ack 607, win 219, options [nop,nop,TS val 3349367920 ecr 857545], length 1372
18:11:15.694766 IP rukia.40894 > a23-1-48-112.deploy.akamaitechnologies.com.http: Flags [.], ack 1373, win 274, options [nop,nop,TS val 857884 ecr 3349367920], length 0
18:11:15.705445 IP a23-1-48-112.deploy.akamaitechnologies.com.http > rukia.40894: Flags [.], seq 1373:2745, ack 607, win 219, options [nop,nop,TS val 3349367920 ecr 857545], length 1372
18:11:15.705575 IP rukia.40894 > a23-1-48-112.deploy.akamaitechnologies.com.http: Flags [.], ack 2745, win 319, options [nop,nop,TS val 857895 ecr 3349367920], length 0
18:11:15.716803 IP a23-1-48-112.deploy.akamaitechnologies.com.http > rukia.40894: Flags [.], seq 2745:4117, ack 607, win 219, options [nop,nop,TS val 3349367920 ecr 857545], length 1372
18:11:15.716884 IP rukia.40894 > a23-1-48-112.deploy.akamaitechnologies.com.http: Flags [.], ack 4117, win 364, options [nop,nop,TS val 857906 ecr 3349367920], length 0
18:11:15.727867 IP a23-1-48-112.deploy.akamaitechnologies.com.http > rukia.40894: Flags [.], seq 4117:5489, ack 607, win 219, options [nop,nop,TS val 3349367920 ecr 857545], length 1372
18:11:15.728011 IP rukia.40894 > a23-1-48-112.deploy.akamaitechnologies.com.http: Flags [.], ack 5489, win 410, options [nop,nop,TS val 857917 ecr 3349367920], length 0
18:11:15.735010 IP a23-1-48-112.deploy.akamaitechnologies.com.http > rukia.40894: Flags [P.], seq 5489:6369, ack 607, win 219, options [nop,nop,TS val 3349367920 ecr 857545], length 880
18:11:15.735091 IP rukia.40894 > a23-1-48-112.deploy.akamaitechnologies.com.http: Flags [.], ack 6369, win 452, options [nop,nop,TS val 857924 ecr 3349367920], length 0
18:11:21.709576 IP rukia.40894 > a23-1-48-112.deploy.akamaitechnologies.com.http: Flags [F.], seq 607, ack 6369, win 452, options [nop,nop,TS val 863899 ecr 3349367920], length 0
18:11:21.875728 IP a23-1-48-112.deploy.akamaitechnologies.com.http > rukia.40894: Flags [F.], seq 6369, ack 608, win 219, options [nop,nop,TS val 3349374112 ecr 863899], length 0
18:11:21.875860 IP rukia.40894 > a23-1-48-112.deploy.akamaitechnologies.com.http: Flags [.], ack 6370, win 452, options [nop,nop,TS val 864065 ecr 3349374112], length 0



$ ping www.redhat.com.out
----------------------------- 
18:08:28.511905 IP rukia.46574 > 192.168.1.1.domain: 62687+ A? www.redhat.com. (32)
18:08:33.517522 IP rukia.46574 > 192.168.1.1.domain: 62687+ A? www.redhat.com. (32)
18:08:33.761295 IP 192.168.1.1.domain > rukia.46574: 62687 4/0/0 CNAME www.redhat.com.edgekey.net., CNAME www.redhat.com.edgekey.net.globalredir.akadns.net., CNAME e86.b.akamaiedge.net., A 23.1.48.112 (179)
18:08:33.762674 IP rukia > a23-1-48-112.deploy.akamaitechnologies.com: ICMP echo request, id 1696, seq 1, length 64
18:08:33.763332 IP rukia.49347 > 192.168.1.1.domain: 3561+ PTR? 112.48.1.23.in-addr.arpa. (42)
18:08:33.937330 IP a23-1-48-112.deploy.akamaitechnologies.com > rukia: ICMP echo reply, id 1696, seq 1, length 64
18:08:33.938242 IP rukia.40419 > 192.168.1.1.domain: 39064+ PTR? 112.48.1.23.in-addr.arpa. (42)
18:08:34.119319 IP 192.168.1.1.domain > rukia.49347: 3561 1/0/0 PTR a23-1-48-112.deploy.akamaitechnologies.com. (98)
18:08:34.164153 IP 192.168.1.1.domain > rukia.40419: 39064 1/0/0 PTR a23-1-48-112.deploy.akamaitechnologies.com. (98)
18:08:34.762516 IP rukia > a23-1-48-112.deploy.akamaitechnologies.com: ICMP echo request, id 1696, seq 2, length 64
18:08:34.930220 IP a23-1-48-112.deploy.akamaitechnologies.com > rukia: ICMP echo reply, id 1696, seq 2, length 64
18:08:35.763586 IP rukia > a23-1-48-112.deploy.akamaitechnologies.com: ICMP echo request, id 1696, seq 3, length 64
18:08:35.933945 IP a23-1-48-112.deploy.akamaitechnologies.com > rukia: ICMP echo reply, id 1696, seq 3, length 64
18:08:36.765364 IP rukia > a23-1-48-112.deploy.akamaitechnologies.com: ICMP echo request, id 1696, seq 4, length 64
18:08:36.807881 ARP, Request who-has rukia tell 192.168.1.1, length 28
18:08:36.807936 ARP, Reply rukia is-at 00:1d:92:c8:ba:86 (oui Unknown), length 28
18:08:36.929440 IP a23-1-48-112.deploy.akamaitechnologies.com > rukia: ICMP echo reply, id 1696, seq 4, length 64
18:08:37.766692 IP rukia > a23-1-48-112.deploy.akamaitechnologies.com: ICMP echo request, id 1696, seq 5, length 64
18:08:37.934324 IP a23-1-48-112.deploy.akamaitechnologies.com > rukia: ICMP echo reply, id 1696, seq 5, length 64
18:08:38.767680 IP rukia > a23-1-48-112.deploy.akamaitechnologies.com: ICMP echo request, id 1696, seq 6, length 64
18:08:38.937725 IP a23-1-48-112.deploy.akamaitechnologies.com > rukia: ICMP echo reply, id 1696, seq 6, length 64
18:08:39.769249 IP rukia > a23-1-48-112.deploy.akamaitechnologies.com: ICMP echo request, id 1696, seq 7, length 64
18:08:39.936562 IP a23-1-48-112.deploy.akamaitechnologies.com > rukia: ICMP echo reply, id 1696, seq 7, length 64
18:08:40.770921 IP rukia > a23-1-48-112.deploy.akamaitechnologies.com: ICMP echo request, id 1696, seq 8, length 64
18:08:40.938532 IP a23-1-48-112.deploy.akamaitechnologies.com > rukia: ICMP echo reply, id 1696, seq 8, length 64
18:08:41.771893 IP rukia > a23-1-48-112.deploy.akamaitechnologies.com: ICMP echo request, id 1696, seq 9, length 64
18:08:41.941533 IP a23-1-48-112.deploy.akamaitechnologies.com > rukia: ICMP echo reply, id 1696, seq 9, length 64
18:08:42.772873 IP rukia > a23-1-48-112.deploy.akamaitechnologies.com: ICMP echo request, id 1696, seq 10, length 64
18:08:42.936630 IP a23-1-48-112.deploy.akamaitechnologies.com > rukia: ICMP echo reply, id 1696, seq 10, length 64
18:08:43.773960 IP rukia > a23-1-48-112.deploy.akamaitechnologies.com: ICMP echo request, id 1696, seq 11, length 64
18:08:43.938019 IP a23-1-48-112.deploy.akamaitechnologies.com > rukia: ICMP echo reply, id 1696, seq 11, length 64
18:08:44.775399 IP rukia > a23-1-48-112.deploy.akamaitechnologies.com: ICMP echo request, id 1696, seq 12, length 64
18:08:44.940052 IP a23-1-48-112.deploy.akamaitechnologies.com > rukia: ICMP echo reply, id 1696, seq 12, length 64
18:08:45.776414 IP rukia > a23-1-48-112.deploy.akamaitechnologies.com: ICMP echo request, id 1696, seq 13, length 64
18:08:45.943544 IP a23-1-48-112.deploy.akamaitechnologies.com > rukia: ICMP echo reply, id 1696, seq 13, length 64
18:08:46.777905 IP rukia > a23-1-48-112.deploy.akamaitechnologies.com: ICMP echo request, id 1696, seq 14, length 64
18:08:46.944875 IP a23-1-48-112.deploy.akamaitechnologies.com > rukia: ICMP echo reply, id 1696, seq 14, length 64
Comment 9 Reartes Guillermo 2011-06-29 13:30:06 UTC 
At least with firefox, disabling ipv6 dns fixed the issue for it. I don't know why it suddenly caused problem.
Comment 10 Reartes Guillermo 2011-06-29 15:10:09 UTC 
The remaining problem seems to be ipv6 related. I am not sure it is nm related since y tried disabing it and using wpa_supplicant manually and it has the same behaviour.

unaffected: opera, links, ping
affected but workarounded by disabling ipv6 dns: firefox 5

affected: lynx, konqueror, yum (specially rpmfusion and adobe "cannot resolve hostname))

maybe i should open a separate bugreport for the ipv6 issue.

hw: wind u100(i386), dell e4310(x86_64) and asus ul80vt (x86_64)
Comment 11 Reartes Guillermo 2011-06-30 01:57:43 UTC 
definitively it was ipv6 related, and maybe (i still need to research a bit) it is related to openwag firmware.

It seems both problems appeared at the same time. I will open another bugreport for the ipv6 stuff if needed.

Currently i disabled ipv6 completely from all notebooks/netbooks.

Regarding the issue of the bugreport (the network-manager crashes), in some laptops i used the downgrade route and in others i used the upgrade to testing route. and the problem seems workarounded (With ipv6 disabled until i can determine that it is openwag related).
Comment 12 Reartes Guillermo 2011-10-19 23:32:32 UTC 
This bug can be closed, since NM is working correctly.
Note You need to log in before you can comment on or make changes to this bug.