[[PageOutline(2-3)]] = Getting MadWifi = There are several ways to get your copy of MadWifi. Stable releases are offered as tarballs which can be downloaded from the several sourceforge.net download mirrors. In order to be on the bleeding edge of the development you should use Subversion to get the latest code from trunk. We also offer tarballs of the latest revisions for those of you that don't want to mess with Subversion. And if you don't want to touch a compiler at all you can get precompiled packages for the distribution you're using. == Downloading stable releases == Stable releases are provided as tarballs via the sourceforge.net [http://sourceforge.net/project/showfiles.php?group_id=82936 download service]. sf.net offers various download mirrors you can choose from. Visit [wiki:Releases] to find out more about recent and past releases. == Downloading via Subversion == Change to a location where you want to keep the sources. Then type: {{{ svn checkout http://svn.madwifi.org/madwifi/trunk madwifi }}} Or if you want to use MadWifi without the proprietary [wiki:About/HAL HAL] module in your kernel use this branch: {{{ svn checkout http://svn.madwifi.org/madwifi/branches/madwifi-old-openhal madwifi }}} However, please note that madwifi-old-openhal is still in an experimental state. Use it at your own risk and only if it's no problem for you to get your hands dirty. If you're behind a proxy, then make sure [wiki:Subversion] [http://subversion.tigris.org/faq.html#proxy knows about it].[[BR]] Refer to link above for the full story, though it boils down to set 2 vars in either the system-wide {{{/etc/subversion/servers}}} or user's {{{~/.subversion/servers}}} config files: {{{ http-proxy-host = proxy-host-name-or-ip http-proxy-port = proxy-port }}} also of interest is the var: {{{ http-proxy-exceptions = comma-separated-list-of-hostnames-or-ip }}} whose purpose should be pretty clear ;)[[BR]] Beware though that '''svn''' makes use of HTTP methods not supported by all http-proxies out there. If yours happens to be one of those, you need to setup some kind of tunneling or TCP-redirector, depending on how much control/access you have on your net. Or, if the repository supports it (that seems not the case for svn.madwifi.org), use HTTPS which usually is proxied transparently. The above commands stores the source in a subdirectory called ''madwifi''. To update to the current version of the source at a later time you just need to change to that subdirectory and type: {{{ svn update }}} Run {{{make clean}}}, then recompile and install the result. For further information on how to work with Subversion refer to the relevant manpages and the excellent [http://svnbook.red-bean.com/ Subversion book]. == Downloading the latest Snapshots == If you can't (or don't want to) handle Subversion, or just don't have a net connection, you could download MadWifi using HTTP (on another machine, if need be). Tarballs for the ''madwifi-ng'' and ''madwifi-old'' code can be found at [http://snapshots.madwifi.org]. However, please note that ''madwifi-old'' is deprecated and unsupported, and you shouldn't use it at all. == Downloading .debs == If you are a [http://www.debian.org Debian] user, then good for you! You can download debs from: * [http://alioth.debian.org/projects/pkg-madwifi/ Alioth pkg-madwifi project releases] are described on '''[wiki:UserDocs/Distro/Debian the Debian UserDocs page]'''. * Or from [http://www.marlow.dk/madwifi Martin List-Petersen] who has full instructions on using ''make-kpkg'' (note that this uses madwifi-old, not madwifi-ng). Precompiled kernel modules for using it on WRAP and soekris: * [http://meshnode.org/downloads/deb-pkgs http://meshnode.org/downloads/deb-pkgs] - This package only works with the meshnode kernel which you can find in the same directory * [http://meshnode.org/wiki http://meshnode.org/wiki] - More information about the package(s) can you find in this wiki == Downloading .rpms == === Red Hat, Red Hat Enterprise Linux, Fedora Core === * madwifi-ng: [http://ATrpms.net/ ATrpms] has [http://ATrpms.net/name/madwifi/ madwifi-ng rpm support for Fedora Core, Red Hat Enterprise Linux and Red Hat Linux]. * Fedora users: [http://rpm.livna.org Livna] has madwifi RPMs for Fedora Core 6, Fedora 7 and onwards. Previous versions of Fedora are not supported anymore by the [http://fedoraproject.org FedoraProject]. You should consider to upgrade to have the lastest security fixes. * Fedora users: pre-built RPMs with experimental support for AR5007 chipsets (based on the patch from #1679) for Fedora 8 can be found [http://tchung.fedorapeople.org/madwifi/ar2425/ here]. * Fedora users: The tarball has a madwifi.spec embedded. If you do rpmbuild --ta you will get your packages. ( In the case you have http://snapshots.madwifi.org/madwifi-ng-current.tar.gz, you need first to rename it in the format madwifi-ng-rxxx-date.tar.gz ; an easy way is to do a tar tvf of the current tar ball and get the real archive filename). For Fedora Core and RHEL see also [wiki:UserDocs/Distro/RedHat]. === openSUSE === Ready-made packages are available in our vendor repository. To add the repository as installation source in YaST, run the '''Installation Source''' module from YaST's '''Software''' menu, and add '''madwifi.org''' as '''HTTP''' source. Afterwards you can use the '''Software Management''' module to install (or update) MadWifi on your system. Repository URLs are: * openSUSE 10.1: http://madwifi.org/suse/10.1 * openSUSE 10.2: http://madwifi.org/suse/10.2 * openSUSE 10.3: http://madwifi.org/suse/10.3 * openSUSE 11.0: http://madwifi.org/suse/11.0 === Other === * [http://dag.wieers.com/packages/kernel-module-madwifi/?M=D Rpms for 2.4 kernels from DAG] * The users of PLD Linux Distribution can build the RPM from spec located in [http://cvs.pld-linux.org/cgi-bin/cvsweb/SPECS/madwifi-ng.spec PLD's CVS], or use prebuilt package from poldek's repository. == Other Download Methods == If you miss instructions for downloading precompiled packages for the distribution you use during installation, please have a look at the [http://madwifi.org/wiki/UserDocs/Distro distribution-specific installation instructions]. If that still doesn't help, please let us know.