From morganb@inetport.com Thu Oct 01 11:26:01 1998 Received: from admin.inetport.com (inetport.com [204.96.100.2]) by tapr.org (8.8.5/8.8.5) with ESMTP id LAA12799 for ; Thu, 1 Oct 1998 11:26:01 -0500 (CDT) Received: from as01-45.inetport.com (as01-45.inetport.com [204.96.100.125]) by admin.inetport.com (8.8.8/8.8.5) with SMTP id LAA18710; Thu, 1 Oct 1998 11:25:59 -0500 (CDT) Message-Id: <3.0.1.16.19981001160108.278fc976@inetport.com> X-Sender: morganb@inetport.com X-Mailer: Windows Eudora Light Version 3.0.1 (16) Date: Thu, 01 Oct 1998 16:01:08 To: "Biekert, Robert" From: "Robert B. Morgan" Subject: Re: APRS networking via TexNet Cc: texnetaxip@tapr.org In-Reply-To: <199810011149.GAA01956@admin.inetport.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 06:47 AM 10/1/98 -0500, you wrote: >What can we do to get TexNet in the Houston area? The Clear Lake ARC (NASA >area) would very much like to tie into the TexNet system. > >My 'real' email is ka5glx@clarc.org > >73 >Bob KA5GLX Fantastic. They are stating to crawl out of the woodwork now. TexNet is in the process of developing some trunking over the internet. It is still under development. It is based on AX25IP tunneling, where we encapsulate AX25 packets inside IP and move them from place to place, over longer paths than we can do with practical radio links. Currently we are planning such links from the main part of TexNet at Austin, Denton, and San Antonio to Midland, Lafayette La, and the other portion of the network in Oklahoma/Arkansas/Missouri. We have had some recent interest from Laredo, and even Reno NV and Sacremento Ca. Current status is that we have secured access through various providers at most of these places, and I have done some bench testing that shows it will work. I am in the midst of writing some async drivers for the Z80 side of the system, and will probably have to enhance the AX25IP side also, which runs under Linux. I thought we would be there by now, but like the APRS addition to the code it took time, and will be ready whenever it is finished and tested. We have been trying to get into the Houston area for quite some time now. Seems like a real series of losing battles over the years. At one time we had a donated wireline that went there, but the facility it terminated at had no roof access for radio antennas. TPRS has sold more TexNet NCP kits to Houston addresses than any other single city, and none of them ever turned up on the air as far as we know. Hopefully they are still around, if only someone knew where they went, so you might ask around to see. The closest RF access from TexNet to Houston is in Victoria. Look around for any cooperative source of internet connectivity which you can make an ethernet connection to (so that it will be fast enough), and plan to install (or share use of) a Linux system with a fixed address, that can support a daemon (AX25IPD) and a serial port, and in a location you can install radios and antennas. Some commercial providers have been known to block some tunneling protocols so inquire ahead of time. This one is based on RFC1226, and it is IP protocol # 93. If you do locate a willing provider, let me know what it is, I would like to ping it a few times and measure response times. We have been seeing numbers well under 100 mSec in most cases, except on the day the Clinton/Lewinsky stuff hit the internet. Let me know what you can come up with. We have a mail reflector on TAPR which is supporting the logistics and planning for this effort, and if you are interested I will arrange to get you on it. In any event I am going to CC that reflector with this reply so that we make a record of the interest. That is texnetaxip@tapr.org and it is one of its SIG reflectors. I am not sure if it is open or closed, but hit www.tapr.org and look at the public SIG's and see if you can sign onto it, if that is your wish. If it is private, leave me an e-mail and I wil let someone, probably Greg know. If you can locate some of the original NCP's fine, if not the only alternative available to run TexNet on at the present is TNC2 clones. A simple node could be no more than using its native 1200b modem on a user frequency and plugging the serial port into the Linux system hosting the AX25IP interface, and dropping our (as yet vaporware) TexNet eprom into the TNC2. A more sophisticated network would attach a modified 9600b TPRS FSK radio modem to each TNC2, which would have to undergo a relatively simple dualport modification we have developed, so that each TNC2 would support two radios, one trunk and one user. You could equip several sites with this setup, of course at least one of them could be an APRS node, the others might be for various connected uses on other frequencies if your plans called for it. Then it would be necessary to have one TNC2 at the ISP location, with one 9600b modem on it and a radio for the UHF trunk, so it could join the rest of the network. Maybe since there are others in Houston wanting to do the same, if they all get together they may be able to combine the internet interface and sit on a common RF trunk around Houston. If very much activity develops it would be advantageous for reliability to have more than one site tied to the internet, so we could route around problems. I have heard from other hams in the Houston area in the past several months. I need to pull together a list of them, but I don't have it in one place right now. Some of the people we are working with are the DXC node sponsors, and some of them are experienced in AX25IP setups already. That tunneling protocol has been around since 1991 and it works pretty well, and it is fairly simple, it really amounts to digipeating over the internet. Off the top of my head, the Houston area callsigns that I heard may be interested or involved are K5CON, N5VDA, and at one time WD5HJP. I met someone at Summerfest, who I didn't have time to write down any details, that knew WD5HJP and was going to contact him. WD5HJP is Bill Wade; when he lived around Dallas helped build the original core part of TexNet in that area, and he lives around Pearland now. It has been a few years since I have been to Houston, but that is one of the parts of town I enjoy visiting, and I have been through NASA several times. Keep me posted with your progress. 73 de Bob WB5AOH Austin Texas morganb@inetport.com From wa5vms@tapr.org Sun Oct 11 05:31:15 1998 Received: from Pjsboro.intellex.com (road207-223.oknet1.net [198.247.207.223]) by tapr.org (8.8.5/8.8.5) with SMTP id FAA23363 for ; Sun, 11 Oct 1998 05:31:14 -0500 (CDT) Message-Id: <3.0.32.19981011061737.00aca080@tapr.org> X-Sender: wa5vms@tapr.org X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 11 Oct 1998 06:17:53 -0500 To: texnetaxip@tapr.org From: "Joe S. Borovetz" Subject: Linux Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hello All There has been a discussion on the need for more info on Linux, the use of the 44. ip address, etc. I wanted to make those with low band capabilities aware of a get together on Saturday mornings where some of these subjects are discussed. A group of us get together on or around 3.858-59 MHz at 7 AM on Saturday mornings. This may be a bit early for some folks but it seems to work out best at this time. All are invited to join in the discussion of packet topics and these topics usually run along the lines of Linux and TCP-IP. Joe From jcm7181@usl.edu Sun Oct 11 14:27:57 1998 Received: from larry.wu3v.net (root@larry.wu3v.net [206.104.42.243]) by tapr.org (8.8.5/8.8.5) with ESMTP id OAA15977 for ; Sun, 11 Oct 1998 14:27:55 -0500 (CDT) Received: from winnt (winnt.wu3v.net [206.104.42.226]) by larry.wu3v.net (8.8.3/8.8.3) with SMTP id TAA09956 for ; Sun, 11 Oct 1998 19:27:52 GMT Message-Id: <3.0.6.32.19981011142731.0094fc50@pop.usl.edu> X-Sender: jcm7181@pop.usl.edu X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 11 Oct 1998 14:27:31 +0000 To: texnetaxip@tapr.org From: Jim Moore Subject: Re: [TEXNETAXIP:104] Linux In-Reply-To: <3.0.32.19981011061737.00aca080@tapr.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 05:32 AM 10/11/98 -0500, you wrote: >Hello All > >There has been a discussion on the need for more info on Linux, the use of >the 44. ip address, etc. I have been running a 44 net gateway and axip since 1991, there are some problems using 44 net for axip with tnos. Jnos works just fine with the 44 net axip's. The builtin ipip inside linux and a 44 net axip will also not work, but that is usually not necessary. If you are comtemplating running 44 net and axip your isp and his upstream provider must transport ip protocoles 4, 93 and 94. These are not tcp ports so be aware that the isp understands the difference. Also it is suggested that the 44 net routes be installed on the gateways that are attempting a 44 net connection if not the routes end up going to ucsd.edu and that will involve unwanted delays in processing the packets. One other point is that ip masquerading will not work for axip, what is required is for both systems to have true internet address that are routable directly on the internet. I have also been unsecessful making an axip work between a 44 net address and an internet address! Jim WU3V From wa5vms@tapr.org Sun Oct 11 19:06:15 1998 Received: from Pjsboro.intellex.com (road207-200.oknet1.net [198.247.207.200]) by tapr.org (8.8.5/8.8.5) with SMTP id TAA05902 for ; Sun, 11 Oct 1998 19:06:13 -0500 (CDT) Message-Id: <3.0.32.19981011195251.00b73668@tapr.org> X-Sender: wa5vms@tapr.org X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 11 Oct 1998 19:52:56 -0500 To: texnetaxip@tapr.org From: "Joe S. Borovetz" Subject: Comments Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hi Jim I understand what you are saying about axip and the 44 addresses. The only reason that I brought up the 44 addresses is that ther has been some discussion concerning those addresses and fuller.net. It is probably a good thing that you mentioned to this group that axip will not work with 44 addresses. I have the TAL radio installed at the ISP. I did have to tweak an antenna, I had a path but at times it was marginal and would drop out. Things seem to be fine now. I am still having a bit of a problem making the ISP understand what I need. I had the TAL radios and my Linux machine set up with the 198 IP address to be at the house. He wanted me to move it to the ethernet port on the remote TAL radio. I did so and of course things are not working. When I get a minute, I will give you a call on the telephone and set up a time that I can get you on the same line with the tech at the ISP. I think a few simple changes on his end will fix the problem. This is a learning process for both myself and the tech at the ISP. Hopefully, we can put together a set of guidelines for establishing such a connection and that may save some folks a bit of trouble in the future. BTW, Mike Foster did a telnet session into the router and he agrees with you and me that the 198 address needs to be on the linux box at my house. Joe From jcm7181@usl.edu Sun Oct 18 20:29:58 1998 Received: from larry.wu3v.net (root@larry.wu3v.net [206.104.42.243]) by tapr.org (8.8.5/8.8.5) with ESMTP id UAA14475 for ; Sun, 18 Oct 1998 20:29:57 -0500 (CDT) Received: from winnt (winnt.wu3v.net [206.104.42.226]) by larry.wu3v.net (8.8.3/8.8.3) with SMTP id BAA17821 for ; Mon, 19 Oct 1998 01:29:55 GMT Message-Id: <3.0.6.32.19981018202941.0095d1f0@pop.usl.edu> X-Sender: jcm7181@pop.usl.edu X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 18 Oct 1998 20:29:41 +0000 To: texnetaxip@tapr.org From: Jim Moore Subject: New TexNet nodes in Louisiana In-Reply-To: <3.0.6.32.19981011142731.0094fc50@pop.usl.edu> References: <3.0.32.19981011061737.00aca080@tapr.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" I have just installed 2 texnet nodes, MAXIE K5USL-4 is installed at the KLFY tv tower, I was employed there for 12 years and still have some good friendships at the transmitting facilities. It is being shared with a 2 metre voice repeater via a 3 port wacom duplexer and packet combiner. The antenna is installed at the 650 foot level on a 1771 foot tower. LFTDXC N5SYF-4 is installed at my home, it will be connected to the dxclusters bpq switch and the linux computer that houses my jnos and xfbb bbs'. Both nodes are currently linked on 145.01. Thanks to all that have helped me along with all the problems notably WB5AOH, N0CCW and of course K5ET Fred the transmitter engineer at KLFY tv. Jim WU3V From jcm7181@usl.edu Sun Oct 18 21:23:52 1998 Received: from larry.wu3v.net (root@larry.wu3v.net [206.104.42.243]) by tapr.org (8.8.5/8.8.5) with ESMTP id VAA16769; Sun, 18 Oct 1998 21:23:51 -0500 (CDT) Received: from winnt (winnt.wu3v.net [206.104.42.226]) by larry.wu3v.net (8.8.3/8.8.3) with SMTP id CAA17961; Mon, 19 Oct 1998 02:23:49 GMT Message-Id: <3.0.6.32.19981018212336.00945df0@pop.usl.edu> X-Sender: jcm7181@pop.usl.edu X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 18 Oct 1998 21:23:36 +0000 To: "Joe S. Borovetz" From: Jim Moore Subject: Re: Route info Cc: texnetaxip@tapr.org In-Reply-To: <3.0.32.19981018215342.00b7993c@tapr.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sorry to listen in Joe but I saw no default route on your linux machine Jim At 09:53 PM 10/18/98 -0500, you wrote: >Hi Mike > >Here is a list of the routes as they appear at the various points. > >Hope you can handle Word 2.0. I did not want to fight some of the auto >formatting in the later versions of Word. > >Joe >