From owner-freebsd-wireless@FreeBSD.ORG Sat Jun 14 23:12:13 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0838A233 for ; Sat, 14 Jun 2014 23:12:13 +0000 (UTC) Received: from mail-vc0-x232.google.com (mail-vc0-x232.google.com [IPv6:2607:f8b0:400c:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B747E2802 for ; Sat, 14 Jun 2014 23:12:12 +0000 (UTC) Received: by mail-vc0-f178.google.com with SMTP id ij19so3702500vcb.9 for ; Sat, 14 Jun 2014 16:12:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=6uz3c+Ei3YkAO9Uu+GMG+v1G0eRvD2b0tKGaQXq7j54=; b=Ub1iBgbwXozfF1Zi47oj8FPYpVFYiG05aUTMF3tGVH4p/Ou+3Y1TqeURNAOEIHW0Nb F15SgkvxQGHIdWNZ2zHA/MeOAEd3bHIfBX+O0QMK4mG2uMkzfv6yIQAiLTAGTiX68Jq/ 19Q9okIA8g+Gf35oifxhcAWYvIfziYB9BpcVsJsf9a09/EiOooXcg4y0is9vRUH0PAf7 IpGijp2zmj1ag70O+OCnyqGlVARcxpMT7jUyMOHHlyMKGwZ3ZO265W9C8/Aw/ar0tQgq oqP3suLxkilrmYK5/86Dd6Wzi9tnwtsaboqail7omX+3QYm+UEQyNQvI6rpBsh4DFa/O X/cw== MIME-Version: 1.0 X-Received: by 10.220.159.4 with SMTP id h4mr8596413vcx.1.1402787531708; Sat, 14 Jun 2014 16:12:11 -0700 (PDT) Received: by 10.220.13.10 with HTTP; Sat, 14 Jun 2014 16:12:11 -0700 (PDT) Date: Sat, 14 Jun 2014 16:12:11 -0700 Message-ID: Subject: in-depth wireless troubleshooting From: Peter Kryszkiewicz To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jun 2014 23:12:13 -0000 I've installed this device (dmesg output) rum0: on usbus1 rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 and had it running fine on a new install, until I started populating the ports tree. Somewhere along the way the interface stopped working. I've done everything I know to diagnose the problem but need some more surgical tools and advice now. Here's what I've got: *>uname -a*: FreeBSD dfwr.worldwins.net 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan16 22:34:59 UTC 2014 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 *>ifconfig -a* nfe0: flags=8843 metric 0 mtu 1500 options=82008 ether 00:1e:8c:36:15:37 inet6 fe80::21e:8cff:fe36:1537%nfe0 prefixlen 64 scopeid 0x1 inet 192.168.0.111 netmask 0xffffff00 broadcast 192.168.0.255 nd6 options=23 media: Ethernet autoselect (100baseTX ) status: active lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 rum0: flags=8843 metric 0 mtu 2290 ether 00:16:44:89:46:1a nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated wlan0: flags=8843 metric 0 mtu 1500 ether 00:16:44:89:46:1a inet6 fe80::216:44ff:fe89:461a%wlan0 prefixlen 64 scopeid 0x4 inet 192.168.1.73 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=23 media: IEEE 802.11 Wireless Ethernet OFDM/48Mbps mode 11g *> less /boot/loader.conf* if_nfe_load="YES" if_rum_load="YES" wlan_scan_ap_load="YES" wlan_scan_stn_load="YES" wlan_ccmp_load="YES" wlan_tkip_load="YES" kern.maxfiles=25000 *> less /var/db/dhclient.leases.wlan0* lease { interface "wlan0"; fixed-address 192.168.1.73; option subnet-mask 255.255.255.0; option routers 192.168.1.254; option domain-name-servers 192.168.1.254; option domain-name "Home"; option dhcp-lease-time 86400; option dhcp-message-type 5; option dhcp-server-identifier 192.168.1.254; renew 0 2014/6/15 09:38:30; rebind 0 2014/6/15 18:38:30; expire 0 2014/6/15 21:38:30; *> less /var/db/dhclient.leases.nfe0* lease { interface "nfe0"; fixed-address 192.168.0.111; option subnet-mask 255.255.255.0; option routers 192.168.0.1; option domain-name-servers 192.168.0.1; option dhcp-lease-time 86400; option dhcp-message-type 5; option dhcp-server-identifier 192.168.0.1; option dhcp-renewal-time 43200; option dhcp-rebinding-time 75600; renew 0 2014/6/15 09:33:27; rebind 0 2014/6/15 18:33:27; expire 0 2014/6/15 21:33:27; *> less /etc/resolv.conf* nameserver 192.168.0.1 *>less /etc/hosts* ::1 localhost localhost.worldwins.net dfwr 127.0.0.1 localhost localhost.worldwins.net dfwr # 192.168.1.111 dfwr.worldwins.net dfwr I've got another machine, a 386 laptop running 10.0, and it uses the same AP. The only difference is that the fixed adress of the internal NIC is 192.168.0.110 and its resolv.conf gives me: *(resolv.conf on laptop)* search Home nameserver 192.168.1.254 When I set the non-working machine's resolv.conf to the same, dhclient resets it immediately to the original contents. I've tried the script fix to disable dhclient from changing resolv.conf, but all that did was kill the network even 'deader' (before that, it looked as though requests were getting out - eg *ping http://someadress.com * would try for a few seconds before finally giving up with 'host name lookup failure'. Where can I go from here? BTW: how can I submit all the source snippets in a cleaner way? I've seen messages where the source was in a scrolling window. Haven't had time to find out how to do that. I have to head for the bush in a few hours, and am hoping to set up my box to install those huge ports before I go. Thanks for your consideration.