From david@portmasters.com Wed Jun 11 15:52:41 2003 Received: from portmasters.com (root@linux2.advmed.com [216.138.104.67]) by linux2.advmed.com (8.11.4/8.11.1) with ESMTP id h5BKqf804220 for ; Wed, 11 Jun 2003 15:52:41 -0500 Received: from davidi (firewall.advmed.com [216.138.104.126]) by portmasters.com (8.11.1/8.11.1) with ESMTP id h5BKpvS13818 for ; Wed, 11 Jun 2003 15:51:57 -0500 From: "David Naraghi" To: Date: Wed, 11 Jun 2003 15:52:30 -0500 Message-ID: <002d01c3305b$5fd270d0$a500000a@davidi> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002E_01C33031.76FC68D0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Cc: Subject: [Portmaster-users] test X-BeenThere: portmaster-users@portmasters.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2003 20:52:41 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_002E_01C33031.76FC68D0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit test ------=_NextPart_000_002E_01C33031.76FC68D0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
test
------=_NextPart_000_002E_01C33031.76FC68D0-- From david@portmasters.com Wed Jun 11 16:36:57 2003 Received: from portmasters.com (root@linux2.advmed.com [216.138.104.67]) by linux2.advmed.com (8.11.4/8.11.1) with ESMTP id h5BLav804764 for ; Wed, 11 Jun 2003 16:36:57 -0500 Received: from davidi (firewall.advmed.com [216.138.104.126]) by portmasters.com (8.11.1/8.11.1) with ESMTP id h5BLaES14068 for ; Wed, 11 Jun 2003 16:36:14 -0500 From: "David Naraghi" To: Date: Wed, 11 Jun 2003 16:36:46 -0500 Message-ID: <003701c33061$8f120670$a500000a@davidi> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0038_01C33037.A63BFE70" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Cc: Subject: [Portmaster-users] Testing some more X-BeenThere: portmaster-users@portmasters.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2003 21:36:57 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0038_01C33037.A63BFE70 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi miles, Hi jake! ------=_NextPart_000_0038_01C33037.A63BFE70 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
Hi = miles, Hi=20 jake!
------=_NextPart_000_0038_01C33037.A63BFE70-- From david@portmasters.com Thu Jun 12 10:12:10 2003 Received: from portmasters.com (root@linux2.advmed.com [216.138.104.67]) by linux2.advmed.com (8.11.4/8.11.1) with ESMTP id h5CFCA811611 for ; Thu, 12 Jun 2003 10:12:10 -0500 Received: from davidi (firewall.advmed.com [216.138.104.126]) by portmasters.com (8.11.1/8.11.1) with ESMTP id h5CFBWS21018 for ; Thu, 12 Jun 2003 10:11:32 -0500 From: "David Naraghi" To: Subject: RE: [Portmaster-users] test Date: Thu, 12 Jun 2003 10:11:58 -0500 Message-ID: <004501c330f4$f7dac910$a500000a@davidi> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0046_01C330CB.0F04C110" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal In-Reply-To: <004101c33069$0f6a7440$9600000a@jake> Cc: X-BeenThere: portmaster-users@portmasters.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jun 2003 15:12:11 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0046_01C330CB.0F04C110 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit La La La talking all day... sent at 10:11 am by david time. -----Original Message----- From: Jake Messinger [mailto:jake@advmed.com] Sent: Wednesday, June 11, 2003 5:29 PM To: David Naraghi; portmaster-users@new.portmasters.com Subject: Re: [Portmaster-users] test Received. ----- Original Message ----- From: David Naraghi To: portmaster-users@new.portmasters.com Sent: Wednesday, June 11, 2003 3:52 PM Subject: [Portmaster-users] test test _____ _______________________________________________ Portmaster-users mailing list Portmaster-users@portmasters.com http://new.portmasters.com/mailman/listinfo/portmaster-users ------=_NextPart_000_0046_01C330CB.0F04C110 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
La La=20 La talking all day... sent at 10:11 am by david = time.
 
-----Original Message-----
From: Jake = Messinger=20 [mailto:jake@advmed.com]
Sent: Wednesday, June 11, 2003 = 5:29=20 PM
To: David Naraghi;=20 portmaster-users@new.portmasters.com
Subject: Re: = [Portmaster-users]=20 test

Received.
----- Original Message -----
From:=20 David=20 Naraghi
To: portmaster-users@new= .portmasters.com=20
Sent: Wednesday, June 11, = 2003 3:52=20 PM
Subject: [Portmaster-users] = test

test

=

