Changes between Version 55 and Version 56 of Old/WiMAX/30

Timestamp:

May 13, 2014, 3:03:24 PM (10 years ago)

Author:

Nilanjan Paul

Comment:

—

Old/WiMAX/30

@@ -382 +382 @@
 === 1. Install Linux ===
 
-Install Ubuntu version 11.04 or later on a netbook.  A Linux kernel of version of 2.6.38 or greater is required to install the drivers; to determine the current systems kernel version run:
+Install Ubuntu version 12.04 a netbook.  A Linux kernel of version of 2.6.38 or greater is required to install the drivers; to determine the current systems kernel version run:
 
 {{{
@@ -390 +390 @@
 If the kernel image needs to be updated then do the following:
 {{{
-$ apt-cache search linux | grep generic
+$ apt-cache search linux-image | grep generic
 }}}
 
 This will provide a list of available kernel images for the running system.
-To install an image:
+To install the linux image version 3.8.0-31:
 {{{
 $ apt-get install linux-image-3.8.0-31-generic
 }}}
 
-Follow all the prompts and reboot if required.
-
-
-The following steps were completed successfully on Ubuntu 11.10 and Ubuntu 12.04.
+Reboot the machine to load the new kernel:
+{{{
+$ reboot
+}}}
+
+
+The following steps were completed successfully on Ubuntu 12.04.
 
 === 2. Resources ===
@@ -410 +413 @@
 Files in the following tarball are required to install the driver: http://wimax.orbit-lab.org/downloads/BeceemSource.tar.gz . The tarball is quite large (~150 MB) and may take a few minutes or more to download. 
 
-It will be assumed that these files were downloaded to the ~/Downloads/ directory for the remainder of the guide. Extract the files:
+Download the tarball and extract the files:
 
 {{{
 $ cd ~/Downloads
+$ wget http://wimax.orbit-lab.org/downloads/BeceemSource.tar.gz
 $ tar -xzf BeceemSource.tar.gz
 }}}
@@ -422 +426 @@
 # apt-get install libssl-dev linux-headers-$(uname -r) make patch unzip
 }}}
-
-Download the source files for the linux kernel distribution into /usr/src:
+It's most likely the linux header files are downloaded into the directory /usr/src.
+
+Download the source files for the linux kernel distribution into /usr/src and create a symlink to simplify installation when building the driver:
 {{{
 # pushd /usr/src
 # apt-get source linux-image-$(uname -r)
+# ln -s <linux-source-directory> linux
 # popd
 }}}
+Note: <the linux-source-directory> should be suffixed with the kernel version.
 
 === 3. Install libeap Library ===
@@ -445 +452 @@
 This library is required to install the wimaxd utility, and does not get installed properly by the script provided in the Sprint tarball.
 
