FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F8.2.0 2010-11-15T17:48:13Z 2010-11-15T17:48:13Z Maxim Sobolev sobomax@FreeBSD.org 2010-11-15T17:48:13Z urn:sha1:f7662e479fb72e1530331c09b1f1898f9729487f Add new tunable 'net.link.ifqmaxlen' to set default send interface queue length. The default value for this parameter is 50, which is quite low for many of today's uses and the only way to modify this parameter right now is to edit if_var.h file. Also add read-only sysctl with the same name, so that it's possible to retrieve the current value. 2010-09-18T08:23:45Z Bernhard Schmidt bschmidt@FreeBSD.org 2010-09-18T08:23:45Z urn:sha1:7a055551c487b302c2f9dbb9305f3c777b1e611d Fix firmware module dependencies. malo and mwl use the firmware framework to access firmware images. Depending on the firmware modules itself is not required and in this case even wrong because no modules with those names exist. Pointed out by: brucec 2009-12-26T18:23:21Z Rui Paulo rpaulo@FreeBSD.org 2009-12-26T18:23:21Z urn:sha1:91e379a2a88cd30a0e9e8af4a7d4885aaa9a17e6 Don't use BUS_DMA_ALLOCNOW as that causes the attachment to fail on Cambria boards. 2009-07-11T15:02:45Z Rui Paulo rpaulo@FreeBSD.org 2009-07-11T15:02:45Z urn:sha1:59aa14a91db84e940b6732cd1ff069f0268793bf net80211 wireless stack. This work is based on the March 2009 D3.0 draft standard. This standard is expected to become final next year. This includes two main net80211 modules, ieee80211_mesh.c which deals with peer link management, link metric calculation, routing table control and mesh configuration and ieee80211_hwmp.c which deals with the actually routing process on the mesh network. HWMP is the mandatory routing protocol on by the mesh standard, but others, such as RA-OLSR, can be implemented. Authentication and encryption are not implemented. There are several scripts under tools/tools/net80211/scripts that can be used to test different mesh network topologies and they also teach you how to setup a mesh vap (for the impatient: ifconfig wlan0 create wlandev ... wlanmode mesh). A new build option is available: IEEE80211_SUPPORT_MESH and it's enabled by default on GENERIC kernels for i386, amd64, sparc64 and pc98. Drivers that support mesh networks right now are: ath, ral and mwl. More information at: http://wiki.freebsd.org/WifiMesh Please note that this work is experimental. Also, please note that bridging a mesh vap with another network interface is not yet supported. Many thanks to the FreeBSD Foundation for sponsoring this project and to Sam Leffler for his support. Also, I would like to thank Gateworks Corporation for sending me a Cambria board which was used during the development of this project. Reviewed by: sam Approved by: re (kensmith) Obtained from: projects/mesh11s 2009-07-05T17:59:19Z Sam Leffler sam@FreeBSD.org 2009-07-05T17:59:19Z urn:sha1:7634012302c6c84599d24bee2002cd4939816700 o add a new facility for components to register send+recv handlers o ieee80211_send_action and ieee80211_recv_action now use the registered handlers to dispatch operations o rev ieee80211_send_action api to enable passing arbitrary data o rev ieee80211_recv_action api to pass the 802.11 frame header as it may be difficult to locate o update existing IEEE80211_ACTION_CAT_BA and IEEE80211_ACTION_CAT_HT handling o update mwl for api rev Reviewed by: rpaulo Approved by: re (kensmith) 2009-06-29T18:42:54Z Sam Leffler sam@FreeBSD.org 2009-06-29T18:42:54Z urn:sha1:7850fa71f55a16f414bb21163d80a03a5ab34522 o new tx ack queue (not used right now) o proxy-sta related changes (no proxy sta in driver) o explicit dwds ena/dis (needed only with proxy sta) o cleanup BA policy handling o new ampdu aggressive mode support o CFEnd use now controllable Approved by: re (kensmith) 2009-06-07T22:03:07Z Sam Leffler sam@FreeBSD.org 2009-06-07T22:03:07Z urn:sha1:73c1905d3a7bdf4d45c7299a9a0260e73b03534a 2009-06-01T18:07:01Z Sam Leffler sam@FreeBSD.org 2009-06-01T18:07:01Z urn:sha1:cf4c5a533126ca1ddb1f070af73f8f53b9e77fd4