The following technical documentation is compiled and updated by the members of Air-Stream Wireless as reference for anyone interested in community wireless networking.
The following articles are intended only as a guide if you can’t find what your looking for please let us know.
|
802.11b |
802.11g |
802.11a |
802.11n |
|
|---|---|---|---|---|---|
IEEE Ratified |
1999 |
2001 |
1999 |
2008 |
|
Frequency |
2.4GHz |
2.4GHz |
5GHz |
2.4GHz |
5GHz |
Non-overlapping Channels |
3 |
3 |
12 |
3 |
12 |
Baseline Bandwidth Per Channel |
11Mbps |
54Mbps |
54Mbps |
65Mbps |
65Mbps |
Number of Spatial Streams |
1 |
1 |
1 |
2, 3* or 4* |
2, 3* or 4* |
Channel Bonding |
No |
No |
No |
No |
Yes |
Max Bandwidth Per Channel |
11Mbps |
54Mbps |
54Mbps |
130Mbps |
270Mbps |
These are some common connectors and pigtails used in the Wireless world. The pictures should help when choosing pigtails to connect a wireless card to an antenna. There are other connectors as well, so hopefully the page will grow to be a definitive guide.
The U.fl connector comes on most MiniPCI cards such as the senao NL-2511MP(prism 2.5 chipset), Senao NL-3054MP(PrismGT chipset), Intel ProWireless, Cisco, Toshiba etc. ( Also known as AMC)

The Lucent connector comes on cards such as the Orinoco PCMCIA. It has a bad reputation as being easily broken. Connects to a antennas that have an N-Female such as the WaveGuide, Yagi, Cantenna and bigger Omni antennas.
The U.fl connector comes on most MiniPCI cards such as the senao NL-2511MP(prism 2.5 chipset), Senao NL-3054MP(PrismGT chipset), Intel ProWireless, Cisco, Toshiba etc. When setting up a WRAP, this pigtail can go on the MiniPCI and the N Female Bulkhead is installed in the case.
The RP-SMA is commonly used on PCI cards and access points/routers that have a removeable antenna. Brands such as Netgear and D-Link have these. Hills Parabolic Dish antennas come with a short length of coax and a N-Male connector, so this pigtail can go between an AP and Hills.
Commonly found on PCMCIA cards such as D-Link, Orinoco and Lucent based cards
Hills Parabolic Dish antennas, among others, come with a short length of coax and a N-Male connector. Connects to alot of anennas that have an N-Female such as the Yagi, Cantenna and bigger Omni antennas.
The RP-SMA Female is commonly used on PCI cards and access points/routers that have a removeable antenna. Brands such as Netgear and D-Link have these.
The RP-SMA Male is commonly used on Antennas that go onto PCI cards and access points/routers that have a removeable antenna. Brands such as Netgear and D-Link have these.
Normal SMA is not commonly used on wireless gear
The RP SMA Female Straight PCB Jack is commonly used on access points/routers and wireless cards that use a removeable antenna. Brands such as Netgear, Mitsubishi, Edimax/UltraWAP,Minitar, and D-Link have these. It is available in a variety of configurations such as straight, right-angled, long straight and edge mount.
All 802.11 a/b/g wireless devices use a number of time constants, defined by the IEEE specifications, to sense other carriers using the wireless media and avoid collisions (compared to 802.3 which only senses collisions) as well as for retransmission of lost frames. The important constants to consider are Slottime, CTS timeout and ACK timeout. Slottime is more important for collision avoidance when multiple stations are connected, or when one is trying to simulate full duplex communication, while ACK timeouts are more important for point to point communication. Other constants that may restrain the maximum link distance are SIFS (Short Inter Frame Spacing), DIFS (Distributed IFS) and PIFS (Point Coordination IFS.) DIFS is the amount of time a station must sense a clear radio before beginning a new transmission sequence. SIFS is the amount of time a station must wait before sending or beginning to receive a RTS, CTS or ACK frame. PIFS is the DIFS for the access point in a special access method known as Point Coordination Function. The times are defined such that the RTS, CTS and ACK frames are given a higher priority (ie once a packet transmission sequence has begun, the station holds onto the channel until it is finished)
In 802.11b, the constants are mandated by IEEE as follows:
In 802.11g:
In 802.11a:
Note: DIFS/SIFS/PIFS are used for physical layer carrier sensing while the MAC layer performs the collision detection using CTS and ACK timeouts. Default CTS and ACK timeouts vary between manufacturers.
Normal Transmission flow without RTS/CTS handshaking
Sender: Wait DIFS, Send Data, Wait SIFS, Listen for and receive ACK (until maximum ACK timeout), Repeat
Receiver: Listen for and receive Data,Wait SIFS, Send ACK, Wait DIFS
Distance Limitations in 802.11b
Optimum ACK Timeout, Slottime and DIFS all depend on Air Propagation Time in some way. The IEEE standard defines Air Propagation Time as 1 µs ±(10% SIFS.) Radio waves propagate at approximately 300 meters per µs.
ACK Timeout: Clearly if the ACK timeout is shorter than the time it takes for the end of the last data packet (+ SIFS) to propagate to the receiver + the start of the ACK for that packet to propagate back to the sender, then the sending MAC will assume that the packet has been lost and will unnecessarily retransmit the data packet. The retransmitted packet will end up colliding with the ACK that is on its way back, inducing the back-off part of the protocol thus reducing throughput. If, conversely, the ACK timeout is set too long, the transmitter waits unncesessarily long before retransmitting any lost frames and thus reduces the throughput of the link (more important as the bit error of the environment increases.) Similar conclusions can be drawn about the CTS timeout, however RTS/CTS is only for reducing collisions with hidden nodes and can be turned off in the majority of cases. Most implementations assume the IEEE recommended one-way Air Propagation Time of 1 µs, thus tune the ACK Timeout of their devices to 300 meters. This is the maximum distance that high throughput can be achieved between a local network of IEEE 802.11b compliant devices out of the box. The links will still work over longer distances, but throughput will drop as the distance increases.
Example: With radio waves propagating at an approximate speed of 300 meters per microsecond, a 3000 m link would require an Air Propagation Time of 10 µs (9 µs more than usual.) The ACK Timeout must account for a round trip propagation, therefore for a 3000 m link to achieve maximum throughput, another 18 µs must be added to a standard ACK Timeout. This maximum throughput will be slightly less than can be achieved at close range, but will be much more than if the ACK Timeout is not changed.
Slottime: A station is only allowed to transmit at the beginning of the slottime, so this time should not end before the signal reaches the destination. This gives a maximum distance of 20 µs x 300 m / µs = 6000 meters. Assuming that the ACK timeouts have been increased accordingly, this is the maximum distance between any station in a point-to-multipoint environment (assuming no hidden stations) without incurring heavy exponential backoff.
DIFS: A station must wait DIFS before initiating a new transfer, in other words, for 802.11b, the stations have 50 µs to sense the channel to avoid collision with a frame sent from the furthest node. This means the maximum distance that the furthest node can be is 300 m / µs x 50 µs = 15000 meters. Assuming that the ACK timeouts have been increased accordingly, this is the maximum point-to-point distance before throughput drops dramatically without the slottime (DIFS is based on slottime) being changed.
Long distance links in 802.11g/a
The principles are the same, but the numbers are different. The default timings are much more strict, so for any reasonable distance link the ACK timeout and Slottime will probably need to be changed, even for point-to-point links. Many Ethernet bridge/gateway devices provide little or no way to change this, however certain miniPCI adapters such as the CM9, Senao and SuperRange cards have driver support in BSD and Linux to alter these settings. The possible throughput that can be achieved when properly tweaked, though not full theoretical rate, is much higher than 802.11b can achieve over the same distance and is worth the effort.
Changing ACK timeout and Slottime
For every further 300 meter increase in distance above 300 meters add 1 µs to the Slottime of your device, and 2 µs to the ACK timeout and CTS timeout.
Every station connected on the same channel should have the same time constants.
Use the furthest distance between any two nodes as the distance in your calculations.
For specific examples for popular operating systems and drivers please see http://www.air-stream.org/Change_ACK
Definitions
ACK Timeout = Air Propagation Time (max) + SIFS + Time to transmit 14 byte ACK frame [14 * 8 / bitrate in Mbps] + Air Propagation Time (max)
Slottime = MAC and PHY delays + Air Propagation Time (max)
DIFS = SIFS + 2 * Slottime
Summary
Moderately long distance 802.11b links may work well "out of the box" due to the lax timings, and even more lenient MAC implementations by some manufacturers. With the right wireless card and some tweaking, 802.11b can maintain almost maximum theoretical throughput over very long distances and thus is the distance king.
However 802.11a is still the throughput king, but specialised cards that allow tweaking are certainly required for any distance links. Tweaking 802.11g requires a card that can be locked into 11g mode so that the slottime doesn't keep reverting every time a 11b client tries to connect. 802.11a wins out over 802.11g because there are more non-overlapping channels in the 5.8 GHz spectrum, meaning most 11a links will more likely be able to maintain their high throughput.
- shadey
AMTA has posted two new fact sheets on its website to explain the safety of Wi-Fi and how it works and the range of radio communications in the community.
See their website for more details.

