Re: NETROM_CALL is it broken or just me?

From: Tomi Manninen OH2BNS (tzuw.gvcf@pspt.fi)
Date: Tue Jul 17 2001 - 11:51:46 EEST

  • Next message: John Feist: "Re: NETROM_CALL DUH!"

    On Tue, 17 Jul 2001, pa3gcu wrote:

    > On Monday 16 July 2001 20:26, Tomi Manninen wrote:

    > > root@oh2bns ~ # netrom_call netrom oh2bns oh2rbi-1 | tr '\r' '\n'

    > One real pitfall here is the portname, netrom, its so simple but so
    > confusing, yes it works with "netrom" as thats what nr0 is called here, but
    > on the otherhand normally speaking netrom connects go via an "ax25"
    > interface, such as scc3 like i was trying to use.

    The whole point of NET/ROM (or any layer 3 / 4 protocol) is that you don't
    need, or even want to know what AX.25 port the connection goes out on. Nor
    do you want to know anything about the route of AX.25 connections it
    travels to get to its destination. Also in a real network the AX.25 port
    and the route can change dynamically at any time and you don't want to
    know about it.

    If you are thinking like that, ie. you want to make a NET/ROM connection
    on the AX.25 port scc3 then you have completely missed the point of
    NET/ROM...

    > Possably a mention of this in the man page would be of much help to
    > dummies like me and a million others who seems to be in the same boot,
    > or so it would seem.

    Well, it is true that other software doesn't really have the concept of
    netrom ports or interfaces. Usually they have one logical netrom port or
    at most two. Like BPQ: one for the "node" function, one for the bbs. But
    you can't separate them.

    So in that sense a mention in the man page might be in order. It's just
    that at some point we need to add the whole genesis (and
    equivalents) in there...

    > Just one question left, why is it that netrom_call ejects such confusing
    > error messges when it is abused by dummies like "me", i am sure it should
    > surpt out "readable" error messages even when invoked on a "remote telnet
    > link".

    I don't find them all that confusing. They are completely readable when
    the program is used like it's intended to be used.

    -- 
    Tomi Manninen           Internet:  ypjk.itwczfilhw@kerailya.tunkki.fi
    OH2BNS                  AX.25:     xbco@pnl.gov
    KP20ME04                Amprnet:   terhi.victor@logonet.com
    

    - To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to arufr@sprint-hsd.net



    This archive was generated by hypermail 2b30 : Tue Jul 17 2001 - 12:07:05 EEST