Re: Questions re pseudo-ports

From: Tomi Manninen (terhi.victor@logonet.com)
Date: Thu Dec 07 2000 - 17:07:56 EET

  • Next message: Jorge Matias: "Re: Yam."

    Hi John,

    and sorry, I simply forgot your earlier email...

    > First, the dmascc driver creates only a network interface, and it does not
    > seem possible to associate this interface with an AX.25 port -- if you
    > try to put "dmascc0" in axports, it barfs, and I see no obvious way to
    > attach a port to a dmascc device. What I've done to get around this is use
    > net2kiss to attach dmascc0 to one end of a pty pair, and then kissattach
    > to associate a KISS axport to the other end. This results in a KISS
    > interface that applications can talk to, but creates two unused network
    > devices and seems kludgy. Is there a better way to associate a KISS
    > interface to a network device?

    The association between a kernel network device and a port in axports is
    via the interface callsign, nothing else. You don't "put dmascc0" to
    axports, nor do you put "ax0" there in case of a KISS interface. The port
    name in axports is completely independent of anything else.

    So to make use of the dmascc0 port, you should create a axports entry with
    any name and a unique callsign. Then set the hw address for the scc
    interface to that callsign: ifconfig dmascc0 hw ax25 <callsign>

    That is really what kissattach does for a KISS port. It opens the serial
    device and tells it to go to a special KISS mode thereby creating a
    network device (axN, the name comes from the kernel). Then it sets a few
    parameters and finally, the most important thing: sets the interface hw
    address to the callsign found in axports.

    Using real interface names in axports is of course legal, but it can cause
    much confusion. There is for example _no_ guarantee that a kissattached
    interface be really called ax0 even if it says so in axports. All the ax25
    utilities of course know it by that name but the real interface name (used
    by ifconfig etc.) might be something else in the ax0...99999 range. That's
    why I prefer to use axports names that don't resemble interface names at
    all, to keep the separation clear.

    -- 
    Tomi Manninen           Internet:  eqt.yirdcyr@kerailya.tunkki.fi
    OH2BNS                  AX.25:     terhi.victor@logonet.com
    KP20ME04                Amprnet:   thnvgur.haefvqohla@imsbiz.com
    

    - To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to ilirsabj@yomi.com



    This archive was generated by hypermail 2b30 : Thu Dec 07 2000 - 17:09:48 EET