On Thu, 1 Jul 1999, Farshad Tavallaei wrote:
> Please call 1-800-458-9966 and open a case with us for your routing issue.
> We need your topology, number of routers (i.e. portmasters, cisco, etc),
> and design for your local network, since I have a feeling that you are not
> running OSPF and are doing everything either statically and/or are using
> RIP. You may need to migrate to OSPF for your internal routing protocol,
> since with several PM3s and PM2s, you are better off doing VLSM for your
> dial in pools, and the only internal dynamic routing protocol that we
> support that is capable of propagating variable length routes for the same
> major network is OSPF. Bridging will not help you in this case...I am
> interested in finding out how you got bridging going between your PM3s.
> None of the Portmasters support bridging. There is no bridging
> functionality in any of the COMOS' yet.
> At 11:09 AM 7/1/99 -0500, Conrad Rockenhaus wrote:
> >Ok, I know this may go beyond the scope of this mailing list, but I need a
> >tremendous amount of help. Before, we had two PM3's and ISDN and
> >Dedicated ISDN customers can connect to either of the PM3's and route just
> >We decided to purchase another PM3, and make that for the DISDN customers
> >only, just fine, except now we have more DISDN customers than the DISDN
> >PM3 can handle. Now the DISDN customers that can't fit on the DISDN PM3
> >must connect to PM3-2, which has is always full usually, so if they get
> >disconnected, and connect to PM3-3, we have to fix the routing on PM3-3 to
> >get them to route.
> >Bridging between the PM3's was working fine with two, but now we can't
> >bridge. Anybody have a solution to this problem?
> >Thanks in advance,
> >To unsubscribe, email 'email@example.com' with
> >'unsubscribe portmaster-modems' in the body of the message.
To unsubscribe, email 'firstname.lastname@example.org' with
'unsubscribe portmaster-modems' in the body of the message.