mgrant@cos.com (Michael Grant) (06/28/89)
I am trying to get isode working on a Sun running SunOs 4.0, Sunlink
MHS, OSI, and X.25. I'm trying to understand how isode is interacting
with Sunlink OSI and X.25. Can anyone tell me:
How does the tsapd pick up TP4 connections that come in from Sunlink
OSI? If it dosn't, (and I suspect that it dosn't), then what is
listening to the network to pick up these REAL-NS network connections
that are destined for isode? Or should I ask, what is listening to
Sun's transport to pick up these TP4 connections destined for isode?
Secondly, I'm having a problem with the tsapd with respect to X.25.
I start the tsapd with the following line:
/usr/local/etc/tsapd -a 031342023004500 -i 03010100
and I get this in the tsapd.log:
6/27 14:11:55 tsapd 09318 (root ) -a: unknown switch
This never used to happen under SunOs 3.5.
I stick the x.25 addresses into the isotailor file, and it seems to be
completely ignored. X.25 calls with that CUD don't get sent to the
tsapd. Here's the isotailor file:
ts_communities: realns intl-x25 internet
x25_local_dte: 31342023004500
x25_intl_zero: on
x25_strip_dnic: on
x25_dnic_prefix: 3134
reverse_charge: 1
x25level: all
x25file: x25.log
compatlevel: all
compatfile: compat.log
addrlevel: all
addrfile: addr.log
tsaplevel: all
tsapfile: tsap.log
ssaplevel: all
ssapfile: ssap.log
psaplevel: all
psapfile: psap.log
psap2level: all
psap2file: psap2.log
acsaplevel: all
acsapfile: acsap.log
rtsaplevel: all
rtsapfile: rtsap.log
rosaplevel: all
rosapfile: rosap.log
Here's my address from isoentities:
osisun default 1.17.4.3.9.3.0 \
NS+4700040034020108002001635400|\
Internet=cos|\
Int-X25(80)=031342023004500+PID+03010100
Any help would be appreciated.
-Mikemgrant@COS.COM (Michael Grant) (06/28/89)
I am trying to get isode working on a Sun running SunOs 4.0, Sunlink
MHS, OSI, and X.25. I'm trying to understand how isode is interacting
with Sunlink OSI and X.25. Can anyone tell me:
How does the tsapd pick up TP4 connections that come in from Sunlink
OSI? If it dosn't, (and I suspect that it dosn't), then what is
listening to the network to pick up these REAL-NS network connections
that are destined for isode? Or should I ask, what is listening to
Sun's transport to pick up these TP4 connections destined for isode?
Secondly, I'm having a problem with the tsapd with respect to X.25.
I start the tsapd with the following line:
/usr/local/etc/tsapd -a 031342023004500 -i 03010100
and I get this in the tsapd.log:
6/27 14:11:55 tsapd 09318 (root ) -a: unknown switch
This never used to happen under SunOs 3.5.
I stick the x.25 addresses into the isotailor file, and it seems to be
completely ignored. X.25 calls with that CUD don't get sent to the
tsapd. Here's the isotailor file:
ts_communities: realns intl-x25 internet
x25_local_dte: 31342023004500
x25_intl_zero: on
x25_strip_dnic: on
x25_dnic_prefix: 3134
reverse_charge: 1
x25level: all
x25file: x25.log
compatlevel: all
compatfile: compat.log
addrlevel: all
addrfile: addr.log
tsaplevel: all
tsapfile: tsap.log
ssaplevel: all
ssapfile: ssap.log
psaplevel: all
psapfile: psap.log
psap2level: all
psap2file: psap2.log
acsaplevel: all
acsapfile: acsap.log
rtsaplevel: all
rtsapfile: rtsap.log
rosaplevel: all
rosapfile: rosap.log
Here's my address from isoentities:
osisun default 1.17.4.3.9.3.0 \
NS+4700040034020108002001635400|\
Internet=cos|\
Int-X25(80)=031342023004500+PID+03010100
Any help would be appreciated.
-Mike