All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Default <default@advaita.sytes.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] wan card routing
Date: Thu, 08 Nov 2007 21:10:25 +0000	[thread overview]
Message-ID: <47337B41.9070308@advaita.sytes.net> (raw)
In-Reply-To: <8595daf70711080912m680da61x2f38da0ab0facbbf@mail.gmail.com>

Hi

 From your description it looks like there are more problems combined or
connected.
I would recommend to first check just your serial connection to next hop
with whatever tools available and only then to try resolving that
"destination unreachable- admin prohibited" problem.

Imthiyaz Ahmed wrote:
> Hi,
>    I am using sangoma S5141 wan card. I have connected my modem to the 
> card in linux machine. The linux distribution I am using is Redhat AS 
> 4, I am trying to replace the cisco router in my office with the 
> sangoma S5141 wan card. I have configured the card in CHDLC where I 
> can able to ping the serial IP, but with 80% of packet loss
Can you show some longer ping output ? 80% loss can be 4 of 5 packets
missing but that shows nothing, longer ping run may show some
non-randomness (like line protocol going up and down you describe) maybe
pointing to encapsulation problems...
You could also try to ping with packets of small and larger sizes and
look for CRC errors...
If the packet loss is completely random, could be
hardware/cable/noise/whatever problem.

> . And If I browse any http  or ftp or any sites I cant able to browse. 
> When I put tcpdump I am seeing the error like one as below, which 
> means the far end is blocking some traffic.
>
>    IP<source IP:port> > yahoo.com <http://yahoo.com>: port host 
> <destination IP> unreachable - admin prohibited
> The protocol status Lip Dev Prot State goes UP and DOWN.
>
if you see interface going up down up down, it can be anything from
hardware to encapsulation.
maybe if you reconnected the old cisco router and tried "sh interfaces
serial", "show controllers serial" and similiar debugging commands, and
then tried checking against output of debugging tools for your new card,
it would show some differences in setup.

hardware or encapsulation problems could confuse upper layers to the
point that other side of the link now refuses to forward packets for you...
>  Any ideas would be appreciated.
And if you've got lots of time, and proper cables and experience, you
could try to connect your card directly to your old router and test your
card and setup locally, but that would require you to really know what
you are doing.

> Thanks
> Imthiyaz.
>
Good luck
john default




-- 
___________________________________
S pozdravom / Best regards

John Default

tel:     + 421 907 294 849
icq:           277 131 242
mail:    default@advaita.sytes.net
jab:     defaultadvaita@jabber.org
__________________________________
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2007-11-08 21:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08 17:24 [LARTC] wan card routing Imthiyaz Ahmed
2007-11-08 18:40 ` Grant Taylor
2007-11-08 21:10 ` John Default [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=47337B41.9070308@advaita.sytes.net \
    --to=default@advaita.sytes.net \
    --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.