Antenna polarization is a very important consideration when choosing and installing an antenna.
Most systems use either vertical, horizontal or circular polarization. Knowing the difference between polarizations and how to maximize their benefit is very important to users.
Polarization
An antenna is a transducer that converts radio frequency electric current to electromagnetic waves that are then radiated into space. The electric field plane determines the polarization or orientation of the radio wave. In general, most antennas radiate either linear or circular polarization.
A linear polarized antenna radiates wholly in one plane containing the direction of propagation. Where a circular polarized antenna, the plane of polarization rotates in a circle making one complete revolution during one period of the wave. If the rotation is clockwise looking in the direction of propagation, the sense is called right-hand-circular (RHC). If the rotation is counter clockwise, the sense is called left-hand-circular (LHC).
An antenna is said to be vertically polarized (linear) when its electric field is perpendicular to the Earth's surface. An example of a vertical antenna is a broadcast tower for AM radio or the "whip" antenna on an automobile. Horizontally polarized (linear) antennas have their electric field parallel to the Earth's surface. Television transmissions use horizontal polarization.

Circular polarized wave radiates energy in both the horizontal and vertical planes and all planes in between. The difference, if any, between the maximum and the minimum peaks as the antenna is rotated through all angles, is called the axial ratio or elliptically and is usually specified in decibels (dB).
If the axial ratio is near 0 dB, the antenna is said to be circular polarized, when using a Helix Antenna. If the axial ratio is greater than 1-2 dB, the polarization is often referred to as elliptical, when using a crossed Yagi.
Important Considerations
Polarization is an important design consideration, as each antenna in a system should be properly aligned for maximum signal strength between stations. When choosing an antenna, it is an important consideration as to whether the polarization is linear or elliptical. If the polarization is linear, is it vertical or horizontal? If circular, is it RHC or LHC?
This is becomes a greater concern in Wireless Lan devices as line-of-sight (LOS) paths are required due to the low power levels involved, consequently the polarization of the antennas at both ends of the path must use the same polarization.
In a linearly polarized system, a misalignment of polarization of 45 degrees will degrade the signal up to 3 dB and if misaligned and 90 degrees the attenuation can be more than 20 dB.
Likewise, in a circular polarized system, both antennas must have the same sense. If not, an additional loss of 20 dB or more will be incurred. Also note that linearly polarized antennas will work with circularly polarized antennas and vice versa. However, there will be up to a 3 dB loss in signal strength. In weak signal situations, this loss of signal will mean a great deal.
Cross polarization is another consideration. It happens when unwanted radiation is present from a polarization, which is different from the polarization in which the antenna was intended to radiate. For example, a vertical antenna may radiate some horizontal polarization and vice versa. However, this is seldom a problem unless there is noise or strong signals are nearby.
Typical Applications
Vertical polarization is most commonly used when it is desired to radiate a radio signal in all directions over a short to medium range.
Horizontal polarization is used over longer distances to reduce interference by vertically polarized equipment radiating other radio noise, which is often predominantly vertically polarized.
Nevertheless both horizontal and vertical polarization may be deployed over long distance if a reflector is deployed to focus the energy being emitted.
So consequently the decision is using the polarization, which offers the best rejection of local unwanted signal.
Circular polarization is most often used in satellite communications. This is particularly desired since the polarization of a linear polarized radio wave may be rotated as the signal passes through any anomalies (such as Faraday rotation) in the ionosphere.
Furthermore, due to the position of the Earth with respect to the satellite, geometric differences may vary especially if the satellite appears to move with respect to the fixed Earth bound station. Circular polarization will keep the signal constant regardless of these anomalies.
These Antennas make very good point-to-point long run connections due to a combination of linear noise rejection and high gain. The two most common a crossed yagi or helix
When setting up an exclusive communications link, it may be wise to first test the link with vertical and then horizontal polarization to see which yields the best performance (if any).
If there are any reflections in the area, especially from structures or towers, one polarization may outperform the other. Further, if there are other RF signals in an area, using a polarization in the opposite predominant high level signals will give some isolation as discussed earlier.
On another note, when radio waves strike a smooth reflective surface, they may incur a 180 degree phase shift, a phenomenon known as specula or mirror image reflection. The reflected signal may then destructively or constructively affect the direct LOS signal.
Circular polarization has been used to an advantage in these situations since the reflected wave would have a different sense than the direct wave and block the fading from these reflections.
Diversity Antennas
Even if the polarizations are matched, other factors may affect the strength of the signal. The most common are long and short-term fading. Long term fading results from changes in the weather (such as barometric pressure or precipitation). Short term fading is often referred to as "multipath" fading since it results from reflected signals interfering with the LOS signal.
Some of these fading phenomenon can be decreased by the use of diversity reception. This type of system usually employs dual antennas with some kind of "voting" system to choose the busiest signal. This is commonly used in many 802.11 wireless network equipment.
However in theory for the best results when using external antennas they should be at least 20 wavelengths apart, so that the signals are no longer correlated, particularlly in medium and long-distance situations.
Some sources define a kilobit to mean 1,024 (that is, 2^10) bits. Although the bit is a unit of the binary number system, bits in data communications are discrete signal pulses and have historically been counted using the decimal number system. For example, 28.8 kilobits per second (Kbps) is 28,800 bits per second. Because of computer architecture and memory address boundaries, bytes are always some multiple or exponent of two.
Off the back of the meeting last night where we were talking about the power output of cards and
antenna gains. I'd thought I'd post how I remember the whacky world of dB gains.
Rule of Thumb: For power gain, every decade of dB adds a zero to the "10".
eg.
0dB = 1
10dB = 10
20dB = 100
30dB = 1000
40dB = 10000
etc.
Rule of Thumb #2: Every doubling of power is +3dB
eg.
100 = 20dB
200 = 23dB
400 = 26dB
etc.
This stems from a formula used to calculate gain in terms of dB,
Av(dB) = 10 log( Av )
Where Av(dB) is the gain in terms of dB, and Av is the raw gain which is determined by
dividing the output power by the input power,
Av=Po/Pi
Also as a side reminder
dBi - Gain of an antenna with respect to a unity-gain isotropic antenna.
dBm - Gain of an amplifier (power output of a transmitter) with respect to 1mW.
Edit: Those wanting to know the dBm of their card, just put the power figure in the formula I mentioned
above (ie. for a 350mW card, 10*log(350)= 25.4dBm)
Effective Isotropic Radiated Power (EIRP) is the output power when a signal is concentrated into a smaller area by the Antenna.
An isotropic radiator radiates power equally in all directions, however a perfect isotropic radiator is only theoretical as even the simplest antennas will concentrate the signal in certain direction(s). E.g. a 1/2 wave dipole has a gain of 2.15 dBi.

The EIRP is calculated using this formula:
EIRP = Effective Isotropic Radiated Power
Pout = transmitter power output (dBm)
Ct = signal loss in cable (dB)
Gt = gain of the antenna (dBi) Pout - Ct + Gt = EIRP
When installing a wireless system with external antenna, your EIRP calculation should not exceed the class license limit. Other wise you must adjust either the transmitter power output, the length of cable and/or the choice of antenna.
Here is scenario...
It’s early in the morning on a cool, clear day. The top of a proposed Air-Stream site is just visible through your binoculars and everything seems good
You go out and purchase and test the necessary wireless equipment, mounting an antenna on the rooftop, then fire it up, and… then nothing but problems.
The link does not seem to cooperate at all. It fades in and out, and the radio signal levels are low when there is any link at all. You check all the connections, twist and turn the antenna, and use your best language to get it to work… no improvement.
On first analysis it appears that some component in the wireless unit is malfunctioning, but the test worked properly and the units performed as expected.
Standing on the roof, you snap open your mobile and call another Air-Stream member. They listen to your story, and then they ask a question:
"Any chance that another signal is interfering with your signal?"
I checked, and can pick out a few other SSIDs but nothing on the same channel "Good", you reply
"Now, do you have clear Radio Line of Sight?" "Of course", is your response “I have some binoculars, and can see the other site from where I’m standing??”
They pauses and then ask "That’s good to know, but what about proper Fresnel Zone clearance?"
Fresnel Zone clearance????
At that moment, you begin to suspect that there are other factors other than a visual sight involved with establishing proper, usable Radio Line of Sight.
So what is going on here?
For two radios, or wireless units, to connect to each other, the radio signal must reach both units with adequate strength, and in a usable form.
For a wireless network spanning many kilometres these factors collectively are known as "Radio Line of Sight", and become very important indeed.
Visual and Radio line of sight: are they different?
Light and radio are both forms of electromagnetic radiation but operating at very different frequencies. Just because you can establish visual line of sight, or see a distant building with binoculars on a clear day, does not mean you can establish a wireless link between them.
What is the Fresnel Effect?
In the early 19th century French physicist, Augustin Fresnel (pronounced "Freh-Nel") made an important observation about the behaviour of light. Fresnel noted that a ray of light passing near a solid object is subject to diffraction, or bending.
This diffraction caused the intensity of the original light beam to increase or decrease depending on how near the object was to the beam. This characteristic of electromagnetic radiation is known as the Fresnel Effect.
Light and radio waves are subject to the same laws of physics, including the Fresnel effect. If an object like a mountain ridge or building is close to the radio signal path, it can affect the quality and strength of the signal.
Radio waves diffracted by such objects can affect the strength of the received signal. This happens even though the obstacle does not directly obscure the direct visual path.
This area, known as the "Fresnel Zone", and must be kept clear of all obstructions. That means the earth curvature, depth of the Fresnel Zone, and height of objects in the radio path must be added together to get the antenna mounting height. It’s usually adequate to use less than the full depth of the Fresnel Zone to calculate clearance.
How much Fresnel Zone clearance do I need?
60% of the Fresnel Zone (F) is the generally accepted portion which must be kept clear. This assumes that there are no buildings or other obstructions in the way. If such obstructions exist, their height must be added to the total antenna mounting height.

