| |
OE1XYA > WAMPES 19.09.99 14:22l 237 Lines 8682 Bytes #-9501 (0) @ WW
BID : J99OE1XAB00T
Read: DB1RAS GUEST
Subj: solaris with dialup ppp 4.0 to wampes
Path: DB0AAB<DB0ZKA<DB0ABH<DB0RGB<OK0PPL<OK0PKL<OK0PPR<OE3XSR<OE1XAB
Sent: 990919/1023z @:OE1XAB.#OE1.AUT.EU [OeVSV-LV1 BBS SysOp OE3DZW] bcm1.41l5
From: OE1XYA @ OE1XAB.#OE1.AUT.EU (Afuverein_x)
To: WAMPES @ WW
X-Info: No login password
hi all !
i am using wampes, written by dieter, since about 2 years , but
not as my favorit packetradio terminal program. wampes is not
a userfriendly frontend for packet radio and i am sure, it isn't
designed as such one. but it support's excelent connectivity
to various types of networks.
i did have a problem. it wasn't possible to access through wampes
from the operating system to the packet radio network.
my idea was, to get a connection over a pseudo tty-pair ( for
example with /dev/ttype and /dev/ptype ) to wampes.
as operating system i am using solaris 2.5.1 on sun sparc platform.
( sun4m voyager )
last days i had success with dp-4.0, this is a dialup-ppp software,
to access ax.25 from the shell.
normaly such a dialup driver is setup over a real serial device
connected to a modem. i did setup dp on a pseudo tty, which is
available as pair. the other end is connected to wampes.
( not directly, i use a little additional selfwritten program,
which will be explaned below and in an other mail , named ptcon )
below i give you an overview and the configuration files
of dp-4.0. dp is explaned well within the package, but to have
some examples is better.
best regards from vienna
hans
oe1smc
OE1SMC @ OE1XAB.#OE1.AUT.EU
mayer@ping.at
------------------------------------------------------------
overview:
=========
+--------------+
ax.25 network | rmnc3 |
<-----------------------------+ flexnet 3.3h |
with or without tcp/ip +-------+------+
| unix extern
if -- -- -- -- -- -- -- | -- -- -- -- -- --
| unix intern
kiss |
|ttya
+-----+ +--------+ +-------+------+ +-----------+
| tnt | host | tfkiss | kiss | wampes | vjslip | os/2.5.1 |
| 1.9 +------+ 1.2.2 +---------+ main gateway +----------+ using |
| :-) | mode | | | as OE1SMC-15 | | dp-4.0 |
+-----+ +--------+ +------+-------+ +-----+-----+
| |
bridge/kissui | |
+------------------+ ip |
| | |
+----+-----+ +------+-----+ +-----+-----+
| wampes | | wampes | | netscape |
| 2nd inst | | 3rd inst. | | others |
+----------+ +------------+ +-----------+
tnt is my userfriendly frontend for poor ax.25 usage.
( and mostly i am using only ax.25 for reading mails without tcp/ip. )
tnt and tfkiss was written by Mark Wahl DL4YBG and is developed now
by a worldwide team of hams and packet interested friends.
tfkiss changes hostmode to kissmode for wampes.
tfkiss could optionally speak directly with rmnc-node over ttya.
( as tfkiss can all 3 dialects of kiss )
wampes is written by Dieter Deyke, DK5SG and previously by Phil Karn, KA9Q
on this place, i will also thanks michaela dd2fx, who
give me a lot of tips.
wampes is wired to a rmnc3/flexnet node, which could also be
a tnc2 with kissmode. ttya is a real rs232 interface.
if necessary i can also start a 2nd or 3rd instance of wampes
with a different configuration file. ( as oe1smc-1 )
this communication goes over a utility program running as daemon
called bridge ( included in wampes package ) listening on 4713/TCP
dp-4.0 shows now ( after installation )
an ip-interface within the unix-system.
dp0: flags=f1<UP,POINTOPOINT,NOTRAILERS,RUNNING,NOARP> mtu 1006
inet 44.143.16.21 --> 44.143.16.66 netmask ff000000
44.143.16.66 is oe1smc-15 which is my wampes maingateway too.
44.143.16.21 is oe1smc and therefore my local interface.
dp is setup itself on a tty-pair. as both, wampes and dp, are
doing an ioctl() on the device, i am using 2 tty-pairs and a
selfwritten program, which connects these 2 pairs of pseudo-ttys.
it's named "ptcon" ( the reason: the backend of the pair pty..
is not to be controlled by ioctl() under solaris )
from the shell-commandline i can now use any program like ping,
telnet, nslookup, sendmail or x-applications like netscape.
all network trafic goes over dp0, which can be checked with
standard tools like "snoop"
dp itself installs a new kernel device.
there is also running permanently a daemon, named dpd.
if traffic goes over the interface, dpd forkes and the
child process is forking a ppp-deamon.
dp-4.0 can support a lot of slip or ppp connections
simultaneously.
root 314 1 0 13:43:02 ? 0:00 /opt/dp/bin/dpd
root 1094 1093 6 22:01:30 ttype 0:01 /opt/dp/bin/ppp -d -as 0
dialup unit 0 /dev/ttype 44.143.16.21:44.143.16.66 slip vjmode rfc1332
root 1093 314 1 22:01:29 ttype 0:00 /opt/dp/bin/dpd
the following is the output from the wampes command "asystat"
oe1smc-15> asy
ttya: [UP] 9600 bps
RX: int 971 chars 24448 hw hi 0
TX: int 328 chars 10166
br0: [UP] 9600 bps
RX: int 8 chars 450 hw hi 0
TX: int 31 chars 1079
ttyrf: [UP] 19200 bps
RX: int 332 chars 8969 hw hi 0
TX: int 329 chars 21654
ttypd: [UP] 9600 bps
RX: int 152 chars 11144 hw hi 426
TX: int 203 chars 10313
tty is the hardware interface to rmnc3 ( or tnc2 )
br0 is the interface from /tcp/utils/bridge to other wampes instances.
ttyrf goes to tfkiss as a tty-pair to /dev/ptyrf
ttypd goes to dp-4.0 ip-interface
------------------------------------------------------------
and now the config-files from dp-4.0
============================================================
/etc/dp/hostnames
------------------------------------------------------------
dp0 44.143.16.21 44.143.16.66
============================================================
/etc/dp/conf
------------------------------------------------------------
IF=dp0
SYS=wampes
MODEMS=wampes
LOGIN_SCRIPT=direct
TRACE=wampes_trace
ACCESS=acc_wampes
"PPP_ARGS=slip,vjmode,rfc1332"
LOG_LEVEL=3
MODEM=wampes DEV=/dev/ttype BAUD=9600 DIAL_SCRIPT=direct
============================================================
/opt/dp/access/acc_wampes
------------------------------------------------------------
DPaccess 2.0
#
# Options to allow only certain protocols, times of use, or specific machines.
# These limit the conditions in order to initiate a call.
#
#times:call {
# weekends || weekdays/[17:00,6:00]
#}
#protos:allow {
# ip/tcp,udp
#}
#addrs:allow {
# src:ip/128.210 || ip/128.46.157.152
#}
timeouts {
failedcall 1:10 # time to mark network as down after failed call
callwait 3:00 # time to allow for call to go through
}
timeouts:dial {
protos:ip/tcp/70,80,[8000,8080] {
non_stream 2:00
last_close 2:00
}
non_stream 1:20
last_close 1:08
inactivity 4:00
}
timeouts:answer {
inactivity 4:00
}
------------------------------------------------------------
the first line of file above sounds bad, but it is
indead version 4.0 - i did copy an existing file and
didn't modify this first line.
============================================================
/opt/dp/modem/wampes.9600.com
------------------------------------------------------------
( this is an empty file )
============================================================
the wampes statement in /tcp/net.rc ( or equiv )
------------------------------------------------------------
attach asy 0 0 vjslip ttypd 0 1006 9600
============================================================
beware:
[ first pair ]
+--------------+
| |
wampes <--> ttypd <--> ptypd <-..
..-> ptcon <--> ptype <--> ttype <--> os/dp-4.0
| |
+--------------+
[ second pair ]
ptcon is my selfwritten pseudo tty connection program
which will be uploaded in a seperate mail.
------------------------------------------------------------
maybe you will ask: "why doing such a complex configuration ?
i am using a simple pr-software named "xyz" and connected a
modem on a serial line on my windoofs pc and can also
use the packet radio network."
i will answer: "maybe i have more flexibility"
------------------------------------------------------------
vienna, 9/1999
Read previous mail | Read next mail
| |
