home  wiki

Spelling: HowToLinkToBackbone



INTRODUCTION

It is possible to create a link in different ways, the commonest ways
are supported in most wireless devices (cards and APs). The simplest
links are those that use BSSBSA, BASS, BESS, BOSS, BUSS, BS, BSD, SS, BSDS, B'S, BBS, BIS, BUS, SSS, BPS, BXS, USS, ASS, BA'S, BUS'S, S'S, SB'S, BE'S, BI'S, BO'S, ABS'S, BK'S, BR'S, OS'S, CS'S mode where an AP is the hub for all
transmissions. This is fine for the DxDC, Dc, Dex, Dix, Dz, D, DJ, TX, X, DA, DD, DE, DI, De, Di, Du, Dy, Dd, Do, Ax, DH, DP, Dr, PX, Rx, Bx, DB, Db, Ex, Ix, Ox, Xx, D's Node you use in the house and
for connecting Client Nodes to a CxCZ, Cox, Cc, Xx, C, X, Cs, CA, CO, Ca, Ce, Ci, Co, Cu, Cy, Ck, Cw, CB, CD, CF, CT, CV, Cb, Cd, Cf, Cl, Cm, Cr, Ct, Cg, Ax, Ch, PX, Rx, TX, Bx, Ex, Ix, Ox, C's Node but has some limitations when
trying to use it for backbone links (the major one being that all
traffic is routed through the AP).