To see the distant end with binoculars, we need only elevate our eye high enough to clear the Earth’s curvature. Remember, you saw the top of the distant site. The problem was that you only confirmed visual line of sight, not radio line of sight.
When it came time for the radio signal to pass from site A to site B, the lack of adequate Fresnel Zone clearance caused signal diffraction, and degradation of the radio signal.
So what do you do?
802.11a and b wireless LAN equipment has proven to be a very useful and a low cost way to setup networks over distance and is commonly used by many individuals, community groups and small businesses.
However for most setting up a wireless network for the first time, one major hurdle that will almost always comes up is the problem of establishing good LOS between sites. LOS or Line of sight is a very important consideration, as without it, it would be impossible to establish a reliable network connection over a few hundred metres regardless of the antenna, equipment or mast deployed.
This is because the high frequency and low power of most standard wireless devices 802.11(a/b/g) is unable to pass through a solid object without a significant reduction and dissipation of the signal.
Where as good LOS it is not uncommon to see links established over 10kms with sustained data rates exceeding 18Mbps in 802.11a Unfortunately, in the real world good LOS between different locations is a rare coincidence for individuals working on their own and it is for this reason many community groups like Air-Stream Wireless have been formed.
By establishing a group, members can help each other by establishing a shared network where specific sites with good LOS become the relay points for others without good LOS consequently overcoming many topographical barriers that an individual would find difficult to overcome on their own.


MIMO an acronym for multiple input, multiple output, and is a system which is deployed along with OFDM (Orthogonal frequency-division multiplexing) in the new 802.11n standard. This new standard offers many advantages over conventional standards such as 802.11g Wireless LAN equipment of which we have become familiar.
MIMO a system which exploits multiple transmitters and antennas to increase the bit rate in a wireless LAN link with no additional power or bandwidth consumption using a method called Spatial Multiplexing (SM). The benefits of MIMO over conventional 802.11g equipment is pronounced.
Benefits include:
Here is a simplified summary of how it all works

The input data stream is split into independent sub-streams which together occupy less bandwidth than is required to transmit the original stream on a single channel. These sub-streams are applied separately to individual transmitters and antennas on the same frequency, where the receivers at the other end recover each sub-stream and merg them back together.
Due to the presence of various scattering objects eg: buildings, walls, cars, trees, etc. signals experience a multi-path propagation and when it is captured by the receiver antenna these signals will arrive with random phase and amplitude. In conventional 802.11g equipment only the strongest signal is used and the other mulit-path signals are rejected as noise.

However in a MIMO device this is turned to an advantage as these deferent phases and amplitudes will have a specific spatial signature. The receivers can be viewed as a bank of superposed spatial weighting filters where every filter aims at extract one of the multiplexed sub-streams by spatially nulling the remaining ones. This not only allows the added benefit of array gain due to multiple antennas, but also diversity techniques which reduce signal fading.

The disadvantages of the MIMO system is mostly the need for multiple Antennas; the cost of the equipment compared to existing equipment available and limited open source driver support.
However as poeple become more aware of the posibilities the standard it is certain to become popular and with this the price should come down significantly. This I'm sure also will see more manufacturers making code available for the Open Source Community, which will enhancing their competitive advantage over other brands and boarder support by wireless network communities and enthusiasts.

Users of wireless LAN equipment over distance are increasingly being effected by rising levels of interference due to the ubiquitous nature of wireless usage in the home and office, further fueled by the low costs, easy setup and the potential benefits that the technology offers.
Also access to the radio bands used by this equipment is relatively unconstrained, called the 'public park' concept the planning objective of regulative authorities is for all users to be able to access a small portion of the total resource and to share that resource in a way that requires minimal regulatory intervention provided the power is kept well down.
The use of a 'public park' approach is administratively efficient and gives great freedom to users, but the price of this freedom is increased risk of interference. What is often miss-understood by many users of wireless LAN equipment is that this framework equally applies to all users regardless if you are a telecommunications carrier or an individual.
Clearly the very thing that has created an environment where communities can establish wide area networks like Air-Stream is the same environment which has created the interference problem.
Consequently, minimising the impact of interference through public awareness, and providing an open platform for users to share information to maximise the effectiveness of their equipment and minimising interference is important to all.
One of the ways to minimise interference is through advertising your SSID so that other users of the band can take steps to avoid interference and conflicts.
For this purpose Air-Stream advertise the SSID on all their AP’s including backhaul links between sites. This not only makes it easier for users to connect, but also provides other wireless users with all the information needed to minimise interference.
This information can be acquired easily via any wireless device when completing a site survey providing information about the user, channels used, general location and the direction in which antennas maybe pointed.
For example an Air-Stream AP will use the SSID: Air-Stream-Location Name and a Back Haul link may have an SSID: Air-Stream-LoacationFrom-LocationTo
The correct use of equipment is another way wireless users can minimise interference, this can be done by ensuring your setup complies to the ACMA regulations.
See: ACMA Requirements
Nevertheless there are some other basic steps that can be deployed to minimize interference and maximise connectivity between sites. This includes:
Newcomers to wireless technology often find terms such as dB, dBm etc confusing. This document explains these terms.
We use certain types of antennas because they have “gain” – they increase signal strength. They don’t magically create extra energy though, they direct radio signals into a smaller beam in the same way a spot light does. The higher the gain the narrower the beam and the more concentrated power – in certain directions only though!
We often talk about this gain in terms of ratios, because the gain is independent of the power level – an antenna that doubles the signal strength of a one watt transmitter will also double the signal strength of a ten watt transmitter.
You can also have losses – a poor cable might lose one half (or more) of the signal power. This is also independent of the absolute power level – one watt becomes half a watt, ten watts becomes five, etc.
Ratios are messy to use though when using several of them together – imagine “I have a seventeen times antenna with a one third power loss in my cable and one tenth of my power lost in the connectors”. It’s hard to figure out just how much overall gain or loss that represents.
To make it easier, we work with deci-Bells (dB), which are defined as ten times the logarithm of the ratio. The beauty of this is that to multiply gains (or losses) we just add the dB numbers. (Gain will be a positive dB number, while loss will be negative, so subtracted) So now “I have a 15dB antenna, with 3dB of cable loss and 2dB of connector loss – a total of 10dB gain”. Much easier!
Here are some examples of dB ratios:
+3dB is doubling the power, -3dB is only a half.
+6dB is Quadrupling power, -6dB is only a quarter.
+10dB is 10 times the power, -10dB is only a tenth.
+20dB is 100 times the power, -20dB is only one percent.
(You can now see why the “ten times” factor is used – it avoids fractions in the log values for commonly encountered ratios)
All of the above deals with RATIOS, which are independent of power. So it’s meaningless to say “How much power will a 23dB antenna give me” – the antenna gets as much power as the transmitter feeds it, but focuses it to give the effect of a 23db stronger (200 times more powerful) transmitter – in the focus direction only. In fact, the effective width of the strengthened signal is specified as “degrees of beamwidth” and is the number of degrees between the points at which the gain falls off by 3dB.
We often talk about the “Effective Radiated Power” and that is the equivalent power level produced by the transmitter/antenna combination (in the highest gain direction). So a 1 watt transmitter with a 20dB (100 times) antenna is producing a ERP of 100 watts.
High gain antennas have narrow beamwidth, and so can be harder to align. It should be noted that gain can be achieved in either the horizontal or vertical plane (or both). Most antennas have quite different patterns of radiation in the vertical and horizontal planes, with different antennas chosen for the different pattern according to their function. Antennae also have a “polarisation” – either horizontal or vertical, which defines the way in which the radio waves are transmitted, but the main connection between signal strength and polarisation is that having different polarisations between transmitter and receiver gives another 20dB or more of loss!
Finally, another term encountered is dBm, and this one IS related to power. Zero dBm is defined as one milliwatt (one thousandth of a watt) and so transmitter powers are often expressed in terms of this reference. This is NOT the same as antenna gain – this is real power. Receiver sensitivity is also expressed in terms of how many dBm or what power level is required to receive a signal. So if I have a 20dBm transmitter, a 15dB gain antenna at each end, 110dB of path loss (signal attenuation in the atmosphere) and a –90dBm receiver, can I get a signal through?
Add them up: 20 plus 15 minus 110 plus 15 gives -60dBm, so I will theoretically have a signal of 30dB more than the minimum I need, so it should be a good path. Of course, this is only theoretical, trees and other obstructions can reduce the signal dramatically, but this is a good starting point before a real-world trial.
Steve Fraser
802.11b applies to wireless LANs and provides 11 Mbps transmission (with a
fallback to 5.5, 2 and 1 Mbps depending on Range and Signal Strength) in the
2.4 GHz band. 802.11b uses only DSSS (Acronym for direct-sequence spread spectrum.
DSSS is one of two types of spread spectrum radio.) 802.11b was a 1999 IEEE
ratification to the original 802.11 standard.
802.11g is a proposed standard, describing a wireless networking method for
a WLAN that operates in the 2.4 GHz radio band. By using OFDM (Orthogonal Frequency
Division Multiplexing) technology, 802.11g-based WLANs will be able to achieve
a maximum speed of 54 Mbps. 802.11g-compliant equipment, such as wireless Access
Points, will be able to provide simultaneous WLAN connectivity for both 802.11g
and 802.11b equipment.

The 802.11a standard uses the same core protocol as the original standard, operates in 5 GHz band, and uses a 52-subcarrier OFDM (Orthogonal Frequency Division Multiplexing) with a maximum raw data rate of 54 Mbit/s, which yields realistic net achievable throughput in the mid-20 Mbit/s. The data rate is reduced to 48, 36, 34, 18, 12, 9 then 6 Mbit/s if required.
Although there are 12 official channels allocated on 802.11a there are actually 18 channels in total, 11 channels can be considered indoor due power limits (Aircraft radar issues) and another 7 which are usable for Community(Outdoor)use.
Note *In Turbo Mode (108Mb) there is only 3 indoor and 2 outdoor channels
| Channel |
Frequency Mhz |
EIRP |
| 36 |
5180 |
200mw |
| 40 |
5200 |
200mw |
| *42 |
5210 |
200mw |
| 44 |
5220 |
200mw |
| 48 |
5240 |
200mw |
| *50 |
5250 |
200mw |
| 52 |
5260 |
200mw |
| 56 |
5280 |
200mw |
| *58 |
5290 |
200mw |
| 60 |
5300 |
200mw |
| 64 |
5320 |
200mw |
| 149 |
5745 |
1000mw |
| *152 |
5760 |
1000mw |
| 153 |
5765 |
1000mw |
| 157 |
5785 |
4000mw |
| *160 |
5800 |
4000mw |
| 161 |
5805 |
4000mw |
| 165 |
5825 |
4000mw |
Channel Separation Layout