_______________________________________________
Portmaster-user= s=20 mailing list
Portmaster-users@portmas= ters.com
htt= p://new.portmasters.com/mailman/listinfo/portmaster-users
------=_NextPart_000_0046_01C330CB.0F04C110-- From david@portmasters.com Tue Jun 17 09:59:44 2003 Received: from portmasters.com (root@linux2.advmed.com [216.138.104.67]) by linux2.advmed.com (8.11.4/8.11.1) with ESMTP id h5HExiA32630 for ; Tue, 17 Jun 2003 09:59:44 -0500 Received: from davidi (firewall.advmed.com [216.138.104.126]) by portmasters.com (8.11.1/8.11.1) with ESMTP id h5HExcS32096 for ; Tue, 17 Jun 2003 09:59:38 -0500 From: "David Naraghi" To: Date: Tue, 17 Jun 2003 09:58:42 -0500 Message-ID: <000201c334e0$f1e37440$a500000a@davidi> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0003_01C334B7.090D6C40" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Cc: Subject: (PM) test X-BeenThere: portmaster-users@portmasters.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2003 14:59:44 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0003_01C334B7.090D6C40 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit test ------=_NextPart_000_0003_01C334B7.090D6C40 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
test
------=_NextPart_000_0003_01C334B7.090D6C40-- From owner-portmaster-users@linux2.advmed.com Wed Aug 30 15:00:11 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id PAA19488 for portmaster-users-outgoing; Wed, 30 Aug 2000 15:00:11 -0500 Received: from localhost (jake@localhost) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id PAA19485 for ; Wed, 30 Aug 2000 15:00:08 -0500 Date: Wed, 30 Aug 2000 15:00:08 -0500 (CDT) From: Jake Messinger X-Sender: jake@linux2.advmed.com To: portmaster-users@portmasters.com Subject: (PM) Just a test Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Jake Messinger This is just a test. Please disregard. -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ Jake Messinger, VP. ph:713-772-6690 Visit: portmasters.com AMS, Inc. fx:713-774-3498 advmed.com 8300 Bissonnet #400 jake@jakes.org disc.cba.uh.edu Houston, Texas 77074 http://jakes.org ICQ# 4403734 Adjunct Professor University of Houston, CBA jake@uh.edu ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ INVENTOR OF the _.,-*~''~*-,._ SQUIGGLES (c) 1978 - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Fri Sep 1 11:41:08 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id LAA25777 for portmaster-users-outgoing; Fri, 1 Sep 2000 11:41:08 -0500 Received: from localhost (jake@localhost) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id LAA25774 for ; Fri, 1 Sep 2000 11:41:06 -0500 Date: Fri, 1 Sep 2000 11:41:06 -0500 (CDT) From: Jake Messinger X-Sender: jake@linux2.advmed.com To: portmaster-users@portmasters.com Subject: (PM) The list move and new comos Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Jake Messinger Please notify me (jake@portmasters.com) if you are experiencing problems with the mailing lists, possibly due to the list move. There should be little to no difference as we are using the same mailing programs. The list move has NOTHING to do with the fate of the pm3. I have it on good authority that they are currently IN production and there are many units in stock. The demand is still there. There will also be a new com os release any day now... Carl will be issuing an announcement. -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ Jake Messinger, VP. ph:713-772-6690 Visit: portmasters.com AMS, Inc. fx:713-774-3498 advmed.com 8300 Bissonnet #400 jake@jakes.org disc.cba.uh.edu Houston, Texas 77074 http://jakes.org ICQ# 4403734 Adjunct Professor University of Houston, CBA jake@uh.edu ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ INVENTOR OF the _.,-*~''~*-,._ SQUIGGLES (c) 1978 - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Fri Sep 1 12:30:59 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id MAA25978 for portmaster-users-outgoing; Fri, 1 Sep 2000 12:30:59 -0500 Received: from wam.defnet.com (wam.defnet.com [207.19.167.3]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id MAA25974; Fri, 1 Sep 2000 12:30:56 -0500 Received: from localhost (merkel@localhost) by wam.defnet.com (8.9.3/8.9.3) with ESMTP id NAA25374; Fri, 1 Sep 2000 13:36:11 -0400 Date: Fri, 1 Sep 2000 13:36:11 -0400 (EDT) From: "Eric J. Merkel" To: Jake Messinger cc: portmaster-users@portmasters.com Subject: Re: (PM) The list move and new comos In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: "Eric J. Merkel" On Fri, 1 Sep 2000, Jake Messinger wrote: > There will also be a new com os release any day now... Carl will be > issuing an announcement. Does it include different modem code or is it just bug fixes? Eric Merkel / MetaLink Technologies, Inc ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~* Email: merkel@metalink.net Phone: 419-782-3472 ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~* - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Fri Sep 1 14:06:06 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id OAA26666 for portmaster-users-outgoing; Fri, 1 Sep 2000 14:06:06 -0500 Received: from linux.advmed.com (root@advmed.com [207.235.58.129]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id OAA26662; Fri, 1 Sep 2000 14:06:05 -0500 Received: from localhost (jake@localhost) by linux.advmed.com (8.9.3/8.9.3) with ESMTP id OAA32644; Fri, 1 Sep 2000 14:11:52 -0500 Date: Fri, 1 Sep 2000 14:11:52 -0500 (CDT) From: Jake Messinger To: "Eric J. Merkel" cc: Jake Messinger , portmaster-users@portmasters.com Subject: Re: (PM) The list move and new comos In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Jake Messinger On Fri, 1 Sep 2000, Eric J. Merkel wrote: > On Fri, 1 Sep 2000, Jake Messinger wrote: > > There will also be a new com os release any day now... Carl will be > > issuing an announcement. > > Does it include different modem code or is it just bug fixes? I dont know... there was an email about it a few days ago. Did the list see that? -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ Jake Messinger, VP. ph:713-772-6690 Visit: portmasters.com AMS, Inc. fx:713-774-3498 advmed.com 8300 Bissonnet #400 jake@jakes.org disc.cba.uh.edu Houston, Texas 77074 http://jakes.org ICQ# 4403734 Adjunct Professor University of Houston, CBA jake@uh.edu ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ INVENTOR OF the _.,-*~''~*-,._ SQUIGGLES (c) 1978 - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Fri Sep 1 16:35:45 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id QAA27841 for portmaster-users-outgoing; Fri, 1 Sep 2000 16:35:45 -0500 Received: from smtp.burgoyne.com (email.burgoyne.com [209.197.0.17]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id QAA27838 for ; Fri, 1 Sep 2000 16:35:38 -0500 Received: from benji (hal35.burgoyne.com [209.197.9.37]) by smtp.burgoyne.com (8.10.2/8.9.1) with SMTP id e81LacX19845 for ; Fri, 1 Sep 2000 15:36:38 -0600 Message-ID: <001301c0145c$9fce7b70$2509c5d1@burgoyne.com> From: "Paul" To: Subject: (PM) Max Ascend 4000 Date: Fri, 1 Sep 2000 15:36:01 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: "Paul" We have inherited a Max Ascend 4000 and don't know the full-access password. Does anyone know how to change that? - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Fri Sep 1 17:15:21 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id RAA28313 for portmaster-users-outgoing; Fri, 1 Sep 2000 17:15:21 -0500 Received: from mail.frontier.net (IDENT:91@frontier.net [199.45.141.1]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id RAA28308; Fri, 1 Sep 2000 17:15:18 -0500 Received: from animas.frontier.net (animas.frontier.net [199.45.141.1]) by mail.frontier.net (Postfix) with ESMTP id D70CB3EE862; Fri, 1 Sep 2000 16:15:47 -0600 (MDT) Date: Fri, 1 Sep 2000 16:15:47 -0600 (MDT) From: Charlie Watts To: Jake Messinger Cc: portmaster-users@portmasters.com Subject: Re: (PM) The list move and new comos In-Reply-To: Message-ID: X-No-Archive: Yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Charlie Watts > The list move has NOTHING to do with the fate of the pm3. I have it on > good authority that they are currently IN production and there are many > units in stock. The demand is still there. It's always a little suspicious when a company no longer runs the support E-mail list for their own products, dontcha think? Why would they do this? I fear for livingston.com. I worry that the domain name is going to go away. > There will also be a new com os release any day now... Carl will be > issuing an announcement. That's good to hear, at least. -- Charlie Watts Quidquid latine dictum sit, altum viditur. cewatts@frontier.net (Whatever is said in Latin sounds profound.) - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Fri Sep 1 17:58:25 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id RAA28780 for portmaster-users-outgoing; Fri, 1 Sep 2000 17:58:25 -0500 Received: from linux.advmed.com (root@advmed.com [207.235.58.129]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id RAA28775; Fri, 1 Sep 2000 17:58:23 -0500 Received: from localhost (jake@localhost) by linux.advmed.com (8.9.3/8.9.3) with ESMTP id SAA02752; Fri, 1 Sep 2000 18:03:54 -0500 Date: Fri, 1 Sep 2000 18:03:53 -0500 (CDT) From: Jake Messinger To: Charlie Watts cc: Jake Messinger , portmaster-users@portmasters.com Subject: Re: (PM) The list move and new comos In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Jake Messinger On Fri, 1 Sep 2000, Charlie Watts wrote: > > The list move has NOTHING to do with the fate of the pm3. I have it on > > good authority that they are currently IN production and there are many > > units in stock. The demand is still there. > > It's always a little suspicious when a company no longer runs the support > E-mail list for their own products, dontcha think? Why would they do this? Keep in mind that Ascend NEVER ran a support mailing list. The support mailing lists sponsored by Livingston were never intended for official technical support. They were provided as a courtesy. > I fear for livingston.com. I worry that the domain name is going to go > away. Im sure the website will not go away without prior notice. Lucent has their eSight support site which has all the portmaster documentation online, and sales info for the Portmaster line on its site. In the future, Livingston.com might also possibly be hosted elsewhere. I plan to greatly expand (with help) the portmasters.com site to offer a support site that will never go away. -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ Jake Messinger, VP. ph:713-772-6690 Visit: portmasters.com AMS, Inc. fx:713-774-3498 advmed.com 8300 Bissonnet #400 jake@jakes.org disc.cba.uh.edu Houston, Texas 77074 http://jakes.org ICQ# 4403734 Adjunct Professor University of Houston, CBA jake@uh.edu ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ INVENTOR OF the _.,-*~''~*-,._ SQUIGGLES (c) 1978 - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Fri Sep 1 18:10:08 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id SAA28918 for portmaster-users-outgoing; Fri, 1 Sep 2000 18:10:08 -0500 Received: from hal.lucentradius.com (root@hal.lucentradius.com [158.222.8.12]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id SAA28913 for ; Fri, 1 Sep 2000 18:10:03 -0500 Received: from lucentradius.com (lina.lucentradius.com [158.222.8.35]) by hal.lucentradius.com (8.9.3/8.9.3) with ESMTP id QAA02817; Fri, 1 Sep 2000 16:11:01 -0700 (PDT) Message-ID: <39B03769.39FA4A3E@lucentradius.com> Date: Fri, 01 Sep 2000 16:10:33 -0700 From: Thomas C Kinnen Organization: Lucent Technologies INS X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Charlie Watts CC: portmaster-users@portmasters.com Subject: Re: (PM) The list move and new comos References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Thomas C Kinnen Charlie Watts wrote: > > > The list move has NOTHING to do with the fate of the pm3. I have it on > > good authority that they are currently IN production and there are many > > units in stock. The demand is still there. > > It's always a little suspicious when a company no longer runs the support > E-mail list for their own products, dontcha think? Why would they do this? None of the Portmaster-* mail lists were ever official support lists. The only official support via e-mail was/is support@livingston.com. -- Thomas C Kinnen - [RADIUS Engineer] - LUCENT Technologies INS "All of the opinions stated above are my own and not my employer's, unless they were given to me by my employer" - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Sat Sep 2 03:21:20 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id DAA31877 for portmaster-users-outgoing; Sat, 2 Sep 2000 03:21:20 -0500 Received: from web115.yahoomail.com (web115.yahoomail.com [205.180.60.88]) by linux2.advmed.com (8.9.3/8.9.3) with SMTP id DAA31874 for ; Sat, 2 Sep 2000 03:20:44 -0500 Received: (qmail 23562 invoked by uid 60001); 2 Sep 2000 08:21:43 -0000 Message-ID: <20000902082143.23561.qmail@web115.yahoomail.com> Received: from [203.197.148.98] by web115.yahoomail.com; Sat, 02 Sep 2000 01:21:43 PDT Date: Sat, 2 Sep 2000 01:21:43 -0700 (PDT) From: Vijay Kolaventy Subject: (PM) LAN Problem To: portmaster-users@portmasters.com Cc: portmaster-users@portmaster.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Vijay Kolaventy Hi I am running an ISP in India and I am using PM3A-2E. The PM3 is running on 3.9b27. I have configured NAT on the machine to use on valid IP as I am short of those. Everything worked fine until recently, my dialin users are not able to access any of my machines on the LAN like the DNS, Web and the Mail servers while they are able to the browse the Internet without any problem. I could not even ping the router which is the gateway for the Internet. Last time this got rectified by itself. Now its the second time and I cannot figure out whats wrong. I am able to ping the PM3 from every machine on the LAN and vice versa. Please help. Best regards, Vijay __________________________________________________ Do You Yahoo!? Yahoo! Mail - Free email you can access from anywhere! http://mail.yahoo.com/ - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Sat Sep 2 13:04:23 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id NAA00567 for portmaster-users-outgoing; Sat, 2 Sep 2000 13:04:23 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id NAA00564 for ; Sat, 2 Sep 2000 13:04:19 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id LAA10454 for ; Sat, 2 Sep 2000 11:00:04 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id LAA17550 for ; Sat, 2 Sep 2000 11:05:14 -0700 (PDT) Received: from server2.thevillagelink.com ([208.169.219.6]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id LAA10450 for ; Sat, 2 Sep 2000 11:00:03 -0700 (PDT) Received: from blue (blue.thevillagelink.com [208.169.219.10]) by server2.thevillagelink.com (8.9.3/8.8.7) with SMTP id OAA23178 for ; Sat, 2 Sep 2000 14:05:58 -0400 Message-ID: <000801c0150a$90d4df20$0adba9d0@thevillagelink.com> From: "annie covert" To: References: Subject: (PM) Weather affecting mail server? Date: Sat, 2 Sep 2000 14:21:08 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: "annie covert" Has anyone heard that weather (dampness, humidity, etc.) will effect customers accessing their email, or is someone just pulling my leg? - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Sat Sep 2 13:49:51 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id NAA00774 for portmaster-users-outgoing; Sat, 2 Sep 2000 13:49:51 -0500 Received: from enterprise.cistron.net (enterprise.cistron.net [195.64.68.33]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id NAA00771 for ; Sat, 2 Sep 2000 13:49:48 -0500 Received: (from daemon@localhost) by enterprise.cistron.net (8.9.1a/8.9.1/Debian/GNU) id UAA03414; Sat, 2 Sep 2000 20:50:57 +0200 From: list-portmaster-users@news.cistron.nl (Miquel van Smoorenburg) Subject: Re: (PM) Weather affecting mail server? Date: 2 Sep 2000 18:50:56 GMT Organization: Cistron Internet Services B.V. Lines: 9 Message-ID: <8ori6g$3ah$1@enterprise.cistron.net> References: <000801c0150a$90d4df20$0adba9d0@thevillagelink.com> X-Trace: enterprise.cistron.net 967920656 3409 195.64.65.200 (2 Sep 2000 18:50:56 GMT) X-Complaints-To: abuse@cistron.nl To: portmaster-users@portmasters.com Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: list-portmaster-users@news.cistron.nl (Miquel van Smoorenburg) In article <000801c0150a$90d4df20$0adba9d0@thevillagelink.com>, annie covert wrote: >Has anyone heard that weather (dampness, humidity, etc.) will effect >customers accessing their email, or is someone just pulling my leg? Yes, it is possible on certain types of links. Check out RFC1149, which talks about these links: http://www.rfc-editor.org/rfc/rfc1149.txt Mike. -- The From: and Reply-To: addresses are internal news2mail gateway addresses. Reply to the list or to miquels@cistron.nl (Miquel van Smoorenburg) - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Sat Sep 2 18:25:21 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id SAA02115 for portmaster-users-outgoing; Sat, 2 Sep 2000 18:25:21 -0500 Received: from egypt.sevenkings.net (egypt.sevenkings.net [216.172.23.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id SAA02112 for ; Sat, 2 Sep 2000 18:25:17 -0500 Received: from jk3329.sevenkings.net (jk3329.sevenkings.net [216.172.23.1]) by egypt.sevenkings.net (8.9.0/8.9.0) with SMTP id TAA13017 for ; Sat, 2 Sep 2000 19:26:10 -0400 (EDT) From: Egan To: portmaster-users@portmasters.com Subject: Re: (PM) Weather affecting mail server? Date: Sat, 02 Sep 2000 19:26:09 -0400 Message-ID: References: <000801c0150a$90d4df20$0adba9d0@thevillagelink.com> <8ori6g$3ah$1@enterprise.cistron.net> In-Reply-To: <8ori6g$3ah$1@enterprise.cistron.net> X-Mailer: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Egan On 2 Sep 2000 18:50:56 GMT, list-portmaster-users@news.cistron.nl (Miquel van Smoorenburg) wrote: >>Has anyone heard that weather (dampness, humidity, etc.) will effect >>customers accessing their email, or is someone just pulling my leg? > >Yes, it is possible on certain types of links. Check out RFC1149, >which talks about these links: http://www.rfc-editor.org/rfc/rfc1149.txt No pigeon feces! But all pigeon feces aside, rain can affect some telephone lines, mostly older ones, to the point that data transmission is degraded. - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Sat Sep 2 21:12:37 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id VAA03006 for portmaster-users-outgoing; Sat, 2 Sep 2000 21:12:37 -0500 Received: from cdsinet.net (server1.cdsinet.net [38.195.110.10]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id VAA03002 for ; Sat, 2 Sep 2000 21:12:34 -0500 Received: from hemroids [38.198.19.14] by cdsinet.net (SMTPD32-6.03) id A3D12CCE02A8; Sat, 02 Sep 2000 21:13:37 -0500 Message-ID: <043701c0154c$4f545ac0$0101a8c0@hemroids> From: "John Narron" To: References: <000801c0150a$90d4df20$0adba9d0@thevillagelink.com> Subject: Re: (PM) Weather affecting mail server? Date: Sat, 2 Sep 2000 21:03:09 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: "John Narron" In a more serious answer (Miquel ;), We have had experiences when the weather is bad, our service is bad. Coincidence, maybe. My only "explanation" is weather affecting the telephone service. We'll notice a drop in high- speed connections on rainy/stormy days and get a lot of complaints from our rural users on such days about not being able to connect at all. If this is a true-case, I'm assuming its a telco problem. What I suggest to our customers experiencing such problems is to check the telco box outside their house for dirty and damaged connectors (please, advise them to NOT DO THIS when raining, there a potential 133V circuit in that box). If so, a little cleaning or a replacement goes a long way. If that doesn't fix the problem, have the customer request that the local telco test the circuit on those days. If you have good (read: not-lazy) workers at the local telco, they'll test it out and "repair" if the noise level is too high. - John ----- Original Message ----- From: "annie covert" To: Sent: Saturday, September 02, 2000 1:21 PM Subject: (PM) Weather affecting mail server? > Has anyone heard that weather (dampness, humidity, etc.) will effect > customers accessing their email, or is someone just pulling my leg? > > - > To unsubscribe, email 'majordomo@portmasters.com' with > 'unsubscribe portmaster-users' in the body of the message. > Searchable list archive: > - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Sun Sep 3 00:31:11 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id AAA03919 for portmaster-users-outgoing; Sun, 3 Sep 2000 00:31:11 -0500 Received: from elroynet.com (elroynet.com [206.57.4.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id AAA03915 for ; Sun, 3 Sep 2000 00:31:08 -0500 Received: from ncdc1000 (ntdc1000.elroynet.com [206.57.4.195]) by elroynet.com (8.9.3/8.9.3) with SMTP id AAA18777 for ; Sun, 3 Sep 2000 00:26:58 -0500 Message-ID: <001201c01568$395ca990$c30439ce@ncdc1000> From: "Tony Harris" To: References: <000801c0150a$90d4df20$0adba9d0@thevillagelink.com> <043701c0154c$4f545ac0$0101a8c0@hemroids> Subject: Re: (PM) Weather affecting mail server? Date: Sun, 3 Sep 2000 00:31:34 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: "Tony Harris" I've seen weather play some really nasty tricks, but it seems to all be based upon the telco and the quality of their gear, and how well they have set themselves up. For example, in a few of our pops we rarely have problems - even in rain we don't see many errors, some static on phone lines that are far out from the CO, but nothing major. But, in another remote pop of ours, it has to be the worst thing EVER. Whenever there is lightning, we get serious packet loss and CRC errors and so forth on our T1, and people dialing into the CT1's have a pain staying connected. I keep trying to tell the telco they need to check their grounding as this doesn't happen with other telco's, but they are rather "thick" when it comes to that and they say I should just accept it as the way it is. Some telcos are great, some suck. - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Sun Sep 3 01:55:59 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id BAA04312 for portmaster-users-outgoing; Sun, 3 Sep 2000 01:55:59 -0500 Received: from olympus.net (quinault.olympus.net [198.133.237.6]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id BAA04309 for ; Sun, 3 Sep 2000 01:55:57 -0500 Received: from coyote.scandaroon.com ([207.149.192.229]) by olympus.net with esmtp (Exim 3.12 #1) id 13VThx-0004DT-00 for portmaster-users@portmasters.com; Sat, 02 Sep 2000 23:56:49 -0700 Mime-Version: 1.0 Message-Id: In-Reply-To: References: <000801c0150a$90d4df20$0adba9d0@thevillagelink.com> <8ori6g$3ah$1@enterprise.cistron.net> Date: Sat, 2 Sep 2000 23:56:04 -0700 To: portmaster-users@portmasters.com From: John W Baxter Subject: Re: (PM) Weather affecting mail server? Content-Type: text/plain; charset="us-ascii" Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: John W Baxter At 19:26 -0400 9/2/00, Egan wrote: >...rain can affect some telephone lines, >mostly older ones, to the point that data transmission is degraded. So can the lack of rain...we have customers whose lines quite predictably worsen significantly after about 3 days of sun following a period (of any length) of rain. Being on the margin of a body of salt water doesn't help any...so many connections, only one of which has to corrode. --John -- John Baxter jwblist@olympus.net Port Ludlow, WA, USA - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Sun Sep 3 02:13:10 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id CAA04431 for portmaster-users-outgoing; Sun, 3 Sep 2000 02:13:10 -0500 Received: from olympus.net (quinault.olympus.net [198.133.237.6]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id CAA04428 for ; Sun, 3 Sep 2000 02:13:08 -0500 Received: from coyote.scandaroon.com ([207.149.192.229]) by olympus.net with esmtp (Exim 3.12 #1) id 13VTyZ-0004RI-00 for portmaster-users@portmasters.com; Sun, 03 Sep 2000 00:13:59 -0700 Mime-Version: 1.0 Message-Id: In-Reply-To: <043701c0154c$4f545ac0$0101a8c0@hemroids> References: <000801c0150a$90d4df20$0adba9d0@thevillagelink.com> <043701c0154c$4f545ac0$0101a8c0@hemroids> Date: Sun, 3 Sep 2000 00:13:13 -0700 To: From: John W Baxter Subject: Re: (PM) Weather affecting mail server? Content-Type: text/plain; charset="us-ascii" Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: John W Baxter At 21:03 -0500 9/2/00, John Narron wrote: >If that doesn't >fix the problem, have the customer request that the local telco >test the circuit on those days. If you have good (read: not-lazy) >workers at the local telco, they'll test it out and "repair" if >the noise level is too high. In our territory, one can submit either a normal voice trouble report, or can submit one via an automated touch-tone menu system. The latter causes an automated line test to be done, with the results attached to the trouble report. The former often causes the agent to refuse to order a line test. Twice I've gotten live callback from a tester within 15 minutes of submitting one of the automated reports, with the line fixed no later than early the next day. [As a counter example, one of my lines developed horrible cross-talk with another customer's line, who had a fax modem (or machine). My attempting to dial a call and reaching ring often caused her fax modem to pick up. That one I reported live, and the agent heard the cross talk quite plainly...fixed the next day by our local cable maintenance guy (whom I encountered at lunch afterwards).] --John -- John Baxter jwblist@olympus.net Port Ludlow, WA, USA - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Sun Sep 3 11:49:42 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id LAA06474 for portmaster-users-outgoing; Sun, 3 Sep 2000 11:49:42 -0500 Received: from mail.stream.net.ph ([216.72.41.250]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id LAA06466 for ; Sun, 3 Sep 2000 11:49:22 -0500 Received: from lloyd [216.72.41.214] by mail.stream.net.ph (SMTPD32-5.05) id A4174A900E6; Mon, 04 Sep 2000 00:49:43 +0800 Message-ID: <002701c015c7$09f10700$d62948d8@lloyd> From: "Lloyd Casafranca" To: Subject: (PM) 2 gateways on a pm3 Date: Mon, 4 Sep 2000 00:50:15 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: "Lloyd Casafranca" anybody know how to add a second default gateway on a portmaster 3, so if the first one fails the portmaster switches to the second gateway. thanks, ---------------------------------------------------------------- Lloyd Casafranca lloyd@stream.net.ph Systems Administrator voice:(632)4382810 Stream Networks, Co. fax:(632)9122784 --------------------http://www.stream.net.ph------------------- - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Mon Sep 4 21:30:52 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id VAA09299 for portmaster-users-outgoing; Mon, 4 Sep 2000 21:30:52 -0500 Received: from missvalley.com (missvalley.com [207.193.103.1]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id VAA09296 for ; Mon, 4 Sep 2000 21:30:46 -0500 Received: from wayne (207-193-103-181.missvalley.com [207.193.103.181]) by missvalley.com (Build 98 8.9.3/NT-8.9.3) with SMTP id VAA15397; Mon, 04 Sep 2000 21:39:43 -0500 Message-ID: <004201c016e0$f4493e20$fe01a8c0@missvalley.com> From: "Wayne Wamsley" To: Cc: , References: <4.3.2.20000623172752.00b96e00@mail.tstar.net> Subject: (PM) Frame Locking up Date: Mon, 4 Sep 2000 21:28:16 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: "Wayne Wamsley" Running 3.8.2c2 on pm3 with a T1 card installed. My connnection via the frame has started locking up to where I have to reboot the machine to get the connection established. Have already changed out all equipment, but the problem persists These are T1 Primary Rate ISDN lines. There was a storm a few weeks ago and they had to change out the smartjacks. Yes, this problem also started occurring about the same time. I am noticing a few CRC errors and bipolar errors, I can dial into the portmaster luckily to do a reboot, and notice when doing a show w48 there is an abort error also. The line just hangs at Statis: Establishing on the Frame line until rebooting. . I have stressed to the telco that there is a problem on their side as i have already installed new equipment and the problem remains. Anybody had a situation similar to this happen? What did you do to resolve the problem? Wayne - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Mon Sep 4 22:59:09 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id WAA09987 for portmaster-users-outgoing; Mon, 4 Sep 2000 22:59:09 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id WAA09984 for ; Mon, 4 Sep 2000 22:59:05 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id UAA22572 for ; Mon, 4 Sep 2000 20:54:29 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id UAA07043 for ; Mon, 4 Sep 2000 20:59:41 -0700 (PDT) Received: from egypt.sevenkings.net (egypt.sevenkings.net [216.172.23.2]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id UAA22568 for ; Mon, 4 Sep 2000 20:54:27 -0700 (PDT) Received: from jk3329.sevenkings.net (jk3329.sevenkings.net [216.172.23.1]) by egypt.sevenkings.net (8.9.0/8.9.0) with SMTP id XAA15706 for ; Mon, 4 Sep 2000 23:59:25 -0400 (EDT) From: Egan To: portmaster-users@livingston.com Subject: (PM) Remote restart after hard lockup Date: Mon, 04 Sep 2000 23:59:25 -0400 Message-ID: <9pr8rs8mm6hvsnefqjnnitrsfp8uk0gfak@4ax.com> References: <1244557220-83828251@mail.mia.net> <027d01c011e7$45c611a0$2cad1fd0@mlode.com> In-Reply-To: <027d01c011e7$45c611a0$2cad1fd0@mlode.com> X-Mailer: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Egan On Tue, 29 Aug 2000 11:30:56 -0700, "Dave" wrote: >The MLPPP has worked pretty well for us, but the multi chassis PPP has a >problem where it will hang a session in the MCPPP master/slave table. This >causes subsequent connections to fail, as the PM3 thinks the session is >still active and does not assign an IP address. A reboot of the PM3 was the >only fix. 3.9 has a fix for this, but unfortunately causes our PM3's to lock >up hard after a couple of weeks or so, and has problems with Courier modems. When a PM3 locks up hard, can it be restarted remotely? - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 03:26:58 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id DAA11331 for portmaster-users-outgoing; Tue, 5 Sep 2000 03:26:58 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id DAA11328 for ; Tue, 5 Sep 2000 03:26:55 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id BAA24211 for ; Tue, 5 Sep 2000 01:22:18 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id BAA12341 for ; Tue, 5 Sep 2000 01:27:31 -0700 (PDT) Received: from flarn.it.ca (it.ca [199.45.111.1]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id BAA24207 for ; Tue, 5 Sep 2000 01:22:16 -0700 (PDT) Received: (from paul@localhost) by flarn.it.ca (8.9.3/8.9.3) id EAA34005 for portmaster-users@livingston.com; Tue, 5 Sep 2000 04:27:02 -0400 (EDT) (envelope-from paul) Date: Tue, 5 Sep 2000 04:27:02 -0400 From: Paul Chvostek To: portmaster-users@livingston.com Subject: Re: (PM) Remote restart after hard lockup Message-ID: <20000905042702.A19758@flarn.it.ca> References: <1244557220-83828251@mail.mia.net> <027d01c011e7$45c611a0$2cad1fd0@mlode.com> <9pr8rs8mm6hvsnefqjnnitrsfp8uk0gfak@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <9pr8rs8mm6hvsnefqjnnitrsfp8uk0gfak@4ax.com>; from Egan on Mon, Sep 04, 2000 at 11:59:25PM -0400 Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Paul Chvostek On Mon, Sep 04, 2000 at 11:59:25PM -0400, Egan wrote: > > When a PM3 locks up hard, can it be restarted remotely? Yes, if you have a Baytech RPC or equivalent. Or, if you're cheap, grab some X-10 hardware. Neither of those solutions is specific to the PM3, though. I'm sure with a bit of experimentation, some spare PM3's and a soldering gun, you could find a reset line on the mainboard and perhaps wire it to a line on a serial port somewhere. -- Paul Chvostek Operations / Development / Abuse / Whatever vox: +1 416 598 0000 IT Canada http://www.it.ca/ - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 07:30:45 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id HAA12170 for portmaster-users-outgoing; Tue, 5 Sep 2000 07:30:45 -0500 Received: from rossini.ednet.co.uk (root@rossini.ednet.co.uk [212.20.226.211]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id HAA12167 for ; Tue, 5 Sep 2000 07:30:41 -0500 Received: from rossini.ednet.co.uk (portmaster@rossini.ednet.co.uk [212.20.226.211]) by rossini.ednet.co.uk (8.9.3/8.9.3) with ESMTP id NAA09768 for ; Tue, 5 Sep 2000 13:31:14 +0100 Date: Tue, 5 Sep 2000 13:31:14 +0100 (GMT) From: Richard Morrell To: portmaster-users@portmasters.com Subject: Re: (PM) 2 gateways on a pm3 In-Reply-To: <002701c015c7$09f10700$d62948d8@lloyd> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Richard Morrell On Mon, 4 Sep 2000, Lloyd Casafranca wrote: > anybody know how to add a second default gateway on a > portmaster 3, so if the first one fails the portmaster switches > to the second gateway. AFAIK, you can't do this statically with the PM3. If you really have to have two gateways you can do it in a couple of ways: 1) Have a couple of routers that support HSRP and point your PM3 at the phantom address. At present, I think Cisco are the only people that support HSRP but I have heard that the linux community are working on something similar. OR 2) Get your pm3 and two gateways running OSPF and have your two gateways advertise default routes via OSPF. Set the gateway on your PM3 to be 0.0.0.0 and it should pickup the default route via OSPF. If you set the cost of your gateway's interfaces to be the same, OSPF should load balance across both routers. If you prefer to have a "main" route that only uses one of the gateways and keeps the other as a backup, just increase the cost on the interface of the backup gateway. Regards, -- Richard Morrell richard@ednet.co.uk System Administrator - edNET: Internet Access for Edinburgh - www.ednet.co.uk - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 07:38:50 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id HAA12210 for portmaster-users-outgoing; Tue, 5 Sep 2000 07:38:50 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id HAA12207 for ; Tue, 5 Sep 2000 07:38:48 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id FAA25472 for ; Tue, 5 Sep 2000 05:34:09 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id FAA15909 for ; Tue, 5 Sep 2000 05:39:22 -0700 (PDT) Received: from rossini.ednet.co.uk (rossini.ednet.co.uk [212.20.226.211]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id FAA25468 for ; Tue, 5 Sep 2000 05:34:07 -0700 (PDT) Received: from rossini.ednet.co.uk (portmaster@rossini.ednet.co.uk [212.20.226.211]) by rossini.ednet.co.uk (8.9.3/8.9.3) with ESMTP id NAA12182 for ; Tue, 5 Sep 2000 13:39:19 +0100 Date: Tue, 5 Sep 2000 13:39:19 +0100 (GMT) From: Richard Morrell To: Portmaster Mailing List Subject: Re: (PM) Remote restart after hard lockup In-Reply-To: <9pr8rs8mm6hvsnefqjnnitrsfp8uk0gfak@4ax.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Richard Morrell On Mon, 4 Sep 2000, Egan wrote: > When a PM3 locks up hard, can it be restarted remotely? If any network device locks up completely, then you aren't going to be able to restart it without going for the power (unless the console is available via a modem or some other route). If you are concerned about remote equipment locking up, I recommend that you invest in some sort of remote power control such as the APC masterswitch: http://www.apcc.com/products/masterswitch/index.cfm -- Richard Morrell richard@ednet.co.uk System Administrator - edNET: Internet Access for Edinburgh - www.ednet.co.uk - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 09:09:46 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id JAA13217 for portmaster-users-outgoing; Tue, 5 Sep 2000 09:09:46 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id JAA13214 for ; Tue, 5 Sep 2000 09:09:44 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id HAA26614 for ; Tue, 5 Sep 2000 07:05:04 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id HAA19266 for ; Tue, 5 Sep 2000 07:10:17 -0700 (PDT) Received: from linux.advmed.com (advmed.com [207.235.58.129]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id HAA26610 for ; Tue, 5 Sep 2000 07:05:03 -0700 (PDT) Received: from localhost (jake@localhost) by linux.advmed.com (8.9.3/8.9.3) with ESMTP id JAA29699; Tue, 5 Sep 2000 09:15:27 -0500 Date: Tue, 5 Sep 2000 09:15:27 -0500 (CDT) From: Jake Messinger To: Egan cc: portmaster-users@livingston.com Subject: Re: (PM) Remote restart after hard lockup In-Reply-To: <9pr8rs8mm6hvsnefqjnnitrsfp8uk0gfak@4ax.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Jake Messinger On Mon, 4 Sep 2000, Egan wrote: > >only fix. 3.9 has a fix for this, but unfortunately causes our PM3's to lock > >up hard after a couple of weeks or so, and has problems with Courier modems. > > When a PM3 locks up hard, can it be restarted remotely? How do you mean a hard lockup? Can commands still be issued over the console port with a null modem cable? Can you dial into it and log in as "!root"? -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ Jake Messinger, VP. ph:713-772-6690 Visit: portmasters.com AMS, Inc. fx:713-774-3498 advmed.com 8300 Bissonnet #400 jake@jakes.org disc.cba.uh.edu Houston, Texas 77074 http://jakes.org ICQ# 4403734 Adjunct Professor University of Houston, CBA jake@uh.edu ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ INVENTOR OF the _.,-*~''~*-,._ SQUIGGLES (c) 1978 - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 10:40:56 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id KAA14394 for portmaster-users-outgoing; Tue, 5 Sep 2000 10:40:56 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id KAA14391 for ; Tue, 5 Sep 2000 10:40:52 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id IAA27715 for ; Tue, 5 Sep 2000 08:36:10 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id IAA24297 for ; Tue, 5 Sep 2000 08:41:23 -0700 (PDT) Received: from ns1.netmdc.com (ns1.netmdc.com [206.29.138.5]) by bast.livingston.com (8.9.3/8.9.3) with SMTP id IAA27711 for ; Tue, 5 Sep 2000 08:36:08 -0700 (PDT) Received: (qmail 12973 invoked by uid 1000); 5 Sep 2000 15:39:11 -0000 Date: Tue, 5 Sep 2000 09:39:10 -0600 (MDT) From: John Gonzalez/netMDC admin To: Jake Messinger cc: portmaster-users@livingston.com Subject: Re: (PM) Remote restart after hard lockup In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: John Gonzalez/netMDC admin Jake brings up a good point, what do you mean by hard lock. Do you mean you are making config changes over ethernet and you fubar'ed the gateway/etc, and it dropped your remote session? If so, you should still be able to dial in with a modem assuming admin access is set on the serial ports. If you mean 'the box crashes' like i think you do, then the only solution is a power cycle. I'm not sure the pinout on the console port, but sometimes it's possible to reset the machine that way, but i doubt it. More then likely, you need to get a powerbox that has dialin capabilities, and you can remotely reset the power on anything that's hooked up to it. Also, you can use old pm2's to hook up to the console port of all the devies at your POP... it's a powerful combination. On Tue, 5 Sep 2000, Jake Messinger wrote: | On Mon, 4 Sep 2000, Egan wrote: | | > >only fix. 3.9 has a fix for this, but unfortunately causes our PM3's to lock | > >up hard after a couple of weeks or so, and has problems with Courier modems. | > | > When a PM3 locks up hard, can it be restarted remotely? | | How do you mean a hard lockup? Can commands still be issued over the | console port with a null modem cable? Can you dial into it and log in as | "!root"? -- _ __ _____ __ _________ ______________ /_______ ___ ____ /______ John Gonzalez/Net.Tech __ __ \ __ \ __/_ __ `__ \/ __ /_ ___/ MDC Computers/netMDC! _ / / / `__/ /_ / / / / / / /_/ / / /__ (505)439-0200/fax-437-3052 /_/ /_/\___/\__/ /_/ /_/ /_/\__,_/ \___/ http://www.netmdc.com [---------------------------------------------[system info]-----------] 9:20am up 117 days, 15:23, 3 users, load average: 0.24, 0.20, 0.23 - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 11:43:10 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id LAA15566 for portmaster-users-outgoing; Tue, 5 Sep 2000 11:43:10 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id LAA15562 for ; Tue, 5 Sep 2000 11:43:02 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id JAA28865 for ; Tue, 5 Sep 2000 09:38:19 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id JAA29066 for ; Tue, 5 Sep 2000 09:43:33 -0700 (PDT) Received: from egypt.sevenkings.net (egypt.sevenkings.net [216.172.23.2]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id JAA28861 for ; Tue, 5 Sep 2000 09:38:17 -0700 (PDT) Received: from jk3329.sevenkings.net (jk3329.sevenkings.net [216.172.23.1]) by egypt.sevenkings.net (8.9.0/8.9.0) with SMTP id MAA16759 for ; Tue, 5 Sep 2000 12:43:16 -0400 (EDT) From: Egan To: portmaster-users@livingston.com Subject: Re: (PM) Remote restart after hard lockup Date: Tue, 05 Sep 2000 12:43:16 -0400 Message-ID: <2g8ars0dc2jo28tnovid32gfeh1fqt95jl@4ax.com> References: <9pr8rs8mm6hvsnefqjnnitrsfp8uk0gfak@4ax.com> In-Reply-To: X-Mailer: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Egan On Tue, 5 Sep 2000 09:15:27 -0500 (CDT), Jake Messinger wrote: >> >only fix. 3.9 has a fix for this, but unfortunately causes our PM3's to lock >> >up hard after a couple of weeks or so, and has problems with Courier modems. >> >> When a PM3 locks up hard, can it be restarted remotely? > >How do you mean a hard lockup? I don't know, I don't have a PM3 (yet). >Can commands still be issued over the console port with a null modem cable? Can >you dial into it and log in as "!root"? That's what I want to know before investing in PM3. Another user said his locked up "hard" with 3.9. I just want to know if recovery in that case means power cycle or not. - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 11:57:02 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id LAA15711 for portmaster-users-outgoing; Tue, 5 Sep 2000 11:57:02 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id LAA15707 for ; Tue, 5 Sep 2000 11:56:59 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id JAA29062 for ; Tue, 5 Sep 2000 09:52:18 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id JAA00346 for ; Tue, 5 Sep 2000 09:57:31 -0700 (PDT) Received: from linux.advmed.com (advmed.com [207.235.58.129]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id JAA29058 for ; Tue, 5 Sep 2000 09:52:16 -0700 (PDT) Received: from localhost (jake@localhost) by linux.advmed.com (8.9.3/8.9.3) with ESMTP id MAA03633; Tue, 5 Sep 2000 12:01:55 -0500 Date: Tue, 5 Sep 2000 12:01:55 -0500 (CDT) From: Jake Messinger To: Egan cc: portmaster-users@livingston.com Subject: Re: (PM) Remote restart after hard lockup In-Reply-To: <2g8ars0dc2jo28tnovid32gfeh1fqt95jl@4ax.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Jake Messinger On Tue, 5 Sep 2000, Egan wrote: > >> When a PM3 locks up hard, can it be restarted remotely? > > > >How do you mean a hard lockup? > > I don't know, I don't have a PM3 (yet). It depends. Usually a PM 3 will NOT hardlock. If it gets to that point, it usually reboots. Most of the time, you can either telnet to it, or dial in as !root and reboot it. -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ Jake Messinger, VP. ph:713-772-6690 Visit: portmasters.com AMS, Inc. fx:713-774-3498 advmed.com 8300 Bissonnet #400 jake@jakes.org disc.cba.uh.edu Houston, Texas 77074 http://jakes.org ICQ# 4403734 Adjunct Professor University of Houston, CBA jake@uh.edu ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ INVENTOR OF the _.,-*~''~*-,._ SQUIGGLES (c) 1978 - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 12:16:40 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id MAA16341 for portmaster-users-outgoing; Tue, 5 Sep 2000 12:16:40 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id MAA16338 for ; Tue, 5 Sep 2000 12:16:37 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id KAA29408 for ; Tue, 5 Sep 2000 10:11:56 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id KAA02174 for ; Tue, 5 Sep 2000 10:17:09 -0700 (PDT) Received: from rossini.ednet.co.uk (rossini.ednet.co.uk [212.20.226.211]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id KAA29404 for ; Tue, 5 Sep 2000 10:11:54 -0700 (PDT) Received: from rossini.ednet.co.uk (portmaster@rossini.ednet.co.uk [212.20.226.211]) by rossini.ednet.co.uk (8.9.3/8.9.3) with ESMTP id SAA15560 for ; Tue, 5 Sep 2000 18:17:07 +0100 Date: Tue, 5 Sep 2000 18:17:07 +0100 (GMT) From: Richard Morrell To: Portmaster Mailing List Subject: Re: (PM) Remote restart after hard lockup In-Reply-To: <2g8ars0dc2jo28tnovid32gfeh1fqt95jl@4ax.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Richard Morrell On Tue, 5 Sep 2000, Egan wrote: > I don't know, I don't have a PM3 (yet). Ooooh, a new customer. I hope everyone at Lucent is watching... :-) > That's what I want to know before investing in PM3. Another user said > his locked up "hard" with 3.9. Was that a beta version or full release? > I just want to know if recovery in that case means power cycle or not. Like everyone else said, it depends on what sort of lock-up you are talking about. Personally, I don't have *anything* (Linux, NT, Cisco, Lucent, HP, etc, etc) installed in a remote location without me having remote control over its power and/or remote console access through an alternate route (modem/ISDN/alternate transit). Although I've had PM3s reboot themselves in the past, they have always come back safely and I've never had one lock up so badly that I've had to go for the power. FMMV -- Richard Morrell richard@ednet.co.uk System Administrator - edNET: Internet Access for Edinburgh - www.ednet.co.uk - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 12:51:41 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id MAA17495 for portmaster-users-outgoing; Tue, 5 Sep 2000 12:51:41 -0500 Received: from borg.denalics.net (postfix@borg.denalics.net [209.112.170.15]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id MAA17488 for ; Tue, 5 Sep 2000 12:51:35 -0500 Received: from borg.denalics.net (borg.denalics.net [209.112.170.15]) by borg.denalics.net (Postfix) with ESMTP id 5DD6248825; Tue, 05 Sep 2000 09:25:43 -0800 (AKDT) Date: Tue, 5 Sep 2000 09:25:43 -0800 (AKDT) From: "Christopher E. Brown" To: John Narron Cc: portmaster-users@portmasters.com Subject: Re: (PM) Weather affecting mail server? In-Reply-To: <043701c0154c$4f545ac0$0101a8c0@hemroids> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: "Christopher E. Brown" On Sat, 2 Sep 2000, John Narron wrote: > In a more serious answer (Miquel ;), > We have had experiences when the weather is bad, our service > is bad. Coincidence, maybe. My only "explanation" is weather > affecting the telephone service. We'll notice a drop in high- > speed connections on rainy/stormy days and get a lot of complaints > from our rural users on such days about not being able to connect > at all. If this is a true-case, I'm assuming its a telco problem. Old cable, split jackets, split insulation. With the severe freeze/thaw we get here (Alaska) it doesn't even have to be old cable. Water will get into every bad seal, every cable jacket break, flood shrooms, etc. Add a little contamination to boost conductivity, and things go to hell. We see a 2 - 4 k drop in average connect speed in most areas, in a few older areas rates drop by half or better (severe cases). > What I suggest to our customers experiencing such problems > is to check the telco box outside their house for dirty and > damaged connectors (please, advise them to NOT DO THIS when > raining, there a potential 133V circuit in that box). If so, a > little cleaning or a replacement goes a long way. If that doesn't > fix the problem, have the customer request that the local telco > test the circuit on those days. If you have good (read: not-lazy) > workers at the local telco, they'll test it out and "repair" if > the noise level is too high. Actually, many places run higher. Line is -48VDC (spec) on hook (can be up to almost 60VDC), and ring is ~ 100 - 230(max) VAC, many places running ~ 180VAC ring. And yes, you really do not want to be touching either leg in the rain when it rings. Specially barefoot on wet ground. --- As folks might have suspected, not much survives except roaches, and they don't carry large enough packets fast enough... --About the Internet and nuclear war. - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 12:51:42 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id MAA17497 for portmaster-users-outgoing; Tue, 5 Sep 2000 12:51:42 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id MAA17487 for ; Tue, 5 Sep 2000 12:51:35 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id KAA00113 for ; Tue, 5 Sep 2000 10:46:54 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id KAA05876 for ; Tue, 5 Sep 2000 10:52:07 -0700 (PDT) Received: from ns1.netmdc.com (ns1.netmdc.com [206.29.138.5]) by bast.livingston.com (8.9.3/8.9.3) with SMTP id KAA00109 for ; Tue, 5 Sep 2000 10:46:52 -0700 (PDT) Received: (qmail 15944 invoked by uid 1000); 5 Sep 2000 17:49:55 -0000 Date: Tue, 5 Sep 2000 11:49:55 -0600 (MDT) From: John Gonzalez/netMDC admin To: Egan cc: portmaster-users@livingston.com Subject: Re: (PM) Remote restart after hard lockup In-Reply-To: <2g8ars0dc2jo28tnovid32gfeh1fqt95jl@4ax.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: John Gonzalez/netMDC admin On Tue, 5 Sep 2000, Egan wrote: | That's what I want to know before investing in PM3. Another user said | his locked up "hard" with 3.9. | | I just want to know if recovery in that case means power cycle or not. Well, i have 9 PMX's and i havent ever had a 'hard lockup' yet.. We stay away from beta code until the list gives it a 'thumbs up' however, and our configs are pretty simple. 3.7 years uptime, never a failure. (knock on wood) -- _ __ _____ __ _________ ______________ /_______ ___ ____ /______ John Gonzalez/Net.Tech __ __ \ __ \ __/_ __ `__ \/ __ /_ ___/ MDC Computers/netMDC! _ / / / `__/ /_ / / / / / / /_/ / / /__ (505)439-0200/fax-437-3052 /_/ /_/\___/\__/ /_/ /_/ /_/\__,_/ \___/ http://www.netmdc.com [---------------------------------------------[system info]-----------] 11:45am up 117 days, 17:48, 4 users, load average: 0.34, 0.20, 0.18 - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 13:01:32 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id NAA17799 for portmaster-users-outgoing; Tue, 5 Sep 2000 13:01:32 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id NAA17796 for ; Tue, 5 Sep 2000 13:01:27 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id KAA00302 for ; Tue, 5 Sep 2000 10:56:46 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id LAA06850 for ; Tue, 5 Sep 2000 11:02:00 -0700 (PDT) Received: from egypt.sevenkings.net (egypt.sevenkings.net [216.172.23.2]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id KAA00298 for ; Tue, 5 Sep 2000 10:56:45 -0700 (PDT) Received: from jk3329.sevenkings.net (jk3329.sevenkings.net [216.172.23.1]) by egypt.sevenkings.net (8.9.0/8.9.0) with SMTP id OAA16952 for ; Tue, 5 Sep 2000 14:01:43 -0400 (EDT) From: Egan To: portmaster-users@livingston.com Subject: (PM) Secure telnet Date: Tue, 05 Sep 2000 14:01:43 -0400 Message-ID: <70darso3q2r6hb63aa6kcj7k4q0mrctja6@4ax.com> References: <2g8ars0dc2jo28tnovid32gfeh1fqt95jl@4ax.com> In-Reply-To: X-Mailer: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Egan On Tue, 5 Sep 2000 12:01:55 -0500 (CDT), Jake Messinger wrote: >It depends. Usually a PM 3 will NOT hardlock. If it gets to that point, it >usually reboots. Most of the time, you can either telnet to it, or dial in >as !root and reboot it. In the environment I am considering, I won't have dial in access to a PM3, only telnet. Is there any secure telnet, SSH, or other software that works with PM3 to prevent passwords being sent clear text? - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 13:21:55 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id NAA18179 for portmaster-users-outgoing; Tue, 5 Sep 2000 13:21:55 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id NAA18173 for ; Tue, 5 Sep 2000 13:21:48 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id LAA00613 for ; Tue, 5 Sep 2000 11:17:05 -0700 (PDT) Received: from phil.lcp.livingston.com ([149.198.164.4]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id LAA08450 for ; Tue, 5 Sep 2000 11:22:18 -0700 (PDT) Received: from hal.lucentradius.com (hal.lucentradius.com [158.222.8.12]) by phil.lcp.livingston.com (8.9.3/8.9.3) with ESMTP id LAA27206 for ; Tue, 5 Sep 2000 11:21:25 -0700 (PDT) Received: from lucentradius.com (misato.lucentradius.com [158.222.8.28]) by hal.lucentradius.com (8.9.3/8.9.3) with ESMTP id LAA04882 for ; Tue, 5 Sep 2000 11:20:55 -0700 (PDT) Message-ID: <39B53845.5ABEE085@lucentradius.com> Date: Tue, 05 Sep 2000 11:15:33 -0700 From: Thomas Kinnen Organization: Lucent RABU X-Mailer: Mozilla 4.51 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: portmaster-users@livingston.com Subject: Re: (PM) Secure telnet References: <2g8ars0dc2jo28tnovid32gfeh1fqt95jl@4ax.com> <70darso3q2r6hb63aa6kcj7k4q0mrctja6@4ax.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Thomas Kinnen Egan wrote: > In the environment I am considering, I won't have dial in access to a > PM3, only telnet. > > Is there any secure telnet, SSH, or other software that works with PM3 > to prevent passwords being sent clear text? ssh to a Unix box that has a direct serial connection to the console port. -- Thomas C Kinnen - [RADIUS Engineer] - LUCENT Technologies INS Selling VHS Tapes: http://www.sobhrach.com/sale.html "All of the opinions stated above are my own and not my employer's, unless they were given to me by my employer" - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 13:54:59 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id NAA18933 for portmaster-users-outgoing; Tue, 5 Sep 2000 13:54:59 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id NAA18928 for ; Tue, 5 Sep 2000 13:54:56 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id LAA01238 for ; Tue, 5 Sep 2000 11:50:14 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id LAA11419 for ; Tue, 5 Sep 2000 11:55:28 -0700 (PDT) Received: from linux.advmed.com (advmed.com [207.235.58.129]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id LAA01230 for ; Tue, 5 Sep 2000 11:50:12 -0700 (PDT) Received: from localhost (jake@localhost) by linux.advmed.com (8.9.3/8.9.3) with ESMTP id OAA05795; Tue, 5 Sep 2000 14:00:37 -0500 Date: Tue, 5 Sep 2000 14:00:37 -0500 (CDT) From: Jake Messinger To: Egan cc: portmaster-users@livingston.com Subject: Re: (PM) Secure telnet In-Reply-To: <70darso3q2r6hb63aa6kcj7k4q0mrctja6@4ax.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Jake Messinger On Tue, 5 Sep 2000, Egan wrote: > Is there any secure telnet, SSH, or other software that works with PM3 > to prevent passwords being sent clear text? Pm3 doesnt support ssh, but you could set up ssh on a linux box at the pm3's site, telnet to it first, then telnet to the pm3 from it. That way the clear text will only be seen on the local net. -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ Jake Messinger, VP. ph:713-772-6690 Visit: portmasters.com AMS, Inc. fx:713-774-3498 advmed.com 8300 Bissonnet #400 jake@jakes.org disc.cba.uh.edu Houston, Texas 77074 http://jakes.org ICQ# 4403734 Adjunct Professor University of Houston, CBA jake@uh.edu ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ INVENTOR OF the _.,-*~''~*-,._ SQUIGGLES (c) 1978 - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 16:23:14 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id QAA23026 for portmaster-users-outgoing; Tue, 5 Sep 2000 16:23:14 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id QAA23021 for ; Tue, 5 Sep 2000 16:23:10 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id OAA03744 for ; Tue, 5 Sep 2000 14:18:27 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id OAA22204 for ; Tue, 5 Sep 2000 14:23:41 -0700 (PDT) Received: from flarn.it.ca (it.ca [199.45.111.1]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id OAA03739 for ; Tue, 5 Sep 2000 14:18:24 -0700 (PDT) Received: (from paul@localhost) by flarn.it.ca (8.9.3/8.9.3) id RAA83246 for portmaster-users@livingston.com; Tue, 5 Sep 2000 17:23:10 -0400 (EDT) (envelope-from paul) Date: Tue, 5 Sep 2000 17:23:10 -0400 From: Paul Chvostek To: portmaster-users@livingston.com Subject: Re: (PM) Remote restart after hard lockup Message-ID: <20000905172310.E19758@flarn.it.ca> References: <2g8ars0dc2jo28tnovid32gfeh1fqt95jl@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Richard Morrell on Tue, Sep 05, 2000 at 06:17:07PM +0100 Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Paul Chvostek On Tue, Sep 05, 2000 at 06:17:07PM +0100, Richard Morrell wrote: > > Although I've had PM3s reboot themselves in the past, they have always > come back safely and I've never had one lock up so badly that I've had to > go for the power. I did not long ago. Its software image got corrupt. It failed to come up after a building-wide power outage, and reported nasties on the console, never initializing its Ethernet interface. I had to netboot the thing and use the netbooted software image to tftp a current one. It's worked like a charm since then. Of course, this problem was one which a simple reboot wouldn't have fixed. Besides this incident, I've never had a PM3 crash. Ever. -- Paul Chvostek Operations / Development / Abuse / Whatever vox: +1 416 598 0000 IT Canada http://www.it.ca/ - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 17:52:27 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id RAA24257 for portmaster-users-outgoing; Tue, 5 Sep 2000 17:52:27 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id RAA24254 for ; Tue, 5 Sep 2000 17:52:20 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id PAA05592 for ; Tue, 5 Sep 2000 15:47:37 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id PAA28942; Tue, 5 Sep 2000 15:52:17 -0700 (PDT) Received: from linux2.advmed.com (linux2.advmed.com [207.235.58.139]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id PAA05585; Tue, 5 Sep 2000 15:46:57 -0700 (PDT) Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id QAA23674 for portmaster-announce-outgoing; Tue, 5 Sep 2000 16:57:35 -0500 Date: Tue, 5 Sep 2000 14:58:01 -0700 (PDT) From: Carl Rigney Message-Id: <200009052158.OAA24689@server.livingston.com> To: portmaster-announce@livingston.com Subject: (PM) (ANNC) ComOS 3.9.1b1 for PortMaster 3 available for FTP Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Carl Rigney 2000/09/5 ComOS 3.9.1b1 Open Beta Release Note for the PortMaster 3 ________________ Introduction The new Lucent Technologies ComOS(R) 3.9.1b1 software release is now available for open beta for the PortMaster(R) 3 Integrated Access Server. This release note applies only to the PortMaster 3. This release is provided at no charge to all Lucent customers. This release note documents commands and features added between ComOS 3.9 and ComOS 3.9.1b1 on the PortMaster 3. Before upgrading, thoroughly read "ComOS 3.9.1b1 Limitations" and "Upgrade Instructions." _______ Modem Code Supported ComOS 3.9.1b1 contains modem code version i12600e---the same modem code included in the ComOS 3.9 release. Support for the obsolete "True Digital V.34 Card" (MDM-PM3-8 and MDM-PM3-10), including support for V.110, has been removed from this release. The "True Digital 56K Card" (MDM-56K-8 and MDM-56K-10) is still supported. _______ Warnings and Important Notices DISREGARD PRIOR WARNING: Any PortMaster 3 unit can run ComOS 3.9.1b1 or any earlier release of ComOS, regardless of manufacture date. WARNING! Due to the increased size of ComOS, the amount of nonvolatile RAM (NVRAM) available for saving configurations has been reduced from 128KB to 64KB. PortMaster products with configurations greater than 64KB will lose some of their configuration. For this reason, be sure to back up your PortMaster configuration before upgrading to this release. You can check the amount of memory used for your configuration with the "show files" command. Ignore any files that also include an uncompressed size. WARNING! The PortMaster 3 must be running ComOS 3.5 or later to upgrade to ComOS 3.9.1b1. If you are running an earlier release of ComOS, upgrade to ComOS 3.5 first, reboot, then upgrade to ComOS 3.9.1b1. IMPORTANT: Any PortMaster 3 running the Border Gateway Protocol (BGP) requires 32MB of dynamic RAM (DRAM) so that it can store the more than 70,000 BGP paths in a full BGP feed. IMPORTANT: Virtual private network (VPN) tunneling, including tunneling based on the IP Security (IPSec) protocol, is not supported in this release. If you purchased an IPSec encryption ("coprocessor") card, contact Lucent NetworkCare(TM) for more information. _______________ Contents Introduction Bugs Fixed in ComOS 3.9.1b1 Reconfiguring NVRAM ComOS 3.9.1b1 Limitations Troubleshooting Modems Upgrade Instructions Technical Support _______________ Bugs Fixed in ComOS 3.9.1b1 The ComOS 3.9.1b1 release fixes the following bugs that were present in the ComOS 3.9 release. * The ending of a Multilink Point-to-Point Protocol (PPP) session no longer causes the PortMaster to run out of memory blocks and reboot unnecessarily. * A condition leading to a crash preceded by messages like the following has been fixed: "ppp_recv (S41): Runt packet - -2 bytes." * A network buffer (netbuf) leak caused by special large packets, which caused the PortMaster to reboot unnecessarily, is now fixed. * The command "show ?" no longer lists syslog twice as an option. * The Password Authentication Protocol (PAP) now disconnects after three failed attempts. This restriction helps to prevent someone from using a dictionary to guess a PAP password. * The Challenge Handshake Authentication Protocol (CHAP) now works with 16-character passwords. * The PortMaster no longer reboots if sent a specific type of malformed UDP packet. * At European sites, PortMaster units using ISDN V.120 encapsulation ran out of memory blocks. This problem has been fixed. * Permanent (hardwired) connections no longer occasionally enter the IDLE state by mistake. * Acct-Delay-Time is now reported properly to RADIUS. Previously, exceedingly large delay times were occasionally reported. * OSPF no longer sends individual host advertisements for dial-in users who have already been advertised as part of the assigned address pool network. _______________ Reconfiguring NVRAM After loading the new ComOS 3.9.1b1 and rebooting, look for messages like the following on the console screen to verify that ComOS has loaded successfully: Testing System Memory.... 1024K Checking Boot Rom.... Calibrating.... 33MHz Starting FLASH Boot..... Loading Image at 0fff0000 17110 flash copy complete Verifying Load Module Checksum... Starting Load Module ... Loading kernel... 691260 bytes Testing High Memory ... . 4096K Loading kernel extensions... 125952 bytes Async found in slot 1 Found 11 ports.... ether0 active ... 16K shared-RAM Reconfiguring FLASH... Malloc size 65534 at 18a208 Opened modules STD file Read 64506 bytes at 18a208 read 1 buffers Call flash format Call freecntl Call save Call f_open Write 64506 bytes at 18a208 done - rebooting _______________ ComOS 3.9.1b1 Limitations The ComOS 3.9.1b1 release has the following limitations. _______ Limitations on Upgrading and Downgrading * The PortMaster must be running ComOS 3.5 or later to upgrade to ComOS 3.9.1b1. If you are running an earlier release of ComOS, upgrade to ComOS 3.5 first, reboot, then upgrade to ComOS 3.9.1b1. * Downgrading a PortMaster 3 from ComOS 3.9.1b1 to a previous release requires two successful downgrades. After the first successful downgrade the PortMaster is operational, but without system messages. The second downgrade applies the system messages. * Downgrading from ComOS 3.9.1b1 to ComOS 3.5 might change the Ether0 IP address. _______ No Online Help File A ComOS online help file is not included in this release; therefore, the "help" command is not supported. _______ Modem Limitations * Support for the obsolete "True Digital V.34 Card" (MDM-PM3-8 and MDM-PM3-10), including support for V.110, has been removed from this release. The "True Digital 56K Card" (MDM-56K-8 and MDM-56K-10) is still supported. * A PCTEL modem set for K56flex in its proprietary bit is incorrectly identified as being set for V.90 by the PortMaster. As a result, the modem fails V.90 negotiations with the PortMaster and falls back to V.34 rates. _______ Frame Relay Limitation You cannot use Inverse Address Resolution Protocol (ARP) on a Frame Relay interface with subinterfaces. The primary Frame Relay interface does not automatically map IP addresses to data link connection identifiers (DLCIs). When you enter a "show arp frm1" command, no ARP tables appear, and the PortMaster cannot ping across the Frame Relay cloud. _______ NAT Limitations * Inbound NAT maps are restricted to static address maps and/or static TCP/UDP port maps only. Outbound NAT maps do not have this limitation. * NAT translates only TCP, UDP, and ICMP packets. Point-to-Point Tunneling Protocol (PPTP) traffic is not translated. _______ L2TP Session Limitation A Layer 2 Tunneling Protocol (L2TP) network server (LNS) can support only 94 L2TP sessions in this release. _______ NFAS Limitations * This release does not support mixing ISDN Primary Rate Interface (PRI) lines that use non-facility associated signaling (NFAS) and ISDN PRI lines that do not use NFAS in the same chassis. If one line is used for NFAS, the other line must be used for NFAS or left empty. * NFAS operates only on National ISDN (NI-2) switch types. * Configuring NFAS settings on a line that is not configured for ISDN or unable to perform ISDN functions makes the line behave strangely. * When you are using NFAS and a problem occurs on the physical PRI line with the D channel, the line sometimes does not return to service until you reset the D channel. * When a PortMaster running NFAS is rebooted, you must sometimes reset the D channel to return the PRI line to service. _______ OSPF Address Pool Limitation for Static Internal Routes To advertise your address pools allocated for static users as internal OSPF routes, you must add them to the OSPF area range as full class C addresses. If these addresses are instead added as subnets of a class C address, they are incorrectly advertised as OSPF type 2 external (E2) routes. An address pool on a PortMaster 3 is most commonly made up of 48 contiguous addresses, the first of which is a network address. For example, suppose you configure an address pool using subnets 192.168.110.16/28 and 192.168.110.32/27, with 192.168.110.16 as the first address. If you add the address pool to the OSPF area range as 192.168.110.0/24, the address pool is correctly advertised as "ospf." However, if you add the address pool to the OSPF area range as 192.168.110.16/28 and 192.168.110.32/27, it is advertised as "ospf/E2." _______________ Troubleshooting Modems As part of modem troubleshooting, confirm that the client modem is running the latest firmware before submitting a modem trouble report. When making a report of a new modem problem, send the following information to Lucent NetworkCare technical support: * ComOS version * Client modem manufacturer * Client modem model * Results on the client modem of commands ATI0 through ATI11 * Whether the problem is reproducible Lucent might want to monitor your PortMaster while the client modem reproduces the problem. _______________ Upgrade Instructions You can upgrade your PortMaster 3 using PMVision 1.11, or pmupgrade from PMTools 4.4. Alternatively, you can upgrade using the older programs pminstall 3.5.3, PMconsole 3.5.3, or PMconsole for Windows 3.5.1.4. You can also upgrade using TFTP with the "tftp get comos" command from the PortMaster command line interface. See ftp://ftp.livingston.com/pub/le/software/java/pmvision111.txt for installation instructions for PMVision 1.11. *** CAUTION! If the upgrade fails, do NOT reboot! Contact *** Lucent NetworkCare Technical Support without rebooting. The upgrade process on the PortMaster 3 erases the configuration area from nonvolatile memory and saves the current configuration into nonvolatile memory. Never interrupt the upgrade process, or loss of configuration information can result. WARNING! Due to the increased size of ComOS, the amount of NVRAM available for saving configurations has been reduced from 128KB to 64KB. PortMaster products with configurations greater than 64KB will lose some of their configuration. For this reason, be sure to back up your PortMaster configuration before upgrading to this release. You can check the amount of memory used for your configuration with the "show files" command. Ignore any files that also include an uncompressed size. WARNING! The PortMaster 3 must be running ComOS 3.5 or later to upgrade to ComOS 3.9.1b1. If you are running an earlier release of ComOS, upgrade to ComOS 3.5 first, reboot, then upgrade to ComOS 3.9.1b1. IMPORTANT: Any PortMaster 3 running BGP requires 32MB of DRAM so that it can store the more than 70,000 BGP paths in a full BGP feed. The installation software can be retrieved by FTP from ftp://ftp.livingston.com/pub/le/software/, and the upgrade image can be found at ftp://ftp.livingston.com/pub/le/upgrades: ComOS Upgrade Image Product _________ _____________ ________________________ 3.9.1b1 pm3_3.9.1b1 PortMaster 3 ____________________________________________________________________ Copyright and Trademarks Copyright 2000 Lucent Technologies Inc. All rights reserved. PortMaster, ComOS, and ChoiceNet are registered trademarks of Lucent Technologies Inc. PMVision, IRX, PortAuthority, NavisRadius, and NetworkCare are trademarks of Lucent Technologies Inc. All other marks are the property of their respective owners. Notices Lucent Technologies Inc. makes no representations or warranties with respect to the contents or use of this publication, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Lucent Technologies Inc. reserves the right to revise this publication and to make changes to its content, any time, without obligation to notify any person or entity of such revisions or changes. Contacting Lucent NetworkCare Technical Support Lucent NetworkCare Professional Services provides PortMaster technical support via voice or electronic mail, or through the World Wide Web at http://www.livingston.com/. Specify that you are running ComOS 3.9.1b1 when reporting problems with this release. Internet service providers (ISPs) and other end users in Europe, the Middle East, Africa, India, and Pakistan must contact their authorized Lucent NetworkCare sales channel partner for technical support; see http://www.livingston.com/International/EMEA/distributors.html. For North America, the Caribbean and Latin America (CALA), and Asia Pacific customers, technical support is available Monday through Friday from 7 a.m. to 5 p.m. U.S. Pacific Time (GMT -8). Dial 1-800-458-9966 within the United States (including Alaska and Hawaii), Canada, and CALA, or 1-925-737-2100 from elsewhere, for voice support. For email support, send to support@livingston.com (asia-support@livingston.com for Asia Pacific customers). - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-announce' in the body of the message. - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 18:28:42 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id SAA24620 for portmaster-users-outgoing; Tue, 5 Sep 2000 18:28:42 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id SAA24617 for ; Tue, 5 Sep 2000 18:28:37 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id QAA06152 for ; Tue, 5 Sep 2000 16:23:53 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id QAA02070 for ; Tue, 5 Sep 2000 16:29:06 -0700 (PDT) Received: from mail.alpha1.net (megatron.alpha1.net [216.88.112.9]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id QAA06148 for ; Tue, 5 Sep 2000 16:23:51 -0700 (PDT) Received: from marius.org (marius.org [216.88.115.170]) by mail.alpha1.net (8.10.1/8.10.1) with ESMTP id e85NRtE37561; Tue, 5 Sep 2000 18:27:55 -0500 (CDT) Date: Tue, 5 Sep 2000 18:29:42 -0500 (CDT) From: Marius Strom X-Sender: marius@marius.org To: Jake Messinger cc: Egan , portmaster-users@livingston.com Subject: Re: (PM) Secure telnet In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Marius Strom If you're gonna put a linux box on the PM3's LAN, might as well VPN between your localnet and the remotenet. -- Marius Strom Professional Geek/Unix System Administrator Alpha1 Internet http://www.marius.org/marius.pgp 0x55DE53E4 Turn off the faucet? We're too busy mopping up the floor! On Tue, 5 Sep 2000, Jake Messinger wrote: > On Tue, 5 Sep 2000, Egan wrote: > > > Is there any secure telnet, SSH, or other software that works with PM3 > > to prevent passwords being sent clear text? > > Pm3 doesnt support ssh, but you could set up ssh on a linux box at the > pm3's site, telnet to it first, then telnet to the pm3 from it. That way > the clear text will only be seen on the local net. > > - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 19:15:08 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id TAA25271 for portmaster-users-outgoing; Tue, 5 Sep 2000 19:15:08 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id TAA25268 for ; Tue, 5 Sep 2000 19:15:03 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id RAA06820 for ; Tue, 5 Sep 2000 17:10:19 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id RAA05023 for ; Tue, 5 Sep 2000 17:15:33 -0700 (PDT) Received: from linux.advmed.com (advmed.com [207.235.58.129]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id RAA06814 for ; Tue, 5 Sep 2000 17:10:18 -0700 (PDT) Received: from localhost (jake@localhost) by linux.advmed.com (8.9.3/8.9.3) with ESMTP id TAA10148; Tue, 5 Sep 2000 19:20:45 -0500 Date: Tue, 5 Sep 2000 19:20:45 -0500 (CDT) From: Jake Messinger To: Marius Strom cc: Egan , portmaster-users@livingston.com Subject: Re: (PM) Secure telnet In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Jake Messinger On Tue, 5 Sep 2000, Marius Strom wrote: > If you're gonna put a linux box on the PM3's LAN, might as well VPN > between your localnet and the remotenet. Well yep thats true. You can set up the linux box to do vpn, which by definition, encryptz the data. -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ Jake Messinger, VP. ph:713-772-6690 Visit: portmasters.com AMS, Inc. fx:713-774-3498 advmed.com 8300 Bissonnet #400 jake@jakes.org disc.cba.uh.edu Houston, Texas 77074 http://jakes.org ICQ# 4403734 Adjunct Professor University of Houston, CBA jake@uh.edu ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ INVENTOR OF the _.,-*~''~*-,._ SQUIGGLES (c) 1978 - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 20:42:54 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id UAA26402 for portmaster-users-outgoing; Tue, 5 Sep 2000 20:42:54 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id UAA26399 for ; Tue, 5 Sep 2000 20:42:50 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id SAA07622 for ; Tue, 5 Sep 2000 18:38:07 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id SAA08331 for ; Tue, 5 Sep 2000 18:43:06 -0700 (PDT) Received: from ns.tcworks.net (ns.tcworks.net [216.61.218.2]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id SAA07618 for ; Tue, 5 Sep 2000 18:37:50 -0700 (PDT) Received: from tcworks.net (stuck.sticky.org [216.61.218.6]) by ns.tcworks.net (8.9.2/8.9.2) with ESMTP id UAA22373 for ; Tue, 5 Sep 2000 20:37:01 -0500 (CDT) (envelope-from ccook@tcworks.net) Message-ID: <39B5A134.11D89294@tcworks.net> Date: Tue, 05 Sep 2000 20:43:16 -0500 From: Chris Cook X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: portmaster-users@livingston.com Subject: (PM) Re: ComOS 3.9.1b1 for PortMaster 3 available for FTP References: <200009052158.OAA24689@server.livingston.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Chris Cook 1st) Thanks for the new ComOS... > _______________ Bugs Fixed in ComOS 3.9.1b1 > > > * Permanent (hardwired) connections no longer occasionally enter the > IDLE state by mistake. Thank God they fixed this bug... it's kinda sad they didn't tell me they knew about it when I called into NetCare though. I'm just happy it's fixed. -- Chris o----< ccook@tcworks.net >-------------------------------------o |Chris Cook - Admin | TCWORKS.NET - http://www.tcworks.net | |The Computer Works ISP | FreeBSD - http://www.freebsd.org | o--------------------------------------------------------------o - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 20:51:43 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id UAA26491 for portmaster-users-outgoing; Tue, 5 Sep 2000 20:51:43 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id UAA26488 for ; Tue, 5 Sep 2000 20:51:40 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id SAA07665 for ; Tue, 5 Sep 2000 18:46:56 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id SAA08719 for ; Tue, 5 Sep 2000 18:52:10 -0700 (PDT) Received: from iav.com (iav.com [12.36.100.2]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id SAA07661 for ; Tue, 5 Sep 2000 18:46:55 -0700 (PDT) Received: from localhost (livingston@localhost) by iav.com (8.8.5/8.7.3) with ESMTP id PAA22131 for ; Tue, 5 Sep 2000 15:51:50 -1000 (HST) Date: Tue, 5 Sep 2000 15:51:50 -1000 (HST) From: "I don't work for LINS (Lucent InterNetworking Systems)" To: portmaster-users@livingston.com Subject: Re: (PM) Weather affecting mail server? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: "I don't work for LINS (Lucent InterNetworking Systems)" On Sat, 2 Sep 2000, John W Baxter wrote: > At 19:26 -0400 9/2/00, Egan wrote: > >...rain can affect some telephone lines, > >mostly older ones, to the point that data transmission is degraded. > > So can the lack of rain...we have customers whose lines quite predictably > worsen significantly after about 3 days of sun following a period (of any > length) of rain. Being on the margin of a body of salt water doesn't help > any...so many connections, only one of which has to corrode. funnily enough yes this can happen... there is an urban legend about a lady whose phone wasn't working properly during the dry season... BUT on occassion she'd know when the phone would ring because her dog would start barking furiously. Technician goes out and sure enough phone isn't working properly. At the moment the dog starts barking and the phone starts to ring with an incoming call. So the technician goes outside to check out this 'psychic' dog. He finds that the dog is chained to a grounding rod. Well the take of this is that the dog gets shocked as the ring voltage comes in, causing the dog to bark and to piss. Needless to say, the piss completes the ground circuit allowing the phone to ring... Again this is an urban legend, but sounds plausible to me ;) -- Aloha from Paradise, Sherwood Got Clue? If so: ISPF! The Forum for ISPs by ISPs, - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 23:31:58 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id XAA29148 for portmaster-users-outgoing; Tue, 5 Sep 2000 23:31:58 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id XAA29145 for ; Tue, 5 Sep 2000 23:31:54 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id VAA08855 for ; Tue, 5 Sep 2000 21:27:09 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id VAA13122 for ; Tue, 5 Sep 2000 21:32:22 -0700 (PDT) Received: from ZIGGYCOM.NET (ns.ziggycom.net [216.79.170.2]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id VAA08851 for ; Tue, 5 Sep 2000 21:27:07 -0700 (PDT) Received: from ziggy1 ([216.79.170.6]) by ZIGGYCOM.NET with SMTP (IPAD 2.52/64) id 1426600; Tue, 05 Sep 2000 23:27:15 -0500 Message-ID: <03bf01c017ba$5578a620$06aa4fd8@ziggycom.net> From: "RSigler - Ziggycom" To: "Chris Cook" Cc: References: <200009052158.OAA24689@server.livingston.com> <39B5A134.11D89294@tcworks.net> Subject: Re: (PM) Re: ComOS 3.9.1b1 for PortMaster 3 available for FTP Date: Tue, 5 Sep 2000 23:24:20 -0500 Organization: Ziggycom MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: "RSigler - Ziggycom" >>ComOS 3.9.1b1 contains modem code version i12600e---the same modem code included in the ComOS 3.9 release<< Where is the beef.. ( updated modem code ) ? Randy ================================================ Ziggycom Online http://www.ziggycom.net "We are not trying to be the biggest, but the most helpful ISP" ================================================ Randy Sigler - Network Administrator 877.576.0671 - Toll Free 270.388.1385 - Pager ================================================ ----- Original Message ----- From: "Chris Cook" To: Sent: Tuesday, September 05, 2000 8:43 PM Subject: (PM) Re: ComOS 3.9.1b1 for PortMaster 3 available for FTP > 1st) Thanks for the new ComOS... > > > > _______________ Bugs Fixed in ComOS 3.9.1b1 > > > > > > * Permanent (hardwired) connections no longer occasionally enter the > > IDLE state by mistake. > > Thank God they fixed this bug... it's kinda sad they didn't tell me they > knew about it when I called into NetCare though. I'm just happy it's > fixed. > > -- > Chris > > o----< ccook@tcworks.net >-------------------------------------o > |Chris Cook - Admin | TCWORKS.NET - http://www.tcworks.net | > |The Computer Works ISP | FreeBSD - http://www.freebsd.org | > o--------------------------------------------------------------o > - > To unsubscribe, email 'majordomo@portmasters.com' with > 'unsubscribe portmaster-users' in the body of the message. > Searchable list archive: - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Tue Sep 5 23:41:36 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id XAA29223 for portmaster-users-outgoing; Tue, 5 Sep 2000 23:41:36 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id XAA29218 for ; Tue, 5 Sep 2000 23:41:32 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id VAA08889 for ; Tue, 5 Sep 2000 21:36:48 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id VAA13232 for ; Tue, 5 Sep 2000 21:42:01 -0700 (PDT) Received: from egypt.sevenkings.net (egypt.sevenkings.net [216.172.23.2]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id VAA08885 for ; Tue, 5 Sep 2000 21:36:41 -0700 (PDT) Received: from jk3329.sevenkings.net (jk3329.sevenkings.net [216.172.23.1]) by egypt.sevenkings.net (8.9.0/8.9.0) with SMTP id AAA17657 for ; Wed, 6 Sep 2000 00:41:36 -0400 (EDT) From: Egan To: portmaster-users@livingston.com Subject: Re: (PM) Secure telnet Date: Wed, 06 Sep 2000 00:41:36 -0400 Message-ID: References: <2g8ars0dc2jo28tnovid32gfeh1fqt95jl@4ax.com> <70darso3q2r6hb63aa6kcj7k4q0mrctja6@4ax.com> <39B53845.5ABEE085@lucentradius.com> In-Reply-To: <39B53845.5ABEE085@lucentradius.com> X-Mailer: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Egan On Tue, 05 Sep 2000 11:15:33 -0700, Thomas Kinnen wrote: >> Is there any secure telnet, SSH, or other software that works with PM3 >> to prevent passwords being sent clear text? > >ssh to a Unix box that has a direct serial connection to the console port. Either that or the VPN idea should work for me. Thanks for the advice. - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Wed Sep 6 12:10:24 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id MAA01215 for portmaster-users-outgoing; Wed, 6 Sep 2000 12:10:24 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id MAA01212 for ; Wed, 6 Sep 2000 12:10:21 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id KAA15922 for ; Wed, 6 Sep 2000 10:05:31 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id KAA08630 for ; Wed, 6 Sep 2000 10:10:46 -0700 (PDT) Received: from vcnserv.vcn.com (vcnserv.vcn.com [209.193.72.7]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id KAA15918 for ; Wed, 6 Sep 2000 10:05:30 -0700 (PDT) Received: by vcnserv.vcn.com with Internet Mail Service (5.5.2650.21) id ; Wed, 6 Sep 2000 11:10:16 -0600 Message-ID: <792759FDC61FF644AF9EC51E8907278D0175AE@vcnserv.vcn.com> From: Jeremy Malli To: "'portmaster-users@livingston.com'" Subject: RE: (PM) Re: ComOS 3.9.1b1 for PortMaster 3 available for FTP Date: Wed, 6 Sep 2000 11:10:15 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Jeremy Malli And not so much as a mention of a bug with the USR Courier with 3.9. That's the entire reason we're not running 3.9 . Jeremy -----Original Message----- From: RSigler - Ziggycom [mailto:randy.sigler@ziggycom.net] Sent: Tuesday, September 05, 2000 10:24 PM To: jeremy@vdom.vcn.com Cc: portmaster-users@livingston.com Subject: Re: (PM) Re: ComOS 3.9.1b1 for PortMaster 3 available for FTP >>ComOS 3.9.1b1 contains modem code version i12600e---the same modem code included in the ComOS 3.9 release<< Where is the beef.. ( updated modem code ) ? Randy ================================================ Ziggycom Online http://www.ziggycom.net "We are not trying to be the biggest, but the most helpful ISP" ================================================ Randy Sigler - Network Administrator 877.576.0671 - Toll Free 270.388.1385 - Pager ================================================ ----- Original Message ----- From: "Chris Cook" To: Sent: Tuesday, September 05, 2000 8:43 PM Subject: (PM) Re: ComOS 3.9.1b1 for PortMaster 3 available for FTP > 1st) Thanks for the new ComOS... > > > > _______________ Bugs Fixed in ComOS 3.9.1b1 > > > > > > * Permanent (hardwired) connections no longer occasionally enter the > > IDLE state by mistake. > > Thank God they fixed this bug... it's kinda sad they didn't tell me they > knew about it when I called into NetCare though. I'm just happy it's > fixed. > > -- > Chris > > o----< ccook@tcworks.net >-------------------------------------o > |Chris Cook - Admin | TCWORKS.NET - http://www.tcworks.net | > |The Computer Works ISP | FreeBSD - http://www.freebsd.org | > o--------------------------------------------------------------o > - > To unsubscribe, email 'majordomo@portmasters.com' with > 'unsubscribe portmaster-users' in the body of the message. > Searchable list archive: - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: From owner-portmaster-users@linux2.advmed.com Wed Sep 6 18:12:37 2000 Received: (from majordomo@localhost) by linux2.advmed.com (8.9.3/8.9.3) id SAA02682 for portmaster-users-outgoing; Wed, 6 Sep 2000 18:12:37 -0500 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by linux2.advmed.com (8.9.3/8.9.3) with ESMTP id SAA02678 for ; Wed, 6 Sep 2000 18:12:32 -0500 Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id QAA21702 for ; Wed, 6 Sep 2000 16:07:40 -0700 (PDT) Received: from bast.livingston.com (bast [149.198.247.2]) by server.livingston.com (8.9.3/8.9.3/1.0) with ESMTP id QAA03517 for ; Wed, 6 Sep 2000 16:12:39 -0700 (PDT) Received: from chatswood.alphanet.net.au (chatswood.alphanet.net.au [203.23.58.2]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id QAA21691 for ; Wed, 6 Sep 2000 16:07:17 -0700 (PDT) Received: from alphanet.net.au (bridge.alphanet.net.au [203.23.58.14]) by chatswood.alphanet.net.au (8.9.3/8.9.3) with ESMTP id LAA17996 for ; Thu, 7 Sep 2000 11:28:11 +1100 Message-ID: <39B6DDA9.3ECCEA02@alphanet.net.au> Date: Thu, 07 Sep 2000 10:13:29 +1000 From: Web Master X-Mailer: Mozilla 4.7 [en-gb] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: portmaster-users@livingston.com Subject: (PM) Performance of IRX References: <200008310600.XAA29843@server.livingston.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-portmaster-users@portmasters.com Precedence: bulk Reply-To: Web Master Does anyone have experience on an IRX running at 2Mb full time? Will it keep up? Regards, Alpha - To unsubscribe, email 'majordomo@portmasters.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: