OpenBTS: N210 Burn Firmware - Revision history

Onnowpurbo: /* Pranala Menarik */

2014-03-10T13:16:06Z

Pranala Menarik

← Older revision		Revision as of 13:16, 10 March 2014
Line 299:		Line 299:
	* [[OpenBTS: Script Membuat GNURadio 3.4.2 di Ubuntu 13.04]]		* [[OpenBTS: Script Membuat GNURadio 3.4.2 di Ubuntu 13.04]]
	* [[OpenBTS: Script Membuat OpenBTS dan yate di Ubuntu 13.04]]		* [[OpenBTS: Script Membuat OpenBTS dan yate di Ubuntu 13.04]]
			* [[OpenBTS: Script Membuat OpenBTS 2.8.0 di RangeNetwork Dev Kit]]
			* [[OpenBTS: Script Membuat OpenBTS di RangeNetwork Dev Kit]]

	===OpenBTS 2.6===		===OpenBTS 2.6===
Line 358:		Line 359:
	* [[OpenBTS: 2.8 dari SVN Install Clock 52MHz di Ubuntu 12.10]] '''RECOMMENDED'''		* [[OpenBTS: 2.8 dari SVN Install Clock 52MHz di Ubuntu 12.10]] '''RECOMMENDED'''
	* [[OpenBTS: 2.8 dari SVN Install Clock 52MHz di Ubuntu 13.04]] '''RECOMMENDED'''		* [[OpenBTS: 2.8 dari SVN Install Clock 52MHz di Ubuntu 13.04]] '''RECOMMENDED'''
			* [[OpenBTS: 2.8 dari SVN 2.8.0 Install Clock 52MHz di Ubuntu 13.04]] '''RECOMMENDED'''
	* [[OpenBTS: 2.8 dari SVN Install Clock 52MHz dengan UHD tanpa GNURadio]] ''NOT RECOMMENDED''		* [[OpenBTS: 2.8 dari SVN Install Clock 52MHz dengan UHD tanpa GNURadio]] ''NOT RECOMMENDED''
	* [[OpenBTS: 2.8 Edit User di sqlite3.db]] '''RECOMMEND'''		* [[OpenBTS: 2.8 Edit User di sqlite3.db]] '''RECOMMEND'''
Line 371:		Line 373:
	* [[OpenBTS: Database SQLite]]		* [[OpenBTS: Database SQLite]]
	* [[OpenBTS: Set SQLite Subscriber Registry secara manual]]		* [[OpenBTS: Set SQLite Subscriber Registry secara manual]]
			* [[OpenBTS: Set SQLite parameter smqueue]]
	* [[OpenBTS: FreeSWITCH]]		* [[OpenBTS: FreeSWITCH]]

Line 377:		Line 380:
	* [[OpenBTS: Pola Multi OpenBTS]] '''RECOMMENDED'''		* [[OpenBTS: Pola Multi OpenBTS]] '''RECOMMENDED'''
	* [[Multi OpenBTS: Catatan Konfigurasi]] '''RECOMMENDED'''		* [[Multi OpenBTS: Catatan Konfigurasi]] '''RECOMMENDED'''
			* [[Multi OpenBTS: Catatan BSIC=NCC+BCC]]
			* [[Multi OpenBTS: Catatan Frekuensi Planning di GSM]]
			* [[Multi OpenBTS: Catatan BTS Color Code BCC di GSM]]
			* [[Multi OpenBTS: Catatan Network Color Code NCC di GSM]]
			* [[Multi OpenBTS: Catatan BCCH]]
			* [[Multi OpenBTS: Catatan Public Land Mobile Network PLMN]]

			===OpenBTS 3.1.x===

			* [[OpenBTS: Install UHD untuk USRP1]]
			* [[OpenBTS: UHD Identifikasi Device]]
			* [[OpenBTS: OpenBTS 3.1.3 Compile]] '''Tidak bisa untuk USRP1'''
			* [[OpenBTS: Yate Compile]]

	===Ettus E110===		===Ettus E110===
