Unpack your new BeagleBone Black, connect it to your network and power it up with a 5V, 2A Walwart. A Debian OS is pre-loaded on the onboard MMC, which is configured to acquire a dynamic IP address from your router / DHCP server. The procedure in this document does not involve downloading any image, burning it to an SD card, etc., the procedure is designed to assist you with taking a new BBB out of the box and getting it online in about 30 minutes.
On our test system, we determined the IP address from the router’s list of DHCP clients and then used an SSH client (such as PuTTy: http://www.chiark.greenend.org.uk/~sgtatham/putty/ ) to login remotely (port 22).
The BBB / base Debian install does not have a root password. Please change it with the ‘passwd’ command. Choose a strong password – a combination of letters and numbers do not forget it!
Should you have a BBB with an existing system on it you can download the Debian Emmc Flasher image at http://beagleboard.org/latest-images. As of the date of producing this document, the image that we recommend is "Debian (BeagleBone Black - 2GB eMMC) 2014-05-14 ". Write the image onto a 2Gig or larger card and insert it into the BBB and power it up – further instructions can be found in the “Getting Started” section of the “Start” menu on the beagleboard webpage. Once the image has been copied to the eMMC, the BeagleBone will power off.
At this point, remove the SD card before powering up the BBB again.
This image does not have a root password. You must login as debian using the default password temppwd. Then change the root password using this command and follow the prompts.
sudo passwd root
Changing the password for the debian user is recommended. So after you have done the above password change just type the following command and follow the same prompts.
passwd
You can then login and follow instructions below.
Network Setup
Most current BBB images (armhf excepted) have usb networking enabled. If you install the drivers and follow instructions available at http://beagleboard.org/getting-started you can login to your BBB via the usb network at 192.168.7.2. You will still need to plug in your BBB to you internet connected wired network to finish the install.
Ramesh Dhami, VA3UV
Page 2 of 13
Appendix F covers how to manage wifi networks. Do not comment out any wlan0 in the interfaces file if you plan to connect to wireless networks.Ready …. Let’s Start!
Plug-in your dvrptr board, GMSK modem, or Red DVAP – reboot and then check to make sure that it is recognized by your BBB. Note once you reboot, you will need to login using your new (static) IP address as set in the preceding section.
Once you’ve rebooted – check to ensure that your BBB ‘sees’ your DVRPTR board (or GMSK modem / DVAP):
root@beaglebone:/tmp# lsusb
Bus 001 Device 002: ID 03eb:2307 Atmel Corp. ← DVRPTR Board 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
Next download the install script and run it:
cd /tmp
wget http://va3uv.com/hp/Free-Star-BBB-C-setup.sh
root@beaglebone:/tmp# chmod +x *.sh
Now run the script:
root@beaglebone:/tmp# ./Free-Star-BBB-C-setup.sh
root@beaglebone:/tmp# date Fri Oct 31 14:35:17 UTC 2014
The script will start by updating the operating system and installed packages on your BeagleBone. You will see a prompt something like the following – press ‘Y’ or ‘y’ to accept:
After this operation, 263 kB of additional disk space will be used. Do you want to continue [Y/n]? y ← select y
Need to get 559 kB of archives.
After this operation, 1026 kB of additional disk space will be used. Do you want to continue [Y/n]? y ← select y
Next – the script will prompt you to select your locales for keyboard layout, etc., [*] en_US.UTF-8 UTF-8
Archive: ircDDB_124_linux.zip
replace IRCClient.cpp? [y]es, [n]o, [A]ll, [N]one, [r]ename: A ← select A
Archive: libber.zip
replace dstar_dv.cpp? [y]es, [n]o, [A]ll, [N]one, [r]ename: A ← select A Please enter the callsign of your Gateway (Repeater):
VA3UV ← If you do not have a unique repeater callsign, you can enter your own personal callsign
Please enter the password provided by the ircDDB-team to enter the system:
1234 (type 1234 for a personal hotspot, where you do not have a unique repeater callsign. In cases where you do have a unique repeater callsign and you wish to connect to the production IRCDDB network, please enter your Gateway password as issued to you by the IRCDDB team)
Ramesh Dhami, VA3UV
Page 4 of 13
10.11.0.127
Please enter your personal callsign (as reg'd on USROOT): VA3UV
Now configuring the GMSK Repeater Software
Please Enter the RF Band --> Enter A for 1.2GHz
Enter B for 440MHz Enter C for 144MHz
Select A, B or C
Is your system Half Duplex (Simplex) or Full Duplex? Enter H for Half Duplex OR F for Full Duplex
Select H or F
FREE STAR* supports four types of repeater interface
A hardware based GMSK Modem (Satoshi, Fred, Mark, Jim, etc...)
the German or Canadian DVRPTR Board v1 Board with v1 Firmware
the Red DVAP
and the German or Canadian DVRPTR v1 or v2 Board with XDVRPTR Firmware
Please select which one of the four scenarios is to be used on your system
Enter G for GMSK Modem
Enter D for DVRPTR - v1 Board with v1 Firmware
Enter P for the Red DVAP
Enter X for DVRPTR v1 or v2 Board with XDVRPTR Firmware
Select which one of the 4 scenarios applies to you. In my case, I have a DVRPTR board, so I will select ‘D’
That’s it…. Your system configuration is complete.
root@beaglebone:/tmp# date
Fri Oct 31 11:05:20 EDT 2014 (30 mins from start to finish!)
Next – before you can use your DVRPTR board, or DVAP – you need to find the serial number – example for the dvrptr board:
Ramesh Dhami, VA3UV
Page 6 of 13
103114 at 11:07:08:Device /dev/ttyACM0 has serial=[12.50.D0.27]103114 at 11:07:08:Closing device /dev/ttyACM0
103114 at 11:07:08:Cant find any FREE ACMx device that matches
<CTRL> c to stop / exit out of the log file.
Now take the above serial # and enter it into your dvrptr.cfg file (in /root/dvrptr folder) –
cd /root/dvrptr nano –w dvrptr.cfg
# Your serial number
DVRPTR_SERIAL=12.50.D0.27 ← Enter the # that you recorded in the previous step
<CTRL> c to exit
Restart the dvrptr service – service dvrptr restart
Monitor the log file:
root@beaglebone:~/dvrptr# tail -f /var/log/dvrptr.log 103114 at 11:11:56:
--- STATUS READ FROM MODEM ---
103114 at 11:11:56:Bit1 : Transmitter enabled = 1 103114 at 11:11:56:Bit2 : PC Watchdog enabled = 0 103114 at 11:11:56:Bit3 : Checksum-Calculation enabled = 0 103114 at 11:11:56:Bit4 : I/O 21 Status = 0
103114 at 11:11:56:Bit5 : I/O 23 Status = 0 103114 at 11:11:56:Bit6 : Duplex-Capability = 1 103114 at 11:11:56:Bit7 : (1) physical layer = 0 103114 at 11:11:56:---
103114 at 11:12:12:From RF: flags=40:00:00, myCall=VA3UV /91AD, yrCall=CQCQCQ , rpt1=VA3UV B, rpt2=VA3UV G
103114 at 11:12:12:End RF, ber=0.50
103114 at 11:12:18:From RF: flags=40:00:00, myCall=VA3UV /91AD, yrCall=CQCQCQ , rpt1=VA3UV B, rpt2=VA3UV G
103114 at 11:12:19:End RF, ber=0.11
If your transmissions are not being decoded, you may need to toggle the RX polarity in the dvrptr.cfg file. Conversely, if you’re not receiving audio from your system, you may need to toggle the TX audio polarity. These are the last 2 lines in the dvrptr.cfg file – e.g:
# These values depend on what type of transceiver is connected to your DV-RPTR modem # Use either 0 or 1
RX_Inverse=1 TX_Inverse=1
After making a change to the dvrptr.cfg file, you will need to restart the dvrptr service – i.e:
service dvrptr restart
Dashboard – the setup script will install the dashboard for you. By default, the webserver listens on port 5088. You can access the dashboard using your local IP address – example:
Ramesh Dhami, VA3UV
Page 8 of 13
You should see something like this:Firewall / Router Settings
Forward the following ports on your router / firewall to the static address that you assigned to your BeagleBone or Raspberry Pi:
TCP 5088 for web / dashboard (optional) UDP 20001 (Optional for personal hotspots) UDP 30001 (Optional for personal hotspots) UDP 40000 (Required for peer-to-peer routing)
Notice that the SSH port has not been listed above, this is entirely optional – however, before enabling remote access, we strongly recommend that you change the SSH port to something other than the default port 22.
The SSH port can be changed in the SSH config file (found in /etc/ssh/sshd_config):
# What ports, IPs and protocols we listen for Port 22 ← Change to something else
Save / Exit and then restart the sshd daemon – service ssh restart
Personal Hotspots
In cases where you do not have control over your firewall / router – e.g., a hotel, public WiFi, etc., you can connect to XRF and REF reflectors using port 20001 (i.e., using the dplus protocol) which is NAT friendly.
To do this, you will need to edit the gwys.txt file (in /root/g2_link) and change the port number for XRF reflectors from 30001 to 20001 – example:
Ramesh Dhami, VA3UV
Page 10 of 13
XRF000 141.22.15.29 30001 Change the port from 30001 to 20001XRF001 75.76.90.90 30001 XRF002 91.201.57.233 30001 XRF003 95.110.157.83 30001 XRF004 96.36.58.9 30001 XRF005 216.16.240.236 30001 XRF006 80.62.20.151 30001 XRF007 84.232.6.94 30001 XRF008 95.110.231.219 30001 XRF009 141.22.15.29 30001 XRF010 87.106.48.7 30001 XRF011 87.106.3.249 30001 XRF012 96.126.101.188 30001 Save / Exit
Next using crontab, edit out this entry so that your gwys.txt file does not get overwritten automatically – e.g:
# update gwys.txt for g2_link
#5 6 * * * /root/my_scripts/get_gwy_list.sh > /var/log/get_gwy_list.log 2>&1 Save / Exit – then restart cron using: service cron restart
Restart g2_link: service g2_link restart
Editing g2_ircddb.cfg
You will need to edit the g2_ircddb.cfg file (in the /root/g2_ircddb folder) to update your Gateway coordinates and frequency - as shown below:
# This is for APRS/GPS SEND_APRS=Y
# The repeater module specifications
# LATITUDE,LONGITUDE,RANGE,DESCRIPTION
# If you do NOT want to define the aprs parameters for a module, # then leave the line BLANK
RPTR_ID_A=
RPTR_ID_B=43.5930,-79.78917,10,FREE STAR* DV 443.8125 +5.00 MHz RPTR_ID_C=43.5930,-79.78917,10,FREE STAR* DV 147.5400 +0.00 MHz
← EDIT the above lines to suit your location / frequencies. If you only have one module, leave the other 2 lines blank (do not delete them!)
# Which local address on your Linux box will be used
# to report to the remote IRC database server(group2, group1,...) # For most installations it is 0.0.0.0 (which binds to all local IP addresses)
# If you have more than one ethernet card, then you may set it to a specific local IP # that is assigned to that specific ethernet card
# If you have one ethernet card, you can use 0.0.0.0 LOCAL_IRC_IP=0.0.0.0
# This is for the Live IRC site SEND_QRGS_MAPS=Y
Ramesh Dhami, VA3UV
Page 12 of 13
QTH=43.5930, -79.78917, Mississauga ON, BeagleBone, www.freestar.us ← EDIT to suit# Frequency, shift, range, antenna's height above ground(agl) QRG_A=
QRG_B=443.8125, 5, 10, 20 ←EDIT these 2 lines.
QRG_C=147.540, -0.0, 10, 20 ← If you only have one module, leave the other 2 lines blank
Once you have edited this file, save / exit... then restart g2_ircddb as follows:
NOTE: By default, the g2_ircddb configuration has been set to use the FREE-STAR IRC server cluster. If this is a personal hotspot (in cases where you do not have a unique repeater callsign), do not change it. However, if you do have a unique repeater callsign and have a password issued from the IRCDDB team, please change the IRC_DDB_HOST and password fields to suit.
service g2_ircddb restart
Dashboard
The dashboard is updated via a scheduled cron job. You may want to either change the update interval or modules reported, etc. This can be done by accessing the crontab editor:
crontab -e to get to the crontab editor.
Example:
# Webpage updates
*/2 * * * * /root/g2_link/g2_lh -m "BC" -o /var/run/lighttpd/index.html -a 192.168.1.124 -b "VE3URU D-STAR" -t /root/g2_link/g2_lh.tpl VE3URU
The -m switch denotes which modules your system has - in the example above, I have module B and C; if your system has (for example, just one module say, module C, you will specify –m “C” or –m “B” for module B.
The -a switch denotes the IP address (if you change your IP at a later time, you will need to update this)
The -b switch denotes the banner tag - edit to suit
Log Files
For troubleshooting, you may wish to enable logging; this can be done by editing the following: Package Enable Logging (By Editing) Log File
g2_ircddb /etc/init.d/g2_ircddb /var/log/g2_ircddb.log
g2_link /etc/init.d/g2_link /var/log/g2_link.log
rptr /root/rptr/rptr.sh /var/log/rptr.log
dvrptr /root/dvrptr/dvrptr.sh /var/log/dvrptr.log
dvrptr2 /root/dvrptr/dvrptr2.sh /var/log/dvrptr2.log
dvap_rptr /root/dvap_rptr/dvap_rptr.sh /var/log/dvap_rptr.sh
We recommend disabling logging once your system is online and stability has been confirmed.
That’s it – welcome to the FREE STAR* project.
Please drop me a note ([email protected]) so that I can add you to my mailing list for system updates, notices, etc.
Ramesh Dhami, VA3UV
Page A1
Appendix A
Radio Settings
The following sections are intended to be used as a guide when programming user radios. Of course the repeater callsigns will need to be modified for your particular system.
Simplex Access Points
ICOM radios do not send RPT1 and RPT2 information in the DV data stream when the radio is in simplex mode. We therefore have to program the radio as follows:
Mode = DV
Duplex enabled (set for + or – DUP)
Set the offset frequency to Ø
URCALL = CQCQCQ
RPT1 = callsign of the simplex access point followed by the module (e.g., VE3RSD B)
RPT2 = callsign of the simplex access point followed by ‘G’ for Gateway (e.g., VE3RSD G).
Note that the ICOM G2 protocol reserves six (6) characters for the callsign. The module / gateway suffix is entered into the eighth (8th) position. Thus a system with a five character callsign will require two spaces in the 6th and 7th position – e.g:
Ramesh Dhami, VA3UV
Page A3
RPT1 = VA3ZZ<space><space>B RPT2 = VA3ZZ<space><space>G.
Repeater Systems
Mode = DV
Duplex enabled (set for + or – DUP)
Set the offset frequency as required (e.g., 5MHz for UHF) – this should already be set as the default.
URCALL = CQCQCQ
RPT1 = callsign of the repeater followed by the module (e.g., VA3PMO B)
Appendix B
DTMF Shortcuts
Ramesh Dhami, VA3UV
Page B2
The FREE STAR* solution supports DTMF dialing to connect and disconnect from reflector systems. The table below summarizes the DTMF syntax in comparison to traditional ‘URCALL’ radio programming:
Action URCALL DTMF
Link to XRF005A XRF005AL #00501
Link to REF016B REF016BL *01602
Link to DCS006B DCS006BL D00602
Link to DCS014K DCS014KL D01411
Link to ICOM repeater WC7SO module C
WC7SO<space>CL N/A
Query Link Status I (in the 8th position) 99
Disconnect U (in the 8th position) 73
The last two digits of the DTMF string represent the numerical equivalent of the remote module that you wish to connect to. This was a necessary change, which accompanied g2_link 3.05 in order to accommodate DCS reflectors, which have 26 modules (five weren’t enough!).
To link your repeater module to an ICOM G2 system running dplus, set URCALL = the repeater callsign, followed by the module in the 7th position and the command in the 8th position of URCALL – e.g., to link to WC7SO module C, set URCALL = WC7SO CL. Note that there is a space between the ‘O’ and ‘C’ since WC7SO is a five letter call.
Appendix C
Callsign Routing
Ramesh Dhami, VA3UV
Page C2
Callsign Routing
Callsign routing is a powerful feature of the G2 protocol that allows users to establish
communication with each other without the need to know which repeater each user is on. This is very handy when a particular user may be taking a long road trip traversing multiple repeater footprints.
Callsign routing – does however, require users to be on the same ircDDB server – whether it be on the same production network, or other test servers. Note the FREE STAR* IRC servers support callsign routing as well as DTMF initiated routing. Please contact us for details.
Callsign (or G2) routing relies on ‘last heard’ information in the ircDDB network (i.e., the last heard position) for each user. Hence when a user traverses multiple repeaters, it is imperative that the user transmits at least once on each repeater so that the repeater can report his / her presence on that repeater to the ircDDB network. This of course relies on each repeater running some form of ircDDB client.
Important Note: The ircDDB Gateways cache the last heard information (user callsign along with gateway callsign and gateway IP address. Callsign routing requests trigger the software to first query the local cache for the remote callsign. If the remote callsign is not available from the local cache, the initial routing request will fail. However, the software queries the ircDDB server for the remote callsign and last heard information making it available for a subsequent routing request – in most cases this will be available within seconds of the first (failed) request.
To contact a user using Callsign (or G2) routing, both users must set each other’s callsign in the URCALL field. The following example illustrates a G2 routing call between VA3UV and
VA3UV Radio Settings WA1SOT Radio Settings
URCALL WA1SOT VA3UV
RPT1 VE3RSD C KB1UAP B
RPT2 VE3RSD G KB1UAP G
The above settings should remain in effect for the entire QSO. When making the initial call, it is important to state that you are using callsign routing so that the station you are calling can use the ‘one-touch’ (RX>CS) feature on ICOM radios to reply. The ‘RX>CS’ button forces the received callsign to be populated into the URCALL field so that when the remote user replies, his call will be routed back to you.
Please note that callsign routing may be initiated at any time, even when the local repeater (or access point) module is connected to a reflector. Using a URCALL value other than ‘CQCQCQ’ blocks data from going out over the reflector. So in the above example, if VA3UV is connected to reflector XRF005A, he can initiate the call to Jim, WA1SOT, using callsign routing as shown above. The call to Jim will not be heard by the users / repeaters connected to the reflector. It will however be broadcast out on the repeater module where Jim was last heard.
Once the call has been established, both parties should disconnect from any reflector or repeater that they may be connected to. This avoids the possibility of clashing / interfering packets coming off the reflector while the repeater is busy.
Callsign routing is very powerful; with the recent addition of ircDDB, it can be used to enable communication between users on home-brewed systems and ICOM G2 systems – providing that the ICOM G2 system is running the ircDDB add-on software.
Ramesh Dhami, VA3UV
Page D1
Appendix D
PRS is a process used to convert raw GPS data into TNC2 formatted APRS messages. D-PRS processing capability is included in g2_ircddb. FREE STAR* systems are therefore able to receive, process, and report position reports from mobiles, portables, command posts, etc., to the APRS-IS server network via a TCP socket over the public Internet.
D-PRS support must be enabled by setting the ‘SEND_APRS’ parameter (in /root/g2_ircddb/g2_ircddb.cfg) to ‘Y’.
The example below illustrates the beacon parameters for a simplex system operating on 2m (port ‘C’)
SEND_APRS=Y RPTR_ID_A= RPTR_ID_B=
RPTR_ID_C=XX.XXXX,-YY.YYYY,ZZ,FREE STAR* DV 147.540 -0.00 MHz
XX.XXXX corresponds to the ‘LATITUDE’ in decimal degrees, use a negative number for the southern hemisphere.
YY.YYYY corresponds to the ‘LONGITUDE’ in decimal degrees, use a negative number for the western hemisphere.
ZZ is the coverage area (radius) in miles.
FREE STAR* DV 147.540 -0.00 MHz is the beacon message; replace 147.540 with your repeater frequency, followed by the offset +/- in MHz as shown.
Ramesh Dhami, VA3UV
Page D3
The FREE STAR* team supports the older style GPS and GPS-A format. Some of the earlier D-STAR radios such as the ID-800 and IC-91AD do not support GPS-A format and therefore are confined to the older GPS format. One of the advantages of the older style GPS format is that it continually sends GPS data in the slow speed data accompanying each transmission. This allows remote users to monitor your position and distance, etc., on their radio(s).
The table below illustrates the 2820 menu hierarchy:
DV GPS GPS Sentence RMC ON
GGA ON
Everything else OFF
GPS Message See 1 below
RX GPS Message Data: _____________
GPS-TX See 2 below
GPS Auto TX: OFF (see 3 below)
GPS-A SET MODE UNPROTO ADDR API282,DSTAR* (see 4
below)
DATA EXTENSION COURSE/SPEED
TIME STAMP HMS
GPS-A SYMBOL <Select to suit> COMMENT (DATA EXT) <Your comment>
1. For ‘GPS’ mode, the GPS-TX message is a combination of the symbol, status text message and a checksum. Please use the D-PRS Calculator from Peter Loveall (AE5PL) to determine the GPS-TX message.
2. Set to ‘GPS’ for the older style GPS format, or GPS-A for the newer GPS-A format. 3. GPS Auto TX: By setting GPS Auto TX to ‘OFF’ this will only send out your position data
when you manually transmit. Auto-beaconing should not be enabled when connected to a reflector as the beacon will generate traffic over the reflector causing disruption to all users of that reflector / linked repeaters, etc.
4. UNPROTO: Format is APInnn where ‘nnn’ is the first 3 digits of your radio model # (e.g., 800, 880, 282). In the case of the IC-80, IC91 and IC92, set the UNPROTO to API80 / API91 / API92.
Ramesh Dhami, VA3UV
Page D5
NOTE: Unlike conventional APRS, SSID’s are not supported in DPRS. The solution to this is to use a terminal suffix. For example, a station can have a home-based APRS station with the call VA3XYZ. If the same user were to use a mobile APRS or DPRS station with the same callsign, this would conflict with the home-based station. Thus a second terminal will be required – e.g., ‘VE3XYZ M’ (Note the ‘M’ is the terminal, which is specified in the 8th position of the user’s ‘MyCall’ settings).
ICOM IC-92AD Setup – Information supplied by Colin, VE3MSC:
The table below illustrates the 92AD menu hierarchy:
Press “MENU” and then scroll using the red arrows (up ^ on 8 key and down v on 2 key) to DV SET MODE, and press Enter (5 key).
DV SET MODE DV DATA TX PTT
- if you wish to send your
position/comment when you push to talk. Good for battery saving.
AUTO
- will send periodically based on GPS AUTO TX setting (described below)
DV SET MODE GPS TX MODE GPS-A
Then press Enter (5 key) or RIGHT > (6 key) for GPS-A SET, for the following sub-menu:
GPS-A SET MODE UNPROTO ADD API92,DSTAR*
DATA EXTENS COURSE/SPEED
GPS-A SYMBO <Select to suit> OTHER: /[ for Jogger You will need to hit the 3 key red a/A to get the right character set.
COMMENT (EXT) <Your comment>
Then escape back out to the DV SET MODE menu by pressing LEFT < (4 key) a couple of times. Then scroll down to GPS AUTO TX
DV SET MODE GPS AUTO TX OFF
You will also want to adjust your preferences and time zone offset.
Press “MENU” and then scroll using the red arrows (up ^ on 8 key and down v on 2 key) to MESSAGE/POS and press Enter (5 key)
MESSAGE/POS GPS SET MOD
Scroll to GPS SET MOD and press Enter. The following sub-menu will appear:
GPS SET MODE GPS SPEED 4800 seems to be default
for use with the HM-175GPS SP/MIC
FORMAT ddd° mm’ ss”
Ramesh Dhami, VA3UV
Page D7
UNITS m = Metres in Canada
ft/ml = for USA feet miles
Personal preference.
COMPASS DIR NORTH REF
UTC OFFSET -05:00 for Eastern Standard
Time. Remember to change it for daylight saving time, e.g. -04:00 for EDT. This is important!
The same comments apply re., use of a terminal ‘suffix’ to avoid conflict of position updates with (for example) a home based station with the same callsign. The procedure below illustrates the addition of a second terminal ‘P’ for portable use.
For example:
Press “MENU” and scroll up to CALL SIGN.
CALL SIGN VA3XYZ P Do this only if you need to
specify a terminal. If this is your only rig on
APRS/DPRS then you don’t need to do this.
Conventions used: P for Portable M for Mobile
Note the terminal suffix is specified in the 8th position
Ramesh Dhami, VA3UV
Page E1
Appendix E
Edit the /etc/network/interfaces file – commands as follows:
cd /etc/network nano –w interfaces
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5).
# The loopback network interface auto lo
iface lo inet loopback
# The primary network interface
#allow-hotplug eth0 ← Replace these 2 lines with the contents of the box below #iface eth0 inet dhcp ←
# Example to keep MAC address between reboots #hwaddress ether DE:AD:BE:EF:CA:FE
# The secondary network interface #allow-hotplug eth1
#iface eth1 inet dhcp
# WiFi Example #auto wlan0
Ramesh Dhami, VA3UV
Page E3
#iface wlan0 inet dhcp# wpa-ssid "essid" # wpa-psk "password"
# Ethernet/RNDIS gadget (g_ether)
# ... or on host side, usbnet and random hwaddr
# Note on some boards, usb0 is automaticly setup with an init script < if your home network uses this network addressing you will need to edit this address or comment out these settings if not used for usb networking.
iface usb0 inet static address 192.168.7.2 netmask 255.255.255.0 network 192.168.7.0 gateway 192.168.7.1 # Static IP address auto eth0
iface eth0 inet static
address 192.168.1.10 ← edit this block
netmask 255.255.255.0
network 192.168.1.0 ← 4th octet is 0
broadcast 192.168.1.255 ← 4th octet is 255
gateway 192.168.1.1 ← your router address
dns-nameservers 192.168.1.1 8.8.8.8 8.8.4.4 ← your router address first
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5).
# The loopback network interface auto lo
iface lo inet loopback
# The primary network interface #allow-hotplug eth0
#iface eth0 inet dhcp
# Example to keep MAC address between reboots #hwaddress ether DE:AD:BE:EF:CA:FE
# static IP address auto eth0
iface eth0 inet static address 192.168.0.125 netmask 255.255.255.0 network 192.168.0.0 broadcast 192.168.0.255 gateway 192.168.0.1 dns-nameservers 192.168.0.1 8.8.8.8 8.8.4.4
Ramesh Dhami, VA3UV
Page E5
#allow-hotplug eth1#iface eth1 inet dhcp
# WiFi Example #auto wlan0
#iface wlan0 inet dhcp # wpa-ssid "essid" # wpa-psk "password"
# Ethernet/RNDIS gadget (g_ether)
# ... or on host side, usbnet and random hwaddr
# Note on some boards, usb0 is automatically setup with an init script iface usb0 inet static
address 192.168.7.2 netmask 255.255.255.0 network 192.168.7.0 gateway 192.168.7.1
Appendix F
Wireless Networks
Managing wireless networks can be endless headaches when connecting to multiple networks. If you have a compatible wifi adapter (this document does not cover unsupported adapters) you can easily manage these networks using a utility called wicd-curses. To install you need to run the following command as root
apt-get install wicd-curses ifconfig
Note the names of your adapters, usually you have eth0 (wired) and wlan0 (wireless)
Running wicd-curses as root you should see the following screen with different networks of course
Press shift+P to set the interfaces for wired and wireless from what you noted above with the ifconfig. Press shift+R to refresh the display. Use the arrow keys to move up or down to the get the wireless network you wish to connect to highlighted and press the enter key. Use the arrow keys again to move to the automatic connect selection box and use the spacebar to check it. Move to the password entry field and enter the wifi password. Press F10 to save settings. Now you have the network configured for automatic connection. To connect highlight the configured network and press shift+C.
You will need to do this for each network you wish to automatically connect to. USB networking is recommended in order to manage these on the “road”.
Ramesh Dhami, VA3UV
Page F2
Some connections require a web browser to activate your connection (ie hotel). Once you have the connection established as above you can then open a pseudo web browser on your BBB. To install this use the following command as root.apt-get install links2
Run the links2 command and attempt to open a web page (press g and enter the page url) and if your connection requires additional configuration you should be presented with it there. If things do not display properly run links2 with the -g switch (starts with a graphical mode). Once you have the required information set up you can verify you have internet access using the browser (navigate to a web page) or attempt a connection to the reflector.
This allows you to also monitor your status page.
For all wifi networks that you do not have access to manage firewall settings you need to change any ports for reflectors you want to connect to from 30001 to 20001 as described in the “Personal Hotspots” section.