-=== 4. Prepare linux-source for Install ===
-
-A kernel environment is required to properly construct the driver. To create this environment from the source files installed with apt-get, run:
-
-{{{
-# cd /usr/src
-# tar -xjf linux-source-X.Y.Z.tar.bz2  # where the kernel version number takes the place of X.Y.Z
-# ln -s linux-sources-X.Y.Z linux
-}}}
-
-The final command creates a symlink, which simplifies later installation by allowing all default paths to be used when building the driver.
-
-=== 5. Build the Driver ===
-
-Unpack the Sprint tarball and run the install script:
+=== 4. Build the Driver ===
+
+Unpack the Sprint tarball and run the script. This will build and install the driver:
 
 {{{
@@ -470 +465 @@
 The installer will prompt for various file paths, if the symlink was created in the previous step then the default choices should be correct.
 
-After the install finishes run the following commands to add the new driver to the startup modules, and verify success:
+On some recent kernels, you will need to blacklist the `bcm_wimax` driver to prevent it from claiming the device on start up.
+
+{{{
+# echo "blacklist bcm_wimax" > /etc/modprobe.d/blacklist-bcm-wimax.conf
+}}}
+
+Run the following command to add the new driver to the startup modules:
 
 {{{
 # modprobe drxvi314
+}}}
+
+To check if above driver registered properly:
+{{{
 # dmesg | grep usbbcm
 }}}
-
-The last command should output a line that includes "Initialised usbbcm" upon a successful kernel install.
-
-On some recent kernels, you will need to blacklist the `bcm_wimax` driver to prevent it from claiming the device. Run
-
-{{{
-# echo "blacklist bcm_wimax" > /etc/modprobe.d/blacklist-bcm-wimax.conf
-}}}
-
-
-=== 6. Reboot, Configure, and Verify ===
-
-Reboot the netbook. After startup copy the following files with the commands:
+This should output a line that includes " usbcore: registered new interface driver usbbcm"
+
+
+=== 5. Reboot, Configure, and Verify ===
+
+Reboot the machine:
+{{{
+# reboot
+}}}
+
+After startup copy the following files with the commands:
 
 {{{
@@ -495 +498 @@
 }}}
 
-Edit the new /etc/wimaxd.conf file as desired, the file is heavily commented and should be self explanitory. Make sure that the network's center frequency can be found in the CenterFrequencyMHz parameter of the config file, the GENI network center frequency (2590) is not one of the default frequencies. The firmware file is copied because the utilities expect that both the macxvi350.bin and macxvi200.bin will be present when utilities are run.
-
-Plug the dongle into a usb port and run:
+In a another terminal window and tail the syslog file. This show the results wimax commands down below.
+{{{
+# tail -f /var/log/syslog
+}}}
+
+Edit the new /etc/wimaxd.conf file as desired, the file is heavily commented and should be self explanatory. Make sure that the network's center frequency can be found in the CenterFrequencyMHz parameter of the config file, the GENI network center frequency (2590) is not one of the default frequencies. The firmware file is copied because the utilities expect that both the macxvi350.bin and macxvi200.bin will be present when utilities are run.
+
+Plug the dongle into a usb port and list the USB devices:
 
 {{{
 $ lsusb
-}}}
-
-One of the devices should include "Beceem Communications Inc." if the installation was successful.
-
-=== 7. Start the Server and Connect ===
+Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
+Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
+Bus 003 Device 002: ID 198f:0220 Beceem Communications Inc. BCSM250 WiMAX Adapter
+Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+}}}
+
+One of the devices should include "Beceem Communications Inc." if the installation was successful. The Bus and Device number may be different.
+
+=== 6. Start the Server and Connect ===
 
 Start the wimax daemon:
@@ -511 +526 @@
 {{{
 # wimaxd -c /etc/wimaxd.conf
-}}}
-
-The prompt "CSCM Server Started" should appear.
-
-Run the connection utility:
-
-{{{
-$ wimaxc -i
-}}}
-
-Start search at the subprompt
-
-{{{
-> search
-}}}
-
-If networks are found then the installation is complete! 
+********** CSCM Server Started ********** 05/13/14 10:24:11
+}}}
+
+Use the connection utility to search for the base station and check for similar output:
+
+{{{
+# wimaxc search
+Beceem CM Server Version 1.1.7.0
+Network search returned 1 base station.
+Idx BSID                    Pre      Freq      BW  RSSI  CINR
+ 0  01:01:44:51:db:00:00:01 0x00 2590.000  10.000   -56    31
+}}}
+
+If networks are found then the installation is complete and the wimax interface will try to connect to a base station. The syslog file should show a similar output:
+{{{
+May 13 10:24:27 localhost kernel: [  260.814967] LinkControlResponseMessage:PHY_SYNC_ACHIVED
+May 13 10:24:34 localhost kernel: [  268.573803] LinkControlResponseMessage:PHS Support Status Recieved In LinkUp Ack : 1
+May 13 10:24:34 localhost kernel: [  268.573806]
+May 13 10:24:35 localhost kernel: [  269.186284] CmControlResponseMessage:### TID RECEIVED 35968
+}}}
 
 If an error occurs, such as the device can not be found, the interface must be started. Determine the interface for the dongle by running
 