Networks provide a means of connecting two or more computers in order to share resources, such as files and printers, and for communication through websites, email, chat and video.
The underlying systems used by computers to communicate, operate regardless of the medium in which they physically travel. Cables, telephone lines, radio signals such as used by Air-Stream and even infrared light beams, can be used to link computers in a network.
The Border Gateway Protocol (BGP) is an inter-autonomous system routing protocol. An autonomous system is a network or group of networks under a common administration and with common routing policies. BGP is used to exchange routing information for the Air-Stream WAN and is the protocol used between our Access Points Routers (APR).
BGP is a very robust and scalable routing protocol, as evidenced by the fact that BGP is the main routing protocol employed on the Internet today. To achieve scalability, BGP uses many route parameters, called attributes, to define routing policies and maintain a stable routing environment.
In addition to the BGP attributes, classless inter-domain routing (CIDR) is used to reduce the size of the routing tables. For example, assume that an APR such as Julia Farr owns the IP address block 10.123.x.x, this block would consist of 256 address blocks 10.123.0.x through to 10.123.255.x. If the APR assigns each block to a member without CIDR it would be necessary for the APR to advertise 256 address blocks to its peers. But CIDR can subnet the address space and advertise only one block 10.123.x.x which is much smaller as it is rendered obsolete by CIDR, allowing a significant reduction in the BGP routing tables.
BGP Attributes
Routes learned via BGP have associated properties that are used to determine the best route to a destination when multiple paths exist to a particular destination eg where an APR has multiple backbones. These properties are referred to as BGP attributes and include:
Weight Attribute
Weight is an attribute that is local to a router. The weight attribute is not advertised to neighbouring routers. If the router learns about more than one route to the same destination, the route with the highest weight will be preferred and will be installed in the IP routing table.
Local Preference Attribute
The local preference attribute is used to prefer an exit point from the local autonomous system (AS). Unlike the weight attribute, the local preference attribute is propagated throughout the local AS. If there are multiple exit points from the AS, the local preference attribute is used to select the exit point for a specific route.
Multi-Exit Discriminator Attribute
The multi-exit discriminator (MED) is used as a suggestion to an external AS regarding the preferred route. The term suggestion is used because the external AS that is receiving the MEDs may be using other BGP attributes for route selection.
Origin Attribute
The origin attribute indicates how BGP learned about a particular route. The origin attribute can have one of three possible values:
AS path Attribute
When a route advertisement passes through an autonomous system, the AS number is added to an ordered list of AS numbers that the route advertisement has traversed.
Next-Hop Attribute
The EBGP next-hop attribute is the IP address that is used to reach the advertising router. For EBGP peers, the next-hop address is the IP address of the connection between the peers. For IBGP, the EBGP next-hop address is carried into the local AS, as illustrated in
Therefore, it is important to have an IGP running in the AS to propagate next-hop routing information.
Community Attribute
The community attribute provides a way of grouping destinations, called communities, to which routing decisions (such as acceptance, preference, and redistribution) can be applied. Route maps are used to set the community attribute. Predefined community attributes are:
BGP could possibly receive multiple advertisements for the same route from multiple sources. BGP selects only one path as the best path. When the path is selected, BGP puts the selected path in the IP routing table and propagates the path to its neighbours. BGP uses the following criteria, in the order presented, to select a path for a destination:
Sample Config Files (for Quagga/Zebra)
Basic settings for a quagga BGP setup:
zebra.conf: ------------------------- hostname blah # your hostname password blah # your password enable password blah interface rl0 # your interfaces interface wi0 interface wi1 line vty ------------------------- bgpd.conf: ------------------------- hostname blah password blah enable password blah router bgp 655xx # your AS network 10.x.x.x/27 # network 10.y.y.y/30 # your networks network 10.z.z.z/30 # neighbor 10.y.y.y remote-as 655yy # peer1 neighbor 10.z.z.z remote-as 655zz # peer2 line vty -------------------------
Good resources for BGP routing are:
So you have made the effort of putting an antenna onto your roof, made the connection to your local AP and got either a coax run to a wireless card in your computer or a ethernet run back from the waterproofed AP on your roof. How do you make sure that all the other machines in your house can use this network too?
There is no single answer to this question that is correct, it all depends on your level of knowledge or how much effort you want to go to.
The internet gateway: typically a hardware ADSL router
One of the most simple ways of getting the rest of your computers on the network is by using network address translation. YOu are probably already using it to get a number of computers on your home LAN connected to the internet concurrently. How this works is you allow one machine on the gateway to the internet to translate from a real world IP to a private address range typically 192.168.x.y. At first I used the private range 192.168.0.0/24 which mean that all the IPs 192.168.0.0 to 192.168.0.255 could be used by my home network and connected to the internet thought my real bigpond address 144.136.177.192, using windows this can be achieve using internet connection sharing.
The wireless gateway: typically a machine with two network interfaces, one to the LAN one to the air-stream mesh.
Using the same philosphy the machine connected to the air-stream AP has its routed wireless mesh address 10.121.0.2 but it also has an internal LAN address in my example 192.168.0.3. It uses the same principal that the internet gateway router usings by sharing this one address among the other machines in my private range.
For this to work we need to do a couple of things. If my internet gateway is 192.168.0.1 then the default route for all my LAN machines will be 192.168.0.1 eg IP 192.168.0.4 netmask 255.255.255.0 gateway 192.168.0.1 DNS 61.9.224.15 (or whatever your ISP suggests). What we can do is put a static route in the machine at 192.168.0.1 to send all traffic bound for the Air-Stream wireless lan (10.96.0.0/11, 10.96.0.0 netmask 255.224.0.0) to be diverted to 192.168.0.3 which has a connection to teh rest fo the air-stream wan.
In the same way that NAT is applied to the internet connection it is also applied to the wireless LAN connection.
The reason NAT provides you with a certain amount of security as you are hiding on an address range that other cannot access but only connection that are requested by you are allowed through.
In order to keep track of all the different ways that traffic can flow around the air-stream mesh a type of advanced routing known as dynamic routing. Where all the parameters regarding the topology of the network are given to a network daemon and it works out the best route to take based on these parameters. As the network grows it becomes more reliant on the dynamic routing to find alternative routes, this would need to be updated by hand on a number of routers if it were to be done by hand.
Border Gateway Protocol (BGP)
The type of routing that is used by Air-Stream is called border gateway protocol, it allows for filtering of routes and instant updates that OSPF and RIP do not allow.
/27 Routed Network using BGP
This allows us to make use of the 32 IPs all network users are entitled to!
If you are technically inclined the idea of using NAT may seems like a waste, as one of the advantages of being part of the WAN is that we have lots of IPs for everybody, unlike the internet which has largely run out of IP real estate.
If you want to advertise your subnet yourself you will need to run the network suite zebra or quagga (preffed) on a Unix, Linux or BSD operating system. Or if you have access to a windows 2003 server it can also run these protocols as can Cisco IOS based routers.
Alternatively you may be able to make arrangements with your AP administrator that they can keep the routing records as part of thier AP and you will only need to prepare a couple of static routes on your end.
Sorry if this is a bit of a glossary more details about dynamic routing can be found on www.quagga.net
Firewalling
Once your machines are routed onto the wireless network you may want to think about firewalling to keep your computers in and to keep unwanted packets out. This should all be done on the same machine that is doing the routing.
Sam Hodge
It is preferable that people be as self sufficent as possible, because the network administrators are under enough load as it is.
If all of this routing stuff is of interest to you I suggest you offer to lend the network administrators a hand or write a brief how-to on the Air-Stream site.
The aim of the LDAP service is to centralize user information for access by different network services e.g. Domain Controllers, Email Severs, Web Servers and other complient services.
It works like a centralised directory service allowing both servers and users to lookup and search user details. LDAP Servers require very low system resources and can be synchronized with other LDAP Servers to offer very high levels of reliability.
LDAP stands for Lightweight Directory Access Protocol. A language based on the X.500 directory standard that allows clients and servers to communicate. The LDAP server allows access to the hierarchical structure of an active directory.
When a router receives a packet of information (as it does thousands of times per second) it inspects the IP Address of that packet, and based on that, can make decisions on which physical path to send it through.
This process is known as routing the packet. Special software protocols have been created to support the routing of network traffic between subnetworks. These protocols operate with ‘smart’ algorithms that can adapt the flow of network traffic when problems occur. Protocols such as Border Gateway Protocol (BGP) and are widely used across the Internet today.
The algorithms employed by these protocols provide great network stability ensuring that if one network connection is lost, the router can quickly adapt to send data through an alternate network path. Consequently, the greater the number of network connections that are available, the greater the reliability and bandwidth for its users.
Computers on a network communicate with each other using a special numbered addressing system. This is known as Internet Protocol (or IP). Each computer has a unique IP Address, which is four sets of numbers from 0-255, separated by a decimal point. This gives a total possible address space from 0.0.0.0 to 255.255.255.255. For example: 203.152.23.202 is an Internet IP Address.
IP addresses can be grouped into smaller logical segments of the entire address space, which can then be assigned to computers in a LAN. Breaking up IP Address space into smaller sub-networks is known as Subnetting.
This allows for logical control of data between LANs, and maps well onto the physical network design outlined.
A group has beem formed by Air-Stream members to work with interested code developers and every day people to look into practical ways to use OpenWRT able wireless devices and OLSR to build a very low cost grass roots community wireless networks.
There is no need to be a Air-Stream Member as anyone can participate, to join trials of the mesh network, all you need is a OpenWRT able wireless device , volenteer and participate.
Hi!
This will be the eventual home of the more formal documentation of all things meshy.
For now the project is under heavy development over at mesh.air-stream.org
Please check there, and if you wish to assist your input is welcomed.
Once the content has been discussed further it will be written up and added to this section of the website.
Cheers,
Simon
To use commercially available hardware along with open source software to create a reliable and redundant Neighbourhood wireless network using mesh routing technologies.
These neighbourhood meshes may be interconnected using routing or VPN over a connection such as the Air-Stream core network or a third party network such as the Internet.
By connecting members directly to other people in their local area, we create a much more community based network. We then have an opportunity to encourage people in the same community to interact and work together, whether it be for gaming, organising local events or sharing stories on the local history. These are all possible on the Internet but are often lost amongst the massive amount of data - in a local network the content becomes more personal.
• Mass producable (easily sourced components)
• Low price
• Compact and professionally presented unit package
• Minimal end user configuration
• Well presented documentation for the end user
• Quality documentation for the technical side
• Network design allowing for large scalability (subnet allocations and network backbones)
• Reliable end user security (so that home LANs are not at risk by joining the network)
• Easily expand the network - a new node could be added in a matter of minutes.
• Reduce the likelihood of a tree or building blocking a user’s network access (as multiple paths for them to access the network).
• Roaming within a subnet would become possible.
• Adding a new node to the mesh will improve redundancy rather than simply dropping shared bandwidth.
• Encourages interactivity between local communities - much simpler than on the Internet due to its scale. This could develop into a working relationship with local councils - both in potential grants and in additional site locations.
• Increases the size of the network - there is a law stating a network is as useful as the square of its users.
• Having a larger membership base can only help in negotiating new sites for the core Air-Stream network.
• Helps to move Air-Stream into the more mainstream community - community wireless becomes accessible to those without extensive networking experience.
• Allows the end user network to grow more independently of Air-Stream allowing it to
focus on developing the core network.
• The ability to access the Air-Stream network, and thus also your home network from a drastically increased number of locations in the city.
• Greater node density allows for faster connections (such as 802.11g) between nodes, since each node is much closer than in the current client/ap setup.
A number of uses the network could be put to. This list will grow much larger with time.
Some of these are also possible on the current Air-Stream network, but would benefit from having many more members interacting on the network.
• Much larger user base leads to many more people available for gaming. Tournaments and championship ladders could be setup.
• Roaming around a subnet using a laptop or PDA.
• VoIP network becoming much larger and the ability to use wireless VoIP handsets.
• Local content able to be streamed across the network - for example a fair or other community event.
• A network of webcams located around the city.
• Local historical societies and schools working with interactive mapping software to create content based on their local area.
(Base on an entry from wikipedia entry or similar, and include diagrams).
OLSR running routing between devices
• Vpn to allow access to LAN side of device (off by default)
• Iptables to filter access to LAN (very strong defaults)
• Httpd to provide basic stats and user info
• Minimal uniform splash page – eg basic contact info for the node and what you can find on this network segment (list of services this user offers on their lan)
• A full httpd would be running elsewhere on this user’s network
• Linked into the OLSR plugin to provide OLSR network stats?
• Frottle or similar program to address the hidden node problem – research more extensively (eg melbwireless and openwrt forums)
• SSHd to allow for secure remote access to the device.
Laptops and other portable devices would run the OLSR client, or hopefully get a DHCP assigned from the AP.
Captive portalling on the AP Would be sweet also if possible.
OLSR is to be used as the routing protocol.
• Linux, Windows, Mac OS X and BSD (?) clients available.
• Open Source and well documented thus fits well in with other software (eg quagga and *nix) already used on the network.
• Documented support for OpenWRT and has been deployed on this platform internationally (eg www.freifunk.net).
• Would also be able to be installed on the WRAP boards.
• Able to be installed on a Linux/BSD platform so we are not limited in our choice of platform for the Zone Server.
A solution to the issue of getting the two dynamic routing protocols (OLSR and BGP/OSPF) to talk to each other is shown in the below diagram.
A better solution would be to integrate the kernel routing so that Quagga dynamically receives the information about the mesh, rather than there simply being a static route set on the Zone Server.
This will be preferable when there are multiple routes into and out of the mesh (which is optimal for redundancy).
The WRAP boards would be well suited for business nodes and more technical orientated members.
• They are able to have two wireless cards onboard (as two Mini-PCI slots) making them suitable for the “supernode” type of setup.
• These would be preferable for business nodes as they are a more flexible platform than the WRT54G, in terms of storage space and OS support.
The Linksys WRT54G devices are ideally suited for the home nodes.
• They are low cost and easily available in shops, so sourcing the unit will not be an issue.
• They have a well developed Linux based OS (OpenWRT) which has support for a large number of packages.
• They have a proven track record in a number of networks internationally, both community based and commercial. Wildcat Wireless in the US currently have 30 of these devices running successfully in a mesh setup.
The standard antenna to be used in the network would be a 4 slot waveguide. In use to date it has been shown potential in being able to meet our requirements.
Power over Ethernet takes advantage of the fact that only two of the four pairs in a Cat5 network cable are used for carrying network data. The other two pairs are left unused and can therefore be used to carry power to the device. This is possible since we are only dealing with low power levels, and saves us having to run an additional cable to the device for power.
This makes the total install simpler and neater.
Additional hardware needed to mount the antenna and weatherproof box, and also for other items such as the cable runs.
Need to decide whether to go for a professional solution (and if so which one) or whether to investigate using PVC downpipe sealed for the casing of the device.
Also need to consider whether to mount the unit as is inside the case or whether to remove the PCB board from the manufacturer’s casing.
Of course temperature and humidity considerations need to also be taken into account.+
Weather Station
• Weather devices
• May be possible to interface some basic weather measurement data to the serial interface of either the WRT54G board or the WRAP units.
• This would then allow us to plot city wide maps based on data collected from our own weather units.
Webcams
It would also be nice if we were able to interface the WRAP boards with USB webcams, providing another feature on the network.
The HttpInfo plugin for OLSR will be set up so that each node’s routing information is available to the rest of the network.
The DotDraw plugin will be setup on the Zone Server to provide a live visual overview of the network.
• The network we will be building, with fast access and wide coverage, will be appealing to a number of non members. Authentication will likely be required to keep the available bandwidth for our members.
It is certainly not aiming to restrict the availability of the network to the community, but helping to ensure that those who wish the participate on the network are able to do so without having their access limited by people taking advantage of their generosity.
• If current solutions do not meet our needs then a possible solution is as follows.
Step by step scenario:
1. User Joe walks up to a mesh member’s house with his laptop in hand. (Is the laptop running OLSR or just wishing for a NAT connection?)
2. Joe’s laptop is handed out an address (eg 10.0.0.100) via the mesh DHCP server.
3. Joe logs onto the zone server (which is a high performance machine capable of running apache, mysql etc) and provides his login details. This is possible since port 80 (and any other relevant port - eg for ssl) is automatically permitted by each mesh router.
4. If login accepted, the zone server then adds his ip to the relevant database. It also adds it to a web page visible to the whole network. Eg 10.0.0.1/accept.txt would then contain 10.0.0.100. This way other routers can check the authenticated user list.
5. Each router will periodically (eg every 5 minutes) check this list and update their local allow cache accordingly (eg just replace should be sufficient). If the router receives a packet from an ip address not in its list, it will then check the zone server’s allow list. When the accept table is updated then the iptables firewall is also updated by the relevant shell script.
6. When Joe has finished his session he can go back to the mesh web page and click a logout button which would remove his entry from the accept.txt file.
• What do we want to do in the even a Zone Server is down - will this break the mesh
15
network’s operation or will it be so infrequent that it is not a major concern?
• Some devices which may not be able to log onto a web page (such as a VoIP handset) may need to be auto added. A solution to this would be to auto forward all VoIP ports (subject to abuse). This also solves the legal issue of providing access to the emergency numbers.
Set up a number of WRT54G routers running OLSR around the event.
The OLSR client could then be provided on a number of cds, allowing laptop users to install the client and test out the network.
Gives a good chance to test scalability and actually using the OLSR application, and encourage people there to interact with the network, rather than just looking at it.
Set up one of the x86 machines so that it can do live visualisation - so we can have a screen running all day that shows the network topology live.
Need to test out the x86 installs, configure the visualisation software and set up the WRT54G devices with the clients. Also need to source a few more WRT devices from members to use for the day.
These will be carried out to establish the real world performance of antenna combinations.
A combination of antennas may also be used such as:
End A (WRT)
End B (Laptop)
4 Slot waveguide
Internal PCMCIA Card
8 Slot waveguide
4 Slot Waveguide
8 dBi Omni
8 Slot Waveguide
8 dBi Omni
1
5dBi Dish
Cantenna
It is likely that a trial mesh network will be carried out in the suburbs of Daw Park/Melrose Park and a number of surrounding suburbs.
• Nodes can be plotted on a 2D metropolitan map to provide a view of the physical layout of the network.
• A GPS unit could be used with a laptop to provide a rough idea of real world network coverage.
These will be need to be answered in future revisions of this document.
• Can the software run in the proposed hardware?
• How easy will it be to deploy and configure the software – see German group who offer a firmware compile based on web page form entries for settings.
• How scalable is it to our needs – would 20-30 nodes in a suburb be fine? – see overseas uses
• What IP ranges are we to use?
• Routing issues?
• Can we add backbones from one side of the mesh to the other to help distribute traffic (eg on a different channel and acting solely as a backbone) – will OLSR scale to this?
• What antennas to use – waveguides are cheap and easy to mass produce and horizontal polarization is preferable but is a 4 slot going to perform ok as 8 slots are quite large.
• How badly will trees kill our signal or conversely will there be too much noise from other devices to make it unusable?
• We would ideally want 250m – 500m coverage for a decent network initially to get the critical mass going.
• Will 54mbps work over some links (eg 802.11g going to run over <1km links alright?)
• Can client connect not running OLSR (routing issues – use NAT in this case – check more in mailing lists)
• Vertical spread of the 4 slot waveguide – eg can someone with one on their roof use their laptop in their backyard to access their home lan?
• How good is OLSR – eg will it meet our needs – check with German etc trials
• Possible to have multiple paths out of the network? How would this go with the routing mixes… eg one supernode connected to Pasadena and another connected to Melrose Park, both could offer a default route out of the network…. Could be an issue that we will just have to bear with later. Preferable to have multiple routes out but cannot expect optimal path selection talking across OLSR and BGP/OSPF. Could be resolved in later
17 1km OLSR releases or could this come from the kernel routing tables on the gateway? Either way an additional hop through the core Air-Stream network is unlikely to cause any hassles and would be better than 8 hops through the wireless mesh, not to mention redundancy if one gateway were to be unavailable.
• How can we recognize local businesses which contribute by funding/hosting a node?
o aim for ads on the zone server page
o this would then mean the zone server would be the portal site for the nodes, eg this is their network home page rather than the main AS page. The AS page news could be fed into this site by RSS or whatever.
• Network updates and information over RSS?
• How will DHCP flow to a home user on the LAN side of the WRT? (check up on mailing list regarding all nodes needing to either run the OLSR client or they will not get routing info and thus must run through NAT) - eg run NAT as per normal home users with a shared DSL modem, and for more advanced users wishing to run a server can simply run the OLSR client which adds them directly into the Neighbourhood mesh subnet. This solves the problem of having to allocate subnets for every home lan and then deal with routing - simplifies each site's configuration
• How to then allow the user to select to use NAT (eg PDA, Voip phone) or OLSR (eg laptop wishing for roaming)?
• What happens when the zone DHCP server goes down - do we want a high redundancy network or is this a tolerable issue in the time it takes to fix the problem? Maybe allocate each of the static mesh nodes (eg those with waveguides on roofs) an ip via the website when they join up so they wont go down with the DHCP server.
• Can each home LAN have a seperate subnet or will that break the OLSR routing?
• How to handle authentication? (answered later)
Our implementation of the mesh will be similar to the reference mesh model discussed above.
However given the geographical size and low population density of Adelaide, implementing a city wide wireless mesh would be very demanding on network resources - the routing tables would be immense and sending a packet from one side of the city to the other could involve over 100 hops!
Therefore this project will aim for a larger number of smaller meshes, consisting of rougly one to three suburbs in size. Some applications may extend this further, such as offering a single mesh to allow for seamless roaming down Belair Road (which would cover 5+ suburbs).
Smaller meshes mean that each mesh is kept to a managable level, whilst still offering the advantages of using mesh technologies.
Each of these smaller meshes would then use a “Zone Server” to interface with the core Air-Stream network. This is the gateway from the mesh to the rest of the network.
The core of the local neighbourhood mesh is the Zone Server. This is the machine that would currently be the local access point, with backbones to remote APs located elsewhere in the network. This machine will handle authentication and provide a link to remote networks. It will also host services such as a local irc, IM and http server, which would be interlinked to other similar servers elsewhere on the network. By localizing these services we provide redundancy so that if a backbone were to fail, the local mesh could still function autonomously. This is currently not the case in a number of wireless networks, where if a backbone were to go down then the local users have no provided services to use.
Is it possible to have multiple zone servers (eg can we have multiple paths out of the mesh?) This would be optimal for redundancy in a network otherwise we have a single point of failure which may isolate the mesh.
• Hosts interlinked IRC and Jabber servers
• At reliable site – preferably business or experienced member
• Uses a more high powered card and waveguide combination mounted high etc to cover as much as possible of the local area. This ensures access to backbone is faster and less network demanding.
• Try to concentrate content locally rather than traffic traversing backbones needlessly.
• Approach community friendly local businesses to see if they would be interested in hosting a zone server or a supernode.
Currently a local wireless network consists of an access point with an omnidirectional antenna to which nearby nodes connect to using directional antennas. This situation is fine for users with line of sight to the access point but means that those who are unfortunate enough to have a tree or building in the way are unable to get any access to the network.
This can be seen in the below example.
The mesh network acts by connecting the nodes to each other. This means that total bandwidth may be reduced, especially when packets are crossing from one side of the network to the other. The compromise is that nodes that previously were unable to connect are now able to be a part of the network, and every new node added expands the network’s coverage, rather than simply reducing the total available bandwidth (as would happen in a spoke network). Also packets sent between two adjacent or nearby nodes can go direct without tying up all the network’s bandwidth.
The Node client is the basic setup to be deployed to the “typical” home or business user wishing to connect into the mesh. It consists of a Linksys WRT unit running OLSR on OpenWRT as described later on. It is connected to a waveguide which is used to interconnect with other nearby units. A Power over Ethernet (see later on for description) module could be created to complete the package.
A “supernode” is simply a Node client with a backbone connected. This backbone is used to help distribute traffic over the network. It would be most effective when used to connect from one side to the other. This way traffic traversing the whole network would have a single hop route to use, rather than having to pass through numerous routers. This will help to free up the network traffic.
This type of setup would be ideal for the more technical members (such as the majority of the current membership base) and on business setups.
A variation on the supernode idea would be to use two 180 degree waveguides with two radios rather than a 360 degree waveguide and single radio. This would effectively double the output signal and allow the two antennas to be mounted independently (eg on the sides of a chimney rather than on top) which may be beneficial in a number of situations.
The second device would not need to run OLSR as the WRT unit could simply add another interface (VLAN) to its OLSR routing config. This opens the way for a high powered unit such as the Senao AP for distance links or the Minitar 802.11g (providing they can do Ad-Hoc) units to be used for shorter links.
The Zone server hardware is simply a router box that is more powerful than a Wrt unit. This is to allow for more complex services to be run. It is connected to a waveguide in the same manner as a standard Client Node. A backbone connects the Zone Server to the core Air-Stream network. Additional configuration is therefore needed to ensure routing between the two interfaces is seamless. (See section on Routing for further information).
In some situations the Zone Server may be unable to connect directly to another Zone Server using wireless, and thus a VPN tunnel using the Internet or another network service may be an option. This would work in a similar fashion to a direct backbone. Details on configuring the VPN tunnel can be found at the Darwin based website: www.the-mesh.org
www.olsr.org
http://www.linux.org/docs/ldp/howto/OLSR-IPv6-HOWTO/index.html
www.openwrt.org
www.freifunk.net
www.the-mesh.org
Read up on http://quagga.net
Get your AS number for your AP and neighbours from the committee
ipkg install quagga ipkg install quagga-zebra ipkg install quagga-bgpd
vi /etc/quagga/zebra.conf
vi /etc/quagga/bgpd.conf
touch /var/bgpd.pid chmod 777 /var/bgpd.pid touch /var/zebra.pid chmod 777 /var/zebra.pid
/etc/init.d/S35quagga
Using OpenWRT from the the downloads.openwrt.org means you are bound to a slow release and testing cycle: White Russian RC6 is the most current release at time of writing
This means that you are stuck with an older kernel 2.4.30 and older builds of the software that is based on that kernel
Also the configuration and management system is a generation behind
The alternative is to use Kamikaze, this is downloaded from a developers site
Anybody with some basic programming skills and some linux experience will have no trouble building the source directly from the Subversion Repository
Take this guide as a glossary, refer to https://dev.openwrt.org/ as your bible
You will need a linux operating system that is installed rather than a live cd as you will need to write to disk and have permissions to build software
I reccomend Gentoo Linux, but Ubuntu and Fedora Core are good forgiving Linux Operating Systems for a new user
In order to download the source from the repository you will need svn
Use your package management system to install svn
http://subversion.tigris.org/project_packages.html
I would be surprised if your linux install didnt have this but avoid a barebones linux like slackware which may lack some of the more standard command line tools
Although the OpenWrt creates a tool chain, this tool chain needs to be compiled itself, before it can be compiled for the target platform
This may mean choosing a "Development" suite of tools for your linux operating system
But I would imagine this would be installed already if you are used to compling your own software
Make sure you have about 3 gigabytes of free disk space
So if you are putting this on a spare system dig out a 20Gb drive
Im not sure of the exact amount, but this will download a lot of data, this requires a broadband connection, without a excess cost scheme
The total amount of data is less than a gigabyte but the disk usage is a lot higher due to decompression
Also the download isnt over once the svn download is done, there will be further wget downloads
Now you have your svn client installed, open a shell, navigate to a location on the disks with 3GB of free space and paste the following command
svn co https://svn.openwrt.org/openwrt/trunk/
Now in the same folder issue the command below
make menuconfig
Intially you can choose the hardware platform you are building for ie broadcom xxxxx for kernel 2.4.32 or broadcom xxxx for kernel 2.6.17
This will allow you to choose what will be put into the firmware you want to make
Anything that is chosen as a [M] will be installed via ipkg, or will be a kernel module
Anything that is chosen as a [*] will be complied into the kernel or will be in the firmware itself
Anything that is chosen as [ ] will not be complied
This is the time to choose that Atheros based kernel for madwifi that you always wanted to run 802.11a under OpenWRT
watch for debug messages as they will help you solve dependancy issues
Once you have locked in all your choices, you simply have to build the firmware ready to install
Unforetunately you are developing for a system that isnt x86 like the system you are compiling on for this you need a special complier called a toolchain
The developers are OpenWRT have taken care of this and it is part of the make file to compile the tool chain for you
make
Initally there will be a massive download and compile cycle to build all the complier tool chains for the various ulibc firmware for the different CPU types you have chosen
Just hang in there and wait, it might be worth doing this on your fastest system if you are in a hurry
Wait
Once the tool chain is built, it can go ahead and compile all the kernel, kernel modules, and software (busybox etc) you need for your openwrt device
Wait
Some packages are chosen by default and they will be compiled and bundled into the firmware or packed into thier own .ipkg files ready to be installed
as outline on the https://dev.openwrt.org page:
Note: Kamikaze only contains the essential set of packages, extra packages can be found in the 'Kamikaze packages' directory above. To use these packages simply symlink them into Kamikaze's package directory.
So if you want quagga, Kismet, olsr etc, you will need to symlink the directories and thier dependancies and hope like hell all the .ipkg files will fit into the flash
you also need to point to a web server where you will host the .ipkg files this will be in the /etc/ipkg.conf on the new install
Wait
find the
bin
folder and install it onto your openwrt device, and give yourself a leet pat on the back
Celebrate
Groups of computers can be connected in many different configurations.
A simple Local Area Network (LAN) consists of a few computers, which are directly connected to each other.
This allows for high-speed communication between the participating machines, but offers little flexibility for adding more clients. Networks like this are generally confined to a relatively small area, such as a home, business or office.
As more clients are added to the LAN, we require more efficient control of network traffic. This is achieved through the deployment of devices such as Switches and Routers.
A network Switch (S) operates like a central hub through which several computers can communicate at high speed. Computers can send out network broadcasts to inform all other computers of their presence, and high speed peer-to-peer communication is maintained.
Routers can be used to interconnect several LANs together, forming a Wide Area Network (WAN). A Router (R) is used at each connection point between the LANs to control and monitor the passage of data.
The use of Routers allows confinement of network broadcasts to the Local Network only, instead of traversing the entire network, and reducing overall efficiency.
The flow control and management of data as it traverses a physical network is known as Routing. Perhaps the best example of this network structure is the Internet, built upon these same principles; it is a worldwide collection of interconnected.
There are two network configurations possible for a client host or network when using an external wireless device. The most simple is a bridged configuration where the hosts on the members network are bridged directly to the wireless network and take IPs from the subnet of remote access point. The other type is a routed configuration in which the members network is given a seperate subnet that is routed onto the network. This page deals with devices capable of bridging (but not necessarily routing.)
Unlike internal wireless devices such as PCI, Mini-PCI, PCMCIA and USB adapters, an important feature required when using the alternative wireless Ethernet device is the ability to bridge or clone the Mac address of the device it is connected to allow seemless packet forwarding between the wireless network and the members network or computer.
The aim being to connect the Mac addresses of the router and the members without wireless Ethernet device(s) Mac address used in the network.