In the backbone it is useful to build redundancy through multiple
connections. Within a node this ideally would be through establishing
connections with multiple physical radios (i.e. a dedicated
transcievertransceiver, transceivers, transceiver's, transfer, transitive for each link) but cost and aavilabilityavailability, availability's, unavailability, inviolability, availabilities of other nodes to
connect to may not make this practical. The advantage of having
multiple connections is that as the density of nodes increases it is
possible that multiple nodes can provide alternative routes for
traffic.

ANTENNAS FOR LINKS

There is a limited set of choices here, somewhat dictated by the
protocol used for establishing the link.

omniOmani, mini, mono, Oman, omen, Omanis, Min, Mon, min, Mani, OMB, Ono, omit, MN, Mn, Mona, ON, om, on, Domini, Odin, Olin, Orin, Anni, Emmi, omens, Ami, oms, one, own, uni, Amii, Arni, Omar, Oona, Agni, Oman's, omen's ------/--- ---/--- omniOmani, mini, mono, Oman, omen, Omanis, Min, Mon, min, Mani, OMB, Ono, omit, MN, Mn, Mona, ON, om, on, Domini, Odin, Olin, Orin, Anni, Emmi, omens, Ami, oms, one, own, uni, Amii, Arni, Omar, Oona, Agni, Oman's, omen's ( hmmm, Ok, if you really have to... )
omniOmani, mini, mono, Oman, omen, Omanis, Min, Mon, min, Mani, OMB, Ono, omit, MN, Mn, Mona, ON, om, on, Domini, Odin, Olin, Orin, Anni, Emmi, omens, Ami, oms, one, own, uni, Amii, Arni, Omar, Oona, Agni, Oman's, omen's ------/--- >-------- directional ( Better, hybrid Bx CxCZ, Cox, Cc, Xx, C, X, Cs, CA, CO, Ca, Ce, Ci, Co, Cu, Cy, Ck, Cw, CB, CD, CF, CT, CV, Cb, Cd, Cf, Cl, Cm, Cr, Ct, Cg, Ax, Ch, PX, Rx, TX, Bx, Ex, Ix, Ox, C's nodes do
this )
directional ----< >-------- directional ( Best!! )

PROTOCOLS FOR LINKS

There are four candidates for protocols that could be used for
establishing links. In reality while any protocol that is supported by
the devices at each end could be used some of thaThai, Thar, Thea, Thia, thaw, Th, Thad, than, that, Ha, TA, Ta, ha, ta, Thu, the, tho, thy, Otha, THC, Tia, tea, FHA, TBA, TVA, TWA, aha, Th's available protocols
are not really the best for links ( as compared to supporting client
connection ).

* BSSBSA, BASS, BESS, BOSS, BUSS, BS, BSD, SS, BSDS, B'S, BBS, BIS, BUS, SSS, BPS, BXS, USS, ASS, BA'S, BUS'S, S'S, SB'S, BE'S, BI'S, BO'S, ABS'S, BK'S, BR'S, OS'S, CS'S
* WDSEDS, WADS, WEDS, DDS, IDS, ODS, W'S, ADS, WES, WIS, WAS, D'S, ED'S, WED'S, WAD'S, AD'S, CD'S, GD'S, MD'S, ND'S, PD'S, RD'S, ID'S, WM'S, WU'S
* Bridge
* IBBSBIBS, BBS, EBBS, IBIS, GIBBS, IBBY, BIB'S, IBBY'S, IBO'S, GIBB'S, IBM'S

BSSBSA, BASS, BESS, BOSS, BUSS, BS, BSD, SS, BSDS, B'S, BBS, BIS, BUS, SSS, BPS, BXS, USS, ASS, BA'S, BUS'S, S'S, SB'S, BE'S, BI'S, BO'S, ABS'S, BK'S, BR'S, OS'S, CS'S

Using BSSBSA, BASS, BESS, BOSS, BUSS, BS, BSD, SS, BSDS, B'S, BBS, BIS, BUS, SSS, BPS, BXS, USS, ASS, BA'S, BUS'S, S'S, SB'S, BE'S, BI'S, BO'S, ABS'S, BK'S, BR'S, OS'S, CS'S for a backbone link can be done, One end runs as an AP
while the other runs as a BSSBSA, BASS, BESS, BOSS, BUSS, BS, BSD, SS, BSDS, B'S, BBS, BIS, BUS, SSS, BPS, BXS, USS, ASS, BA'S, BUS'S, S'S, SB'S, BE'S, BI'S, BO'S, ABS'S, BK'S, BR'S, OS'S, CS'S client. Each end would also has other
links so this is just a single circuit of the ones that are available.
This is a good choice for establishing a link in the initial instance
and while traffic is light. at the AP end the same radio could support
multiple links while at the client end there are a number of choices
of device that could be used.

Using this protocol the AP end is probably already correctly
configured for routing while the client end will need some further
configuration to work as a router rather than as a stand alone client
of the AP. The client may be an AP in client mode or a PC with a radio
card. Details of how to configure routing in a client device are on
the RoutingHowtoRoutinised, Routinized, Rotundity, Rotund, Rotunded, Rottenest, Rotunda, Reinhard [1] page.

Note: BSSBSA, BASS, BESS, BOSS, BUSS, BS, BSD, SS, BSDS, B'S, BBS, BIS, BUS, SSS, BPS, BXS, USS, ASS, BA'S, BUS'S, S'S, SB'S, BE'S, BI'S, BO'S, ABS'S, BK'S, BR'S, OS'S, CS'S is probably the most common protocol for AP-to-client
connection, the protocol being devised for this use. Using BSSBSA, BASS, BESS, BOSS, BUSS, BS, BSD, SS, BSDS, B'S, BBS, BIS, BUS, SSS, BPS, BXS, USS, ASS, BA'S, BUS'S, S'S, SB'S, BE'S, BI'S, BO'S, ABS'S, BK'S, BR'S, OS'S, CS'S for
establishing an inter-node (Bx-to-Bx or Bx-to-Cx) is a different use.

WDSEDS, WADS, WEDS, DDS, IDS, ODS, W'S, ADS, WES, WIS, WAS, D'S, ED'S, WED'S, WAD'S, AD'S, CD'S, GD'S, MD'S, ND'S, PD'S, RD'S, ID'S, WM'S, WU'S

WDSEDS, WADS, WEDS, DDS, IDS, ODS, W'S, ADS, WES, WIS, WAS, D'S, ED'S, WED'S, WAD'S, AD'S, CD'S, GD'S, MD'S, ND'S, PD'S, RD'S, ID'S, WM'S, WU'S is a higher level protocol that is used to support a roaming
environment for a Client. Multiple Nodes use the same ESSIDES SID, ES-SID, EASED, ESSIE, ASSAD, ASIDE, ISSUED, SAID, EAST, SID, ACID, ESPIED, EST, ESSA, ESSY, ISSI, ENID, ESTA, ASST, ERST, USED, ARSED, FESSED, MESSED, YESSED, ISSIE, OSSIE, ESSAY, ESSEN, ESTER, ASSET, ASTIR, ESSIE'S, ESSA'S, ESSY'S, ISSI'S and a
mobile client node is passed from Node to node based on signal
strength. WDSEDS, WADS, WEDS, DDS, IDS, ODS, W'S, ADS, WES, WIS, WAS, D'S, ED'S, WED'S, WAD'S, AD'S, CD'S, GD'S, MD'S, ND'S, PD'S, RD'S, ID'S, WM'S, WU'S is a suitable protocol for the client Node cloud but
inappropriate for establishing the network backbone links.

Well, actually WDSEDS, WADS, WEDS, DDS, IDS, ODS, W'S, ADS, WES, WIS, WAS, D'S, ED'S, WED'S, WAD'S, AD'S, CD'S, GD'S, MD'S, ND'S, PD'S, RD'S, ID'S, WM'S, WU'S is not so bad for establishing a link if a
dedicated radio is used at one or both ends. A lot of APsApes, Apps, Apse, Asp, Pas, Alps, Amps, Asps, AP, As, PS, UPS, Ops, Ups, Baps, Caps, Gaps, Laps, Maps, Naps, Paps, Raps, Saps, Taps, Yaps, Zaps, A's, AIs, APO, PPS, Ape, App, Ass, ABS, APB, APR, Apr, Ats, DPs, Abs, Ads, Ans, Apt, Bps, Cps, Fps, Rps, Alp's support WDSEDS, WADS, WEDS, DDS, IDS, ODS, W'S, ADS, WES, WIS, WAS, D'S, ED'S, WED'S, WAD'S, AD'S, CD'S, GD'S, MD'S, ND'S, PD'S, RD'S, ID'S, WM'S, WU'S
and it means an AP that cannot be configured in client mode ( like the
AVAYA-AP3 ) can be used as one end of a link. The AP-3 can be set up
to use one radio for the WDSEDS, WADS, WEDS, DDS, IDS, ODS, W'S, ADS, WES, WIS, WAS, D'S, ED'S, WED'S, WAD'S, AD'S, CD'S, GD'S, MD'S, ND'S, PD'S, RD'S, ID'S, WM'S, WU'S connection and the other as the Node AP.
To the Node at theotherthe other, the-other, thither, Thoth, tether, Heather, heather, theater, whether, either, hither, tither, ether, other, Thatcher, thatcher, toothier, aether, bother, mother, nether, pother, teethe, Thoth's end ( also configuedconfigured, configure, confided, confined, confirmed, confide, confused, confuted, confound, congaed, converged, convoked, confider, connived, convicted to support WDSEDS, WADS, WEDS, DDS, IDS, ODS, W'S, ADS, WES, WIS, WAS, D'S, ED'S, WED'S, WAD'S, AD'S, CD'S, GD'S, MD'S, ND'S, PD'S, RD'S, ID'S, WM'S, WU'S ) it is
like a special client. The down side is a possible reduction in
available bandwidth if data is going from a wireless client at the
upstream end to the Node at the end of the WDSEDS, WADS, WEDS, DDS, IDS, ODS, W'S, ADS, WES, WIS, WAS, D'S, ED'S, WED'S, WAD'S, AD'S, CD'S, GD'S, MD'S, ND'S, PD'S, RD'S, ID'S, WM'S, WU'S link. The use of
multiple radio devices ate either end is a good compromise and would
not result in any splitting of the bandwidth.

