Re: Linuxnode appears broken

From: Tomi Manninen OH2BNS (vesoh.fkfw@carr-sheppards.co.uk)
Date: Tue Oct 02 2001 - 10:45:47 EEST

  • Next message: ROBERT MOOMA: "URGENT AND CONFIDENTIAL"

    On Mon, 1 Oct 2001, Roger Harris wrote:

    > Thanks for the reply. I tried reading /proc/net/nr_neigh and it looked OK
    > and didn't cause an error.
    >
    > Anyway, the problem has now been solved, simply by rebooting without
    > reading my routes config file (the file which my system updates once an
    > hour with nodesave). This gave me an empty routes table and the node worked
    > OK. I then read in just the routes (not the nodes) from my saved config
    > file, and let it re-learn the nodes. The node is now functioning perfectly.

    This is really interesting.

    > I've kept a copy of my old routes config file. It must have an entry in
    > which upsets the node. At first sight, it looks OK, but I'll take a closer
    > look.

    Please send it to me also. 

    -- 
Tomi Manninen           Internet:  hjkun@nationwideaccess.co.uk
OH2BNS                  AX.25:     zng.niomjycssa@hagrid.pulsnet.pl
KP20ME04                Amprnet:   terhi.victor@logonet.com

    -
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to terhi.victor@logonet.com
More majordomo info at  http://vger.kernel.org/majordomo-info.html

    This archive was generated by hypermail 2b30 : Tue Oct 02 2001 - 10:53:08 EEST