Esteban, Nachazo e quem quer Wireless. [INACTIVE]

[Marcelo - Brazil]

Estebam, comecei a traduzir e 'adaptar' o que o Mazzei tentou explicar aos brasileiros.
Precisamos "reescrever" de maneira mais "didatica", ou ninguém (exceto os brasileiros...) vai entender.
Esteban, vc pode ir acertando este texto diretamente, os demais que ajudarem, avisam em seus posts e vamos acertando.
Eu penso que: um bom e correto tutorial, já é 90% do caminho andando.

Abaixo está uma tradução automática e eu já corrigi uma parte,
com ela pronta teremos tanto a em inglês como a em castelhano.

Wireless Tutorial

Step 01:

If you use any previous version of BrazilFW 2,26 (Coyote and BrazilFW 2,25) change for new version.
It’s more easy to start with a clean installation.

For a Wireless system it is recommended to use the HD based installation.
The Wireless packages are big and not fit in a 1.44 floppy. (could be used at 1.68 or 1.80 formated floppy disk, but the system used to generate these floppyes not function in Windows NT/2000/XP.

Create the bfw floppyes, do the full instalation, and boot without wireless board instaled.
Do your desired configuration to run BFW.


Step 2:
Goes to WebAdmin - Tools of Diagnosis -Read the Log of the System and pay attention for this line:

PCI: PCI BIOS revision, the value after this must be 2.1 or great (2.2 or 2.3)

Below 2.1 change your mother board, because the mojoirty of the wireless boards (97%) only Works under PCI 2,1 or superior ! (before they ask to me - RTL8180 PCI 2.0 and ISA WIRELESS BOARD is the 3%).

Power off the computer and installs the Wireless board.
Power on and see if everything works.
(Do not install drivers yet.)
BrazilFW looks fine ? Let’s go !

Step 3:
Install the wireless board driver package (only driver not it iwtools.tgz) and remake the tests, if everything run fine, ok install iwtools.tgz,





MY REVISON STOPS HERE.....CONTINUES TOMORROW....;)





if it gave some problem before, we go to try to decide below: - the plate of wireless Removes, when to restart the BrazilFW depending on the model of plate and to driver goes to appear the messages of error in log of the system, if understood the errors tries to decide if it does not send for forun to see if galera decides here! - Normally if vc use driver's with ndiswrapper, advise to always place the plate of Wireless in the first PCI, will have a plate any in the place change one for the other! - the majority of driver's (until ndiswrapper) exactly giving error therefore did not find the plate, loads in the memory modulates it verifies using the WebAdmin - Tools of Diagnosis - Loaded Modules, will be had modulate it there are good signal, mean that I modulate it is functioning the error can be that driver it does not serve for plate (Plates with Rev. x has of these exploits) orders for fórum the specifications of its plate for galera in fórum to give a reply here!


Room Step: I restart the BrazilFW and edit the archive /etc/rc.d/pkgs/mod.wireless to configure essid, channel, way of operation, key wep, etc... these configurations I vary very of a plate for another one, in the end of this article I place some plates that had given certain with me. Who to obtain to make to function makes the gentility to order the archive rc.wireless for my email or the Master Claude. This goes in helping them to automatize the process in the next versions. It informs to the BrazilFW that you intend to use the plate wireless editing the archive /etc/coyote/coyote.conf (Attention, when to use atheros plates wlan0 must be changed by ath0) For who it goes to use the plate wireless in the InterNet uses: IF_INET=wlan0 For who goes to use the plate wireless in the local net uses: IF_LOCAL=wlan0 IF_INET=eth0


Fifth Step: If everything ran well makes back-up normal of the BrazilFW, restarts and tests (please forehead is for verifying if everything ran well is not for aiming the head in the poor person of the micron and....) and goes the parts boats, first, it uses a floppy formatted with boot (linux or Of) it gives boot for this floppy and it has access the partition of the HD (hda1 for linux and C: for the one Of) and it copies the following archives for this floppy: /config/coyote.cfg /iwtools.tgz /modules.tgz /etc.tgz /O to driver of the plate of wireless type xxxxx.tgz Pra that this? Good if vc like migraine (Taste if does not argue) do not need to make, now if it does not like vc really has back-up final of its Wireless system and BrazilFW (without the configurations of firewall, QoS and etc... I am only explaining wireless galera) Second, Way AP and Ad-Hoc, for plates that accept these ways and vc wants to place in functioning, for AP that vc purchase in the store type baratinho (same Baratinho) changing to the way of operation of the plate the BrazilFW goes well to function as AP, now for AP super expensive, still lacks ones coisinhas in the BrazilFW that is in tests at this moment for galera more than, thus that it will have something defined goes to be explained as, Ad-Hoc way, Taking off the RTL8180L (L in the end tá galera) the plates in Ad-Hoc way accepts 2 connected microns, is as to have a Windows 98 net, without master, server and etc..., good to mount a system of private net small this functions well better of the one than way AP and its net is a little more protege, to only understand a thing, some drivers of windows (especially for 98) only accepts AD-Hoc 2 microns, this is problem of driver not of the plate, it complains with the uncle Bill, or uses one to driver of another manufacturer who uses chip the same, functions in the majority of the times!