AP-3s used for WDSEDS, WADS, WEDS, DDS, IDS, ODS, W'S, ADS, WES, WIS, WAS, D'S, ED'S, WED'S, WAD'S, AD'S, CD'S, GD'S, MD'S, ND'S, PD'S, RD'S, ID'S, WM'S, WU'S link

+---------+ +---------+ | | | | | +-----+ Node 1 AP Node 2 AP
+-----+ | | | A |-< CH 1 CH 11 >-| A | | | +-----+ +-----+ | | | | | |
+-----+ CH 6 WDSEDS, WADS, WEDS, DDS, IDS, ODS, W'S, ADS, WES, WIS, WAS, D'S, ED'S, WED'S, WAD'S, AD'S, CD'S, GD'S, MD'S, ND'S, PD'S, RD'S, ID'S, WM'S, WU'S link +-----+ | | | B |-< ///////// >-| B | | LAN
Interface| +-----+ +-----+ |LAN interface =============| | |
|============= +---------+ +---------+
In this case CH 6 is used only for the link. Either end could also
use the WDSEDS, WADS, WEDS, DDS, IDS, ODS, W'S, ADS, WES, WIS, WAS, D'S, ED'S, WED'S, WAD'S, AD'S, CD'S, GD'S, MD'S, ND'S, PD'S, RD'S, ID'S, WM'S, WU'S interface to link to further nodes, so WDSEDS, WADS, WEDS, DDS, IDS, ODS, W'S, ADS, WES, WIS, WAS, D'S, ED'S, WED'S, WAD'S, AD'S, CD'S, GD'S, MD'S, ND'S, PD'S, RD'S, ID'S, WM'S, WU'S works as a P2MP
link.