Line 410:		Line 426:
	===RangeNetworks===		===RangeNetworks===

			* [[OpenBTS: RangeNetwork Foto]]
			* [[OpenBTS: RangeNetwork menggunakan USB recovery image]]
	* [[OpenBTS: RangeNetwork Default Setting]]		* [[OpenBTS: RangeNetwork Default Setting]]
			* [[OpenBTS: RangeNetwork Instalasi UHD]]
			* [[OpenBTS: RangeNetwork Compile GNURadio UHD]]
			* [[OpenBTS: RangeNetwork Compile]]
			* [[OpenBTS: RangeNetwork Compile OpenBTS 2.8.0]]
			* [[OpenBTS: RangeNetwork Compile OpenBTS 3.1.3]]
			* [[OpenBTS: RangeNetwork Yate Compile]] '''RECOMMENDED'''
			* [[OpenBTS: RangeNetwork Web Interface]]
			* [[OpenBTS: RangeNetwork Trunk ke Asterisk Lain]]
			* [[OpenBTS: RangeNetwork Audit]]
			* [[VoIP: Trunk]]

	===GPRS===		===GPRS===
Line 464:		Line 492:
	* [[OpenBTS: Permohonan Kanal dan DID untuk OpenBTS]]		* [[OpenBTS: Permohonan Kanal dan DID untuk OpenBTS]]
	* [[OpenBTS: 2013/02/19 - OpenBTS TelkomSel Mengudara di Muscat Oman]]		* [[OpenBTS: 2013/02/19 - OpenBTS TelkomSel Mengudara di Muscat Oman]]
			* [[OpenBTS: Beroperasi di Papua]]

	===Dokumentasi Video===		===Dokumentasi Video===

Onnowpurbo: /* Pranala Menarik */

2014-01-06T11:00:37Z

Pranala Menarik

← Older revision		Revision as of 11:00, 6 January 2014
Line 288:		Line 288:
	* [[USRP: Kalibrasi ClockTamer]]		* [[USRP: Kalibrasi ClockTamer]]
	* [[USRP: ClockTamer Control Protocol]]		* [[USRP: ClockTamer Control Protocol]]
			* [[USRP: ClockTamer Flashing]]
	* [[USRP: Instalasi Board]]		* [[USRP: Instalasi Board]]
	* [[OpenBTS: GIT Source Code]]		* [[OpenBTS: GIT Source Code]]
Line 293:		Line 294:
	* [[OpenBTS: Tethr untuk Bencana Alam]]		* [[OpenBTS: Tethr untuk Bencana Alam]]
	* [[USRP: Tip Pemesanan]]		* [[USRP: Tip Pemesanan]]

			===Script===

			* [[OpenBTS: Script Membuat GNURadio 3.4.2 di Ubuntu 13.04]]
			* [[OpenBTS: Script Membuat OpenBTS dan yate di Ubuntu 13.04]]


	===OpenBTS 2.6===		===OpenBTS 2.6===
Line 360:		Line 367:
	* [[OpenBTS: 2.8 Menjalankan]] '''RECOMMENDED'''		* [[OpenBTS: 2.8 Menjalankan]] '''RECOMMENDED'''
	* [[OpenBTS: 2.8 Konfigurasi]]		* [[OpenBTS: 2.8 Konfigurasi]]
			* [[OpenBTS: 2.8 Konfigurasi Cognitive Radio Elsabagh]]
	* [[OpenBTS: 2.8 Konfigurasi Subscriber Registery]]		* [[OpenBTS: 2.8 Konfigurasi Subscriber Registery]]
	* [[OpenBTS: Database SQLite]]		* [[OpenBTS: Database SQLite]]
			* [[OpenBTS: Set SQLite Subscriber Registry secara manual]]
			* [[OpenBTS: FreeSWITCH]]

	===Multi OpenBTS 2.8===		===Multi OpenBTS 2.8===