Sixth Passo: Attention I made one iwtools.tgz that he has all the commands but what is in fórum is another one therefore if its plate to need iwtools.tgz complete, informs here in fórum to see what can add! The specific configurations are of plates that I tested. Common configuration the almost all driver's (Only testing). Attention, when to use atheros plates wlan0 must be changed by ath0. iwconfig wlan0 mode auto # plate to enter it in way of AP search. ifconfig wlan0 192.168.1.1 # IP of the plate of Wireless net. iwconfig wlan0 essid "server" # Name of host of the BrazilFW. iwconfig wlan0 channel 1 # the Canal of 1 11 or 14 for Japanese. iwlist wlan0 scan # List the AP's that driver it searched. iwconfig wlan0 rate 11M auto # Speed of transference (1M, 2m, 5.5M and etc...). # parametro auto and will have ruido the plate if it turns and it adjusts the speed best. It verifies if all orderly one with: iwconfig wlan0 To activate WEP (AVISO-AVISO-AVISO ISSO É UM EXEMPLO). iwconfig wlan0 key 1234567890 iwconfig wlan0 key 1234-1234-5678-5678-1234-1234-99 If it will be to use a WEP more than: iwconfig wlan0 key [ 2 ] 1234-1234-5678-5678-1234-1234-12 If it does not want to use the WEP or it made besteira! iwconfig wlan0 key off To verify the WEP: iwlist wlan0 key iwconfig wlan0 AP XX:XX:XX:XX:XX:XX # Ajusta AP MAC address in managed way to be associated with some essid BSS. Pull of the cat for thus saying it Ad-Hoc to function with some customers iwconfig wlan0 AP XX:XX:XX:XX:XX:XX # Ajusta which MAC address for bssid in ad-hoc mode.

===== Drive HostAP (Chip's Prism, Orinoco, Hermes) ====== iwconfig wlan0 mode to master Only places this if it wants AP. iwconfig wlan0 mode Ad-hoc Alone places this if it wants Ad-hoc. ===== Driver for the Chip's Atheros ======= iwpriv ath0 mode 1 Constraint the operation for 11a. iwpriv ath0 mode 2 Constraint the operation for 11b. iwpriv ath0 mode 3 Constraint the operation for 11g. iwpriv ath0 mode 0 Auto-adjustment 11a/b/g (default). === Driver for Chip RTL8180 and RTL8180L using to ndiswrapper ===== ifconfig wlan0 promisc # Abilita the way promisc in the way managed/ad-hoc. ifconfig wlan0 - promisc # Desabilita the way promisc in the way managed/ad-ho. iwpriv wlan0 activates scan 1 # If it wants to have activated performance NIC, 0 for liabilities. Activating the plate of wireless: iwpriv wlan0 enable To activate WEP iwpriv wlan0 wlan_para encmode=wep, wepmode=wep104, wepdkeyid=0 iwpriv wlan0 wlan_para wepdkey104_1=0123456789abcdef0123456789 === Driver for ChipRTL8180 and RTL8180L using the Driver of the Master Claude ==== No special configuration! ===== Driver for Chip AM1771 AMD Alchemy ======= No special configuration!


Seventh Passo: Optimizing the communication of Wireless: I only go to divulge this later that to be understood the following one: The BrazilFW functions and well, does not have necessity none to modify occult parametros of linux so that the BrazilFW functions, the performance increase is of the 20% order if its system is slow in relation to one another assembly verifies first if it was not some configuration, these parametros that I know if they find in the HOWTO of kernel, iptables and wireless, also the versions in Italian of this HOWTO's has edited parts guesses for who? That it is well clearly this, if its system is slow looks the error does not advance to place what I write if its system is not orderly. Attention, when to use atheros plates wlan0 must be changed by ath0. Iwconfig allows to configure RTS and the levels of spalling. level RTS in driver HostAP for example is of 2,347 that effectively it incapacitates RTS Clearing. In a system that has much occult load or has nodes, it can be configured using parametro rts_threshold of rts. iwconfig wlan0 rts 500 The value "default" of the level of of spalling in driver HostAP for example is of 2,346. In noisy environments, it can be better to lower the spalling level to reduce the amount of data that must be relayed when it loses the packages. It configures parámetro using fragmentation_threshold of iwconfig. It can configure enters 256 up to 2,356, only that in values pairs please. fragmentation_threshold can be shortened as frag. iwconfig wlan0 frag 500 The customers wireless keeps some accountants of transmission attempts. When the packages are relayed "exaggerated times" or wait "time too much" to be relayed, are discarded. The accountants of attempts are kept. Long retry to counter is configured with parámetro retry, is the number of times that if tries to transmit a package wider than the level of spalling RTS. The shorts retry to counter are configured with parámetro retry min, are the number of times that will relay a lesser package that the level of spalling RTS. Some drivers makes that iwconfig also allows to configure the maximum duration of a package with parámetro retry lifetime. To specify a value in milliseconds or microseconds, it adds to a "m" or a "u" to the value.


iwconfig wlan0 retry 4 iwconfig wlan0 retry min 7 iwconfig wlan0 retry lifetime 400m P.S.: If vc to reduce the transmission tax the signal of the plate increase, then it does not advance to place amplifier or "the 11 botina" if vc it is transmitting for example Mbps, it will normally detail link of the InterNet alone has 1Mbps then it makes one forcinha extra and it configures the BrazilFW and its customers for a tax of compatible transmission, the interference of radio waves is thankful!

[Esteban]

Marcelo,
Do you have by any chance the original article in portuguese? Sometimes I find it easier to compare the portuguese version with the english one rather than having just the text in english.

[Claudio]

Não se esforcem muito com esse texto.

Eu só não escrevi um material decente ainda porque isso está prestes a mudar, e mudar muito.

[Marcelo - Brazil]

ok, esperando por uns dias....