However the confussion lies when members purchase an AP which works in both AP mode and client/bridge mode such as the Classic Minitar "the ideal" but remember that this is only the ideal if you intend that at a later stage to use it in other modes.
In most cases an AP that works in both modes are capable of connecting using only one IP address. However unless the AP, when operating in client mode can bridge correctly or can clone the members Mac address, it will not forward packets correctly and disallow the use of other subnets.
Some examples of bridges and APs that could be used as a Wireless Client Ethernet Bridge:
Most 802.11g devices will operate in 802.11b automatically but should be set to 802.11b only in the firmware to improve performance.
Note: Air-Stream is not a supplier of equipment and prices listed are only listed as a guide only. Please visit member discounts for some of our preferred suppliers.
Some definitions:
Access Point Mode
Access Point mode is used to connect to one or more wireless clients. Wireless clients can only communicate to APs in Access Point mode.
Access Point Client / Wireless Client Mode
AP Client or Wireless Client mode allows the Access Point to effectively become a wireless client to another AP. In essence the AP has now become a wireless adapter card. You would use this mode to allow the device to communicate with an existing AP. Wireless cards will not communicate with access points in AP Client / Wireless Client mode.
Point-to-Point / Wireless Bridge
Point-to-Point / Wireless Bridge mode allows the Access Point to communicate with another Access Point capable of point-to-point bridging. However, be aware that most manufacturers use proprietary settings when enabling bridging mode in the Access Point. A typical scenario for this selection is connecting two routers at Mac level through a wireless connection (ie mac3 and mac2 in the diagram above)
Point-to-Multipoint / Multi-point Bridge
Point-to-Multi-point / Multi-point Bridge mode is the same as Point-to-point / Wireless Bridge mode, however this mode allows you to use more than two Access Points.
Repeater Mode
As a Wireless Repeater, the Access Point extends the range of the wireless network by repeating the wireless signal of the remote AP (Access Point). The Ethernet MAC address of the remote AP is required for the Access Point to act as a wireless range extender. The repeater appears to the remote AP as just another client, so this mode does not require any special proprietary bridging protocols.
Air-Stream uses private addressing from the 10/8 range utilising 10.96.0.0/11, this is designed to allow interconnection into wireless networks around Australia should the day ever come.
These are:
General rule of thumb is that an Access Point will be assigned 1x/27 for the Nodes hanging off it, 1x/27 for the Local LAN at the access point if applicable and each node will be assigned a single address from the Access Points /27 pool to which they then can route their very own /27 to if they wish.
In some circumstances an AP may require additional IP’s in which case another /27 is made available or a single /26 can be provisioned, it is unlikely and not very smart to run more than 30 nodes off a single Radio so the above would apply only to AP’s with multiple radios offering node access.
The majority of the Air-Stream backbones are run on /30’s
The Addressing scheme has been designed to allow scalability while also allowing good use of VLSM(Variable Length Subnet Masking) in the future to summarize route tables, each area is designated an inner and outer segment, inner being within 20km of the CBD and outer being further than 20km.
Glossary:This is how IPs are allocated, based on Adelaide CBD being the centre:
| Section | Access Point Nodes | Back Bone | Member Subnets |
| North(In) | 10.121.128.0/18 | 10.125.128.0/18 | 10.106.0.0/16 |
| North(Out) | 10.121.192.0/18 | 10.125.192.0/18 | 10.107.0.0/16 |
| North-East(In) | 10.122.0.0/18 | 10.126.0.0/18 | 10.108.0.0/16 |
| North-East(Out) | 10.122.64.0/18 | 10.126.64.0/18 | 10.109.0.0/16 |
| East(In) | 10.122.128.0/18 | 10.126.128.0/18 | 10.110.0.0/16 |
| East(Out) | 10.122.192.0/18 | 10.126.192.0/18 | 10.111.0.0/16 |
| South-East(In) | 10.123.0.0/18 | 10.127.0.0/18 | 10.112.0.0/16 |
| South-East(Out) | 10.123.64.0/18 | 10.127.64.0/18 | 10.113.0.0/16 |
| South(In) | 10.123.128.0/18 | 10.127.128.0/18 | 10.114.0.0/16 |
| South(Out) | 10.123.192.0/18 | 10.127.192.0/18 | 10.115.0.0/16 |
| South-West(In) | 10.120.0.0/18 | 10.124.0.0/18 | 10.100.0.0/16 |
| South-West(Out) | 10.120.64.0/18 | 10.124.64.0/18 | 10.101.0.0/16 |
| West(In) | 10.120.128.0/18 | 10.124.128.0/18 | 10.102.0.0/16 |
| West(Out) | 10.120.192.0/18 | 10.124.192.0/18 | 10.103.0.0/16 |
| North-West(In) | 10.121.0.0/18 | 10.125.0.0/18 | 10.104.0.0/16 |
| North-West(Out) | 10.121.64.0/18 | 10.125.64.0/18 | 10.105.0.0/16 |
Air-Stream primarily uses BGP for routing around the domain, some AP owners choose to run another protocol such as OSPF/RIP locally then redistribute into the BGP network, this is fine.
There are filters run on the Air-Stream operated routers to control routing updates and what can and can’t be routed, it’s generally fairly open.
Each AP is assigned its own Private AS (Autonomous System) and AP owners have full control of their own AS in regards to what goes in and out. Initally we started off with OSPF but ran into multicast and topology issues, BGP allowed us to work around this while providing added control over the network so it was a win win situation.
As previously mentioned we like to summarise addresses where possible at the routers and have a good design in place to allow for huge growth. We are able to provide BGP templates for people to use as configs, it really isn’t that hard and configuration isn’t overly advanced for the nodes, about the most interesting thing is that they run in a route reflector client mode due to the topology and iBGP.
QoS
We have QoS(Quality of Service) in place on the Air-Stream routers giving precedence to traffic seen to be important by us(the committee) and the members, we are always open to new suggestions of what should be given more precedence, it’s not the easiest thing to implement when you are going between cisco,linux and bsd routers around the network but it seems to work quite well.
There are a many permutations of wireless equipment deployed by Air-Stream members when setting up their wireless networks, each have their pro’s and con’s the following articles explore some of this equipment.
Generally there are five parts to consider for a fixed wireless installation. In most Air-Stream installations these are considered seperately so that the best individual parts can be customised for the situation, however there are also all-in-one solutions available which incorporate all five parts. These five parts are:
A computer board that controlles one or more wireless radios. This is usually a dedicated single board computer such as a Mikrotik Routerboard. The computer board is loaded with software that drives the wireless hardware as well as providing any networking and routing services required.
A module that is controlled by the host which provides IEEE 802.11 a/b/g/n MAC layer to the board through an interconnect such as MiniPCI and the 'wireless' radiofrequency physical layer to an antenna through an antenna port such as an MMCX connector.
To connect the antenna to the wireless radio invariably requires a length of coaxial cable. Most antennas have N type or RP-SMA plugs while the radio modules have MMCX connectors (see Common Wifi Connectors). This connection is usually achieved by having a small length (10-20cm) of flexible cable called a pigtail to bring the antenna port to a bulkhead then a longer length (1-5 meters) of low loss coaxial cable connecting the antenna to the bulkhead.
The antenna selection depends on the purpose of the installation. Broadly there are two types of antennas used, directional and omni-directional. Directional antennas are used for 'client' connections (ie to connect into an existing access point to gain network acces). Omni-directional antennas are used for access points where clients connect in (ie to provide an access point for 'clients' to gain network access.)
Weatherproof enclosures, power supplies, Ethernet cables, masting, u-bolts, cable ties, self-amalgamating tape and other hardware required to mount and power the equipment.
Often referred to as Client Premesis Equipment (CPE) there are a number of vendors who provide integrated solutions for connecting to existing wide area wireless networks such as the Air-Stream wireless network. This equipment integrates the job of host, wireless radio, antenna and accessories into one product. The main advantage of this is the cost saving and simplicity associated with buying a single product. The main disadvantage is the lack of options in customisation, software and upgradeability.

