| |
PA2AGA > TCPDIG 29.12.97 20:32l 178 Lines 6163 Bytes #-10119 (0) @ EU
BID : TCP_97_97B
Read: DL3MCW GUEST
Subj: TCP-Group Digest 97/97B
Path: DB0AAB<DB0ZKA<DB0LX<DB0RBS<DB0SWR<DB0FP<DB0SRS<DB0AIS<DB0NDK<DB0ACH<
PI8JOP<PI8ZAA<PI8GCB<PI8WFL<PI8MBQ<PI8VNW
Sent: 971229/1531Z @:PI8VNW.#ZH2.NLD.EU #:65288 [Hoek v Holland] FBB5.15c
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : TCPDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA43092 ; Mon, 29 Dec 97 15:10:07 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.64/7.1) with SMTP
id AA00005627 ; Mon, 29 Dec 97 15:18:30 MET
Date: Mon, 29 Dec 97 15:14:21 MET
Message-Id: <tcp_97_97B>
From: pa2aga
To: tcp_broadcast@pa2aga
Subject: TCP-Group Digest 97/97B
X-BBS-Msg-Type: B
it is an X-1JR4 node that is tied to two others on a "Node stack"
(those would be n9cfn-4 [44.92.20.2] and ke9pw-5 [44.92.20.8]. Together,
they form a bridge/router/gateway setup. n9oly only has to know how to get
to ke9lz-5, and which addresses go that way. Our radio LAN area has a
subnet 44.92.20.xx, as you might have guessed.
Which brings us to the routing issue. All of the other subnets
you see are routed by the "node stack". In WNOS, the syntax of the
route command is:
route add <ip_address> <interface_name> <gateway_ip_address>
In the case of n9oly, the radio interface is called "vhf" and
the ethernet interface is called "ether". Not terribly inventive, but
pretty descriptive. Here is a portion of the routing file for n9oly:
# NODES.ROU
#---------------------------------------------------
#
# Define IP routing to other remote nodes.
#
#---------------------------------------------------
# IP addresses routed via ethernet:
#
# Permanent routing for kb9aln.ampr.org
# via ethernet
route add 44.92.20.9 ether
# Permanent route for n9oly-5.ampr.org
# via ethernet
route add 44.92.20.37 ether
#
# -----------------------
#
# reached over netrom
# (none - this is a bad way to do business, and X-1J
# has IP routing capability anyway.)
#
# ---------------------------
#
# Route for any local 44.92.20.xx addresses tha
t need
# to be reached via radio:
#
route add 44.92.20.5 vhf
#
# This is the vhf node tied to the "stack", and our gateway
# to the rest of the radio network.
#
# ---------------------------
# reached ax25 via a ip switch
#
route add 44.92.20.3 vhf 44.92.20.5
route add 44.92.20.2 vhf 44.92.20.5
#route add 44.92.20.4 vhf 44.92.20.5
route add 44.92.20.20 vhf 44.92.20.5
route add 44.92.20.24 vhf 44.92.20.5
route add 44.92.20.32 vhf 44.92.20.5
#
# ----------------------------
# reached via other gateways:
#
route add 44.92.20.31 vhf 44.92.20.11
#
# ----------------------------
#
# direct routing for 44.xx.xx.xx addresses reached
# over the 2m AX.25 vhf radio channel
#
route add 44.92.20.0/24 vhf
#
# only looks at the first 24 bits of the IP address on
# the radio amprnet, and tries them directly.
#
# ---------------------------
#
# Catch-all routes for vhf 44.xx.xx.xx addresses
# reached through the radio gateway (default ax25 route)
#
route add 44.0.0.0/8 vhf 44.92.20.5
#
# only looks at the first 8 bits of the ip address -
# - the radio amprnet - and sends them to the gateway
# ke9lz-5 [44.92.20.5].
#
# -------------------------
#
# The End.
You will note that most everything n9oly can't reach directly is
sent to ke9lz-5 [44.92.20.5], with the exception of 44.92.20.31. That
is another gentleman who has a setup similar to ours - except that
his is one computer connected to another via slip. Same principle
holds here - we use his radio computer as a gateway to get to the
"slipped" computer.
I also occasionally run Linux on kb9aln (without any ax.25
compiled into the kernel, and not running any kind of NOS under it).
With this, the routing commands are similar. The ethernet interface is
called eth0, which appears to be the Unix convention for the first
ethernet interface. When any kind of NOS is run under Unix/Linux,
generally a pseudo-slip interface or a tunnel interface is used to couple
the NOS to the Unix or Linux kernel. Naturally, a route is established to
that IP address with the appropriate netmask, etc. Conversely, the
Unix/Linux kernel has a route back to the NOS with the appropriate
netmask, as well. You probably know this anyway, the netmask in Unix/Linux
is generally set with the ifconfig command. I don't mean to repeat what
you already know, but this info might be useful to others who "lurk" on
the list, as I do :)
In any case, I do hope this info is helpful. I do hope to play
with WAMPES for Linux/UNIX myself soon. WNOS was developed from it,
and it does have a very good "radio-friendly" ax.25 front-end with
the ability to learn ax.25 routes. It adapts very nicely to a crowded
radio channel and is very kind to other radio stations, backing off
when it sees the radio channel is busy.
I wish you good luck with this, Bill and I hope to hear success
stories from you in the future. Again, apologies to the rest of the
group who may find this message long - but hey, we needed some
friendly activity here!
73,
Andy Nemec
andy@hardware.cae.wisc.edu
Amateur Radio:kb9aln.ampr.org
------------------------------
Date: Sun, 28 Dec 1997 16:35:18 -0500 (EST)
From: Darxus <darxus@Op.Net>
Subject: TCP/IP over AX.25 on a wearable ?
one of the problems with wearable computing seems to be networking.
options being wireless modems (expensive air time), or wireless lan type
stuff (short range).
AX.25 is a wonderful thing I ran across a while ago on the web -- a
protocol that runs over packet radio (hams). TCP/IP can be (and is)
encapsulated in AX.25, and gatewayed to the Internet. the whole TCP/IP
over AX.25 seemed like it would be most cool if everybody had a tranciever
-- broadcasting & recieving their own signals, and relaying other people's
signals to distant sites.
now I ask my question and snow how little I know about packet radio: can
the equipment necessary to do AX.25 be built into a wearable computer --
is it small enough, and does it require little enough power to run off of
batteries ?
for those of you on the AX.25 related list, more info on wearable
computing can be found at
http://lcs.www.media.mit.edu/projects/wearables/
-- people are wearing computers that cost less than laptops, and have 10
hour battery lives....
for you wearables folk, do some web searches, and maybe check out the
linux ax25-howto (yeah, my kernel knows more about this stuff than I do).
To be continued in digest: tcp_97_97C
Read previous mail | Read next mail
| |
