802.11 specifies two principle modes of operation, IBSS [1] and BSS
[2]. The reason this is important is because it can change the way
that the layer two connectivity appears to hosts.
To begin, have a look at this explanation [3].
If the host has an interface running in IBSS [4] mode, then it will
be able to contact a subset of other hosts within the IBSS domain. For
those hosts that are reachable, the network will look as if it is a
broadcast domain (ie. like ethernet, not like ATM). For those hosts
that aren't in range, it simply will not be able to address. However
for each individual host, the set of reachable and unreachable hosts
will differ. The implications of this on IP networking in IBSS mode
are explained below.
If the host has an interface in BSS [5] mode though, the point
control function ensures that each host in the BSS domain can hear all
other hosts within the same domain. This way everyone has the same set
of reachable hosts.
So if a host is operating in BSS mode, the layer two looks the same
as any other broadcast layer two medium, e.g. the most common, 802.3
ethernet. You can assign a subnet to the interface, and can be certain
that if an IP within that subnet is active on another interface, that
it will be addressable at layer two by every other host on the same
subnet. In other words, if host A needs to talk to host B, A can use
ARP (address resolution protocol) to discover B's hardware address,
and then proceed to talk directly.
In contrast, in IBSS mode, if you allocate a subnet to the interface,
you cannot be certain that you will be able to address other hosts on
the same subnet at layer two. You may need to rely on another node[s
[6]] to forward your frames/packets in order for them to reach the
destination. However if you decide that this is no good, and try to
assign a subnetwork for the hosts that are reachable at layer two,
then in general, the hosts in the IBSS domain will be unable to agree
on who is in the set and who is out. This implies that you need
several sets, possibly one per host - so you have a large number of IP
addresses assigned to the one interface, sub-interfaces if you like.
Additionally, every time another host is added to the IBSS domain,
these networks change, so configurations must be changed as well.
Links:
------
[1] http://melbournewireless.org.au/?IBSS
[2] http://melbournewireless.org.au/?BSS
[3] http://seattlewireless.net/index.cgi/PointToPoint
[4] http://melbournewireless.org.au/?IBSS
[5] http://melbournewireless.org.au/?BSS
[6] http://melbournewireless.org.au/?s
[EditText] [Spelling] [Current] [Raw] [Code] [Diff] [Subscribe] [VersionHistory] [Revert] [Delete] [RecentChanges]
Node Statistics | |
---|---|
building | 132 |
gathering | 193 |
interested | 515 |
operational | 233 |
testing | 214 |