http://www.meraki.net/mini.html
Meraki Mini
Meraki Mini Hardware Specifications
* 180MHz MIPS CPU (Atheros AR2315 SoC)
* 8MB Flash, 32MB SDRAM
* 60mW 802.11b/g radio
* External RP-SMA antenna connector, internal chip diversity antenna
* 10/100 Mbit/s auto-crossover Ethernet port
* Headers for 3.3v serial port, GPIO pins
* 5.6-18V DC tolerance, for use in developing countries or with batteries
* Power-over-Ethernet support (non-802.3af)
The Meraki Minis include one 2dBi antenna and a 7.5V DC power supply. The Meraki Mesh firmware is also configured to let users login over ssh and experiment with their own software. Custom USB-serial adapters designed for the Mini are available though the Summer Beta program.
The Meraki port of Linux 2.6 for the Mini is available at www.meraki.net/linux. It includes a new Ethernet driver and watchdog timer support for the AR2315.
OpenWRT firmware available: Download
A computer board that controlles one or more wireless radios.

This wireless device is a consumer wireless gateway
These items are End of Line as far as I know
www.dealsdirect.com.au had them running out for as little as $49.95 + ph
If you can get your hands on one spend the money, its a lot of fun and and stable device
There was also a bulk buy so there are a number out there in the hands of members
Under the hood
This is identical to an ASUS WL500G unit, in fact it is made by ASUS and rebadged to Diamond Data.
there is an entire forum dedicated to hacking this unit
wl500g.info
This unit is able to run various types of firmware that were started with the Linksys WRT54G and hence the names:
Be sure to get the firmware for broadcom (bcrm) mips when downloading the firmware, as there are a number of choices
When in doubt read the instructions or ask advice from someone else who has done it.
There isn't much to lose, as the unit can be put back to recovery mode and you can put the old firmware on
All you will lose is your configuration time.
Be sure not to forget the last IP you leave your device on by default it is 192.168.1.1 so that is a good place to start looking
The reason we run a custom firmware as it allows the unit to have altered/improved functionality
Don't expect the hacking process to be easy
there are a number of hurdles:
There are lots of resources about Linux out there
Given the number of interfaces there are a great number of affordable modifcations:
The screws are under the little rubber feet
Pull the rubber feet off with a finger nail
You waranttee is now void
As you are running a Linux Operating System Space and CPU willing there is nothing you cannot do




