🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.protocols.iso.dev-environ
Article #9

Re: iaed problems

#9
From: Takahiro Kanbe
Date: Mon, 27 Jul 1992 11:25
51 lines
2210 bytes
Hi, dear ISODE'er.

In article <BqGn8u.ABy@fulcrum.bt.co.uk>
	igb@fulcrum.bt.co.uk (Ian G Batten) writes:
> It would appear that the tsap_addr_cmp routine doesn't work.  iaed is the
> only reference I can find.
I examined this problem recently.  It seems that that:

    - It might not be the problem of tsap_addr_cmp().

    -  One of reason is the change (or enhance) in ISO-address handling.


Description:

Iaed(8) in ISODE 7.0 and tsapd(8) in 8.0 compares only the selectors of
two TSAP-address (at least, RFC-1006 TS-stack).  In 8.0 it compares not
also TSAP selectors but NSAP address.

And, presentation address which support/bootsvc script generates forms:

presentationAddress= Internet=hostname

This address will convert into ISODE internal format with NSAP-address
part which has hostname's IP-address and *zero* port number.

Thus, when iaed(8) compares two TSAP-address, NSAP-address part, port
number dose not match.

Both iaed(8) and tsapd(8) still listens iso-tsap port in this case.


Solution:

One point of view is that zero port means default (or any) port.  I'm
not sure this is correct or not.  But changing nsap_addr_cmp() in
compat/nsapcmp.c is one of possible solution.

Another is change each presentationAddress which iaed(8) listens:

presentationAddress= Internet=hostname+102

The port number 102 is iso-tsap port.  Now, iaed(8) got correct port
number in NSAP-address (in TSAP-address).  This works for me, but not
tested very much.

Thanks.

--
Takahiro Kanbe				FXIS / Network Team.
					taka@fxis.fujixerox.co.jp
Technical Details
Message-ID: <Bs1p35.Hro@fxisms.fxis.fujixerox.co.jp>
Path: arc1-ca.pugleaf.net!sparky!uunet!sun-barr!sh.wide!fxmxgw!fxisms!taka
References: <1992Jun25.234529.425@cu23.crl.aecl.ca> <BqGn8u.ABy@fulcrum.bt.co.uk>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!sun-barr!sh.wide!fxmxgw!fxisms!taka
From: taka@fxis.fujixerox.co.jp (Takahiro Kanbe)
Newsgroups: comp.protocols.iso.dev-environ
Subject: Re: iaed problems
Message-ID: <Bs1p35.Hro@fxisms.fxis.fujixerox.co.jp>
Date: 27 Jul 92 11:25:50 GMT
References: <1992Jun25.234529.425@cu23.crl.aecl.ca>
 <BqGn8u.ABy@fulcrum.bt.co.uk>
Sender: news@fxisms.fxis.fujixerox.co.jp (USETNET News)
Organization: Fuji Xerox Information Systems Co., Ltd., Tokyo, Japan.
Lines: 51
In-Reply-To: igb@fulcrum.bt.co.uk's message of 26 Jun 92 16:02:54 GMT
Nntp-Posting-Host: litra.nwt.fxis.fujixerox.co.jp