From owner-freebsd-questions@FreeBSD.ORG Sat Nov 19 03:54:53 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4BCE16A41F for ; Sat, 19 Nov 2005 03:54:53 +0000 (GMT) (envelope-from m0laria@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA86143D58 for ; Sat, 19 Nov 2005 03:54:50 +0000 (GMT) (envelope-from m0laria@gmail.com) Received: by zproxy.gmail.com with SMTP id 9so340833nzo for ; Fri, 18 Nov 2005 19:54:50 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=dIR5PjEHH2jGputixsuKjR00RkrT/uMwbJ2S5X0V3/Q7dSlWKa8qlPD2yyLzHVvSS7e7xNsSJKw/Ue11jWJdQODR2+dNBNmXymbWrjBFFV1BglqOK/oA/lVqLNVLQb5aqtTMMvo8cVUGgfsxN90iaLGZsqTtUasuZQQo10v2Cyc= Received: by 10.36.43.6 with SMTP id q6mr505911nzq; Fri, 18 Nov 2005 19:54:50 -0800 (PST) Received: from ?192.168.107.5? ( [68.68.56.135]) by mx.gmail.com with ESMTP id 38sm731879nza.2005.11.18.19.54.49; Fri, 18 Nov 2005 19:54:50 -0800 (PST) Message-ID: <437D5192.9040404@gmail.com> Date: Thu, 17 Nov 2005 19:59:14 -0800 From: Bryan White User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matt Emmerton , freebsd-questions@freebsd.org References: <1132286768.978.15.camel@localhost> <019501c5ebf6$fe9a3b90$1200a8c0@gsicomp.on.ca> <437D3679.2010800@gmail.com> <001101c5ecb4$a890af90$1200a8c0@gsicomp.on.ca> In-Reply-To: <001101c5ecb4$a890af90$1200a8c0@gsicomp.on.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: cannot get IP working between associated ath0 & AP, what to do? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2005 03:54:53 -0000 Ok... looks like add route default got it to work. Thanks a ton. Matt Emmerton wrote: >[ top-posting corrected ] > > > >>Matt Emmerton wrote: >> >> >> >>>>>Hi, >>>>> >>>>>I have an SMC PCMCIA wireless adapter, model SMCWCB-G, based on an >>>>>Atheros 5212 chipset, in a laptop running a fresh install of FreeBSD >>>>>6.0-RC1. >>>>> >>>>>The card associates fine, but then fails to send any IP packets in >>>>>the air, or at least that's what I presume is going on. I cannot >>>>>ping the AP, I cannot get a lease using DHCP, basically the only >>>>>thing I can do is associate. I think it does associate because when >>>>>I set an invalid wep key, t# Wireless NIC cards >>>>> >>>>> > > > >>>>I type in: >>>> >>>># ifconfig ath0 channel 7 ssid gibsons wepmode on >>>># ifconfig ath0 weptxkey *****etc. >>>># ifconfig ath0 up >>>># ifconfig ath0 >>>>ath0: flags=8843 mtu 1500 >>>> inet6 fe80::213:46ff:fe0f:3f66%ath0 prefixlen 64 scopeid 0x4 >>>> ether 00:13:46:0f:3f:66 >>>> media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) >>>> status: associated >>>> ssid gibsons channel 7 bssid 00:0c:41:a0:2c:46 >>>> authmode OPEN privacy ON deftxkey UNDEF txpowmax 38 protmode CTS >>>> bintval 100 >>>># ifconfig ath0 inet 192.168.107.15 >>>># ping 192.168.107.1 >>>> >>>>I am unable to ping my router. (linksys bewfs42) >>>> >>>>It seems like i'm missing something really simple here...anyone able to >>>>help point me in the right direction? Thanks. >>>> >>>> >>>Maybe deftxkey needs to be set? >>> >>> > > > >>Tried it...I think i've tried almost every combination of weptxkey and >>deftxkey and starting up things in different orders... However, when I >>disabled WEP on my router I can connect to my router and get an IP, but >>no internet. >> >> > >When you ping, do you see "ping: sendto: Host is down" errors or "ping: >sendto: No route to host" errors, or just nothing at all from ping? > >If it's either of the latter two options, then perhaps setting a default >route (route add default 192.168.107.1) is what you need. > >-- >Matt Emmerton > > > >