BRIDGE

A bridge makes two physiclyphysical, physically, physic, physicals, physics, physic's, physicality isolated network segments look like the
same segment. The bridging device at either end forewardsfore wards, fore-wards, forewords, foreword's, forwards, forewarns, rewards, foreword, foreparts, reward's, firewood's, forepart's traffic
across the bridge. This is a common use of WiFiWife, Fifi, Wini [2] in a private
network. A bridge could be used to link two nodes but typically each
node would have it's own address range. The bridging device at one end
or another would have to act as a router or would have to feed into a
port on a router to allow each node to control it's own address space.

Bridge spanning two physical segments
192.168.1.0 +-----+ +-----+ 192.168.1.0 |================| |-< >-|
|==================| +-----+ +-----+ Bridge with additional router at
receiving end
192.168.1.0 +-----+ +-----+ 192.168.1.0 +-----+ 192.168.2.0
|================| |-< >-| |=============| |===============| +-----+
+-----+ +-----+

IBBSBIBS, BBS, EBBS, IBIS, GIBBS, IBBY, BIB'S, IBBY'S, IBO'S, GIBB'S, IBM'S

IBBSBIBS, BBS, EBBS, IBIS, GIBBS, IBBY, BIB'S, IBBY'S, IBO'S, GIBB'S, IBM'S is probably the best protocol to use to establish a link between
two nodes. It is a lower lvellevel, Lovell, lively, lovely, levels, label, libel, Lev, Lela, Love, lave, live, love, Laval, Levi, Levy, Lyle, levy, Leela, Levey, levee, lever, liver, lover, lovey, Lyell, lapel, laved, laves, lived, liven, lives, loved, loves, LVN, Lil, lvi, Havel, Pavel, Ravel, bevel, gavel, hovel, navel, novel, ravel, revel, Lief, feel, fuel, lief, loll, lull, lvii, Lvov, evil, oval, Love's, Lev's protocol than BSSBSA, BASS, BESS, BOSS, BUSS, BS, BSD, SS, BSDS, B'S, BBS, BIS, BUS, SSS, BPS, BXS, USS, ASS, BA'S, BUS'S, S'S, SB'S, BE'S, BI'S, BO'S, ABS'S, BK'S, BR'S, OS'S, CS'S ( doesn't try to solve
the hidden node problem and routing decisions are promoted to layer 3
rather than being addressed at layer 2 see Layer2Assumptions).

192.168.1.0 +-----+ +-----+ 192.168.2.0 |================| |-< >-|
|===================| +-----+ +-----+

Links:
------
[1] http://melbourne.wireless.org.au/?RoutingHowto
[2] http://melbourne.wireless.org.au/?WiFi

[EditText] [Spelling] [Current] [Raw] [Code] [Diff] [Subscribe] [VersionHistory] [Revert] [Delete] [RecentChanges]

> home> about> events> files> members> maps> wiki board   > home   > categories   > search   > changes   > formatting   > extras> site map

Username
Password

 Remember me.
>

> forgotten password?
> register?
currently 0 users online
Node Statistics
building130
gathering193
interested492
operational241
testing205