Line 375:		Line 385:
	* [[OpenBTS: E110 Mengubah Master Clock]]		* [[OpenBTS: E110 Mengubah Master Clock]]
	* [[OpenBTS: E110 Kalibrasi Clock]]		* [[OpenBTS: E110 Kalibrasi Clock]]
			* [[OpenBTS: E110 Konfigurasi Jaringan]]
	* [[OpenBTS: E110 Bekerja dengan opkg]]		* [[OpenBTS: E110 Bekerja dengan opkg]]
			* [[OpenBTS: E110 Instalasi iptables]]
	* [[OpenBTS: E110 GNURadio]]		* [[OpenBTS: E110 GNURadio]]
	* [[OpenBTS: E110 Compile UHD]] '''RECOMMENDED'''		* [[OpenBTS: E110 Compile UHD]] ''Not Recommended''
	* [[OpenBTS: E110 UHD burn EEPROM RFX Board]] ''~~'RECOMMENDED'~~''		* [[OpenBTS: E110 Compile UHD dari Release Bukan git]] ''Not Recommended''
	* [[OpenBTS: E110 Install UHD Image]] ''~~'RECOMMENDED'~~''		* [[OpenBTS: E110 UHD burn EEPROM RFX Board]] ''Not Recommended''
			* [[OpenBTS: E110 Install UHD Image]] ''Not Recommended''
	* [[OpenBTS: E110 Instalasi OpenBTS]]		* [[OpenBTS: E110 Instalasi OpenBTS]]
	* [[OpenBTS: E110 Instalasi OpenBTS 2.6]] ''NOT RECOMMENDED''		* [[OpenBTS: E110 Instalasi OpenBTS 2.6]] ''NOT RECOMMENDED''
	* [[OpenBTS: E110 Instalasi OpenBTS 2.8 untuk MultiBTS]] '''RECOMMENDED'''		* [[OpenBTS: E110 Instalasi OpenBTS 2.8 untuk MultiBTS]] '''RECOMMENDED'''
			* [[OpenBTS: E110 Yate Softswitch]]

	===Ettus N210===		===Ettus N210===
Line 393:		Line 407:
	* [[OpenBTS: N210 Yate Config Test]]		* [[OpenBTS: N210 Yate Config Test]]
	* [[OpenBTS: N210 Burn Firmware]]		* [[OpenBTS: N210 Burn Firmware]]

			===RangeNetworks===

			* [[OpenBTS: RangeNetwork Default Setting]]

	===GPRS===		===GPRS===

	* [[OpenBTS: GPRS]]		* [[OpenBTS: GPRS]]
			* [[OpenBTS: GPRS Konfigurasi]]
			* [[OpenBTS: GPRS untuk dibelakang Router dengan NAT]]

			===Briker OpenBTS===

			* [[OpenBTS: Briker]]

			===FreeSWITCH OpenBTS===

			* [[OpenBTS: FreeSWITCH]]

	===Power Amplifier===		===Power Amplifier===
Line 446:		Line 474:
	* http://youtu.be/6LCuoeI57ak (5/6)		* http://youtu.be/6LCuoeI57ak (5/6)
	* http://youtu.be/-dEqcHoIlYk (6/6)		* http://youtu.be/-dEqcHoIlYk (6/6)
			* http://www.youtube.com/watch?v=Ff_rw4kAOZg&feature=share

			===Perjuangan OpenBTS===

			* http://www.technologyreview.com/news/522371/how-remote-places-can-get-cellular-coverage-by-doing-it-themselves/?utm_campaign=socialsync&utm_medium=social-post&utm_source=twitter



	[[Category: Wireless]]		[[Category: Wireless]]
	[[Category: Selular]]		[[Category: Selular]]

Onnowpurbo: /* Monitor the host network traffic */

2013-07-30T23:34:30Z

Monitor the host network traffic

Onnowpurbo: /* Communication Problems */

2013-07-30T23:31:52Z

Communication Problems

