Setting up a Packet--Internet Gateway Email: wkt@csadfa.cs.adfa.oz.au Warren Toomey VK1XWT -- April 1992 Abstract This paper discusses the reasons for setting up an amateur packet radio to Internet gateway, technical and hardware features of such a gateway, and security aspects of maintaining a gateway. Several sections of this paper require some knowledge of amateur packet radio operation, Internet site operation, connecting hardware, and Internet security. These sections will be marked, and I will try to summarise each section in a manner that does not require this knowledge. This paper is intended for people who have to install a packet-Internet gateway, people who must maintain a packet-Internet gateway (both at the software and hardware level), people who manage a set of Internet machines, and people who provide the facilities for a set of Internet machines (such as a University). This is a wide range of readers, so I apologise in advance if you find some of the material too far below or above your level of understanding. Introduction The Internet is a large network of academic and commercial computers in the United States that provide a number of communication services (such as electronic mail and file transfers) to its users, via the TCP/IP network protocols. This network is connected to other networks, such as the AARNet in Australia, and networks in Europe and Japan, to provide a global computer network. The amateur radio service consists of a large number of individuals (known as amateurs or Hams) throughout the world who use radio communications to pass messages, chat, do research into aspects of radio communications and exchange information with other amateurs on several radio frequencies that are allocated for their use. To become an amateur, an individual must undergo an examination which tests the individual's knowledge of the technical operation of radio equipment, radio propagation, electronic theory, as well as legal and other aspects of amateur radio. Thus amateurs form a highly technical, capable and responsible group of people, who are able to provide communication during emergencies, natural disasters, as well as for their own use. The amateur radio service is also actively involved in finding new and more efficient forms of radio communication - techniques such as single sideband radio and reduced spectrum radio were invented by amateurs. In the last decade or so, amateur radio operators have been involved in researching new forms of digital radio communications. This research has led several amateurs to experiment with different communication protocols for digital radio communications, including the TCP/IP protocols used on the Internet (see Appendix A). The Internet protocols have been found to be very useful for radio networking, and are now used widely by amateurs. To this end, a block of 16,387,064 Internet addresses has been allocated to the worldwide amateur radio service. Fast and effective digital radio communications is limited over large distances, due to the distortion and noise introduced by the atmosphere, and the curvature of the Earth. Amateurs have sought several methods to overcome these limitations, such as amateur satellites, which are designed and built by amateurs, and provide store and forward message capabilities as well as digital repeater services. Another method of overcoming the distance limitation is to use the Internet itself to route digital messages between distant amateur stations. This is easy to accomplish as amateurs are able to use the same network protocols, TCP/IP, as used on the Internet. This method of long-distance amateur communication has been implemented at several places in the world: Australia, America, Switzerland, the Netherlands and Canada, and has been found to be very simple to set up and operate, and is very reliable. There are two legal/policy aspects of these amateur radio--Internet gateways. The first is the amateur radio service enforces that amateur communications must be between two (or more) licensed amateurs: therefore, non-amateur Internet users must not be able to use the gateways to transmit messages. The second is that many AARNet/Internet sites' policy is to prevent non-registered users from accessing local/Internet resources: therefore amateurs may only pass messages to other amateur gateways. The software that controls the packet--Internet gateways has been written to solidly enforce these two conditions. The Gateway A packet--Internet gateway obviously must be able to communicate to both the Internet, and the amateurs in its local area. Therefore, it must have at least two interfaces, one to the Internet, and one to the amateur community. The gateway is a machine that runs the software that enables it to perform its function. Currently, this means that it must be an IBM PC computer or clone, running the latest version of the NOS software by Phil Karn, Gerard van der Grinten, and other flavours. The software itself is freely available, but is copyright by the software authors. For performance reasons, I would recommend a computer with at least the performance of a 10MHz IBM XT, with 640K or memory. An AT of course would be better. If you plan on providing file transfer or mail access, a hard disk is needed. Each interface must have a unique IP address, so that both the local amateurs and the other gateways can communicate with it. The Internet interface's address is assigned by the AARNet/Internet administrator of the institution, and the amateur radio interface's address is assigned by the local amateur IP administrator. Each interface must also have the appropriate hardware needed for it to communicate with its destination. On the amateur radio side, a Terminal Node Controller, a transceiver and anantenna convert the packets from the gateway into radio transmissions that can be received by amateur stations. On the Internet side, there are two main options: anEthernet card connects the gateway to the local area network, which is part of the AARNet/Internet, or a serial line connects the gateway to another machine in the institution which is on the local area network, and hence is part of the AARNet/Internet. The serial line can run either the SLIP or PPP protocol to communicate with the other machine. That completes the overview of the hardware setup of the gateway. This leads on to several considerations: + The gateway and other hardware must bereliable, and be readily available to the maintainer of the gateway to fix unforseen problems. + The gateway must be placed in a physical position to suit both its connection to the AARNet/Internet, and to the TNC/transceiver. + The transceiver and antenna must be in a position to satisfy both the needs of the local amateur community, and the wishes of the institution where they are to be situated. + If using Ethernet, the gateway's position must allow it to be physically connected to the local area network. At this point, it should be mentioned that at least one of the people maintaining the gateway must have a current amateur radio license. The institution providing the Internet connection may also wish to appoint another person to ensure the gateway meets the policies of the institution; this of course may be the same person. How the Gateway Works At an elementary level, the gateway works as follows: Messages are broken up intopackets when they are sent over the Internet. When the gateway receives a packet on one interface, it checks the destination IP address in the packet, and according to its table ofroutes, it retransmits that packet on the interface that will send the packet to its destination. For example, a packet from the local amateur radio community to a gateway in another country will be received by the local gateway, retransmitted by the gateway on its Internet interface, and will travel along the Internet to the destination gateway, where it will be received and retransmitted by the transceiver at that gateway. In practice, this is not as simple, because of the following reason. Even though the global amateur community has been allocated a block of valid Internet addresses, none of the Internet machines in the world know how to send packets to these addresses. This is because up until recently, no amateur computers were connected to the Internet. The easiest solution would be to advertise the routes to these addresses to all Internet machines, but this was not done for the following reasons: + Amateur stations are not as geographically fixed as most Internet computers, as their computers are generally smaller, and the radio medium allows amateurs to move around and still communicate with each other, and + Advertising amateur computer addresses to all Internet machines greatly increases the possibility of non-amateurs accessing amateur transmitters. The solution adopted was to encapsulate amateur packets received by the gateways inside another packet, transmit this bigger packet to the destination gateway, which unwraps the packet and transmits the contents [Woodburn et al. 1991]. The local gateway determines which remote gateway this packet must be passed to, and encapsulates the packet inside a new packet, with source and destination addresses being the Internet addresses of the local and remote gateway. The packet is then placed on the Internet, where it is passed to the remote gateway. This encapsulated packet is seen by the Internet to have a valid source and destination address, and can be passed to the remote gateway. The Internet sees the wrapped packet as data, which it ignores. At the remote gateway, the packet is received and unwrapped; this is the third packet in Figure 2. The remote gateway determines which interface to transmit the unwrapped packet, according to the destination address. Reply messages are encapsulated in exactly the same manner. Security Aspects of Encapsulation The encapsulation method satisfies the security considerations discussed in the Introduction: + Because no Internet machines know how to route packets to amateur gateways, there is no possibility that non-amateur packets will be transmitted on amateur transmitters. + All incoming amateur packets are encapsulated by the local gateway, preventing amateurs from accessing any Internet machines, except for remote gateways. Therefore, amateurs see the connection between the gateways as a very long piece of wire. There are, however, other ways of overcoming these barriers, by using some of the applications built into the gateway software; these can be easily prevented, and are discussed in a later section. AX.25 Encapsulation One of the first digital protocols used by amateurs, and still the most widely used, is AX.25, a reliable protocol based on X.25. One of its limitations is that AX.25 packets cannot pass through more that 7 intermediate machines before reaching their destination. This limits the distance AX.25 packets can travel. The latest versions of NOS include AX.25 encapsulation, which operates in exactly the same way as normal IP encapsulation, thereby allowing long distance AX.25 communication while still obeying the 7 step limit [Kantor 1991]. Preparing the Gateway Machine This section discusses the aspects of preparing the gateway for the software that will make the gateway work. It is assumed that: + You have a fairly good idea of the Internet and how it works. + You have a reasonable understanding of the NOS software. If you don't, you can either obtain a `plug 'n play' disk from me by mailing me a note to my email address at the beginning of the paper, or you can anonymous ftp to the machine minnie.cs.adfa.oz.au, cd to hamradio/packet/plugplay, and get the software from there. + You have a copy of the NOS software dated at least June 1991. Either the ka9q version or the pa0gri will do. The latest version of NOS can be obtained fromucsd.edu, grivel.une.oz.au, or minnie.cs.adfa.oz.au. The `plug 'n play' software mentioned before has the requisite bits. + You have a gateway that meets the hardware specifications given in the Introduction, and the hardware needed to form the interfaces -- that is, a TNC, a transceiver, an antenna, and an Ethernet board or a serial link to a machine on the Internet that can talk SLIP or PPP. The gateway will also need around 1 Megabyte of free disk space if it is to provide file transfer or mail access. + You have a local amateur IP address for the machine, and a local Internet IP address for the machine. Your first step is to give the gateway two domain names, a name for the other gateways to know, and a name for the amateurs to know. Your Internet name should follow any rules specified for your institution. Your amateur domain name should be of the following form: name.callsign.ampr.org where the callsign is the callsign of the amateur that will be operating the gateway, and the name is whatever name you want to call the machine. An example of Internet and amateur domain names is minnie.cs.adfa.oz.au and minnie.vk1xwt.ampr.org. You need to register the Internet name on the Domain Name Server for your local area network. You then need to register your amateur domain name with the Domain Name Server for the amateur service. This is the DNS server at ucsd.edu. To do this, send email to the following address: ampraddr@ucsd.edu. The subject line should be empty, and the email should have the following line: name.callsign. IN A amateur.radio.ip.address For example, the line I sent in for my gateway was: minnie.vk1xwt. IN A 44.136.0.31 Aside: For those who understand DNS records, ucsd.edu will also accept CNAME and MX records. Also, you can delete previous entries by sending the same line, with the last field on the line the word `delete'. Additions and changes to the DNS at ucsd.edu usually take a few days to be entered, so make sure you get things right first. Installing the NOS Software Installing the NOS software can be done in three stages: + Install the software, and set the gateway up as a local amateur radio station; this includes setting up the TNC, transceiver and antenna. This should not be too hard to do, as the local amateur community can provide information on how to do this. + Alter the setup to include an interface to the AARNet/Internet, using either an Ethernet board, or a serial link running SLIP or PPP. You will need an appropriate Ethernet driver if you are using an Ethernet board -- these can be obtained from ucsd.edu in the directory hamradio/drivers. Read the documentation that comes with the driver package. + Finally, set up encapsulated routes to the other amateur gateways, and email their operators so that they will set up routes back to your gateway. Use the `ping', `telnet' and `ftp' commands in NOS to ensure that the encapsulation is working. An example setup file is given in Appendix C, and is currently in use at the minnie.cs.adfa.oz.au gateway. This section will discuss aspects of a gateway's setup that I think need attention. To begin with, the hostname of the gateway should be the gateway's amateur domain name, as it will be used mainly by amateurs. Ensure that the gateway has a valid amateur callsign. Every interface used by the gateway should use the amateur IP address, except for the single interface to the Internet, which should use the Internet IP address. The default route should be the Internet interface, as badly addressed packets will not affect anybody there. Ensure that routes are as specific as possible: for example, if your local amateur address are of the form $44.136.0.x$, then you should add a route to 44.136.0/24. Add ARP entries for both the Ethernet address of the gateway's Ethernet board, and an Ethernet broadcast address for the local area network. Adding Encapsulated IP Routes Adding the encapsulated IP routes to other gateways is very easy, as is shown in the example setup file in Appendix C. Note that you must specify the Internet IP address of the gateway, and not the amateur IP address. Adding Encapsulated AX.25 Routes Due to the implementation aspects of AX.25 encapsulation, each encapsulated AX.25 route appears as a new interface under NOS, and as such, needs to have a new SSID (Station Sequence ID), as well as a new interface name. For example, the pseudo-interfaces used by the minnie gateway have SSIDs vk1xwt-2, vk1xwt-3, vk1xwt-4, vk1xwt-5 and vk1xwt-6. These are different than the callsign used for the gateway, vk1xwt-1. According to the AX.25 protocol, this allows up to 15 pseudo-interfaces, with SSIDs of --1 to --15, as well as the local amateur interface. For AX.25 encapsulation to work, you need to already have an encapsulated IP route defined to the destination gateway, and vice versa. When using the encapsulated AX.25 service, you must remember that you need to use the SSID of the interface you want to connect through. For example, to connect to minnie locally, you would do: net> connect vk1xwt-1 However, to connect to a machine in Hawaii through minnie, you need to use minnie's SSID of --4: net> connect ah6bw-1 vk1xwt-4 Similarly, a user in Hawaii connects to vk1xwt-4, but connects through vk1xwt-1. Other Security Considerations If you use your gateway with no applications running, you can guarantee the security of your gateway. However, with three applications, the mailbox, SMTP and RIP, your security can be breached. Fortunately, two of these three can be set up to prevent security breaches. RIP RIP is the routing protocol that is used to pass routing information around between machines on the Internet. Strictly speaking, a packet--Internet gateway does not need to run RIP, as all of its routes are statically defined. The only reason for a gateway to run RIP is to inform and/or learn from other gateways when new gateways become available. If you think that using RIP is a good idea, you must ensure that: + You do not broadcast your routing table to your local network; if you do, non-amateur machines will learn about routes to the amateur gateways, and may allow non-amateurs to use amateur transceivers. + You refuse all RIP broadcasts from your local network; if you do not, amateurs will learn about the Internet addresses on your local network, which are non-amateur addresses. + You only send your routing table to destination amateur gateways, as they are the only machines who are interested in your routes. I would receommend not running RIP at all. The Mailbox The mailbox application can be accessed in two ways: by a local amateur connecting to your machine using the AX.25 protocol, or by an amateur or non-amateur connecting to your machine by the Telnet protocol. The mailbox provides features that you do not want amateur or non-amateur users to access: + A Telnet capability which can connect to both amateur and non-amateur machines. + A Gateway capability which can connect using AX.25 to amateur machines. + A Netrom capability which can connect using NETROM to amateur machines. + A Remote operation capability which allows a user to change the current setup of the gateway. Fortunately, these are easily disabled by including an entry in the ftpusers file for the user `anonymous', with permissions `1', no password, and a home directory the directory/pub. Make sure that the ftpusers file is not kept in the pub directory, or any of its subdirectories. You may wish to add other users entries, so that you can remotely Telnet to the gateway and modify its state. These entries should have a password, and you should never Telnet to the gateway from another amateur machine, as the password will be broadcast over the airwaves for other people to hear. SMTP Once the above security holes are closed, SMTP is the only way to bypass security, as it allows non-amateurs to send electronic mail to amateurs, and vice versa, and SMTP cannot be easily set up to prevent this. To ensure complete security, turn SMTP off. You may initially have SMTP enabled, and monitor the use of email to see if there is any current security problems; however, this leaves the gateway open for email interchange which may be illegal. Other Applications With the mailbox and Telnet set up correctly, the gateway is secure to my knowledge. The following applications can be started without breaching security: echo, discard, ftp, finger, telnet, ttylink, ax25 and netrom. Conclusion To summarise, the packet--Internet gateway provides fast and reliable long-distance digital amateur radio communication, which up until recently has been difficult if not impossible. The use of TCP/IP protocols allows easy connection to the AARNet/Internet, as well as the local amateur community. This long-distance connection not only provides reliable communication for amateur and emergency use, but gives the amateur radio community another avenue for research into radio communication techniques. The gateway software provides the method to connect amateur gateways together, while at the same time ensures the gateway can be operated correctly from both the amateur and non-amateur point of view. I have operated and maintained a packet--Internet gateway in Canberra since April 1991, and have found it to be very reliable, very easy to maintain, and very secure. Moreover, due to the communication speeds used in the amateur community, the gateway has added a negligible burden to the AARNet/Internet use of my local network. I would be glad to answer any questions that are emailed to me at the Internet mail address given at the beginning of this paper, although I cannot guarantee the promptness of my replies. I would also greatly appreciate comments, criticisms and suggestions about this paper and how it can be improved. Warren Toomey vk1xwt. Bibliography This bibliography includes the papers describing the encapsulation protocols used by a packet radio--Internet gateway, as well as some example papers published by amateurs in the field of packet radio. [Diersing et al. 1989] R.J.Diersing, J.W.Ward. Packet Radio in the Amatuer Satellite Service. IEEE J Selected Areas in Communications, Vol 7 No 2. February 1989. [Enmore 1990] G. Enmore n6gn. Physical Layer Considerations in Building a High Speed Amateur Radio Amateur Network. ARRL/CRRL Amateur Radio 9th Computer Networking Conference. London, Ontario. Canada. September 1990. [Flaherty 1988] P. Flaherty n9fzx. Digital Radio Networks and Spectrum Management. ARRL/CRRL Amateur Radio 7th Computer Networking Conference. Columbia, Maryland, America. October 1988. [Geier et al. 1990] J. Geier, M. DeSimio wb8mpf and B. Welsh kd8wg. Network Routing Techniques and Their Relevance to Packet Radio Networks. ARRL/CRRL Amateur Radio 9th Computer Networking Conference. London, Ontario. Canada. September 1990. [Ioannidis et al. 1991] J. Ioannidis, D. Duchamp and G. Maguire Jr. IP-Based Protocols for Mobile Networking. ACM SIGCOMM '91 Conference. Zurich, Switzerland. September, 1991. [Kahn et al. 1985] P.R.Kahn, H.E.Price, R.J.Diersing. Packet Radio in the Amateur Service. IEEE J Selected Areas in Communications, Vol 3, No 5. May 1985. [Kantor 1991] B. Kantor wb6cyt. Internet Protocol Encapsulation of AX.25 Frames. Request for Comments memo 1226. May 1991. [Karn 1990] P. Karn ka9q. MACA -- A New Channel Access Method for Packet Radio. ARRL/CRRL Amateur Radio 9th Computer Networking Conference. London, Ontario. Canada. September 1990. [Neben 1983] B. Neben k9bl. Packet Radio for Emeergency Communications. ARRL Amateur Radio 2nd Computer Networking Conference. San Francisco, California. March 1983. [Sproul et al. 1990] M. Sproul kb2ici and K. Sproul wu2z. Long Distance Packet Mail via Satellite. ARRL/CRRL Amateur Radio 9th Computer Networking Conference. London, Ontario. Canada. September 1990. [Woodburn et al. 1991] R. Woodburn and D. Mills. A Scheme for an Internet Encapsulation Protocol. Request for Comments memo 1241. July 1991. Existing Packet--Internet Gateways Following is a table of the existing gateways as at the 28th of April, 1992. Area Operator Email Address Canberra, Australia Warren Toomey vk1xwt wkt@csadfa.cs.adfa.oz.au Newcastle, Australia Dave Walmsley vk2xpx ccdrw@cc.newcastle.edu.au Sydney, Australia Terry Dawson vk2ktj terryd@extro.su.oz.au Melbourne, Australia Peter Hallgarten vk3ave vk3ave@csource.oz.au Queensland, Australia Andy Joyce vk4kiv joyce@qut.edu.au Central Virginia, USA Jim De Arras wa4ong jmd@emperor.handheld.com Parts of Europe Marco Zollinger hb9cat marco@srztm601.alcatel.ch Ottawa, Canada Barry McLarnon ve3jf barry@dgbt.doc.ca Ontario, Canada Roger Sanderson ve3rks rsanders@sunee.uwaterloo.ca Hawaii, USA Antonio Querubin ah6bw tony@mpg.phys.hawaii.edu Pennsylvania, USA Joe Reinhardt af2j jmr@ecl.psu.edu South Texas, USA Kurt Freiberger wb5bbw kurt@cs.tamu.edu San Antonio, USA Jack Spitznagel kd4iz kd4iz@giskard.uthscsa.edu Chicago, USA Bob Van Valzah ke9yq bob@imsa.edu Indiana, USA Dwight Hazen wb9tlh hazen@hazen.ucs.indiana.edu Illinois, USA Chuck Henderson wb9uus chuck@bradley.bradley.edu Illinois, USA Jay Freeman wt9s freeman@eagle.sangamon.edu Colorado, USA Bdale Garbee n3eua bdale@gag.com Houston, USA Remi Hutin fe6cn bhutin@asl.slb.com Nevada, USA Bill Healy n8khn healy@moriah.unr.edu Example Gateway Setup File The following is the setup file `autoexec.net' used by the gateway minnie.cs.adfa.oz.au. # A U T O E X E C . N E T F O R N O S # # Last update 2:00pm 920423 # # minnie.cs.adfa.oz.au provides an ftp site for minix. It also collects # news for comp.os.minix from the local nntp server Minnie has two # interfaces: ec0 is a 3c501 Ethernet interface to the Internet via # cs.adfa's LAN, and sl0 is a dial-in SLIP link, which is used to gateway # packets from the local amateur radio network, 44.136.0.0/24. # # ec0 has the ip address minnie.cs.adfa.oz.au, and both sl0 and encap # have the address minnie.vk1xwt.ampr.org. # # Local Definitions # hostname minnie.vk1xwt.ampr.org ax25 mycall vk1xwt-2 ip address minnie.vk1xwt.ampr.org # # Memory Parameters # # nibufs - number of interrupt buffers # eff - efficient. It's a better memory allocation algorithm. mem nibufs 10 mem eff on # # Attach ports # # We have up to 2 possible interfaces: # sl0 can connect minnie to switch.vk1kcm via SLIP # ec0 connects minnie to the ADFA net attach asy 0x3f8 4 slip sl0 2048 1500 2400 v attach packet 0x6e ec0 8 1500 # # Publish Ethernet numbers # arp add minnie.cs.adfa.oz.au ether 02:60:8c:09:41:23 mode ec0 datagram # # Domain Servers # domain cache wait 30000 domain cache size 100 domain cache clean off domain addserver ucsd.edu domain addserver ccadfa.cc.adfa.oz.au domain addserver cspyr1.cs.adfa.oz.au dom maxwait 30 # # Routing # # The default route is via ec0. Other routes are to 44.136.0.0 via sl0, # and IP encapsulation to other 44. networks via the Internet. See the # file `gateways.xxx' for more details. route addprivate default ec0 cs_gate.cs.adfa.oz.au route addprivate 131.236.20/24 ec0 route add 44.136.0/24 sl0 route add 44.14/16 encap ampr.wslab.hawaii.edu route add 44.32.0/24 encap hpcsos.col.hp.com route add 44.48/16 encap k9iu.ucs.indiana.edu route add 44.62/16 encap wa4ong.handheld.com route add 44.72/16 encap wb9uus.bradley.edu route add 44.72.192/18 encap owl.sangamon.edu route add 44.72.0/18 encap ke9yq.imsa.edu route add 44.76.0/24 encap hamgate.cs.tamu.edu route add 44.76.2/24 encap giskard.uthscsa.edu route add 44.76.4/24 encap aslp18.aslvx3.slb.com route add 44.80.32/24 encap af2j.ece.psu.edu route add 44.112/16 encap af2j.ece.psu.edu route add 44.125.128/17 encap hamgate.ee.unr.edu route add 44.130/16 encap hb9ab.alcatel.ch route add 44.135.54/20 encap hydra-gw.carleton.ca route add 44.135.96/24 encap hydra-gw.carleton.ca route add 44.135.114/20 encap hydra-gw.carleton.ca route add 44.135.84.0/24 encap at.ve3uow.watstar.waterloo.edu route add 44.137/16 encap hb9ab.alcatel.ch route add 44.142/16 encap hb9ab.alcatel.ch route add 44.136.8/24 encap radio.gw.uts.edu.au route add 44.136.16/24 encap vk2fkj.newcastle.edu.au route add 44.136.17/24 encap vk2fkj.newcastle.edu.au route add 44.136.18/24 encap vk2fkj.newcastle.edu.au route add 44.136.72/21 encap murban.met.unimelb.edu.au route add 44.136.80/20 encap murban.met.unimelb.edu.au route add 44.136.96/19 encap murban.met.unimelb.edu.au route add 44.136.128/21 encap murban.met.unimelb.edu.au route add 44.136.136/23 encap murban.met.unimelb.edu.au # # Interface addresses # # Although minnie's default ip address is minnie.v1kxwt, we need to use a # `real' Internet address for the ec0 connection. ifc encap ipa minnie.vk1xwt.ampr.org ifc encap mtu 256 ifc sl0 ipa minnie.vk1xwt.ampr.org ifc ec0 ipa minnie.cs.adfa.oz.au ifc ec0 broadcast 255.255.0.0 # # AX.25 encapsulation # # We encapsulate ax.25 packets according to rfc1226 for some destinations. # Each axip interface must have a different callsign. # # To connect TO an axip box, use the callsign of the incoming route. # For example, you would do c interf vk1xwt-4. # # But to connect THRU an axip box, use the callsign of the outgoing route. # For example, you would do c interf ah6bw-3 vk1xwt-2. # Note the different xwt callsign. # # Similarly, to connect THRU ah6bw to kh6gpi, # do c interf kh6gpi vk1xwt-2 ah6bw-1. # # The INCOMING callsigns for the axip routes are given below: # Hawaii: ah6bw-3 thru ampr.wslab.hawaii.edu, digi thru -1 to -4. # Europe: hb9ab-3 thru hb9ab.alcatel.ch # Canberra: vk1kcm-3 thru switch.vk1kcm, unti minnie gets a rig # Illinois: wb9uus-? thru pc1701.bradley.edu # Canada: ve3uow-1 thru at.ve3uow.watstar.waterloo.edu # Sydney: vk2sut-? thru radio.gw.uts.edu.au # Queensland: vj4kiv-2 thru vk4kiv.star.qut.edu.au # Victoria: vk3rum-4 thru murban.met.unimelb.edu.au attach axip hawaii 256 ampr.wslab.hawaii.edu vk1xwt-2 attach axip europe 256 hb9ab.alcatel.ch vk1xwt-3 attach axip canb 256 bbs.vk1kcm.ampr.org vk1xwt-4 attach axip illinois 256 pc1701.bradley.edu vk1xwt-5 attach axip canada 256 at.ve3uow.watstar.waterloo.edu vk1xwt-6 # Reserved for Michigan vk1xwt-7 attach axip sydney 256 radio.gw.uts.edu.au vk1xwt-8 attach axip qld 256 vk4kiv.star.qut.edu.au vk1xwt-9 attach axip vic 256 murban.met.unimelb.edu.au vk1xwt-10 ifc hawaii ipadd minnie.cs.adfa.oz.au ifc europe ipadd minnie.cs.adfa.oz.au ifc canb ipadd minnie.vk1xwt.ampr.org ifc illinois ipadd minnie.cs.adfa.oz.au ifc canada ipadd minnie.cs.adfa.oz.au ifc sydney ipadd minnie.cs.adfa.oz.au ifc qld ipadd minnie.cs.adfa.oz.au ifc vic ipadd minnie.cs.adfa.oz.au # # Set TCP and IP parameters # ip ttl 32 tcp mss 1450 # Window of 2900 gives good downloading, bad uploading. # Window of 1024 gives the opposite :-S #tcp window 2400 tcp window 2900 tcp irtt 10000 tcp syndata on # # NNTP stuff # nntp dir /ka9q/spool/news /ka9q/spool/news nntp addserver sserve 3600 nntp groups comp.os.minix misc.activism.progressive sci.environment nntp quiet on nntp trace 0 # # SMTP parameters # smtp timer 500 smtp batch on smtp usemx on smtp trace 0 smtp maxclients 7 smtp batch on # # Mbox parameters # mbox timer 3600 mbox tiptimeout 300 # # Start Servers # # The telnet server is activated so that people coming in from other 44. boxes # or via ai0 can leave mail, and eventually see what other calls to connect to. # Only vk1xwt has telnet, gateway & netrom access. start echo start discard start ftp start smtp start finger start telnet start ttylink stop rip start ax25 # # Misc # log nos.log attended off mbox attend off mb motd " Minnie is run by Warren vk1xwt, with some support from ADFA" motd " Minnie is run by Warren vk1xwt, with some support from ADFA"