NF/ Observatory Networking with Linux
The WNMU Node is NFO's connection to the Internet. The eth0 interface is an NE2000 card connected to Western New Mexico University's system. The eth1 interface is the Wavelan card that talks to both the Pinos Altos Node and to the David's Basement Node. Wavelan works very well over the one mile path to David's Basement. The WNMU Node is unique in that it must act as the proxy server for the computers not directly connected to WNMU's system. Check the arp settings in the following rc.local file:
#! /bin/sh echo "setting ttyS2 to irq 5" /bin/setserial /dev/ttyS2 irq 5 echo "sending commands to TNC" sleep 1 /bin/stty 9600 clocal < /dev/cua2 /bin/echo -ne "\300\001\025\300" > /dev/cua2 /bin/echo -ne "\300\002\377\300" > /dev/cua2 /bin/echo -ne "\300\003\004\300" > /dev/cua2 /bin/echo -ne "\300\004\004\300" %gt; /dev/cua2 /bin/echo "Commands to TNC done..." #echo "setting /dev/ttyS3 to irq 11" #/bin/setserial /dev/ttyS3 irq 11 /sbin/ifconfig eth0 18.104.22.168 /sbin/ifconfig eth1 22.214.171.124 echo "Starting WWW Server" /etc/httpd echo "Attaching AX25 link to Radio Port" /sbin/axattach -s 9600 /dev/ttyS2 KC5ZG-1 sleep 1 /sbin/ifconfig sl0 126.96.36.199 /sbin/ifconfig sl0 mtu 512 /sbin/route -n add 188.8.131.52 eth1 /sbin/route -n add 184.108.40.206\ gw 220.127.116.11 eth1 /sbin/route -n add 18.104.22.168\ gw 22.214.171.124 eth1 /sbin/route -n add 126.96.36.199\ gw 188.8.131.52 eth1 /sbin/route -n add 184.108.40.206\ gw 220.127.116.11 eth1 /sbin/route -n add 18.104.22.168 eth0 /sbin/route -n add default gw 22.214.171.124 eth0 /sbin/route -n add 126.96.36.199 eth0 /sbin/route -n add 188.8.131.52 sl0 /sbin/route -n add 184.108.40.206 sl0 /sbin/route -n add 220.127.116.11 gw 18.104.22.168\ sl0 /sbin/route -n add 22.214.171.124 gw 126.96.36.199\ sl0 /sbin/route -n add 188.8.131.52 gw 184.108.40.206\ sl0 /sbin/route -n add 220.127.116.11 eth1 /sbin/route -n add 18.104.22.168 gw 22.214.171.124\ sl0 /sbin/route -n add 126.96.36.199\ gw 188.8.131.52 eth1 /sbin/route -n add 184.108.40.206 eth1 /sbin/route -n add 220.127.116.11 gw 18.104.22.168\ sl0 /sbin/route -n add 22.214.171.124 gw 126.96.36.199\ sl0 /sbin/route -n add 188.8.131.52 gw 184.108.40.206 sl0 echo "Clearing stale file locks" rm /etc/mtab~ rm /nos/spool/mail/*.lck rm /nos/spool/mqueue/*.lck rm /nos/spool/*.lck echo "Publishing wnmu arp entries" /sbin/arp -s 220.127.116.11 00:c0:df:46:b1:b6 pub /sbin/arp -s 18.104.22.168 00:c0:df:46:b1:b6 pub /sbin/arp -s 22.214.171.124 00:c0:df:46:b1:b6 pub
The ham radio equipment for this node is similar to that used at the NF/ Ranch Node with the exception the the transceiver which is a TEKK data radio. In its spare time www.wnmu.edu also acts as the web server for the University and NFO.
This node is located in the basement of a Victorian mansion in downtown Silver City. It is the mail server for the observatory and connects the Wavlan part of the network to a coaxial cable Ethernet that is the LAN for the computers we use for teaching an advanced astronomy class. These computers are located near the astro mansion. The data reduction computer is also on the Ethernet LAN and is in a house around the corner from the astro mansion. rc.local looks like this:
#! /bin/sh /sbin/ifconfig eth1 126.96.36.199 echo "Adding routes" #/sbin/route -n add 188.8.131.52 sl0 #/sbin/route -n add 184.108.40.206 gw 220.127.116.11 sl0 /sbin/route -n add 18.104.22.168 eth1 /sbin/route -n add default gw 22.214.171.124 eth1 /sbin/route -n add 126.96.36.199 eth0 /sbin/route -n add 188.8.131.52 eth0 /sbin/route -n add 184.108.40.206 eth0 /sbin/arp -s 220.127.116.11 00:40:95:26:76:fb /sbin/arp -s 18.104.22.168 00:40:95:26:77:ab echo "Publishing wnmu arp entries" /sbin/arp -s 22.214.171.124 00:40:95:14:ea:41 pub /sbin/arp -s 126.96.36.199 00:40:95:14:ea:41 pub /sbin/arp -s 188.8.131.52 00:40:95:14:ea:41 pub /sbin/arp -s 184.108.40.206 00:40:95:14:ea:41 pub /sbin/arp -s 220.127.116.11 00:40:95:14:ea:41 pub /sbin/arp -s 18.104.22.168 00:40:95:14:ea:41 pub /sbin/arp -s 22.214.171.124 00:40:95:14:ea:41 pub /sbin/arp -s 126.96.36.199 00:40:95:14:ea:41 pub /sbin/arp -s 188.8.131.52 00:40:95:14:ea:41 pub /sbin/arp -s 184.108.40.206 00:40:95:14:ea:41 pub /sbin/arp -s 220.127.116.11 00:40:95:14:ea:41 pub /sbin/route add 18.104.22.168 gw 22.214.171.124\ eth1 /sbin/route add 126.96.36.199 gw 188.8.131.52\ eth1
I Hope I've provided enough detail in this article to help others set up their own wide area network. Some of the ham radio information will be useful only to licensed amateur radio operators, but the Spread Spectrum devices are available to everyone.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Tech Tip: Really Simple HTTP Server with Python
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide