Star OS V3 Valemount Networks Corporation Lonnie Nunweiler, President
Copyright 2006, Valemount Networks Corporation and David A. Bandel, all rights reserved.
FCC Regulatory Compliance All Lucaya Wireless Advanced Routers have been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions may cause harmful interference to radio communications.
Table of Contents Getting Started.............................................................................................................................. ...............7 Section 1...................................................................................................................... .....................7 Loading your system....................................................................................... .......................7 Installing via RAW image............................
SSH client........................................................................................... ........................28 Telnet client........................................................................................................... ......28 System Console.............................................................................. ............................29 The Interfaces Menu....................................................................................................... ......
Virtual Distribution System (VDS) Setup...............................................................................50 Creating an Ethernet Bridge..................................................................................... ..50 Routing Menu........................................................................................................................................... 52 Configuring routing...................................................................................................
Cables................................................................................................................... ..........................85 Ethernet/POE cables................................................................................ ............................85 Antenna cables.................................................................................................................... ..86 Antennas......................................................................................
Chapter 1 Getting Started This chapter will deal with your first exposure to StarOS v3. Section 1 will show you how to load StarOS onto your WRAP or WAR board or upgrade your board from V2 to V3. Section 2 will then take you through a few first essential steps so you can start using your StarOS router. All attempts have been made to make getting started as easy as possible. The same can be said about subsequent chapters, but only you can judge how successful we've been.
Section 2 Initial Configuration Once the system starts, you can log in from a console or via SSH on your network. By default, StarOS will start up with the default IP 192.168.1.1 on the first ethernet port and a default gateway of 192.168.1.254. You need to login via SSH (ssh or dropbear client in UNIX or putty.exe in Windows) and use the username admin with password 1234. You'll be greeted with a trial screen (unless an activation key was entered for you).
fig 1: License Entry Dialog fig 2: Sample VNC Request Key screen
In Windows, you should be able to use a shift+left mouse button and drag to select, and shift+right mouse button to paste. In UNIX using X, you'll need to experiment, but shift+left mouse button and drag selects, and shift+middle mouse button for paste has worked for me. This may be window manager dependent, your mileage may vary. The unlock key will be a GPGtype key. Just paste into the box and select Accept.
Changing Network information Select interfaces > ether1 > ip assignments to change the IP address. The box will allow you to create, remove, edit, or disable/enable an IP address. You can tab between fields if not using a mouse, or use the +hotkey combination to select the appropriate field. (see fig 4) fig 4: Interfaces menu While here, look at the bottom of the box labeled “Ethernet Bridge Number (19, 0=disabled)”.
fig 5: device configuration screen If you've made this interface part of a bridge, you'll want to include other interfaces as part of the bridge, so select interfaces > wpci1 (substituting your desired bridge interface here) > ip assignments, and put a 1 in the Ethernet Bridge box. Now go to the routing dropdown and select static and default routes. Edit the gateway to correspond to the gateway of the IP you assigned to the Ethernet interface. For more details, see page 38.
fig 6: wireless dropdown fig 7: wireless configuration
The BSS channel can be either a channel number (as shown in the Available Channels box to the right) or the frequency in megahertz. You must select a valid channel number or frequency. Selecting an invalid channel number or frequency will result in the system using the lowest frequency in that range. The Custom checkbox will force the system to use only those frequencies shown in the Custom Scan List. You can remark out the entries and put select frequency lists (one list or frequency per line).
The Network Type determines whether the system will act as a client or Access Point. Pointtopoint only is not supported. However, if you need a wireless bridge, see page 39, Creating an Ethernet Bridge. Operating mode determines if you are operating as 8011.b (2.4GHz DSSS), 802.11g (2.4GHz OFDM), or 802.11a (5.x GHz OFDM), a mixed or homogeneous b/g network, and whether these modes use turbo mode or not (802.11g and 802.11a only).
After you've done all the above, you're ready to begin testing your system. The changes made above will only get you started. You've probably noticed nothing has actually changed yet. Changing the IP address didn't disconnect you. So you'll need to activate the changes you made above. Select the File pulldown menu (see fig 9). In it you'll see: save changes, activate changes, reboot machine, and exit. You may save your changes at any time.
fig 9: file dropdown Both activate changes and reboot machine will prompt you to save any changes. If you say No, a reboot will reset the system to its state just after the last time you saved your configuration. This, combined with the system > services > ping watchdog, can save you a long trip if a change you made prevents access to a remote system. On bridges and routers Most wireless systems are bridges by design.
be implemented to ensure packets don't run around in circles accidentally (STP is enabled by default in StarOS). Bridges are also not as scalable as routers. If you anticipate extensive growth, you might be better served starting off using routing. Another problem with wireless bridges is that while APs are true bridges, clients are psuedobridges and use proxy arp to simulate a bridge.
Chapter 2 The Main Window This chapter will look at information presented on the main screen. (see fig 1) This information will differ slightly depending on your equipment and its function. So we'll look at what information is presented and its importance to your wireless network. fig 1: main window The Menu Bar The menu bar allows access to all of the StarOS configuration functions. Anything you can do or configure, you'll find in the menu bar.
Generic Information Below the menu bar, you'll see information regarding StarOS. Normally this will be StarV3(tm) Advanced Wireless Platform. Below the brand should appear the system name inside square brackets. This is the fully qualified domain name (hostname.domain.tld) of your system and can be changed by selecting Advanced > dns server list. In the hostname: box put just the hostname of the system. In the domain box put the domain name with the top level domain.
turned off. Most of these services have corresponding items in one of the menus, but some don't (at least not directly). Wireless Devices The wireless devices header section lists Qual(ity), Signal, Noise, Rate, Freq(uency) Mode, and Link Information. In client mode, all these fields will contain associated information. In AP mode, less information is shown, link specific details can be found in the Interfaces > wpci# > wireless configuration> client list.
Chapter 3 File and System Menus This chapter will address the two smallest dropdown menus, the File menu dropdown and the System menu dropdown. These two dropdowns are among the smallest, but most important of the dropdowns. Section 1 File Menu The file menu dropdown will be one of your most used dropdowns as you configure and test your system. Nearly all functions will require activation to make the system start using them (see fig 1).
Activate changes After making a change that is not immediate in nature, you must activate it for it to take effect. When selected, you will be presented a dialog box asking if you want to save the changes, not save the changes, or cancel. Not saving the changes permits you to test a feature that may disconnect you when activated. This option, combined with the system > services> ping watchdog, will allow you to recover access to a remote system should the new configuration not work as anticipated.
Section 2 System menu While not often used, the system menu is, nonetheless, important as it changes essential parameters (see fig 2).
Services Five services are available for configuration/activation under this menu: DNS cache server, SNMP agent, DHCP server, Ping Watchdog, and PPPOE server (see fig 3). Each service has a configuration box to allow you to choose to restart the daemon on reboot (don't forget to issue a file > save changes command after making these changes, no file > activate required). The services also have a service activation option to perform an immediate start/stop/restart of the daemon.
to reenable it before activating (but not saving) questionable changes. It might save you a long drive. You can also use it if you're making changes that might cause you to lose access to a remote system. Using the watchdog with the file > activate and selecting “no” when asked to save changes has saved me more than once from a long drive or climbing back up a tower.
fig 5: PPPOE bootup/configuration dialog fig 6: PPPOE Radius setup
Configure background color The first option allows you to configure the background color. At this time, your choices are between black and blue. Foreground colors remain the same. Change password This option allows you to change the system password. You'll need to know the old password to make the change. The default password for the admin user is 1234. This should be changed before the system is deployed. Update / Enter License Key This is where you enter the system key.
System Console A new feature available in V3 is a system console (see fig 7). The system console is designed for those more comfortable with a command line than a menu system. fig 7: system console Upon entering the system console, you'll see the warplatform prompt. Typing “?” will show you what commands are available. This is also true if you enter the system directory by typing “system”. To change directories back up, you can enter “exit” or “..”.
It is also possible to enter the system console through the serial port. Presented below are a few comments about the CLI commands available in the shell. The ip command will permit you to enter via console and check/change the ip address on any system. For those not familiar with ip, just issue the command you want with “show”. Commands may also be abbreviated.
Chapter 4 The Interfaces Menu The interfaces menu will allow you to do a wide range of networking setups, including choosing to bridge interfaces, and create virtual distribution systems (VDS) – more on that later. Only the barest of basics was covered in the Getting Started chapter. Much of what is here is new. But first, the basics. Configuring Interfaces The Interfaces menu is split into three sections (see fig 1).
beginning with 0 in the usual UNIX custom. Device submenus Each physical device has a submenu to provide access to various configuration items. (see fig 2). fig 2: physical devices submenu IP assignments Most systems will require at least one of your devices to have an IP address. While it is possible for a bridged system to run without an IP address, access to the system would then only be possible via the serial port (if available).
fig 3: IP assignments box The main box shows any IPs assigned to the interface with the subnet mask in VLSM (CIDR) notation, followed by the beginning of any comment you may have for that card. If no IPs are assigned to an interface, this box will have the notation . IPs that are disabled are shown by an asterisk in front of the IP. To perform a function on an IP, select that line then the function you want to perform to the right.
need at least 18 devices to create this many bridges). Bridge number 0 disables bridging for the device. Use either Close or to leave the box and return to the main menu. In either case, all changes remain, but must be activated using the File>Activate menu to take effect. Any changes not saved will not remain through a reboot. Wireless Configuration The wireless configuration menu is now part of the interface menu to which it pertains (see fig 4).
fig 5: wireless card configuration screen ESSID This is where you'll put your network name. ESSID stands for Extended Service Set Identification, ESSID. You have space for a 16 digit alphanumeric sequence, but I suggest you don't extend it that far. Choose a unique name that is representative of your system, either its location or function, that is short. After all, you'll have to type it into all your client radios (or select it when the signal is seen). BSS Channel The base station system channel.
The Custom Scan list can be edited. A # sign will act as a remark. You may enter one frequency per line to only scan certain frequencies or put two hyphen separated frequencies as shown in the Custom Scan List to scan a range, one range per line. Transmit Rate (mbps) The transmit rate refers to the connection speed you want the radios to connect at. The default is auto, and the cards will autobaud to the best speed depending on conditions (noise, SNR, etc.). You can preset a speed to lock systems in.
connector. This facilitates running your AP or client at the optimum power setting without exceeding EIRP maximums for your area. A word of caution: setting the dbm to 0 will not provide 1mW output power as you might expect, but will set the card to its default power setting. The default is normally 15dbm (generally between 3035mW) for most cards. Also, not all cards are capable of running at 1W (30 dbm). Check your cards specifications for default and maximum power.
InterBSS Relay If you want clients to be able to communicate between each other when connected to the same AP, you'll need to enable this setting. When checked, clients can talk to other clients. When unchecked, clienttoclient traffic is suppressed. Outdoor Only When selected, any frequencies that, by regulation (according to the chosen country code) can only output reduced power levels, are considered indoor frequencies and will be removed from the Available Channels list.
WEP Security submenu WEP (Wireless Encryption Protocol) has been shown to have serious defects. But using it is definitely better than not. Combined with other authentication mechanisms, WEP helps keep your data private. But if you need real data security, you'll be better off building encrypted tunnels. The VDS menu under interfaces can do this. But if you need many tunnels, consider building them through your radios rather than between them. Meanwhile, select the best WEP encryption you can.
Note that MAC address spoofing can bypass your access controls. An ACL isn't foolproof, but adds yet another layer of control. fig 7: Access Control List Client List The client list, shown on the AP as the client display list (see fig 8) shows details of all clients as well as the state of the AP itself.
fig 8: Association List/Client display list The first line shows the network name (unless changed). Subsequent lines show client names if input. This is followed by the MAC address (last two words only, the first four are suppressed in the interests of space). Then comes the last IP seen passing through the AP from that client, again, only the last two octets are shown to conserve space. The next several fields describe the connection itself.
Site Survey The site survey, greyed out when in AP mode (because this really does only make sense in station mode), shows sites the system knows about because it has seen them (see fig 9). fig 9: site survey Where sites do not have an ssid showing (ssid: “”), it is because that APs essid is hidden. The rest of the information shown should be selfexplanatory.
Ethernet Configurations Like the wireless cards, the ethernet cards also have ethernet settings peculiar to them, which may be accessed and changed via the Interfaces > ethernet# > ethernet configuration link (see fig 10) Ethernet Link Settings This will bring up a dialog box showing the current mode of the ethernet port, and options to change it. By default, the ethernet port will do autonegotiation. This can be turned off, and the speed (10Mb or 100Mb) may be specified, as well as full duplex or not.
Interface Features Any given interface currently has three features that my be activated (see fig 11). fig 11: interface features If the System > Service > PPPOE Server setup is used and you want to allow PPPOE connections on this interface, then this should be turned on. When the status of a particular interface is changed from off to on or vice versa, the PPPOE server must be restarted.
fig 12: dhcp autoauth configuration Basically, the information is the same as for any DHCP server, with the exception that you have two checkboxes: use radius, and create hotspot session. These permit a RADIUS server to perform authentication, and the session created by autoauth be a “hotspot session”. The Lease Duration is in seconds, the default of 1700 corresponding to 28 minutes. Other entries should be selfexplanatory.
fig 13: autoauth configuration menu
Beacon real-time traffic monitor The beacon realtime traffic monitor (see fig 2) will allow you to see visually communications passing through the selected interface. Selecting this option presents the user with the box shown in fig 14. First select those options you want to display. Always displayed is the rate or count. If no display options are selected before selecting Start, only one line will be displayed showing the selected rate or count.
DHCP Client Information If and only if this interface is a dhcp client, then you can access information regarding the active lease. or renew the lease information (see fig 15). This is grayed out when dhcp client is not active. fig 15: dhcp client information/renewal 802.1q Virtual Lan (VLAN) Setup The VLAN setup is accessed from the interfaces menu (see fig 2). When selected, a setup box appears (see fig 16). VLAN's are frames that carry special tags in the headers.
keep the traffic separated.
Virtual Distribution System (VDS) Setup The Virtual Distribution System (VDS) is basically a VPN that permits the creation of a virtual circuit from one end to another. VDS will allow you to create an ethernet bridge between any two radios, but unlike most ethernet bridges you purchase, with VDS you can have several radios in between. See below for how to create an ethernet bridge between two radios. First, select interfaces>virtual distribution system (vds) setup. Then select create new vds (see fig 17).
fig 17: vds submenu fig 18: vds setup box
Chapter 5 Routing Menu While a very short menu, it is an important one. It would be difficult to do much of anything without routing. Configuring routing The routing menu is split into two parts (see fig 1). The upper part is basic routing and routing daemons. The lower part is advanced and policy routing. Since it is unlikely you'll have a system without at least a default route, we'll start there. The rest will follow.
If you disable a route, the route will have a '*' following the line number, as in fig 2 below. fig 2: Static routes configuration box Dynamic Routing Selecting dynamic routing (rip, ospf & mesh) provides you with an option to use one of the dynamic routing methods available in StarOS.
fig 3: dynamic routing daemons startup/shutdown screen Once started, you can access the configuration menu (see fig 4) by selecting “Configure”. In the case of OSPF, you should at least configure the default route. For those of you familiar with Cisco console menus, the routing daemon console menus function in the same way (see fig 4). When in doubt, entering a question mark '?' will provide a context sensitive list of available options. Also for those familiar with Cisco, the same shortcuts exist, e.g.
fig 4: daemon configuration console fig 5: olsr configuration console
Policy and Advanced Routing The policy and advanced routing section allows you to do some funky routing tricks (see fig 6). Policy routing allows you to route different networks out different gateways, such as if you have two downstream providers. You can route each ones packets out correctly. Advanced routing works similarly, but uses firewall marks (see Advanced menu chapter) to route packets.
Chapter 6 Advanced Menu Without doubt, this menu will be the most used of all, particularly the last three items. Don't let the “Advanced” label scare you. A number of these items are extremely important to troubleshooting. fig 1: the Advanced menu dropdown Configuration notes Here, you can record anything you want in narrative form about this radio. Completely optional, but a good idea for those who may need to look at this radio after you've been promoted.
Static ARP Static ARP allows you to remap the arp table for directly connected hosts. Instructions are simple. Be careful with this, or you may be wondering why some hosts cannot be contacted. This should only be necessary for clients you haven't been able to reconfigure for your network and who have an IP hard coded.
802.1d Bridging Options Spanning tree protocol is used to prevent bridge loops. Unlike router loops, bridge loops could theoretically never time out because unlike routers, bridges do not decrement the TTL counter. If you have anything more than a simple ethernet bridge, you should leave STP enabled. The defaults suffice for most. The benefits of using STP far outweigh the detrimental effects of turning it off when it's needed. fig 3: 802.
DNS Server List The DNS server list configuration menu allows you to assign a name to your system and tell it which DNS servers to use. While in many instances you might think this unnecessary, you'll find that services like the dropbear SSH server respond more quickly with it. It also allows you to check connectivity using the ping and traceroute utilites with names vice IP only, and the ability to resolve names with tcpdump.
Connection Tracking Setup Connection tracking setup is required for NAT. If you use NAT, you'll need to enable this, and you'll want to review which protocol helpers are enabled. If you don't enable the protocol helpers for these particular protocols, you'll find those protocols won't work properly for NATed clients. The FTP helper is for active FTP sessions. Passive FTP session (such as those set up by most web browsers) will work just fine. The IRC helper is for Internet Relay Chat.
Connection Table Size The connection tracking table size configuration menu is used if you need to increase the size of your connection tracking table (used for NAT). Since each connection must be tracked to be properly routed back to clients, this table must be large enough to accommodate all simultaneous connections. Old connections are dropped after a period of time.
NTP and Zone configuration If you configure nothing else, consider configuring your NTP server. Keeping your radios in time sync helps track problems in the logs, since they use the time according to the radio. If you've configured your DNS servers (above) and don't have ntp, openntp, chrony, or other ntp daemons running on a system local to your network, you can always use the publicly available pool.ntp.org servers. Each time ntp starts, it will query pool.ntp.org and use one of the available ntp servers.
Remote Syslog Using a remote syslog is highly recommended for troubleshooting because StarOS does not save syslog entries between reboots. To prepare for doing this, you'll need to set up a central logging server that starts the syslog daemon with the r option. This will open UDP port 514 and accept syslog input from external hosts. To prevent DOS attacks, use a packet filter (pf in *BSD or iptables in Linux) to block unauthorized hosts.
System Log The system log can be reviewed via the system log box. This log is not saved between reboots or syslog restarts (such as when remote logging is configured, above). So for troubleshooting purposes, using remote logging is a good idea. You can still review the logs here even when using remote logging.
The Scripts Dropdown Submenu The scripts submenu provides access to three areas: bandwidth management (via CBQ), firewall (packet filter) and port forwarding settings, and NAT (static and dynamic masquerading). It also allows you to activate any changes made to scripts. You'll still need to do a File>Save to save the configuration between reboots, but the activate script command activates script changes immediately.
Class Based Queueing script The CBQ script editor will allow you to set up bandwidth control and rudimentary quality of service for various classes of traffic/IPs. The script contains a number of examples, and in general handles setting up the root class for you. While CBQ works well, if you need finer grained control, consider using either HTB (hierarchical token bucket) in a Linux router or AltQ (via pf) in *BSD.
Advanced Firewall and Port Forwarding script With the Advanced firewall script, you can allow or deny classes of traffic based on IP address (source or destination), port, or interface. You can also port forward traffic on one interface to a system behind another interface based on port or IP address.
NAT and Static NAT The NAT and Static NAT script allows you to perform either of static 1:1 mapping, where a number of IPs behind one interface have a 1:1 mapping to other IPs on another interface. But the most common usage by far is to perform “masquerading”, which is to map all private IPs behind one interface to a public IP on another interface. This anonymizes the systems on the private network and prevents direct access to them from the outside.
System Reports The system reports dropdown menu allows you to choose between a report on CBQ traffic and a system information report.
The CBQ Traffic Report The CBQ traffic report will show you the amount of traffic transmitted and received in each individual queue. This will give you a good indication of traffic through this particular radio.
View System Information The system information report will show you what the system knows about itself and connected systems.
Active PPP user list If you are using PPP, your active users will show up in this list.
Network Utilities The heart of network troubleshooting, this will probably be your first stop following complaints of networkrelated problems. This dropdown menu allows you access to ping, tcpdump, and throughput test.
Ping Utility If you really want to know if you have a solid connection, this should be your first stop. The box will accept an IP or DNS hostname, but must have DNS configured (above) to use a hostname to ping. By default, your packet size will be 56 bytes. This, combined with 28 bytes for the header gives you an 84 byte packet. Often, however, the problem is not small packets, but large ones.
Ping response The response box will show you the IP being sent ICMP ping packets, the packet number, the size, the round trip time (RTT), and the percent loss. You should normally not lose packets. If you calculated 1500 byte packets by subtracting the 28 byte header, but see packets of size 1528 being sent, you probably are running a VLAN and didn't compensate. If packets don't pass, somewhere along the route you have an interface that has a 1524 byte limitation.
tcpdump Utility box The tcpdump utility will allow you to see traffic passing through the chosen interface. Note that if you choose a bridged interface, you'll see a lot of traffic not destined for the chosen interface. All valid tcpdump expressions can be used (read the man page for a relatively complete list). You can choose to resolve IP names, but only if you have enabled DNS (above). Be aware that this will slow down your dump and cause you to miss packets because they will be dropped.
tcpdump response box The tcpdump response box will show you the normal, nonverbose output showing a summary of the headers. How to read this dump is beyond the scope of this text, but the man page is an excellent place to start.
Throughput Test Box If you're curious how capable your link is, this is a good place to start. One word of caution, this test is extremely detrimental to network traffic, and should not be used on a production link (unless of course you want to hear a lot of screaming about a slow connection from users).
Throughput Test Response Box The throughput test response box will update every second until the test ends. Throughput is measured in K bytes per second. To find bits per second, multiply the number by 8.
Chapter 7 Configuration, Upgrades, Tips and Tricks StarOS comes with a command line utility called starutil which will allow you to perform a range of operations on a system. This includes but is not limited to, uploading new software, up and down loading the radio's configuration, rebooting remotely, etc. The starutil utility is available from www.staros.com for Windows and Linux. BSD systems can run the Linux binary if that option has been selected during system setup.
Saving and restoring configurations To save a radio's configuration, use the following command: starutil d which will look like this: starutil 192.168.1.1 1234 d radio1.dat To load a radio with a known good configuration, run the following command: starutil u which looks like this: starutil 192.168.1.1 1234 u radio1.dat You can add the a to have the system activate the file upon successful upload.
you running the new version. If you do not continue the upgrade, the radio will continue to boot from the old image. Starutil has a number of other commands, but some of these commands are not available to version 3 of StarOS, at least not yet. For example, getting the status of wireless connections is not supported. Tips and Tricks Some of you may be interested in some quick tips and tricks. If you have a favorite tip or trick, please let us know in the forum.
Chapter 8 Wireless Practices This chapter will focus on a number of pitfalls and ways to ensure you put up good links. Some things will be glossed over a bit. For example, we'll discuss antenna selection, but there's little sense in reproducing hundreds of pages of HAM antenna theory. We will, however, cover in depth how to set up long distance links (the most difficult). So hold on to your hats. Your radio We've covered the basics (and more) of configuring your radio.
has a clear, unobstructed path to the best ground you can afford to put in. So what constitutes a good ground and a clear unobstructed path? Remember when dealing with lightning, that we're talking about static DC discharge of extremely high voltages. Also understand that while lightning is DC, it acts like high frequency AC (basically radio frequency – RF – signal). That means that what we install has to conform to good radio signal passing procedures.
protect them. All that said, Ethernet cables can pick up EMP when strung like a clothesline from a client on a post in the yard to the house. Long horizontal Ethernet cable runs should be buried. Antenna cables Most folks deploying detached antenna systems opt to build their own antenna cables. After all, how hard can it be? Unfortunately, many also opt not to purchase the proper equipment to build the cables. While a crimper is essential, most believe proper cable strippers are not.
signals much better. In the field, nothing beats a good pair of ears. I've seen folks install wireless systems, find the link is weak, and decide the best thing to do is slap an amp on. While their signal improved, for the marginal improvement, they added greatly to the ambient noise, probably interfered with a likeminded operator who will also just slap an amp on, and no one wins. When you use an amplifier, you amplify noise as much as you do signal.
DS they affect it negatively, while for OFDM they have a more positive effect. Anyone who's set up a long pointtopoint across a hot flat expanse of desert using DSSS has probably seen this effect demonstrated very vividly. Your Fresnel zone is a cigarshaped area that is widest in the center. A number of wireless calculators exist on the Internet, including one linked from http://www.pananix.com/ that will calculate your Fresnel zone and more.
Appendix 1 StarOS Country Codes Codes sorted alphabetically by digraph NA AL AE AM AR AT AU AZ BE BG BH BN BO BR BY BZ CA CH CL CN CO CR CY CZ DE DK DO DZ EC EE EG NO_COUNTRY_SET ALBANIA UNITED ARAB EMIRATES ARMENIA ARGENTINA AUSTRIA AUSTRALIA AZERBAIJAN BELGIUM BULGARIA BAHRAIN BRUNEI DARUSSALAM BOLVIA BRAZIL BELARUS BELIZE CANADA SWITZERLAND CHILE CHINA COLOMBIA COSTA RICA CYPRUS CZECH REPUBLIC GERMANY DENMARK DOMINICAN REPUBLIC ALGERIA ECUADOR ESTONIA EGYPT
ES FI FR GB GE GR GT HK HN HR HU ID IE IL IN IR IS IT J1 J2 J3 J4 J5 JO JP K2 KP KR KW KZ LB LI LT LU LV MA MC MK MO MX SPAIN FINLAND FRANCE UNITED KINGDOM GEORGIA GREECE GUATEMALA HONG KONG HONDURAS CROATIA HUNGARY INDONESIA IRELAND ISRAEL INDIA IRAN ICELAND ITALY JAPAN1 JAPAN2 JAPAN3 JAPAN4 JAPAN5 JORDAN JAPAN KOREA REPUBLIC2 NORTH KOREA KOREA REPUBLIC KUWAIT KAZAKHSTAN LEBANON LIECHTENSTEIN LITHUANIA LUXEMBOURG LATVIA MOROCCO MONACO MACEDONIA MACAU MEXICO
MY NL NO NZ OM PA PE PH PK PL PR PT QA RO RU SA SE SG SI SK SV SY TH TN TR TT TW UA US UY UZ VE VN YE ZA ZW MALAYSIA NETHERLANDS NORWAY NEW ZEALAND OMAN PANAMA PERU PHILIPPINES PAKISTAN POLAND PUERTO RICO PORTUGAL QATAR ROMANIA RUSSIA SAUDI ARABIA SWEDEN SINGAPORE SLOVENIA SLOVAK REPUBLIC EL SALVADOR SYRIA THAILAND TUNISIA TURKEY TRINIDAD & TOBAGO TAIWAN UKRAINE UNITED STATES URUGUAY UZBEKISTAN VENEZUELA VIET NAM YEMEN SOUTH AFRICA ZIMBABWE
Codes sorted alphabetically by country NO_COUNTRY_SET ALBANIA ALGERIA ARGENTINA ARMENIA AUSTRALIA AUSTRIA AZERBAIJAN BAHRAIN BELARUS BELGIUM BELIZE BOLVIA BRAZIL BRUNEI DARUSSALAM BULGARIA CANADA CHILE CHINA COLOMBIA COSTA RICA CROATIA CYPRUS CZECH REPUBLIC DENMARK DOMINICAN REPUBLIC ECUADOR EGYPT EL SALVADOR ESTONIA FINLAND FRANCE GEORGIA GERMANY GREECE GUATEMALA HONDURAS HONG KONG NA AL DZ AR AM AU AT AZ BH BY BE BZ BO BR BN BG CA CL CN CO CR HR CY CZ DK DO EC EG SV EE FI FR GE DE GR GT HN HK
HUNGARY ICELAND INDIA INDONESIA IRAN IRELAND ISRAEL ITALY JAPAN JAPAN1 JAPAN2 JAPAN3 JAPAN4 JAPAN5 JORDAN KAZAKHSTAN KOREA REPUBLIC KOREA REPUBLIC2 KUWAIT LATVIA LEBANON LIECHTENSTEIN LITHUANIA LUXEMBOURG MACAU MACEDONIA MALAYSIA MEXICO MONACO MOROCCO NETHERLANDS NEW ZEALAND NORTH KOREA NORWAY OMAN PAKISTAN PANAMA PERU PHILIPPINES POLAND HU IS IN ID IR IE IL IT JP J1 J2 J3 J4 J5 JO KZ KR K2 KW LV LB LI LT LU MO MK MY MX MC MA NL NZ KP NO OM PK PA PE PH PL
PORTUGAL PUERTO RICO QATAR ROMANIA RUSSIA SAUDI ARABIA SINGAPORE SLOVAK REPUBLIC SLOVENIA SOUTH AFRICA SPAIN SWEDEN SWITZERLAND SYRIA TAIWAN THAILAND TRINIDAD & TOBAGO TUNISIA TURKEY UKRAINE UNITED ARAB EMIRATES UNITED KINGDOM UNITED STATES URUGUAY UZBEKISTAN VENEZUELA VIET NAM YEMEN ZIMBABWE PT PR QA RO RU SA SG SK SI ZA ES SE CH SY TW TH TT TN TR UA AE GB US UY UZ VE VN YE ZW
Appendix 2 Network Primer Introduction This appendix is intended to aid novice network technicians understand and build a routed network. This text will not be allencompassing, but is intended to get you over the initial hurdle of subnetting and routing an IPv4 network. Background For those who have been assigned a “Class C” network by their providers, but don't know where to go from here, this text will provide that help. It is really simple once you understand.
these numbers are derived. Additionally, these unique decimal numbers can also be used by your web browser in the URL bar. But the reason we use IP addresses in dotted decimal notation is to help network admins better “see” the contiguous parts of the network (i.e., which IPs are neighbors and which aren't).
0: 00000000 So we can have a netmask that looks like: 255.255.255.224, or 255.255.248.0, or 255.240.0.0. But we cannot have 255.0.240.0 or any decimal number not listed above (e.g., 255.255.255.220). VLSM Notation Along with the use of VLSM and netmasks composed of other than 0 and 255, a new convention was designed to more easily denote these new VLSM subnets. This VLSM notation is nothing more complicated than counting the number of ones in the netmask and showing how many there are.
It's easiest to start at one end or other of the netblock and start carving out the biggest chunks first. So our first two blocks will be the two /27 netblocks. The first is too easy: 192.168.1.0/27. == 192.168.1.0192.168.1.31. Then we have: 192.168.1.32/27 == 192.168.1.32192.168.1.63. Remember, the .0 and .32 addresses are the network addresses; the .31 and .63 are the broadcast addresses. It's best to pick a policy for how to set your gateways.
These two networks have 16 IPs each (2^(3228)). If we divide the upper network's network address by 16, we get 64 / 16 = 4. This number is even and tells us that opening our subnet (i.e., changing our subnet to a /27) will not allow these two subnets to be combined. In fact, if the 192.168.1.64 was opened even further, it would only continue to expand upward, not down into the original 192.168.1.48 network: 64 / 32 = 2. It is only when we get to a /25 suffix, do the two networks in this example combine.
On my principal router I have: Pointtopoint frame relay to my provider (pvc0) ethernet for local distribution and routing (eth0) ifconfig shows me: pvc0: 169.254.19.13/30 eth0: 10.10.1.1/27 eth0:1 192.168.255.1 routing table looks like this: 10.10.1.0/27 10.10.1.1 10.10.1.32/27 192.168.255.2 10.10.1.64/27 192.168.255.3 10.10.1.96/27 192.168.255.4 0.0.0.0/0 169.254.19.14 What the above says is that the network 10.10.1.0/27 is routed locally. Each of the other 10.10.1.
interfaces. While the number of clients I service is small (less than 200), the network covers over 900 square miles.