Linux-Hams archive - September 1998: Re: Problem with slip link

Re: Problem with slip link

John Reilly (objrg@mailit.tunk.net)
Sat, 12 Sep 1998 21:14:51 -0700


This is a multi-part message in MIME format.
--------------96E80104BD91A143B559B7DE
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Ronnie-
It looks like I'm still stuck. The link appears to be established. There are no
errors showing now in dotnos nor in the autoexec.nos. But I cannot ping linux
from tnos or tnos from linux. I don't know of any other tests that can be made.
I'll attach a copy of my dotnos.
Tnos seems to be running much the same as the jnos I have used but there is one
weird thing. Incoming mail for aa6vn.ampr.org ends up in
/tnos/spool/mail/ampr/org.txt. I have not attempted to send any messages from
tnos. I'm not sure how to go about it.
pnvmygkb@tvc-ip.com

Ronnie Hale wrote:

> >
> Hi John,
> Here is a working "dojnos" file using dip. I think I have it
> commented fairly well, but if you don't understand something, just give
> me a holler. Be sure to edit your hostname for mine, and the
> corresponding lines to be inserted in jnos/tnos autoexec.nos are
> included. If you wish to start jnos/tnos in the current tty, use this
> as the exec command: exec ./jnos -d/jnos -g2
> If you wish to have jnos start on bootup, call the 'dojnos' file in
> your rc.local file.
> -----
> --
> 73, Ronnie.
> icbhp@e-weyer.com

--------------96E80104BD91A143B559B7DE
Content-Type: text/plain; charset=us-ascii; name="dotnos"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="dotnos"

#################### /sbin/dotnos Sept 14, 1998 #######################
#! /bin/sh

# Script to invoke the Linux Jnos. Usage: dojnos [optional_args]
# User should edit definitions for jnosroot and autoexec, and edit the
# $local and $remote addresses in the DIP script below:

tnosroot=/tnos
autoexec=autoexec.nos

# *** This group commented out as errors were produced ***
#if [ $TERM = xterm ]; then
# TERM=xterm-color # xterms is another possibility
#fi
#tset 2> /dev/null

cd $tnosroot
rm spool/mqueue/*.lck 2>/dev/null

###### Edit this:
#QRZDRV=/cdrom
#export QRZDRV
MSGUSER=aa6vn
USER=aa6vn
export MSGUSER USER

# See if we already have a DIP process running for ptye
DODIP=1
ps ax|grep -e "-dip (" > /tmp/dip.$$
if [ -s /tmp/dip.$$ ]; then
grep -q " pe " /tmp/dip.$$
DODIP=$? # 0 => dip already running
fi

# Establish a slip link from Linux via pseudo-tty "e" to a Jnos task
# (use 'dip -k' to kill dip daemon)
if [ $DODIP -ne 0 ]; then
dip -t << \=EOF=
port ptype
###### Linux address:
get $local linux.aa6vn.ampr.org
###### Jnos/Tnos address:
get $remote aa6vn.ampr.org
get $netmask 255.255.255.0
get $mtu 1500
mode slip
#proxyarp
exit
=EOF=
fi

rm /tmp/dip.$$
# It seems that the proxyarp DIP cmd is failing...so we do it ourselves.
# We want the Linux ip stack to respond to ARPs for the Jnos IP addr,
# for those packets received via eth0 (ethernet).
####### Edit this for jnos hostname
arp -Ds aa6vn.ampr.org ppp0 pub

# Corresponding to the above slip setup, are matching Jnos attachments:
# in autoexec.nos file: (linux is interface name in jnos, but can be
# sl0 or whatever you wish to call it)
# attach asy ttype 0 slip linux 3000 1500 9600
# asyconfig linux txq 15
# asyconfig linux rxq 15

# Rename any existing core file so we can use GDB later to debug it
if [ -f core ]; then
mv core core.`date "+%y%m%d-%T"`
fi

# *** will do this later ***
# Starts jnos in tty7:
# exec ./jnos -d/jnos -g2 </dev/tty7 > /dev/tty7 2>& 1 &

# *** TEMPORARY ****
exec ./tnos

echo "exec of tnos returned error code $?"
# End of dojnos.

--------------96E80104BD91A143B559B7DE--