Re: Randomly changed txdelay ?

From: Tomi Manninen OH2BNS (kkgftha.easbs@gilead.com)
Date: Tue Oct 23 2001 - 18:29:54 EEST

  • Next message: Nick Papadonis: "Re: Soundmodem-0.5 ???"

    On Tue, 23 Oct 2001, g3orh wrote:

    > Hi List,
    > Monitoring my main ax25/netrom channel (which is port eth for
    > ethernet) and which feeds the BPQ nodes system for cluster traffic (Spider)
    > I noticed over the last 2 days (using listen eth -a -c) this :-
    >
    > eth: Txdelay 1420 ms
    >
    > This was sent about 2 or 3 times mixed with other traffic then nothing for a
    > while. This seemed to occurr around the time that my nr_neighbour went
    > choke. He handles my cluster link feed and user input/output so I expect him
    > to choke occasionally (9k6 link simplex maxframe 4).
    >
    > Can anyone tell me why this happens. No txdelay of that value is set
    > anywhere by me so it appears to be set by the system randomly if there is a
    > small hiccup somewhere.

    Most probably it's a packet that gets somehow corrupted on its way to
    listen. That happens at times. I don't think the whole concept of txdelay
    applies to BPQ ethernet... 

    -- 
Tomi Manninen           Internet:  pzav.xkasbxrum@ncsc.mil
OH2BNS                  AX.25:     xikmxt.qwngu@dsl-157-43.utaonline.at
KP20ME04                Amprnet:   qge.zhmlpw@host155-101.crowley.pl

    -
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to qalavlcz.xnlctnehq@proxy01.r-it.at
More majordomo info at  http://vger.kernel.org/majordomo-info.html

    This archive was generated by hypermail 2b30 : Tue Oct 23 2001 - 18:42:27 EEST