| |
PA2AGA > TCPDIG 29.12.97 20:36l 164 Lines 6214 Bytes #-10119 (0) @ EU
BID : TCP_97_97A
Read: DJ8QC GUEST
Subj: TCP-Group Digest 97/97A
Path: DB0AAB<DB0ZKA<DB0LX<DB0RBS<DB0SWR<DB0FP<DB0SRS<DB0AIS<DB0MW<DB0ERF<
DB0HSK<PI8DRS<PI8DAZ<PI8APD<PI8WNO<PI8VAD<PI8VNW
Sent: 971229/1536Z @:PI8VNW.#ZH2.NLD.EU #:65291 [Hoek v Holland] FBB5.15c
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : TCPDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA43091 ; Mon, 29 Dec 97 15:00:35 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.64/7.1) with SMTP
id AA00005624 ; Mon, 29 Dec 97 15:18:16 MET
Date: Mon, 29 Dec 97 15:14:16 MET
Message-Id: <tcp_97_97A>
From: pa2aga
To: tcp_broadcast@pa2aga
Subject: TCP-Group Digest 97/97A
X-BBS-Msg-Type: B
TCP-Group Digest Mon, 29 Dec 97 Volume 97 : Issue 97
Today's Topics:
Merry Christmas and wampes.
TCP/IP over AX.25 on a wearable ? (2 msgs)
Wireless WearComp
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from ftp.UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
Loop-Detect: TCP-Group:97/97
----------------------------------------------------------------------
Date: Sun, 28 Dec 1997 12:43:43 -0600 (CST)
From: RHS Linux User <andy@hardware.cae.wisc.edu>
Subject: Merry Christmas and wampes.
Hi, Bill and the Group.
In response to Bill Walker's message that appeared here recently:
> Thanks to Brian for his "keep-alive" message. Merry Christmas
> to all, and here is something for idle moments:
> I have compiled wampes on SCO OSR5.0.4, using egcs-1.0
> for a compiler. It "seems" to run, but I have decided that I
> really don't know how to make it "talk" correctly.
> I can make ax25 connections at will. I am evidently quite
> confused about the tcp/ip routing tables, though. The _only_ station
> near me that has any kind of tcp/ip capability is a local digipeater.
> Am I right in thinking that I must enter an address with
> "arp" as well as a route with "route" ? No matter what I do, I
> can't seem to "ping" the digi. Note that I can ping the digi with
> K5JB's "net" running tcp/ip, so I am sure the digi can respond to
> a ping.
> wampes _can_ query the DNS on my SCO box and find IP addresses,
> but then it won't ping even the localhost. Clearly I have something
> set up very wrongly.
> Anyone have any advice or experience running wampes as the primary
> software ? I have tried to duplicate the "example" startup file
> that is included with wampes. I must confess that "routing" in the
> amateur sense confuses me.
>
> 73 de Bill W5GFE
> --
> Bill Walker Ph.D.
> Chairman, Dept. of Computer Science
> East Central University
> Ada, Oklahoma 74820-6899
> e-mail: bw@cs.ecok.edu
> phone: 580 332 8000 ext. 594
> FAX: 580 332 4616
First off, the best of holiday greetings to all on the list. I
usually "lurk" here on the group, generally someone else comes up
with an answer to a question before I can respond. I've gotten a lot of
good information from the group and appreciate it. As I haven't seen an
answer to this appear here just yet, I will take a stab at answering
Bill's questions.
Here at my house, we have a little network set up using an
ethernet at 10Mb, along with a 1200 bps radio port. The machine with
the radio port runs WNOS (the DOS cousin of Wampes). The other
machines can run WNOS, Linux, or (Ugh) Windows TCP/IP. Here is what
it looks like:
----------- ------------- ------------- -----
| kb9aln | | n9oly-5 | | n9oly |---| TNC |
| 44.92.20.9 | | 44.92.20.37 | | 44.92.20.23 | | |
----------- ------------- ------------- -----
| | |
----------------------------------------
^ Ethernet
The picture is included for clarity, and I suspect that you may
be dealing with a similar situation if this is at your .edu site
(perhaps an incorrect assumption, but I will go with it anyway). Actually,
you would probably reach any ether addresses through the your SCO box.
More on that in a little bit.
The syntax of the commands may be different than in your situation,
but here is a portion of the arp entries for n9oly.ampr.org, contained in a
file that WNOS calls "/nodes.arp":
# NODES.ARP
#---------------------------------------------------
# Define the mapping of internal host names to the 'real world' names
# using ARP.
#
# ARP Broadcasts need to respond to AX.25 destination "QST"
#
arp add 44.255.255.255 ax25 QST-0
#
arp add 44.92.20.37 ether 00:00:1b:22:5a:2e
arp add 44.92.20.9 ether 00:00:1b:41:29:c9
#
# Reach directly across a 2m AX.25 link
#
arp add 44.92.18.5 ax25 kb9byq-5
arp add 44.92.18.12 ax25 ka9jac-2
arp add 44.92.20.2 ax25 n9cfn-4
arp add 44.92.20.4 ax25 ke9lz
arp add 44.92.20.5 ax25 ke9lz-5
arp add 44.92.20.6 ax25 ke9pw
arp add 44.92.20.8 ax25 ke9pw-5
arp add 44.92.20.9 ether kb9aln
arp add 44.92.20.11 ax25 n9pav
arp add 44.92.20.22 ax25 n9paw
arp add 44.92.20.23 ax25 n9oly
arp add 44.92.20.24 ax25 n9ncq
arp add 44.92.20.31 ax25 n9pav-2
arp add 44.92.31.2 ax25 k9aeg-6
arp add 44.92.31.6 ax25 n9wvd
arp add 44.92.31.12 ax25 n9wbr
#
# The End.
You will note that the first entry is for arp requests - "What
interface address (call-sign) belongs to this IP address, please?". Other
computers set to "arp publish" will reply via radio, pretty much in the
same manner as is the convention. The difference is that the arp request
is directed (via a "UI" ax.25 packet) to a call-sign of "QST" (call anybody
who will answer). Also note that the addresses for the stations/computers
on the ethernet at our house are "arp'ed" to ethernet addresses, this is
probably what you are used to seeing in the "non-amateur" world. The IP
addresses that are reached over the radio network are matched to
call-signs. I've also included an arp entry for the ethernet-reached IP
addresses matched to call-signs. This may not be necessary, but I included
it anyway.
ke9lz-5 (44.92.20.5) is functionally equivalent to your "Digi",
To be continued in digest: tcp_97_97B
Read previous mail | Read next mail
| |
