Date: Wed, 04 Jan 2006 09:26:59 -0800 From: Sam Leffler <sam@errno.com> To: dandee@volny.cz Cc: freebsd-current@freebsd.org Subject: Re: dhclient ignoring link on wi0 Message-ID: <43BC0563.3050600@errno.com> In-Reply-To: <001401c61124$5c5f4480$6508280a@tocnet28.jspoj.czf>
index | next in thread | previous in thread | raw e-mail
Daniel Dvorak wrote: >>-----Original Message----- >>From: owner-freebsd-current@freebsd.org >>[ <mailto:owner-freebsd-current@freebsd.org> > > mailto:owner-freebsd-current@freebsd.org] On Behalf Of David Gilbert > >>Sent: Wednesday, January 04, 2006 1:03 AM >>To: Alexander Leidinger >>Cc: freebsd-current@freebsd.org; David Gilbert >>Subject: Re: dhclient ignoring link on wi0 >> >> >>I also thought that someone might have comments about a wi0 >>as an access point. This used to work, but all clients (even >>windoze) seem to loose association every 20 to 40 minutes >>(although the timing is random it seems). >> >> >>Dave. > > > Not only this one, to make the picture complete. For example, another > relevant issue is: > > from rc.conf: > > ifconfig_wi1="inet w.x.y.z/m ssid A mediaopt hostap channel 4 up" > > reality ? > > # ifconfig wi1 > wi1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > > media: IEEE 802.11 Wireless Ethernet autoselect <hostap> (DS/2Mbps > <hostap>) > status: associated > > authmode OPEN privacy OFF txpowmax 100 dtimperiod 1 bintval 100 > > It has never reached more than DS/2Mbps in hostap mode. That is a firmware issue. OTOH there are patches floating around that bypass the firmware and select the tx rate in the host and which make operation better. > > ... and other issue is about transmit power limit, no chance to limit tx, > txpowmax does not work at all. Card transmits at full power. This is a firmware issue. Find a driver that supports changing the tx power and you will find a driver that works only for certain cards and certain revs of firmware. Feel free to supply patches for this; you can get them from the linux hostap driver for example. > > I know from my friend there exists some patch for the first issue, but CVS > does not contain it even in 7-CURRENT, let alone 6-STABLE. Becuase the person working on the patch received feedback that it did not work in all cases and has not had time to identify the issue. Samhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43BC0563.3050600>