All of lore.kernel.org
 help / color / mirror / Atom feed
From: "bar" <bar1@poczta.onet.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] OSPF problems
Date: Sun, 30 Mar 2003 12:06:35 +0000	[thread overview]
Message-ID: <marc-lartc-104902606003236@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104873807508259@msgid-missing>


> Message: 3
> Date: Wed, 26 Mar 2003 20:06:14 -0800 (PST)
> From: Jeff Nye <jeffnye20@yahoo.com>
> To: lartc@mailman.ds9a.nl
> Subject: [LARTC] OSPF problems
>
> I have a fairly simply laid out network that could easily use static
routing.  However, I
> plan to expand quickly and don't wish to spend the better part of my life
maintaining
> static routes.
>
> INTERNET
>    |
> ---------
> Gateway | - LAN 172.16.1.x
>         | - LINK 192.168.1.1
> ---------
>    |<----wifi
> ---------
> router 2 | -LAN 172.16.2.x
>          | -Link 192.168.1.2
> ---------
>    |<----wifi
> ---------
> router 3 | -LAN 172.16.3.x
>          | -Link 192.168.1.3
> ---------
>
>
> OSPF seems to work however when connected to the LAN on either router 2 or
3 I get
> periodic time outs.  It looks like the routers keep trying to elect a new
chief and the
> little indians are getting extremely confused.  Does anyone know what
would be causing
> this and how I might avoid it.  I tested it on a LAN with cross over
cables where the
> wifi is and I get the same errors.
>
> I am running RH 8.0, ZEBRA version 0.93A.  I used the example found in the
"Linux
> Advanced Routing & Traffic Control HOWTO" chapter 17.  I have searched
many many websites
> in search of help and now turn to you the experts to help a fellow geek.

if you could show output from commands:
sh ip o n
sh ip o d

Regards,
bar


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2003-03-30 12:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-27  4:06 [LARTC] OSPF problems Jeff Nye
2003-03-30 12:06 ` bar [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-104902606003236@msgid-missing \
    --to=bar1@poczta.onet.pl \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.