← Older revision		Revision as of 23:31, 30 July 2013
Line 111:		Line 111:
	When setting up a development machine for the first time, you may have various difficulties communicating with the USRP device. The following tips are designed to help narrow down and diagnose the problem.		When setting up a development machine for the first time, you may have various difficulties communicating with the USRP device. The following tips are designed to help narrow down and diagnose the problem.

	RuntimeError: no control response		===RuntimeError: no control response===

	This is a common error that occurs when you have set the subnet of your network interface to a different subnet than the network interface of the USRP device. For example, if your network interface is set to 192.168.20.1, and the USRP device is 192.168.10.2 (note the difference in the third numbers of the IP addresses), you will likely see a 'no control response' error message.		This is a common error that occurs when you have set the subnet of your network interface to a different subnet than the network interface of the USRP device. For example, if your network interface is set to 192.168.20.1, and the USRP device is 192.168.10.2 (note the difference in the third numbers of the IP addresses), you will likely see a 'no control response' error message.

	Fixing this is simple - just set the your host PC's IP address to the same subnet as that of your USRP device. Instructions for setting your IP address are in the previous section of this documentation.		Fixing this is simple - just set the your host PC's IP address to the same subnet as that of your USRP device. Instructions for setting your IP address are in the previous section of this documentation.
	Firewall issues
			===Firewall issues===

	When the IP address is not specified, the device discovery broadcasts UDP packets from each ethernet interface. Many firewalls will block the replies to these broadcast packets. If disabling your system's firewall or specifying the IP address yields a discovered device, then your firewall may be blocking replies to UDP broadcast packets. If this is the case, we recommend that you disable the firewall or create a rule to allow all incoming packets with UDP source port 49152.		When the IP address is not specified, the device discovery broadcasts UDP packets from each ethernet interface. Many firewalls will block the replies to these broadcast packets. If disabling your system's firewall or specifying the IP address yields a discovered device, then your firewall may be blocking replies to UDP broadcast packets. If this is the case, we recommend that you disable the firewall or create a rule to allow all incoming packets with UDP source port 49152.
	Ping the device
			===Ping the device===

	The USRP device will reply to ICMP echo requests. A successful ping response means that the device has booted properly and that it is using the expected IP address.		The USRP device will reply to ICMP echo requests. A successful ping response means that the device has booted properly and that it is using the expected IP address.

Onnowpurbo: /* Multiple devices per host */

2013-07-30T23:30:59Z

Multiple devices per host

← Older revision		Revision as of 23:30, 30 July 2013
Line 89:		Line 89:
	USRP2 device IPv4 address: 192.168.20.2		USRP2 device IPv4 address: 192.168.20.2

	Change the USRP2's IP address		===Change the USRP2's IP address===

	You may need to change the USRP2's IP address for several reasons:		You may need to change the USRP2's IP address for several reasons:

	to satisfy your particular network configuration		* to satisfy your particular network configuration
	to use multiple USRP2s on the same host computer		* to use multiple USRP2s on the same host computer
	to set a known IP address into USRP2 (in case you forgot)		* to set a known IP address into USRP2 (in case you forgot)

	Method 1: To change the USRP2's IP address, you must know the current address of the USRP2, and the network must be setup properly as described above. Run the following commands:		Method 1: To change the USRP2's IP address, you must know the current address of the USRP2, and the network must be setup properly as described above. Run the following commands:

Onnowpurbo: /* Setup host interface */

2013-07-30T22:36:43Z

Setup host interface

← Older revision		Revision as of 22:36, 30 July 2013
Line 67:		Line 67:
	sudo ifconfig <interface> 192.168.10.1		sudo ifconfig <interface> 192.168.10.1

	~~Note that~~ <interface> ~~is usually something like eth0~~. ~~You can discover the names of the network interfaces in your computer by running ifconfig without any parameters:~~		Untuk mengetahui nama <interface> yang ada di komputer kita. Jalankan perintah

	ifconfig -a		ifconfig -a

	~~Note~~: ~~When using~~ UHD software, ~~if an~~ IP address ~~for the~~ USRP2 ~~is not specified~~, ~~the~~ software ~~will use~~ UDP broadcast ~~packets to locate the~~ USRP2. ~~On some systems~~, ~~the~~ firewall ~~will block~~ UDP broadcast ~~packets~~. ~~It is recommended that you change or disable your~~ firewall ~~settings~~.		Catatan: Jika menggunakan UHD software, jika IP address dari USRP2 tidak di berikan, software akan mengunakan paket UDP broadcast untuk melokalokasi USRP2 yang ada. Di beberapa sistem, firewall akan memblok paket UDP broadcast. Sangat di rekomendasikan jika kita dapat mengubah atau mendisable setting firewall tersebut.

	===Multiple devices per host===		===Multiple devices per host===

Onnowpurbo: /* Setup the host interface */

2013-07-30T22:29:12Z

Setup the host interface

← Older revision		Revision as of 22:29, 30 July 2013
Line 58:		Line 58:
	Akan tetapi, interface 10/100 Mbps dapat tersambung langsung ke USRP2 melalui Gigabit Ethernet switch.		Akan tetapi, interface 10/100 Mbps dapat tersambung langsung ke USRP2 melalui Gigabit Ethernet switch.

	===Setup ~~the~~ host interface===		===Setup host interface===

	~~The~~ USRP2 ~~communicates at the~~ IP/UDP ~~layer over the~~ gigabit ethernet. ~~The default~~ IP address ~~of the~~ USRP2 is 192.168.10.2. ~~You will need to configure the~~ host's Ethernet interface ~~with a static~~ IP address ~~to enable communication~~. An address of 192.168.10.1 ~~and a~~ subnet mask of 255.255.255.0 ~~is recommended~~.		USRP2 berkomunikasi pada layer IP/UDP melalui gigabit ethernet. Default IP address USRP2 192.168.10.2. Kita perlu mengkonfigurasi host Ethernet interface dengan statik IP address agar dapat berkomunikasi.
			Di rekomendasikan untuk menggunakan address 192.168.10.1 dan subnet mask 255.255.255.0.

	~~On a~~ Linux ~~system~~, ~~you can~~ set ~~a static~~ IP address ~~very easily by using the 'ifconfig' command~~:		Di Linux, set statik IP address dapat menggunakan perintah:

	sudo ifconfig <interface> 192.168.10.1		sudo ifconfig <interface> 192.168.10.1

Onnowpurbo: /* Setup Networking */

2013-07-30T22:03:50Z

Setup Networking

← Older revision		Revision as of 22:03, 30 July 2013
Line 53:		Line 53:
	Jika berada di safe-mode, device USRP-N selalu mempunyai IP address 192.168.10.2.		Jika berada di safe-mode, device USRP-N selalu mempunyai IP address 192.168.10.2.

	==Setup ~~Networking~~==		==Setup Jaringan==

	~~The~~ USRP2 ~~only supports~~ Gigabit Ethernet ~~and will not work with a~~ 10/100 Mbps ~~interface~~. ~~However~~, a 10/100 Mbps ~~interface can be connected indirectly to a~~ USRP2 ~~through a~~ Gigabit Ethernet switch.		USRP2 hanya mendukung Gigabit Ethernet dan tidak akan bekerja dengan LAN 10/100 Mbps.
	Setup the host interface		Akan tetapi, interface 10/100 Mbps dapat tersambung langsung ke USRP2 melalui Gigabit Ethernet switch.

			===Setup the host interface===

	The USRP2 communicates at the IP/UDP layer over the gigabit ethernet. The default IP address of the USRP2 is 192.168.10.2. You will need to configure the host's Ethernet interface with a static IP address to enable communication. An address of 192.168.10.1 and a subnet mask of 255.255.255.0 is recommended.		The USRP2 communicates at the IP/UDP layer over the gigabit ethernet. The default IP address of the USRP2 is 192.168.10.2. You will need to configure the host's Ethernet interface with a static IP address to enable communication. An address of 192.168.10.1 and a subnet mask of 255.255.255.0 is recommended.
Line 69:		Line 71:

	Note: When using UHD software, if an IP address for the USRP2 is not specified, the software will use UDP broadcast packets to locate the USRP2. On some systems, the firewall will block UDP broadcast packets. It is recommended that you change or disable your firewall settings.		Note: When using UHD software, if an IP address for the USRP2 is not specified, the software will use UDP broadcast packets to locate the USRP2. On some systems, the firewall will block UDP broadcast packets. It is recommended that you change or disable your firewall settings.
	Multiple devices per host
			===Multiple devices per host===

	For maximum throughput, one Ethernet interface per USRP2 is recommended, although multiple devices may be connected via a Gigabit Ethernet switch. In any case, each Ethernet interface should have its own subnet, and the corresponding USRP2 device should be assigned an address in that subnet. Example:		For maximum throughput, one Ethernet interface per USRP2 is recommended, although multiple devices may be connected via a Gigabit Ethernet switch. In any case, each Ethernet interface should have its own subnet, and the corresponding USRP2 device should be assigned an address in that subnet. Example:

Onnowpurbo: /* Device recovery and bricking */

2013-07-30T22:00:42Z

Device recovery and bricking

← Older revision		Revision as of 22:00, 30 July 2013
Line 43:		Line 43:
	Tool dapat ditemukan di: <install-path>/share/uhd/utils/usrp_n2xx_simple_net_burner		Tool dapat ditemukan di: <install-path>/share/uhd/utils/usrp_n2xx_simple_net_burner

	==Device ~~recovery and~~ bricking==		==Menyelamatkan Device dan bricking==

	~~Its possible to put the~~ device ~~into an unusable state by loading bad images~~. ~~Fortunately~~, ~~the~~ USRP-N Series ~~can be booted into a~~ safe (read-only) ~~image~~. ~~Once booted into the~~ safe image, ~~the~~ user ~~can once again~~ load ~~images onto the~~ device.		Kadang kala device masuk ke kondisi tidak stabil karena load image yang jelek / gagal. Untungnya, USRP-N Series dapat di boot ke safe image (read-only). Setelah boot ke safe image, user dapat sekali lagi load image ke device.

	~~The~~ safe-mode ~~button is a pushbutton switch~~ (S2) ~~located inside the enclosure~~. To boot ~~into the~~ safe image, ~~hold-down the~~ safe-mode ~~button while power-cycling the~~ device. ~~Continue to hold-down the button until the front-~~panel ~~LEDs blink and remain solid~~.		Tombol safe-mode adalah tombol (S2) yang berada di dalam kotak.
			Untuk boot ke safe image, tekan tombol safe-mode saat kita menyalakan device.
			Terus tekan tombol sampai kedipan LED di panel depan selesai dan menjadi nyala terus menerus.

	~~When in~~ safe-mode, ~~the~~ USRP-N ~~device will always have the~~ IP address 192.168.10.2.		Jika berada di safe-mode, device USRP-N selalu mempunyai IP address 192.168.10.2.

	==Setup Networking==		==Setup Networking==

Onnowpurbo: /* Burning image tanpa Python */

2013-07-30T21:46:13Z

Burning image tanpa Python

← Older revision		Revision as of 21:46, 30 July 2013
Line 41:		Line 41:
	Untuk user yang tidak ingin menginstalasi Python, sebuah script baru tersedia di UHD 003.005.000: USRP N2XX Simple Net Burner. Tool ini memberikan fungsi yang sama dengan tool dari Python, tapi secara default, dia akan automatis menginstalasi image default tanpa kita perlu menspesifikasikan lokasinya di command line.		Untuk user yang tidak ingin menginstalasi Python, sebuah script baru tersedia di UHD 003.005.000: USRP N2XX Simple Net Burner. Tool ini memberikan fungsi yang sama dengan tool dari Python, tapi secara default, dia akan automatis menginstalasi image default tanpa kita perlu menspesifikasikan lokasinya di command line.

	~~The utility can be found at~~: <install-path>/share/uhd/utils/usrp_n2xx_simple_net_burner		Tool dapat ditemukan di: <install-path>/share/uhd/utils/usrp_n2xx_simple_net_burner

	==Device recovery and bricking==		==Device recovery and bricking==

← Older revision		Revision as of 23:34, 30 July 2013
Line 137:		Line 137:

	Use Wireshark to monitor packets sent to and received from the device.		Use Wireshark to monitor packets sent to and received from the device.
	Addressing the Device
	Single device configuration		==Addressing the Device==

			===Single device configuration===

	In a single-device configuration, the USRP device must have a unique IPv4 address on the host computer. The USRP can be identified through its IPv4 address, resolvable hostname, or by other means. See the application notes on device identification. Use this addressing scheme with the single_usrp interface.		In a single-device configuration, the USRP device must have a unique IPv4 address on the host computer. The USRP can be identified through its IPv4 address, resolvable hostname, or by other means. See the application notes on device identification. Use this addressing scheme with the single_usrp interface.