Air-Stream Recommended Routerboard comparison: (RouterBOARD 433 is Air-Streams current choice for AP deployments.)
Routerboards come with a fairly comprehensive commercial operating system called RouterOS (see below.)
Software
RouterOS comes mainly level 4 license. Level 3 supports only client and bridging mode, while level 4 supports access point mode. RB411A, RB411AH, RB433 and RB600 come with level 4, and RB433AH comes with level 5. License levels can be easily upgraded. The RouterOS package is like a super beefed up version of the "default web interface" you will find on any access point, and is designed for outdoors with gems like automatic ACK timeout setting. It can be accessed via web, telnet, ssh or by a GUI application called Winbox. Winbox provides the most features including fequency usage dynamic graphs, traffic monitoring, antenna alignment helper, hotspot gateway, bandwidth management, routing (BGP, OSPF, RIP), packet sniffing, wireless snooping, ping flooding and more. A screenshot of Winbox is shown below.
Weatherproofing
Routerboard 133 and 133C, loaded with miniPCI modules, fit snuggly inside a 171mm x 121mm x 55mm polycarbonate or diecast aluminium enclosure using a 6-12 mm cable gland for the Ethernet/PoE cable and N-F or RPSMA-F bulkheads for the antennas.

TWO Routerboard 433, loaded with miniPCI modules, fit snuggly inside a 222mm x 146mm x 55mm sealed diecast aluminum enclosure using a 6-12 mm cable gland for the Ethernet/PoE cable and N-F bulkheads for the antennas.


Purchasing
Routerboards and accessories (power supplies, PoE, enclosures) can be purchase from Wifi Extreme
The PC Engines WRAP board is a Single Board Computer (SBC) designed specifically for cost-effective development of wireless routers and other network devices. The Wrap.2E board, shown below, has the following features
Speed
233 MHz Geode SC1100 CPU
Memory
64 MB or 128 MB RAM
Storage
Compact Flash card or Microdrive
Power
7-18V DC external power supply or passive Power over Ethernet (not 802.3af compliant). Uses about 3 to 5W at 12V DC (excluding miniPCI cards)
Connectivity
1 ethernet port, 2 miniPCI slots, 1 serial port (console)
Size
100W x 166L (mm)
Weight
128g
Software Supported
GNU/Linux - OpenWrt, DD-Wrt, EmbCop, GNAP, Metrix Pyramid, Voyage Linux, GNAP and other distributions
FreeBSD - m0n0wall, pfSense
NetBSD
OpenBSD
Commercial - StarOS and others


These WRAPs are popular amongst Air-Stream members and are ideal for a customised "up the mast" application, that is with the wireless router sitting next to the antennas at the top of the mast. The two miniPCI slots allow two different wireless cards to be controlled by this one small board. A common application this allows for is using one card connected to a directional antenna for the "backbone" link to the Air-Stream Network and the second card connected to an omni-directional or sectored antenna for further node connections.
Software
The architecture is supported by various different open source operating systems and there are many ready made distributions for the PC Engines WRAP. The operating system is stored on a compact flash card (not supplied with the board.)
Weatherproofing
The boards are conveniently sized just right to fit inside the well priced sealed diecast aluminium enclosures* available at Dick Smith and Jaycar, which are designed to IP65 and NEMA4 standards.
Power Supply
Power is supplied through a DC jack or via power over ethernet - directly into the ethernet port on the board. Power supplies must be purchased seperately.
Purchasing
PC Engines WRAPs are supplied by Yawarra Information Appliances
*Note: To comply with Australian emissions regulations these boards need to be enclosed in a metal case.
Note (8/6/2007) on SC1100 based WRAPs: Experience shows there is not enough internal bandwidth to support two high speed backbone connections. SC1100 is in End of Life status now and newer WRAPs will be powered by Geode LX800 or ARM9 CPUs which will hopefully resolve this
A module or device which provides IEEE 802.11 a/b/g/n MAC layer to a host and a physical layer to an antenna.

The card feature good output power performance and high receive sensitivity as they are designed with long distance outdoor wireless networks in mind. The cards also have built-in Heat-sinks that make them ideal for Australian conditions.
Dbii Networks has recently given Air-Stream Wireless a number of samples to trial on our network, which are currently with the Network Planning Team for deployment.
Units for testing include:This is our first real-world trail of the F20-Pro - 2.4Ghz 802.11b/g and the F50-Pro - 5.8Ghz 802.11a mini PCI cards produced by Dbii Networks which will soon be installed at two new core nodes in the South Metro Network marked in red below.
The new site at Seaview Downs will provide a back-haul link between Melrose Park (marked Blue) and a large commercial building at Bedford Park which will significantly increased coverage in Marion area.

Edimax EW-7206APg is a new ethernet access point (AP) that is similar to the old Minitars but also have a 802.11g mode. They support all the features of the Minitar like client mode and MAC cloning.
Download the factsheet (Cached)
Download the users manual (Cached)
Mass production of these units have just begun, hopefully these units will proove to be as good as the old Minitars and will help the network grow. These units will benifit clients who just want to connect to an access point and dont have *nix skills.
Similarities:
Size/form factor: Identical (same factory)
Power/POE: Identical
Features: All MNWAPB features are there, including setting MAC addres on a 'client' (MAC cloning).
TX Power: Same (60 mW) in 802.11b mode.
Antenas connectors: 1 x RP-SMA
Price: About same as MNWAPB
Differences:
+ 802.11g
+ 'Universal repeater' mode. This is a simultaneous AP+Client. And the AP and client can have different SSIDs
Link to info about the radio inside
| EW-7206APg | |||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||
|
Wireless-g 54Mbps Access Point
|
|
||||||||||||||||||||||||||||||||
|
Key Features
Specifications
|
|||||||||||||||||||||||||||||||||