Date: Thu, 03 Aug 2006 12:07:59 +0100 From: Florent Thoumie <flz@FreeBSD.org> To: Jonathan Herriott <herriojr@gmail.com> Cc: freebsd-net@FreeBSD.org, freebsd-ports@freebsd.org Subject: Re: ipw-firmware port (Intel Pro/Wireless 2100) Message-ID: <1154603279.92929.9.camel@mayday.esat.net> In-Reply-To: <6a56d69c0608021501l52690648y4f9b4a6c0a70999c@mail.gmail.com> References: <6a56d69c0608021501l52690648y4f9b4a6c0a70999c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-3zfYyyor5A/leP8M40Ce Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2006-08-02 at 18:01 -0400, Jonathan Herriott wrote: > Hi All! >=20 > I have been having trouble using the ipw-firmware port. I am able to > get it up and running, and it is even associated to my wireless > network. I use dhclient to get a lease and set everything up, which > works fine (this is after I enter the encryption and stuff). >=20 > The problem is when I try to ping or access any other IP address, even > my router I'm connected to. Just pinging my router yields no results. > I have loaded wlan_wep and provided the correct key (tried retyping > the key several times) to make sure I provided that portion correctly. > I also tried disabling wep in my router to make sure it was not a > problem with the wlan_wep module. >=20 > Here's a dump of ifconfig ipw0 >=20 > ipw0: flags=3D8847<UP,BROADCAST,DEBUG,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > inet6 fe80::204:23ff:fe6b:37ad%ipw0 prefixlen 64 scopeid 0x5 > inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255 > ether 00:04:23:6b:37:ad > media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) > status: associated > ssid JONNET channel 11 bssid 00:09:5b:6a:ad:bc > authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpowmax 100 > bintval 100 >=20 > I tried specifying the debug option, but I do not where I will get the > output (could not find a specified log file). >=20 >=20 > I was wondering what other information I may need to provide to help > in troubleshooting this issue or if anyone knows what is going on. Followup to -net, as it's not a ports issue. I think you can define ipw.debug to something > 0. Check the output of 'sysctl -a | grep ipw | grep debug' to find the right sysctl. --=20 Florent Thoumie flz@FreeBSD.org FreeBSD Committer --=-3zfYyyor5A/leP8M40Ce Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQBE0dkPMxEkbVFH3PQRAi0+AJ90pmRNjwXxAEhWk6oz+TBN0cHONACgjBV5 TAVOUgDxVIR3Ymq6RWQuC0s= =3+2f -----END PGP SIGNATURE----- --=-3zfYyyor5A/leP8M40Ce--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1154603279.92929.9.camel>