Line 144:		Line 146:
	Example device address string representation for a USRP2 with IPv4 address 192.168.10.2:		Example device address string representation for a USRP2 with IPv4 address 192.168.10.2:

	addr=192.168.10.2		addr=192.168.10.2

	Multiple device configuration		===Multiple device configuration===

	In a multi-device configuration, each USRP device must have a unique IPv4 address on the host computer. The device address parameter keys must be suffixed with the device index. Each parameter key should be of the format <key><index>. Use this addressing scheme with the multi_usrp interface.		In a multi-device configuration, each USRP device must have a unique IPv4 address on the host computer. The device address parameter keys must be suffixed with the device index. Each parameter key should be of the format <key><index>. Use this addressing scheme with the multi_usrp interface.

	The order in which devices are indexed corresponds to the indexing of the transmit and receive channels.		* The order in which devices are indexed corresponds to the indexing of the transmit and receive channels.
	The key indexing provides the same granularity of device identification as in the single device case.		* The key indexing provides the same granularity of device identification as in the single device case.

	Example device address string representation for 2 USRP2s with IPv4 addresses 192.168.10.2 and 192.168.20.2:		Example device address string representation for 2 USRP2s with IPv4 addresses 192.168.10.2 and 192.168.20.2:

	addr0=192.168.10.2, addr1=192.168.20.2		addr0=192.168.10.2, addr1=192.168.20.2

	Using the MIMO Cable		==Using the MIMO Cable==

	The MIMO cable allows two USRP devices to share reference clocks, time synchronization, and the Ethernet interface. One of the devices will sync its clock and time references to the MIMO cable. This device will be referred to as the slave, and the other device, the master.		The MIMO cable allows two USRP devices to share reference clocks, time synchronization, and the Ethernet interface. One of the devices will sync its clock and time references to the MIMO cable. This device will be referred to as the slave, and the other device, the master.

	The slave device acquires the clock and time references from the master device.		* The slave device acquires the clock and time references from the master device.
	The master and slave may be used individually or in a multi-device configuration.		* The master and slave may be used individually or in a multi-device configuration.
	External clocking is optional and should only be supplied to the master device.		* External clocking is optional and should only be supplied to the master device.

	Shared ethernet mode		===Shared ethernet mode===

	In shared Ethernet mode, only one device in the configuration can be attached to the Ethernet.		In shared Ethernet mode, only one device in the configuration can be attached to the Ethernet.

	Clock reference, time reference, and data are communicated over the MIMO cable.		* Clock reference, time reference, and data are communicated over the MIMO cable.
	Master and slave must have different IPv4 addresses in the same subnet.		* Master and slave must have different IPv4 addresses in the same subnet.

	Dual ethernet mode		===Dual ethernet mode===

	In dual Ethernet mode, both devices in the configuration must be attached to the Ethernet.		In dual Ethernet mode, both devices in the configuration must be attached to the Ethernet.

	Only clock reference and time reference are communicated over the MIMO cable.		* Only clock reference and time reference are communicated over the MIMO cable.
	The master and slave must have different IPv4 addresses in different subnets.		* The master and slave must have different IPv4 addresses in different subnets.

	Configuring the slave		===Configuring the slave===

	In order for the slave to synchronize to the master over MIMO cable, the following clock configuration must be set on the slave device:		In order for the slave to synchronize to the master over MIMO cable, the following clock configuration must be set on the slave device:

	uhd::clock_config_t clock_config;		uhd::clock_config_t clock_config;
	clock_config.ref_source = uhd::clock_config_t::REF_MIMO;		clock_config.ref_source = uhd::clock_config_t::REF_MIMO;
	clock_config.pps_source = uhd::clock_config_t::PPS_MIMO;		clock_config.pps_source = uhd::clock_config_t::PPS_MIMO;
	usrp->set_clock_config(clock_config, slave_index);		usrp->set_clock_config(clock_config, slave_index);

	==Alternative stream destination==		==Alternative stream destination==