-{{{
-$ ifconfig
-}}}
-
-Match the hardware/MAC address of one of the eth interfaces with the dongle address. Then run the command on that interface (ethX in the code below):
-{{{
-# ifconfig ethX up
-}}}
-
-The wimaxc utility should successfully find the hardware and search.
+
+=== 7. Configure the interface ===
+Once connected the wimax dongle should come up as an ''eth'' interface. Match the dongle's MAC address to ''eth'' interface. In this example, the MAC address of the wimax dongle used is b8:61:6f:0d:a0:6d.
+To see a list of interfaces:
+{{{
+$ ifconfig -a
+eth0      Link encap:Ethernet  HWaddr 00:03:1d:0c:7d:d0
+          BROADCAST MULTICAST  MTU:1500  Metric:1
+          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
+          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
+          collisions:0 txqueuelen:1000
+          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
+          Interrupt:20 Memory:f0700000-f0720000
+
+eth1      Link encap:Ethernet  HWaddr 00:03:1d:0c:7d:d1
+          inet addr:10.10.7.10  Bcast:10.10.255.255  Mask:255.255.0.0
+          inet6 addr: fe80::203:1dff:fe0c:7dd1/64 Scope:Link
+          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
+          RX packets:710 errors:0 dropped:0 overruns:0 frame:0
+          TX packets:576 errors:0 dropped:0 overruns:0 carrier:0
+          collisions:0 txqueuelen:1000
+          RX bytes:71675 (71.6 KB)  TX bytes:92532 (92.5 KB)
+          Interrupt:17 Memory:f0600000-f0620000
+
+eth2      Link encap:Ethernet  HWaddr b8:61:6f:0d:a0:6d
+          BROADCAST MULTICAST  MTU:1400  Metric:1
+          RX packets:35246 errors:0 dropped:0 overruns:0 frame:0
+          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
+          collisions:0 txqueuelen:1000
+          RX bytes:11366 (11.3 KB)  TX bytes:0 (0.0 B)
+
+lo        Link encap:Local Loopback
+          inet addr:127.0.0.1  Mask:255.0.0.0
+          inet6 addr: ::1/128 Scope:Host
+          UP LOOPBACK RUNNING  MTU:65536  Metric:1
+          RX packets:35 errors:0 dropped:0 overruns:0 frame:0
+          TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
+          collisions:0 txqueuelen:0
+          RX bytes:2590 (2.5 KB)  TX bytes:2590 (2.5 KB)
+
+
+}}}
+
+The wimax dongle came up on ''eth2''. We'll configure this interface as working example:
+{{{
+# ifconfig eth2 10.41.41.29 netmask 255.255.0.0 up
+}}}
+
+Now check ''eth2'' interface.
+{{{
+# ifconfig eth2
+eth2      Link encap:Ethernet  HWaddr b8:61:6f:0d:a0:6d
+          inet addr:10.41.41.29  Bcast:10.41.255.255  Mask:255.255.0.0
+          inet6 addr: fe80::ba61:6fff:fe0d:a06d/64 Scope:Link
+          UP BROADCAST RUNNING MULTICAST  MTU:1400  Metric:1
+          RX packets:41362 errors:0 dropped:0 overruns:0 frame:0
+          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
+          collisions:0 txqueuelen:1000
+          RX bytes:13174 (13.1 KB)  TX bytes:168 (168.0 B)
+}}}
+
+Test the interface by pinging the gateway (10.41.0.1):
+{{{
+# ping 10.41.0.1 -c 5
+PING 10.41.0.1 (10.41.0.1) 56(84) bytes of data.
+64 bytes from 10.41.0.1: icmp_req=1 ttl=254 time=61.7 ms
+64 bytes from 10.41.0.1: icmp_req=2 ttl=254 time=59.9 ms
+64 bytes from 10.41.0.1: icmp_req=3 ttl=254 time=57.9 ms
+64 bytes from 10.41.0.1: icmp_req=4 ttl=254 time=61.9 ms
+64 bytes from 10.41.0.1: icmp_req=5 ttl=254 time=60.9 ms
+
+--- 10.41.0.1 ping statistics ---
+5 packets transmitted, 5 received, 0% packet loss, time 4005ms
+rtt min/avg/max/mdev = 57.951/60.522/61.963/1.494 ms
+}}}
+