From: Yasser Abdullah (yasser@alharbitelecom.com)
Date: Tue Jun 08 2004 - 05:08:24 GMT-3
Its working fine with me. Are you using the loopback as DLSW source &
destination? Are loopback networks reachable via the bri?
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Tom
Rogers
Sent: Tuesday, June 08, 2004 5:17 AM
To: Richard Dumoulin; Ahmed Mustafa; ccielab@groupstudy.com
Subject: RE: DLSW over ISDN
I am having the same issues.
I am running ppp encapsulation on Bri interfaces and dialer group with
interesting traffic as all ip and demand-circuit on one side.
ISDN dials whenever there is a change in topology, no issue's there.
But DLSW is not intiating the link even though I have no keepalive 0.
I am wondering what is happening too.
Normally one would think that id DLSW and Bri are on the same router, one
would put keepalive 0 or deny 2065 as an interesting traffic.
Tom
Richard Dumoulin <richard.dumoulin@vanco.es> wrote:
Can you type debug dialer packets ?
-----Original Message-----
From: Ahmed Mustafa [mailto:ahmed.mustafa@sbcglobal.net]
Sent: lunes, 07 de junio de 2004 22:53
To: ccielab@groupstudy.com
Subject: DLSW over ISDN
I was testing DLSW over ISDN, and was in shock that my DLSW peers won't get
established. As a matter of fact, ISDN doesn't even initiate the call and
some how doesn't see DLSW traffic as an interesting traffic.
TCP is a part of IP stack, and simply using the dialer-list 1 protocol ip
permit should bring up the ISDN link, but it won't. I even hard coded TCP
port 2065 at both ends, but interestingly ISDN won't get initiated.
Any help will be appreciated.
Regards,
This archive was generated by hypermail 2.1.4 : Sat Jul 03 2004 - 19:40:35 GMT-3