Changes between Version 11 and Version 12 of Internal/AtherosDriverLimits

Timestamp:

Sep 14, 2006, 3:59:39 PM (18 years ago)

Author:

Gautam D. Bhanage

Comment:

—

Internal/AtherosDriverLimits

@@ -3 +3 @@
  Virtual access point(s) may be defined as logical abstraction(s) built on an underlying physical device.  Once defined on a physical device each virtual access point is capable of operating as an independent entity from other virtual devices defined on the same physical device. The current Atheros cards on the orbit nodes come with a MadWifi driver that supports setting up of multiple virtual access points on a single physical device.
 
-== Limitations With the Virtual Device Declarations ==
+== Limitations ==
  
  * Each physical device on a Atheros card is able to support upto 4 virtual access points and a single station. 
@@ -21 +21 @@
  The user request the creation of two networks on a given set of nodes. Each network will have an access point and a station. The access point and the station are bound by the same essid's and would exist in the same subnet. In the underlying architecture the user chooses the same physical interface on a node to act as a different access point on two seperate networks. The script shows that the user may be oblivious to the fact that he/she is requesting the same node to be acting as different AP's, thereby simulating the requests of two different users for two independent networks with the involvement of a common node (the virtual AP) without each others knowledge. The sample ruby script is as given below:
 {{{
- #
+#
 # Define nodes used in experiment
 #
+
 # Physical Station for net 01.
 defNodes('sender', [9,4]) {|node|
@@ -83 +84 @@
 }
 
-# allNodes.net.w0 { |w|
-#  w.type = 'b'
-#  w.essid = "net01"
-#  w.ip = "%192.168.%x.%y"
-#}
-
 #
 # Now, start the application
@@ -100 +95 @@
   Experiment.done
 }
-
-
 }}}