From owner-freebsd-isp@FreeBSD.ORG Sun Dec 17 20:21:12 2006 Return-Path: X-Original-To: FreeBSD-ISP@FreeBSD.org Delivered-To: FreeBSD-ISP@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 313F116A412 for ; Sun, 17 Dec 2006 20:21:12 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by mx1.FreeBSD.org (Postfix) with SMTP id 5458A43CA3 for ; Sun, 17 Dec 2006 20:21:09 +0000 (GMT) (envelope-from jan@digitaldaemon.com) Received: (qmail 13902 invoked by uid 98); 17 Dec 2006 20:21:08 -0000 Received: from 63.105.9.34 by digitaldaemon.com (envelope-from , uid 89) with qmail-scanner-1.25 (clamdscan: 0.87/1195. Clear:RC:1(63.105.9.34):. Processed in 0.044565 secs); 17 Dec 2006 20:21:08 -0000 X-Qmail-Scanner-Mail-From: jan@digitaldaemon.com via digitaldaemon.com X-Qmail-Scanner: 1.25 (Clear:RC:1(63.105.9.34):. Processed in 0.044565 secs) Received: from digitaldaemon.com (HELO ?16.81.101.2?) (63.105.9.34) by digitaldaemon.com with SMTP; 17 Dec 2006 20:21:08 -0000 Message-ID: <4585A6B0.6010800@digitaldaemon.com> Date: Sun, 17 Dec 2006 15:21:04 -0500 From: Jan Knepper User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: FreeBSD ISP Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: FreeBSD 5.5 -> 6.1 for ISP purposes X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Dec 2006 20:21:12 -0000 Hi... Currently running FreeBSD 5.5-STABLE, but am considering running jails with ezjail however nullfs does not seem to be stable in 5.5. Has any of you upgrade a life system 5.x to 6.1-STABLE? Any serious gotcha's? How is 6.1-STABLE for server purposes stability wise? (Dual Opteron machines with 2 GB of RAM and 256GB SATA drives) Thanks! Jan From owner-freebsd-isp@FreeBSD.ORG Mon Dec 18 06:14:55 2006 Return-Path: X-Original-To: FreeBSD-ISP@freebsd.org Delivered-To: FreeBSD-ISP@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EFFF516A40F for ; Mon, 18 Dec 2006 06:14:55 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 098F743CA2 for ; Mon, 18 Dec 2006 06:14:54 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.21] (andersonbox1.centtech.com [192.168.42.21]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id kBI5peWt059779; Sun, 17 Dec 2006 23:51:41 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <45862C79.9080204@centtech.com> Date: Sun, 17 Dec 2006 23:51:53 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.7 (X11/20061015) MIME-Version: 1.0 To: Jan Knepper References: <4585A6B0.6010800@digitaldaemon.com> In-Reply-To: <4585A6B0.6010800@digitaldaemon.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2352/Sun Dec 17 14:22:59 2006 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: FreeBSD ISP Subject: Re: FreeBSD 5.5 -> 6.1 for ISP purposes X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2006 06:14:56 -0000 On 12/17/06 14:21, Jan Knepper wrote: > Hi... > > Currently running FreeBSD 5.5-STABLE, but am considering running jails > with ezjail however nullfs does not seem to be stable in 5.5. > > Has any of you upgrade a life system 5.x to 6.1-STABLE? Any serious > gotcha's? > > How is 6.1-STABLE for server purposes stability wise? (Dual Opteron > machines with 2 GB of RAM and 256GB SATA drives) > > Thanks! > Jan 6-STABLE is very solid. I've upgraded about 20 systems from 5.x to 6.x. One thing I did on all of them was to go to the latest 5-STABLE code first, then hop to 6-STABLE. I highly recommend 6-STABLE for the many many UFS/VFS bug fixes. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology An undefined problem has an infinite number of solutions. ------------------------------------------------------------------------ From owner-freebsd-isp@FreeBSD.ORG Mon Dec 18 14:42:23 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5791916A412 for ; Mon, 18 Dec 2006 14:42:23 +0000 (UTC) (envelope-from akachler@telcom.net) Received: from mail.telcom.net (mail.telcom.net [200.62.2.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E80343CB6 for ; Mon, 18 Dec 2006 14:40:43 +0000 (GMT) (envelope-from akachler@telcom.net) Received: from [127.0.0.1] (adsl-2-152-135.mia.bellsouth.net [65.2.152.135]) by mail.telcom.net (8.13.8/8.13.6) with ESMTP id kBIE7muo069352; Mon, 18 Dec 2006 09:07:50 -0500 (EST) (envelope-from akachler@telcom.net) Message-ID: <4586A0A8.5090703@telcom.net> Date: Mon, 18 Dec 2006 09:07:36 -0500 From: Arie Kachler Organization: Telcom.Net User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Jan Knepper , freebsd-isp@freebsd.org References: <4585A6B0.6010800@digitaldaemon.com> In-Reply-To: <4585A6B0.6010800@digitaldaemon.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: FreeBSD 5.5 -> 6.1 for ISP purposes X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: akachler@telcom.net List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2006 14:42:23 -0000 Hi Jan, We run some very high traffic mail systems on 6.1R. We did have issues before ftp://ftp.freebsd.org/pub/FreeBSD/ERRATA/notices/FreeBSD-EN-06:02.net.asc was released. But 6.1 + above patch is rock solid and very fast on high-end servers. We tried running a production server on Fedora 5. I was very dissapointed on how unstable it is under heavy loads. Needless to say, we went back to 6.1. I've been reading that there are some issues with shared IRQ setups. Since this doesn't apply to us, I don't know much about it. I can't say enough good things about 6.1. Arie Jan Knepper wrote: > Hi... > > Currently running FreeBSD 5.5-STABLE, but am considering running jails > with ezjail however nullfs does not seem to be stable in 5.5. > > Has any of you upgrade a life system 5.x to 6.1-STABLE? Any serious > gotcha's? > > How is 6.1-STABLE for server purposes stability wise? (Dual Opteron > machines with 2 GB of RAM and 256GB SATA drives) > > Thanks! > Jan > > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" > > > . > From owner-freebsd-isp@FreeBSD.ORG Mon Dec 18 15:58:02 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7EA9816A407 for ; Mon, 18 Dec 2006 15:58:02 +0000 (UTC) (envelope-from fclements@inetu.net) Received: from xmail01.inetu.net (xmail01.inetu.net [209.235.223.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 779D343CA4 for ; Mon, 18 Dec 2006 15:56:34 +0000 (GMT) (envelope-from fclements@inetu.net) X-Header-Check: INU-79dfeaebfdc3e45c Received: from kelt.int.inetu.net ([172.20.1.12]) by xmail01.inetu.net (8.13.1/8.13.1) with ESMTP id kBIFdlSb006341; Mon, 18 Dec 2006 10:39:47 -0500 (EST) (envelope-from fclements@inetu.net) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 18 Dec 2006 10:40:00 -0500 Message-ID: In-Reply-To: <4586A0A8.5090703@telcom.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FreeBSD 5.5 -> 6.1 for ISP purposes Thread-Index: Accissu0/a9KYv+WSreuda7sLt6OowAB33Rw From: "Frank Clements" To: "Jan Knepper" , X-Virus-Scanned: ClamAV 0.88.6/2354/Mon Dec 18 03:50:31 2006 on xmail01.inetu.net X-Virus-Status: Clean Cc: Subject: RE: FreeBSD 5.5 -> 6.1 for ISP purposes X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2006 15:58:02 -0000 Jan, =20 I recently ran into nfsd load issues related to quotas in 6.1-RELEASE. Turning quota option off in the kernel fixed it. So if you'll be using nfsd w/ quotas you may want to go with 6.0 as I don't believe that has the problem. Information can be found here: http://lists.freebsd.org/pipermail/freebsd-bugs/2006-June/018939.html Regards, -Frank C. -----Original Message----- From: owner-freebsd-isp@freebsd.org [mailto:owner-freebsd-isp@freebsd.org] On Behalf Of Arie Kachler Sent: Monday, December 18, 2006 9:08 AM To: Jan Knepper; freebsd-isp@freebsd.org Subject: Re: FreeBSD 5.5 -> 6.1 for ISP purposes Hi Jan, We run some very high traffic mail systems on 6.1R. We did have issues before ftp://ftp.freebsd.org/pub/FreeBSD/ERRATA/notices/FreeBSD-EN-06:02.net.as c was released. But 6.1 + above patch is rock solid and very fast on high-end servers. We tried running a production server on Fedora 5. I was very dissapointed on how unstable it is under heavy loads. Needless to say, we went back to 6.1. I've been reading that there are some issues with shared IRQ setups.=20 Since this doesn't apply to us, I don't know much about it. I can't say enough good things about 6.1. Arie Jan Knepper wrote: > Hi... > > Currently running FreeBSD 5.5-STABLE, but am considering running jails > with ezjail however nullfs does not seem to be stable in 5.5. > > Has any of you upgrade a life system 5.x to 6.1-STABLE? Any serious=20 > gotcha's? > > How is 6.1-STABLE for server purposes stability wise? (Dual Opteron=20 > machines with 2 GB of RAM and 256GB SATA drives) > > Thanks! > Jan > > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" > > > . > _______________________________________________ freebsd-isp@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-isp To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" From owner-freebsd-isp@FreeBSD.ORG Mon Dec 18 20:55:40 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ED44E16A412 for ; Mon, 18 Dec 2006 20:55:40 +0000 (UTC) (envelope-from estover@nativenerds.com) Received: from www.nativenerds.com (host-70-0-111-24.midco.net [24.111.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CF3343CA2 for ; Mon, 18 Dec 2006 20:55:37 +0000 (GMT) (envelope-from estover@nativenerds.com) Received: from [69.77.198.205] (helo=[192.168.1.89]) by www.nativenerds.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.50) id 1GwOQp-000JZA-NI; Mon, 18 Dec 2006 12:45:52 -0700 Message-ID: <4586F311.8050004@nativenerds.com> Date: Mon, 18 Dec 2006 12:59:13 -0700 From: Ed Stover User-Agent: Thunderbird 1.5.0.7 (X11/20060918) MIME-Version: 1.0 To: Bob Martin References: <20061024000805.GA12810@uncanny.net> <453D5EBE.1050306@mawer.org> <453D67C6.4050402@buckhorn.net> In-Reply-To: <453D67C6.4050402@buckhorn.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus-Scanner: Scanned with ClamAV. Cc: freebsd-isp@freebsd.org Subject: Re: Internet Link Detective Audit X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2006 20:55:41 -0000 Bob Martin wrote: > There is also the old and venerable ntop, in the ports. > > Bob Martin > > Antony Mawer wrote: >> On 24/10/2006 10:08 AM, Edward Elhauge wrote: >> >>> I'm hoping someone on this list can steer me in the right direction >>> towards figuring out what is going on with my internet link. (Or rather >>> the tools to figure it out on my own). >>> >> ... >> >>> >>> What I'd like is a tool running on FreeBSD that will sort IP traffic >>> coming across my Internet interface by: >>> SRC IP, PROTOCOL and PORT >>> DEST IP, PROTOCOL and PORT >>> then give me total KBs passed in that interval. >> >> >> I was recently in a similar situation and went looking for a similar >> tool, and came across "darkstat" in the ports collection: >> >> http://www.freshports.org/net-mgmt/darkstat >> >> While I did find it a bit rough around the edges in terms of some of >> its data display, it gave me a way to monitor and visualise my traffic >> flows and identify the large offenders... >> >> In my case it turned out an OS X machine was set to automatically >> download system updates, but because no one had applied them yet, it >> was re-downloading them every day... :-) >> >> Hope it helps! >> >> -- Antony >> I know this is a old post but no one covered iftop and trafshow . The combination of those two has helped me track bad bandwidth "leaks" for a while now. From owner-freebsd-isp@FreeBSD.ORG Tue Dec 19 16:40:04 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 77EC016A47B for ; Tue, 19 Dec 2006 16:40:04 +0000 (UTC) (envelope-from samstand@surfside.net) Received: from mail12.mdx.safepages.com (mail12.mdx.safepages.com [216.127.154.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17E3243CA6 for ; Tue, 19 Dec 2006 16:40:03 +0000 (GMT) (envelope-from samstand@surfside.net) Received: by mail12.mdx.safepages.com (Postfix, from userid 1012) id E539AB6F2; Tue, 19 Dec 2006 16:20:33 +0000 (GMT) Received: from [127.0.0.1] (cpe-75-83-148-27.socal.res.rr.com [75.83.148.27]) by mail12.mdx.safepages.com (Postfix) with ESMTP id 68AA4B726 for ; Tue, 19 Dec 2006 16:20:33 +0000 (GMT) Message-ID: <45881141.6060503@surfside.net> Date: Tue, 19 Dec 2006 08:20:17 -0800 From: samstand User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: freebsd-isp@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: [server bounce message] Regarding a recent mail delivery attempt. X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2006 16:40:04 -0000 My son wants his ISP to filter out spam as mine does. My ISP is /surfside.net./ Evidently /surfside.net/ uses your spam screening program. How can I tell my son something for him to do to get rid of his spam? Maybe get his host server to buy or subscribe to your program??? Please help! Big problem! Thanks for any help you care to offer. Sam Stand Fullerton, Calif. From owner-freebsd-isp@FreeBSD.ORG Wed Dec 20 09:46:38 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 90C0E16A412 for ; Wed, 20 Dec 2006 09:46:38 +0000 (UTC) (envelope-from "") Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5470543CBB for ; Wed, 20 Dec 2006 09:46:10 +0000 (GMT) (envelope-from "") Received: from mail105-ce5 (mail105-ce5 [10.13.9.127]) by smtpout.mac.com (Xserve/8.12.11/smtpout04/MantshX 4.0) with ESMTP id kBK9YJxg000355 for ; Wed, 20 Dec 2006 01:34:19 -0800 (PST) Resent-Date: Wed, 20 Dec 2006 01:34:19 -0800 (PST) Resent-Message-Id: <200612200934.kBK9YJxg000355@smtpout.mac.com> Received: from autoreply-daemon.ms105.mac.com by ms105.mac.com (iPlanet Messaging Server 5.2 HotFix 2.08 (built Sep 22 2005)) id <0JAK00B02FX7UZ@ms105.mac.com> for freebsd-isp@freebsd.org; Wed, 20 Dec 2006 01:34:19 -0800 (PST) Date: Wed, 20 Dec 2006 01:34:19 -0800 (PST) From: brettjolly@mac.com In-reply-to: <200612200933.kBK9XUfv014597@mac.com> Resent-to: freebsd-isp@freebsd.org To: freebsd-isp@freebsd.org Message-id: <0JAK00B03FX7UZ@ms105.mac.com> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Resent-From: MAILER-DAEMON Subject: Re: Returned mail: see transcript for details X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Dec 2006 09:46:38 -0000 This is an automated reply service, thanks for your mail, I'm currently in holiday until 14th January 2007, I will however download my mail regulary, failing which you may telephone my P.A. Nicky Steele on +27 (0)726592111 who will ensure your message will be forwarded to me according to its urgency. Brett Jolly. From owner-freebsd-isp@FreeBSD.ORG Wed Dec 20 10:36:01 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BA6D816A412 for ; Wed, 20 Dec 2006 10:36:01 +0000 (UTC) (envelope-from brettjolly@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6287A43CA2 for ; Wed, 20 Dec 2006 10:36:01 +0000 (GMT) (envelope-from brettjolly@mac.com) Received: from mac.com (webmail014-S [10.13.128.14]) by smtpout.mac.com (Xserve/8.12.11/smtpout10/MantshX 4.0) with ESMTP id kBKAOh8q022608 for ; Wed, 20 Dec 2006 02:24:43 -0800 (PST) Received: from webmail014 (localhost [127.0.0.1]) by mac.com (8.13.8/webmail014/MantshX 4.0) with ESMTP id kBKAOf5X021228 for ; Wed, 20 Dec 2006 02:24:43 -0800 (PST) Date: Wed, 20 Dec 2006 02:24:41 -0800 From: Brett Jolly To: freebsd-isp@freebsd.org Message-ID: <8A05FE9E-010F-1000-897E-7BEE620344C2-Webmail-10020@mac.com> in-reply-to: <200612200933.kBK9XUfv014597@mac.com> references: <200612200933.kBK9XUfv014597@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Originating-IP: 217.72.182.43 Received: from [217.72.182.43] from webmail.mac.com with HTTP; Wed, 20 Dec 2006 02:24:41 -0800 X-Brightmail-Tracker: AAAAAA== X-Brightmail-scanned: yes Subject: Re: Returned mail: see transcript for details X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Dec 2006 10:36:01 -0000 How do I know that you are bona fide "mac" and not just another whoever trying to get me to install a proxy server or whatever, your e-mail address is "freebsd" for god sake. From owner-freebsd-isp@FreeBSD.ORG Wed Dec 20 15:42:42 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6EBB616A412 for ; Wed, 20 Dec 2006 15:42:42 +0000 (UTC) (envelope-from jtregunna@blurgle.ca) Received: from picard.blurgle.ca (picard.blurgle.ca [64.187.9.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id A960C43CB5 for ; Wed, 20 Dec 2006 15:42:33 +0000 (GMT) (envelope-from jtregunna@blurgle.ca) Received: from [192.168.7.5] (office.highspeedfx.net [64.187.18.74]) (authenticated bits=0) by picard.blurgle.ca (8.13.8/8.13.8) with ESMTP id kBKFD8jK060682 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO) for ; Wed, 20 Dec 2006 10:13:09 -0500 (EST) (envelope-from jtregunna@blurgle.ca) Mime-Version: 1.0 (Apple Message framework v752.3) To: freebsd-isp@freebsd.org Message-Id: <2004672F-664F-4331-A09F-D09A0C9DD99E@blurgle.ca> From: Jeremy Tregunna Date: Wed, 20 Dec 2006 10:14:27 -0500 X-Mailer: Apple Mail (2.752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: RADIUS/PPPoE Dead Connections X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Dec 2006 15:42:42 -0000 I've got a FreeBSD NAS and a FreeBSD RADIUS server (both running 6.1) serving up access to a wireless network. In any event, everything seems to work peachy when a user logs in and disconnects manually. But if for instance, someone closes the lid on their laptop and their wireless card powers off due to standby mode, the connection to the NAS is broken and the disconnect request never makes it from the NAS to the RADIUS server to inform it that the client went offline. Now then, I'm not so much worried about that stale entry staying on the RADIUS server until the user tries to log in again (I don't care much about time used, only bandwidth numbers); but ultimately it would be nice to have one of two solutions: (1) A user tries to log in when he's already logged in, have it disconnect that user and then log in; or (2) Have the NAS send a Disconnect-Request to the RADIUS server when-- as in the above example--someone closes the lid on their laptop. An idle timeout isn't a workable solution for me, neither is a session timeout; I need both to have no fixed limit for all clients. My ppp.conf file is basically defined as: ### ppp.conf begin default: set log Chat Command Phase enable pap allow mode direct enable proxy disable ipv6cp set radius /etc/radius.conf set mru 1492 set mtu 1492 accept dns ### end ppp.conf The relevant users portion is like: DEFAULT Auth-Type := System Service-Type := Framed-User, Framed-Protocol := PPP, Framed-IP-Address := 192.168.8.50, Framed-IP-Netmask := 255.255.255.0, Framed-Routing := Broadcast-Listen, Framed-MTU := 1492 And the relevant portions of attrs is like: DEFAULT Service-Type == Framed-User, Framed-Protocol == PPP, Framed-MTU == 1492, Framed-Filter-ID =* ANY, Reply-Message =* ANY, Session-Timeout == 0, Idle-Timeout == 0, Port-Limit <= 2 Any assistance would be greatly appreciated. Regards, Jeremy Tregunna From owner-freebsd-isp@FreeBSD.ORG Wed Dec 20 17:14:15 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1EBE016A47C for ; Wed, 20 Dec 2006 17:14:15 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by mx1.FreeBSD.org (Postfix) with SMTP id 4496443CA0 for ; Wed, 20 Dec 2006 17:14:11 +0000 (GMT) (envelope-from jan@digitaldaemon.com) Received: (qmail 72785 invoked by uid 98); 20 Dec 2006 17:07:29 -0000 Received: from 63.105.9.34 by digitaldaemon.com (envelope-from , uid 89) with qmail-scanner-1.25 (clamdscan: 0.87/1195. Clear:RC:1(63.105.9.34):. Processed in 0.968378 secs); 20 Dec 2006 17:07:29 -0000 X-Qmail-Scanner-Mail-From: jan@digitaldaemon.com via digitaldaemon.com X-Qmail-Scanner: 1.25 (Clear:RC:1(63.105.9.34):. Processed in 0.968378 secs) Received: from digitaldaemon.com (HELO ?184.157.101.2?) (63.105.9.34) by digitaldaemon.com with SMTP; 20 Dec 2006 17:07:28 -0000 Message-ID: <45896DCC.9080609@digitaldaemon.com> Date: Wed, 20 Dec 2006 12:07:24 -0500 From: Jan Knepper User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Frank Clements References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-isp@freebsd.org Subject: Re: FreeBSD 5.5 -> 6.1 for ISP purposes X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Dec 2006 17:14:15 -0000 Thanks Frank! Not planning on using nfsd (I think) with quota's. The main thing at this moment is Internet services as Apache (1.3), qmail, vpopmail, nntp, cvs, cvsup, etc. Hopefully I will not have to rebuild all that stuff on 6.x to make them work Than the new things is going to be jails (ezjail) which uses nullfs to preserve disk space. Thanks! Jan Frank Clements wrote: > Jan, > > I recently ran into nfsd load issues related to quotas in 6.1-RELEASE. > Turning quota option off in the kernel fixed it. So if you'll be using > nfsd w/ quotas you may want to go with 6.0 as I don't believe that has > the problem. > > Information can be found here: > http://lists.freebsd.org/pipermail/freebsd-bugs/2006-June/018939.html > > Regards, > -Frank C. > > -----Original Message----- > From: owner-freebsd-isp@freebsd.org > [mailto:owner-freebsd-isp@freebsd.org] On Behalf Of Arie Kachler > Sent: Monday, December 18, 2006 9:08 AM > To: Jan Knepper; freebsd-isp@freebsd.org > Subject: Re: FreeBSD 5.5 -> 6.1 for ISP purposes > > Hi Jan, > > We run some very high traffic mail systems on 6.1R. > We did have issues before > ftp://ftp.freebsd.org/pub/FreeBSD/ERRATA/notices/FreeBSD-EN-06:02.net.as > c > was released. > But 6.1 + above patch is rock solid and very fast on high-end servers. > We tried running a production server on Fedora 5. I was very > dissapointed on how unstable it is under heavy loads. Needless to say, > we went back to 6.1. > I've been reading that there are some issues with shared IRQ setups. > Since this doesn't apply to us, I don't know much about it. > I can't say enough good things about 6.1. > > Arie > > > Jan Knepper wrote: > >> Hi... >> >> Currently running FreeBSD 5.5-STABLE, but am considering running jails >> > > >> with ezjail however nullfs does not seem to be stable in 5.5. >> >> Has any of you upgrade a life system 5.x to 6.1-STABLE? Any serious >> gotcha's? >> >> How is 6.1-STABLE for server purposes stability wise? (Dual Opteron >> machines with 2 GB of RAM and 256GB SATA drives) >> >> Thanks! >> Jan >> >> _______________________________________________ >> freebsd-isp@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-isp >> To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" >> >> >> . >> >> > > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" > > > From owner-freebsd-isp@FreeBSD.ORG Wed Dec 20 17:16:27 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E1AD316A4CA for ; Wed, 20 Dec 2006 17:16:27 +0000 (UTC) (envelope-from akachler@telcom.net) Received: from mail.telcom.net (mail.telcom.net [200.62.2.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7E7743CAE for ; Wed, 20 Dec 2006 17:16:18 +0000 (GMT) (envelope-from akachler@telcom.net) Received: from [127.0.0.1] (adsl-2-152-135.mia.bellsouth.net [65.2.152.135]) by mail.telcom.net (8.13.8/8.13.6) with ESMTP id kBKHGBxT096826; Wed, 20 Dec 2006 12:16:13 -0500 (EST) (envelope-from akachler@telcom.net) Message-ID: <45896FCC.3010805@telcom.net> Date: Wed, 20 Dec 2006 12:15:56 -0500 From: Arie Kachler Organization: Telcom.Net User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Jan Knepper References: <4585A6B0.6010800@digitaldaemon.com> <4586A0A8.5090703@telcom.net> <45896C5B.5040002@digitaldaemon.com> In-Reply-To: <45896C5B.5040002@digitaldaemon.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-isp@freebsd.org Subject: Re: FreeBSD 5.5 -> 6.1 for ISP purposes X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: akachler@telcom.net List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Dec 2006 17:16:28 -0000 Hi again Jan, It was not an upgrade. It was a 6.1R install. Good luck! Jan Knepper wrote: > Hi Artie! > > Thanks for the response! > Great to hear 6.1+ is as solid for server applications as it has > seemed to be for my desktop. > Did you every update a 5.5-STABLE box to 6.x? Did you follow any > specific procedure? > I personally am too much into the BSD's to ever seriously try a Linux > again... ;-) > > Thanks! > Jan > > > > Arie Kachler wrote: >> Hi Jan, >> >> We run some very high traffic mail systems on 6.1R. >> We did have issues before >> ftp://ftp.freebsd.org/pub/FreeBSD/ERRATA/notices/FreeBSD-EN-06:02.net.asc >> was released. >> But 6.1 + above patch is rock solid and very fast on high-end servers. >> We tried running a production server on Fedora 5. I was very >> dissapointed on how unstable it is under heavy loads. Needless to >> say, we went back to 6.1. >> I've been reading that there are some issues with shared IRQ setups. >> Since this doesn't apply to us, I don't know much about it. >> I can't say enough good things about 6.1. >> >> Arie >> >> >> Jan Knepper wrote: >>> Hi... >>> >>> Currently running FreeBSD 5.5-STABLE, but am considering running >>> jails with ezjail however nullfs does not seem to be stable in 5.5. >>> >>> Has any of you upgrade a life system 5.x to 6.1-STABLE? Any serious >>> gotcha's? >>> >>> How is 6.1-STABLE for server purposes stability wise? (Dual Opteron >>> machines with 2 GB of RAM and 256GB SATA drives) >>> >>> Thanks! >>> Jan >>> >>> _______________________________________________ >>> freebsd-isp@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-isp >>> To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" >>> >>> >>> . >>> >> >> _______________________________________________ >> freebsd-isp@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-isp >> To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" >> >> > > > . > From owner-freebsd-isp@FreeBSD.ORG Wed Dec 20 17:28:38 2006 Return-Path: X-Original-To: FreeBSD-ISP@freebsd.org Delivered-To: FreeBSD-ISP@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 40E1416A415 for ; Wed, 20 Dec 2006 17:28:38 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by mx1.FreeBSD.org (Postfix) with SMTP id 4F4CC43DDA for ; Wed, 20 Dec 2006 17:27:01 +0000 (GMT) (envelope-from jan@digitaldaemon.com) Received: (qmail 72321 invoked by uid 98); 20 Dec 2006 16:59:04 -0000 Received: from 63.105.9.34 by digitaldaemon.com (envelope-from , uid 89) with qmail-scanner-1.25 (clamdscan: 0.87/1195. Clear:RC:1(63.105.9.34):. Processed in 0.301075 secs); 20 Dec 2006 16:59:04 -0000 X-Qmail-Scanner-Mail-From: jan@digitaldaemon.com via digitaldaemon.com X-Qmail-Scanner: 1.25 (Clear:RC:1(63.105.9.34):. Processed in 0.301075 secs) Received: from digitaldaemon.com (HELO ?184.157.101.2?) (63.105.9.34) by digitaldaemon.com with SMTP; 20 Dec 2006 16:59:03 -0000 Message-ID: <45896BD5.9030402@digitaldaemon.com> Date: Wed, 20 Dec 2006 11:59:01 -0500 From: Jan Knepper User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Eric Anderson References: <4585A6B0.6010800@digitaldaemon.com> <45862C79.9080204@centtech.com> In-Reply-To: <45862C79.9080204@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD ISP Subject: Re: FreeBSD 5.5 -> 6.1 for ISP purposes X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Dec 2006 17:28:38 -0000 Thanks! Any specific procedure you followed? I tried: http://people.freebsd.org/~rse/upgrade/freebsd-upgrade-5x-6x.txt But that does seem to have some minor problems as audit does not exist in /etc/group for instance. Thanks! Jan Eric Anderson wrote: > On 12/17/06 14:21, Jan Knepper wrote: >> Hi... >> >> Currently running FreeBSD 5.5-STABLE, but am considering running >> jails with ezjail however nullfs does not seem to be stable in 5.5. >> >> Has any of you upgrade a life system 5.x to 6.1-STABLE? Any serious >> gotcha's? >> >> How is 6.1-STABLE for server purposes stability wise? (Dual Opteron >> machines with 2 GB of RAM and 256GB SATA drives) >> >> Thanks! >> Jan > > 6-STABLE is very solid. I've upgraded about 20 systems from 5.x to > 6.x. One thing I did on all of them was to go to the latest 5-STABLE > code first, then hop to 6-STABLE. I highly recommend 6-STABLE for the > many many UFS/VFS bug fixes. > > Eric > > > From owner-freebsd-isp@FreeBSD.ORG Wed Dec 20 17:29:30 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3658D16A403 for ; Wed, 20 Dec 2006 17:29:30 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by mx1.FreeBSD.org (Postfix) with SMTP id 831B743CB2 for ; Wed, 20 Dec 2006 17:28:07 +0000 (GMT) (envelope-from jan@digitaldaemon.com) Received: (qmail 72513 invoked by uid 98); 20 Dec 2006 17:01:17 -0000 Received: from 63.105.9.34 by digitaldaemon.com (envelope-from , uid 89) with qmail-scanner-1.25 (clamdscan: 0.87/1195. Clear:RC:1(63.105.9.34):. Processed in 0.216422 secs); 20 Dec 2006 17:01:17 -0000 X-Qmail-Scanner-Mail-From: jan@digitaldaemon.com via digitaldaemon.com X-Qmail-Scanner: 1.25 (Clear:RC:1(63.105.9.34):. Processed in 0.216422 secs) Received: from digitaldaemon.com (HELO ?184.157.101.2?) (63.105.9.34) by digitaldaemon.com with SMTP; 20 Dec 2006 17:01:16 -0000 Message-ID: <45896C5B.5040002@digitaldaemon.com> Date: Wed, 20 Dec 2006 12:01:15 -0500 From: Jan Knepper User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: akachler@telcom.net References: <4585A6B0.6010800@digitaldaemon.com> <4586A0A8.5090703@telcom.net> In-Reply-To: <4586A0A8.5090703@telcom.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-isp@freebsd.org Subject: Re: FreeBSD 5.5 -> 6.1 for ISP purposes X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Dec 2006 17:29:30 -0000 Hi Artie! Thanks for the response! Great to hear 6.1+ is as solid for server applications as it has seemed to be for my desktop. Did you every update a 5.5-STABLE box to 6.x? Did you follow any specific procedure? I personally am too much into the BSD's to ever seriously try a Linux again... ;-) Thanks! Jan Arie Kachler wrote: > Hi Jan, > > We run some very high traffic mail systems on 6.1R. > We did have issues before > ftp://ftp.freebsd.org/pub/FreeBSD/ERRATA/notices/FreeBSD-EN-06:02.net.asc > was released. > But 6.1 + above patch is rock solid and very fast on high-end servers. > We tried running a production server on Fedora 5. I was very > dissapointed on how unstable it is under heavy loads. Needless to say, > we went back to 6.1. > I've been reading that there are some issues with shared IRQ setups. > Since this doesn't apply to us, I don't know much about it. > I can't say enough good things about 6.1. > > Arie > > > Jan Knepper wrote: >> Hi... >> >> Currently running FreeBSD 5.5-STABLE, but am considering running >> jails with ezjail however nullfs does not seem to be stable in 5.5. >> >> Has any of you upgrade a life system 5.x to 6.1-STABLE? Any serious >> gotcha's? >> >> How is 6.1-STABLE for server purposes stability wise? (Dual Opteron >> machines with 2 GB of RAM and 256GB SATA drives) >> >> Thanks! >> Jan >> >> _______________________________________________ >> freebsd-isp@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-isp >> To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" >> >> >> . >> > > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" > > From owner-freebsd-isp@FreeBSD.ORG Wed Dec 20 19:15:18 2006 Return-Path: X-Original-To: FreeBSD-ISP@freebsd.org Delivered-To: FreeBSD-ISP@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C5A3916A403 for ; Wed, 20 Dec 2006 19:15:18 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B99E43CB3 for ; Wed, 20 Dec 2006 19:14:50 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id kBKIl8FL021007; Wed, 20 Dec 2006 12:47:08 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <45898537.1080103@centtech.com> Date: Wed, 20 Dec 2006 12:47:19 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.7 (X11/20061015) MIME-Version: 1.0 To: Jan Knepper References: <4585A6B0.6010800@digitaldaemon.com> <45862C79.9080204@centtech.com> <45896BD5.9030402@digitaldaemon.com> In-Reply-To: <45896BD5.9030402@digitaldaemon.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2361/Wed Dec 20 09:30:05 2006 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: FreeBSD ISP Subject: Re: FreeBSD 5.5 -> 6.1 for ISP purposes X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Dec 2006 19:15:18 -0000 On 12/20/06 10:59, Jan Knepper wrote: > Thanks! > > Any specific procedure you followed? > I tried: http://people.freebsd.org/~rse/upgrade/freebsd-upgrade-5x-6x.txt > But that does seem to have some minor problems as audit does not exist > in /etc/group for instance. I don't use those instructions, and I'm not sure what those really apply to exactly. I use what is recommended in /usr/src/UPDATING. First, I copy the new GENERIC, and make my changes like I had in my old kernel. I make sure I have COMPAT_FREEBSD5 in the new kernel. Then, something like: make buildworld make kernel KERNCONF=YOUR_KERNEL_HERE mergemaster -pmake installworld make delete-old mergemaster -i reboot That's what *I* do, but that isn't the recommended path from official @freebsd.org people. See /usr/src/UPDATING and read it carefully. > > Eric Anderson wrote: >> On 12/17/06 14:21, Jan Knepper wrote: >>> Hi... >>> >>> Currently running FreeBSD 5.5-STABLE, but am considering running >>> jails with ezjail however nullfs does not seem to be stable in 5.5. >>> >>> Has any of you upgrade a life system 5.x to 6.1-STABLE? Any serious >>> gotcha's? >>> >>> How is 6.1-STABLE for server purposes stability wise? (Dual Opteron >>> machines with 2 GB of RAM and 256GB SATA drives) >>> >>> Thanks! >>> Jan >> 6-STABLE is very solid. I've upgraded about 20 systems from 5.x to >> 6.x. One thing I did on all of them was to go to the latest 5-STABLE >> code first, then hop to 6-STABLE. I highly recommend 6-STABLE for the >> many many UFS/VFS bug fixes. >> >> Eric >> >> >> -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology An undefined problem has an infinite number of solutions. ------------------------------------------------------------------------ From owner-freebsd-isp@FreeBSD.ORG Wed Dec 20 19:15:35 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9338A16A503 for ; Wed, 20 Dec 2006 19:15:35 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5678743CA6 for ; Wed, 20 Dec 2006 19:15:18 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id kBKIlksx021135; Wed, 20 Dec 2006 12:47:46 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <4589855D.5010100@centtech.com> Date: Wed, 20 Dec 2006 12:47:57 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.7 (X11/20061015) MIME-Version: 1.0 To: Jan Knepper References: <4585A6B0.6010800@digitaldaemon.com> <4586A0A8.5090703@telcom.net> <45896C5B.5040002@digitaldaemon.com> In-Reply-To: <45896C5B.5040002@digitaldaemon.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2361/Wed Dec 20 09:30:05 2006 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-isp@freebsd.org, akachler@telcom.net Subject: Re: FreeBSD 5.5 -> 6.1 for ISP purposes X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Dec 2006 19:15:35 -0000 On 12/20/06 11:01, Jan Knepper wrote: > Hi Artie! > > Thanks for the response! > Great to hear 6.1+ is as solid for server applications as it has seemed > to be for my desktop. > Did you every update a 5.5-STABLE box to 6.x? Did you follow any > specific procedure? > I personally am too much into the BSD's to ever seriously try a Linux > again... ;-) I've done this lots of times, and it's worked fine for me each time. Eric > Arie Kachler wrote: >> Hi Jan, >> >> We run some very high traffic mail systems on 6.1R. >> We did have issues before >> ftp://ftp.freebsd.org/pub/FreeBSD/ERRATA/notices/FreeBSD-EN-06:02.net.asc >> was released. >> But 6.1 + above patch is rock solid and very fast on high-end servers. >> We tried running a production server on Fedora 5. I was very >> dissapointed on how unstable it is under heavy loads. Needless to say, >> we went back to 6.1. >> I've been reading that there are some issues with shared IRQ setups. >> Since this doesn't apply to us, I don't know much about it. >> I can't say enough good things about 6.1. >> >> Arie >> >> >> Jan Knepper wrote: >>> Hi... >>> >>> Currently running FreeBSD 5.5-STABLE, but am considering running >>> jails with ezjail however nullfs does not seem to be stable in 5.5. >>> >>> Has any of you upgrade a life system 5.x to 6.1-STABLE? Any serious >>> gotcha's? >>> >>> How is 6.1-STABLE for server purposes stability wise? (Dual Opteron >>> machines with 2 GB of RAM and 256GB SATA drives) >>> >>> Thanks! >>> Jan >>> >>> _______________________________________________ >>> freebsd-isp@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-isp >>> To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" >>> >>> >>> . >>> >> _______________________________________________ >> freebsd-isp@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-isp >> To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" >> >> > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology An undefined problem has an infinite number of solutions. ------------------------------------------------------------------------ From owner-freebsd-isp@FreeBSD.ORG Thu Dec 21 11:42:39 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1082116A509 for ; Thu, 21 Dec 2006 11:42:39 +0000 (UTC) (envelope-from jtregunna@blurgle.ca) Received: from picard.blurgle.ca (picard.blurgle.ca [64.187.9.69]) by mx1.freebsd.org (Postfix) with ESMTP id 66E5A13C475 for ; Thu, 21 Dec 2006 11:42:38 +0000 (UTC) (envelope-from jtregunna@blurgle.ca) Received: from [10.0.0.5] (locutus.blurgle.ca [66.38.165.231]) (authenticated bits=0) by picard.blurgle.ca (8.13.8/8.13.8) with ESMTP id kBKNOFhD070406 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Wed, 20 Dec 2006 18:24:19 -0500 (EST) (envelope-from jtregunna@blurgle.ca) In-Reply-To: <56245.24.122.21.214.1166649785.squirrel@secure.interplex.ca> References: <2004672F-664F-4331-A09F-D09A0C9DD99E@blurgle.ca> <56245.24.122.21.214.1166649785.squirrel@secure.interplex.ca> Mime-Version: 1.0 (Apple Message framework v752.3) X-Priority: 3 (Normal) Message-Id: From: Jeremy Tregunna Date: Wed, 20 Dec 2006 18:25:35 -0500 To: dblais@interplex.ca X-Mailer: Apple Mail (2.752.3) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-isp@freebsd.org Subject: Re: RADIUS/PPPoE Dead Connections X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Dec 2006 11:42:39 -0000 My apologies, I just did some local testing here at home using it, =20 and although the setup isn't exactly the same, it's close enough for =20 testing purposes. Using mpd, logging in and then disconnecting by way =20= of putting the machine to standby, then bringing it back out, =20 reconnecting; I don't have this issue any longer -- seems to work great. Much appreciated Regards; Jeremy Tregunna On 20-Dec-06, at 4:23 PM, Dominic Blais wrote: > Try mpd instead of ppp, great performances... we're using it as a =20 > pppoe > concentrator for more than 100 simultaneous connections.. > > See /usr/ports/net/mpd > > mpd4 is beta, don't try it for production. > > > >> >> I've got a FreeBSD NAS and a FreeBSD RADIUS server (both running 6.1) >> serving up access to a wireless network. In any event, everything >> seems to work peachy when a user logs in and disconnects manually. >> But if for instance, someone closes the lid on their laptop and their >> wireless card powers off due to standby mode, the connection to the >> NAS is broken and the disconnect request never makes it from the NAS >> to the RADIUS server to inform it that the client went offline. >> >> Now then, I'm not so much worried about that stale entry staying on >> the RADIUS server until the user tries to log in again (I don't care >> much about time used, only bandwidth numbers); but ultimately it >> would be nice to have one of two solutions: >> >> (1) A user tries to log in when he's already logged in, have it >> disconnect that user and then log in; or >> (2) Have the NAS send a Disconnect-Request to the RADIUS server =20 >> when-- >> as in the above example--someone closes the lid on their laptop. >> >> An idle timeout isn't a workable solution for me, neither is a >> session timeout; I need both to have no fixed limit for all clients. >> >> My ppp.conf file is basically defined as: >> >> ### ppp.conf begin >> >> default: >> set log Chat Command Phase >> enable pap >> allow mode direct >> enable proxy >> disable ipv6cp >> set radius /etc/radius.conf >> set mru 1492 >> set mtu 1492 >> accept dns >> >> ### end ppp.conf >> >> The relevant users portion is like: >> >> DEFAULT Auth-Type :=3D System >> Service-Type :=3D Framed-User, >> Framed-Protocol :=3D PPP, >> Framed-IP-Address :=3D 192.168.8.50, >> Framed-IP-Netmask :=3D 255.255.255.0, >> Framed-Routing :=3D Broadcast-Listen, >> Framed-MTU :=3D 1492 >> >> And the relevant portions of attrs is like: >> >> DEFAULT >> Service-Type =3D=3D Framed-User, >> Framed-Protocol =3D=3D PPP, >> Framed-MTU =3D=3D 1492, >> Framed-Filter-ID =3D* ANY, >> Reply-Message =3D* ANY, >> Session-Timeout =3D=3D 0, >> Idle-Timeout =3D=3D 0, >> Port-Limit <=3D 2 >> >> Any assistance would be greatly appreciated. >> >> Regards, >> >> Jeremy Tregunna >> >> >> >> _______________________________________________ >> freebsd-isp@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-isp >> To unsubscribe, send any mail to "freebsd-isp-=20 >> unsubscribe@freebsd.org" >> > > > --=20 > Dominic Blais > Administrateur r=E9seau > Interplex T=E9l=E9com Inc. > http://www.interplex.ca > > > > !DSPAM:4589a963678325368818224! > From owner-freebsd-isp@FreeBSD.ORG Thu Dec 21 11:42:39 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A100516A510 for ; Thu, 21 Dec 2006 11:42:39 +0000 (UTC) (envelope-from jtregunna@blurgle.ca) Received: from picard.blurgle.ca (picard.blurgle.ca [64.187.9.69]) by mx1.freebsd.org (Postfix) with ESMTP id 57BFB13C45F for ; Thu, 21 Dec 2006 11:42:39 +0000 (UTC) (envelope-from jtregunna@blurgle.ca) Received: from [10.0.1.50] (locutus.blurgle.ca [66.38.165.231]) (authenticated bits=0) by picard.blurgle.ca (8.13.8/8.13.8) with ESMTP id kBKMmLhE069667 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Wed, 20 Dec 2006 17:48:21 -0500 (EST) (envelope-from jtregunna@blurgle.ca) In-Reply-To: <56245.24.122.21.214.1166649785.squirrel@secure.interplex.ca> References: <2004672F-664F-4331-A09F-D09A0C9DD99E@blurgle.ca> <56245.24.122.21.214.1166649785.squirrel@secure.interplex.ca> Mime-Version: 1.0 (Apple Message framework v752.3) X-Priority: 3 (Normal) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <6FA799B6-ED28-47A5-9A45-E90C86280A65@blurgle.ca> Content-Transfer-Encoding: quoted-printable From: Jeremy Tregunna Date: Wed, 20 Dec 2006 17:49:38 -0500 To: dblais@interplex.ca X-Mailer: Apple Mail (2.752.3) Cc: freebsd-isp@freebsd.org Subject: Re: RADIUS/PPPoE Dead Connections X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Dec 2006 11:42:39 -0000 On 20-Dec-06, at 4:23 PM, Dominic Blais wrote: > Try mpd instead of ppp, great performances... we're using it as a =20 > pppoe > concentrator for more than 100 simultaneous connections.. That's fine and dandy, but I've already got this box deployed, and I =20 don't like making major changes mid-stream. Unless I can guarantee =20 that mpd won't suffer this same issue, I'm not interested in even =20 considering changing, I'm more interested in fixing my problem. Regards; Jeremy Tregunna > > See /usr/ports/net/mpd > > mpd4 is beta, don't try it for production. > > > >> >> I've got a FreeBSD NAS and a FreeBSD RADIUS server (both running 6.1) >> serving up access to a wireless network. In any event, everything >> seems to work peachy when a user logs in and disconnects manually. >> But if for instance, someone closes the lid on their laptop and their >> wireless card powers off due to standby mode, the connection to the >> NAS is broken and the disconnect request never makes it from the NAS >> to the RADIUS server to inform it that the client went offline. >> >> Now then, I'm not so much worried about that stale entry staying on >> the RADIUS server until the user tries to log in again (I don't care >> much about time used, only bandwidth numbers); but ultimately it >> would be nice to have one of two solutions: >> >> (1) A user tries to log in when he's already logged in, have it >> disconnect that user and then log in; or >> (2) Have the NAS send a Disconnect-Request to the RADIUS server =20 >> when-- >> as in the above example--someone closes the lid on their laptop. >> >> An idle timeout isn't a workable solution for me, neither is a >> session timeout; I need both to have no fixed limit for all clients. >> >> My ppp.conf file is basically defined as: >> >> ### ppp.conf begin >> >> default: >> set log Chat Command Phase >> enable pap >> allow mode direct >> enable proxy >> disable ipv6cp >> set radius /etc/radius.conf >> set mru 1492 >> set mtu 1492 >> accept dns >> >> ### end ppp.conf >> >> The relevant users portion is like: >> >> DEFAULT Auth-Type :=3D System >> Service-Type :=3D Framed-User, >> Framed-Protocol :=3D PPP, >> Framed-IP-Address :=3D 192.168.8.50, >> Framed-IP-Netmask :=3D 255.255.255.0, >> Framed-Routing :=3D Broadcast-Listen, >> Framed-MTU :=3D 1492 >> >> And the relevant portions of attrs is like: >> >> DEFAULT >> Service-Type =3D=3D Framed-User, >> Framed-Protocol =3D=3D PPP, >> Framed-MTU =3D=3D 1492, >> Framed-Filter-ID =3D* ANY, >> Reply-Message =3D* ANY, >> Session-Timeout =3D=3D 0, >> Idle-Timeout =3D=3D 0, >> Port-Limit <=3D 2 >> >> Any assistance would be greatly appreciated. >> >> Regards, >> >> Jeremy Tregunna >> >> >> >> _______________________________________________ >> freebsd-isp@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-isp >> To unsubscribe, send any mail to "freebsd-isp-=20 >> unsubscribe@freebsd.org" >> > > > --=20 > Dominic Blais > Administrateur r=E9seau > Interplex T=E9l=E9com Inc. > http://www.interplex.ca > > > > !DSPAM:4589a963678325368818224! > From owner-freebsd-isp@FreeBSD.ORG Thu Dec 21 11:54:22 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EC64616A47E for ; Thu, 21 Dec 2006 11:54:22 +0000 (UTC) (envelope-from dblais@interplex.ca) Received: from smtp1.interplex.ca (smtp1.interplex.ca [207.134.105.5]) by mx1.freebsd.org (Postfix) with ESMTP id 9DBBD13C46D for ; Thu, 21 Dec 2006 11:54:22 +0000 (UTC) (envelope-from dblais@interplex.ca) Received: by smtp1.interplex.ca (Postfix, from userid 106) id 801152ACCC; Wed, 20 Dec 2006 18:17:11 -0500 (EST) Received: from secure.interplex.ca (webapps.interplex.ca [207.134.105.8]) by smtp1.interplex.ca (Postfix) with ESMTP id 400B42ACB4; Wed, 20 Dec 2006 18:17:11 -0500 (EST) Received: from 24.122.21.214 (SquirrelMail authenticated user dblais) by secure.interplex.ca with HTTP; Wed, 20 Dec 2006 18:17:11 -0500 (EST) Message-ID: <37692.24.122.21.214.1166656631.squirrel@secure.interplex.ca> In-Reply-To: <6FA799B6-ED28-47A5-9A45-E90C86280A65@blurgle.ca> References: <2004672F-664F-4331-A09F-D09A0C9DD99E@blurgle.ca> <56245.24.122.21.214.1166649785.squirrel@secure.interplex.ca> <6FA799B6-ED28-47A5-9A45-E90C86280A65@blurgle.ca> Date: Wed, 20 Dec 2006 18:17:11 -0500 (EST) From: "Dominic Blais" To: "Jeremy Tregunna" User-Agent: SquirrelMail/1.4.8 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-isp@freebsd.org, dblais@interplex.ca Subject: Re: RADIUS/PPPoE Dead Connections X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dblais@interplex.ca List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Dec 2006 11:54:23 -0000 If your radius server has an sql backend, change the sql request so that it accepts the person if it's the same mac address as the last person that was connected with the same account. This is a good behaviour to avoid problems but you should keep on finding your solution... this is just a workaround.. > > On 20-Dec-06, at 4:23 PM, Dominic Blais wrote: > >> Try mpd instead of ppp, great performances... we're using it as a >> pppoe >> concentrator for more than 100 simultaneous connections.. > > That's fine and dandy, but I've already got this box deployed, and I > don't like making major changes mid-stream. Unless I can guarantee > that mpd won't suffer this same issue, I'm not interested in even > considering changing, I'm more interested in fixing my problem. > > Regards; > > Jeremy Tregunna > >> >> See /usr/ports/net/mpd >> >> mpd4 is beta, don't try it for production. >> >> >> >>> >>> I've got a FreeBSD NAS and a FreeBSD RADIUS server (both running 6.1) >>> serving up access to a wireless network. In any event, everything >>> seems to work peachy when a user logs in and disconnects manually. >>> But if for instance, someone closes the lid on their laptop and their >>> wireless card powers off due to standby mode, the connection to the >>> NAS is broken and the disconnect request never makes it from the NAS >>> to the RADIUS server to inform it that the client went offline. >>> >>> Now then, I'm not so much worried about that stale entry staying on >>> the RADIUS server until the user tries to log in again (I don't care >>> much about time used, only bandwidth numbers); but ultimately it >>> would be nice to have one of two solutions: >>> >>> (1) A user tries to log in when he's already logged in, have it >>> disconnect that user and then log in; or >>> (2) Have the NAS send a Disconnect-Request to the RADIUS server >>> when-- >>> as in the above example--someone closes the lid on their laptop. >>> >>> An idle timeout isn't a workable solution for me, neither is a >>> session timeout; I need both to have no fixed limit for all clients. >>> >>> My ppp.conf file is basically defined as: >>> >>> ### ppp.conf begin >>> >>> default: >>> set log Chat Command Phase >>> enable pap >>> allow mode direct >>> enable proxy >>> disable ipv6cp >>> set radius /etc/radius.conf >>> set mru 1492 >>> set mtu 1492 >>> accept dns >>> >>> ### end ppp.conf >>> >>> The relevant users portion is like: >>> >>> DEFAULT Auth-Type := System >>> Service-Type := Framed-User, >>> Framed-Protocol := PPP, >>> Framed-IP-Address := 192.168.8.50, >>> Framed-IP-Netmask := 255.255.255.0, >>> Framed-Routing := Broadcast-Listen, >>> Framed-MTU := 1492 >>> >>> And the relevant portions of attrs is like: >>> >>> DEFAULT >>> Service-Type == Framed-User, >>> Framed-Protocol == PPP, >>> Framed-MTU == 1492, >>> Framed-Filter-ID =* ANY, >>> Reply-Message =* ANY, >>> Session-Timeout == 0, >>> Idle-Timeout == 0, >>> Port-Limit <= 2 >>> >>> Any assistance would be greatly appreciated. >>> >>> Regards, >>> >>> Jeremy Tregunna >>> >>> >>> >>> _______________________________________________ >>> freebsd-isp@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-isp >>> To unsubscribe, send any mail to "freebsd-isp- >>> unsubscribe@freebsd.org" >>> >> >> >> -- >> Dominic Blais >> Administrateur réseau >> Interplex Télécom Inc. >> http://www.interplex.ca >> >> >> >> !DSPAM:4589a963678325368818224! >> > > -- Dominic Blais Administrateur réseau Interplex Télécom Inc. http://www.interplex.ca From owner-freebsd-isp@FreeBSD.ORG Thu Dec 21 13:01:13 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2E10416A417 for ; Thu, 21 Dec 2006 13:01:13 +0000 (UTC) (envelope-from dblais@interplex.ca) Received: from smtp1.interplex.ca (smtp1.interplex.ca [207.134.105.5]) by mx1.freebsd.org (Postfix) with ESMTP id 96D4913C468 for ; Thu, 21 Dec 2006 13:01:12 +0000 (UTC) (envelope-from dblais@interplex.ca) Received: by smtp1.interplex.ca (Postfix, from userid 106) id 033A22AD87; Wed, 20 Dec 2006 16:23:05 -0500 (EST) Received: from secure.interplex.ca (webapps.interplex.ca [207.134.105.8]) by smtp1.interplex.ca (Postfix) with ESMTP id AFCB12AD49; Wed, 20 Dec 2006 16:23:05 -0500 (EST) Received: from 24.122.21.214 (SquirrelMail authenticated user dblais) by secure.interplex.ca with HTTP; Wed, 20 Dec 2006 16:23:05 -0500 (EST) Message-ID: <56245.24.122.21.214.1166649785.squirrel@secure.interplex.ca> In-Reply-To: <2004672F-664F-4331-A09F-D09A0C9DD99E@blurgle.ca> References: <2004672F-664F-4331-A09F-D09A0C9DD99E@blurgle.ca> Date: Wed, 20 Dec 2006 16:23:05 -0500 (EST) From: "Dominic Blais" To: "Jeremy Tregunna" User-Agent: SquirrelMail/1.4.8 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-isp@freebsd.org Subject: Re: RADIUS/PPPoE Dead Connections X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dblais@interplex.ca List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Dec 2006 13:01:13 -0000 Try mpd instead of ppp, great performances... we're using it as a pppoe concentrator for more than 100 simultaneous connections.. See /usr/ports/net/mpd mpd4 is beta, don't try it for production. > > I've got a FreeBSD NAS and a FreeBSD RADIUS server (both running 6.1) > serving up access to a wireless network. In any event, everything > seems to work peachy when a user logs in and disconnects manually. > But if for instance, someone closes the lid on their laptop and their > wireless card powers off due to standby mode, the connection to the > NAS is broken and the disconnect request never makes it from the NAS > to the RADIUS server to inform it that the client went offline. > > Now then, I'm not so much worried about that stale entry staying on > the RADIUS server until the user tries to log in again (I don't care > much about time used, only bandwidth numbers); but ultimately it > would be nice to have one of two solutions: > > (1) A user tries to log in when he's already logged in, have it > disconnect that user and then log in; or > (2) Have the NAS send a Disconnect-Request to the RADIUS server when-- > as in the above example--someone closes the lid on their laptop. > > An idle timeout isn't a workable solution for me, neither is a > session timeout; I need both to have no fixed limit for all clients. > > My ppp.conf file is basically defined as: > > ### ppp.conf begin > > default: > set log Chat Command Phase > enable pap > allow mode direct > enable proxy > disable ipv6cp > set radius /etc/radius.conf > set mru 1492 > set mtu 1492 > accept dns > > ### end ppp.conf > > The relevant users portion is like: > > DEFAULT Auth-Type := System > Service-Type := Framed-User, > Framed-Protocol := PPP, > Framed-IP-Address := 192.168.8.50, > Framed-IP-Netmask := 255.255.255.0, > Framed-Routing := Broadcast-Listen, > Framed-MTU := 1492 > > And the relevant portions of attrs is like: > > DEFAULT > Service-Type == Framed-User, > Framed-Protocol == PPP, > Framed-MTU == 1492, > Framed-Filter-ID =* ANY, > Reply-Message =* ANY, > Session-Timeout == 0, > Idle-Timeout == 0, > Port-Limit <= 2 > > Any assistance would be greatly appreciated. > > Regards, > > Jeremy Tregunna > > > > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" > -- Dominic Blais Administrateur réseau Interplex Télécom Inc. http://www.interplex.ca From owner-freebsd-isp@FreeBSD.ORG Thu Dec 21 13:03:18 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ECE7616A57E for ; Thu, 21 Dec 2006 13:03:18 +0000 (UTC) (envelope-from nikola@vlaeonline.com) Received: from munem.it-box.org (munem.it-box.org [67.159.30.92]) by mx1.freebsd.org (Postfix) with ESMTP id BD5F313C68A for ; Thu, 21 Dec 2006 13:02:58 +0000 (UTC) (envelope-from nikola@vlaeonline.com) Received: from Nikola (unknown [85.30.84.134]) by munem.it-box.org (Postfix) with ESMTP id 0C65D1B24064 for ; Wed, 20 Dec 2006 16:21:51 -0500 (EST) Message-ID: <001a01c7247c$dfd6a800$02170a0a@Nikola> From: "Nikola Stojanoski" To: References: <2004672F-664F-4331-A09F-D09A0C9DD99E@blurgle.ca> Date: Wed, 20 Dec 2006 22:21:46 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Subject: Re: RADIUS/PPPoE Dead Connections X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Dec 2006 13:03:19 -0000 Hello, add this lines in your ppp.conf and it should be okay for more informations man ppp enable echo set echoperiod 5 enable lqr set lqrperiod 10 Regards ----- Original Message ----- From: "Jeremy Tregunna" To: Sent: Wednesday, December 20, 2006 4:14 PM Subject: RADIUS/PPPoE Dead Connections > > I've got a FreeBSD NAS and a FreeBSD RADIUS server (both running 6.1) > serving up access to a wireless network. In any event, everything seems > to work peachy when a user logs in and disconnects manually. But if for > instance, someone closes the lid on their laptop and their wireless card > powers off due to standby mode, the connection to the NAS is broken and > the disconnect request never makes it from the NAS to the RADIUS server > to inform it that the client went offline. > > Now then, I'm not so much worried about that stale entry staying on the > RADIUS server until the user tries to log in again (I don't care much > about time used, only bandwidth numbers); but ultimately it would be nice > to have one of two solutions: > > (1) A user tries to log in when he's already logged in, have it > disconnect that user and then log in; or > (2) Have the NAS send a Disconnect-Request to the RADIUS server when-- > as in the above example--someone closes the lid on their laptop. > > An idle timeout isn't a workable solution for me, neither is a session > timeout; I need both to have no fixed limit for all clients. > > My ppp.conf file is basically defined as: > > ### ppp.conf begin > > default: > set log Chat Command Phase > enable pap > allow mode direct > enable proxy > disable ipv6cp > set radius /etc/radius.conf > set mru 1492 > set mtu 1492 > accept dns > > ### end ppp.conf > > The relevant users portion is like: > > DEFAULT Auth-Type := System > Service-Type := Framed-User, > Framed-Protocol := PPP, > Framed-IP-Address := 192.168.8.50, > Framed-IP-Netmask := 255.255.255.0, > Framed-Routing := Broadcast-Listen, > Framed-MTU := 1492 > > And the relevant portions of attrs is like: > > DEFAULT > Service-Type == Framed-User, > Framed-Protocol == PPP, > Framed-MTU == 1492, > Framed-Filter-ID =* ANY, > Reply-Message =* ANY, > Session-Timeout == 0, > Idle-Timeout == 0, > Port-Limit <= 2 > > Any assistance would be greatly appreciated. > > Regards, > > Jeremy Tregunna > > > > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" From owner-freebsd-isp@FreeBSD.ORG Thu Dec 21 13:33:50 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A12BE16A40F for ; Thu, 21 Dec 2006 13:33:50 +0000 (UTC) (envelope-from technical@halenet.com.au) Received: from helen.halenet.com.au (helen.halenet.com.au [203.55.33.243]) by mx1.freebsd.org (Postfix) with ESMTP id 1FC0B13C45B for ; Thu, 21 Dec 2006 13:33:50 +0000 (UTC) (envelope-from technical@halenet.com.au) Received: from localhost (localhost.halenet.com.au [127.0.0.1]) by helen.halenet.com.au (Postfix) with ESMTP id 0AF5011496 for ; Thu, 21 Dec 2006 08:13:39 +1000 (EST) X-Virus-Scanned: amavisd-new at halenet.com.au Received: from helen.halenet.com.au ([127.0.0.1]) by localhost (helen.halenet.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2t+QE6uEIYP9 for ; Thu, 21 Dec 2006 08:13:38 +1000 (EST) Received: from laptopt (gw1.halenet.com.au [203.55.33.225]) by helen.halenet.com.au (Postfix) with SMTP id 7BE6D11495 for ; Thu, 21 Dec 2006 08:13:38 +1000 (EST) Message-ID: <007c01c72484$0b2b0440$6500a8c0@laptopt> From: "Lists" To: References: <2004672F-664F-4331-A09F-D09A0C9DD99E@blurgle.ca> Date: Thu, 21 Dec 2006 08:13:13 +1000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Subject: Re: RADIUS/PPPoE Dead Connections X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Dec 2006 13:33:50 -0000 Hi Jeremy You may want to try adding enable echo enable lqr echo set lqrperiod 15 to your ppp.conf man ppp may also help This will close the ppp session if the customer connection drops and radius should then send the accounting data You should be getting your accounting data regardless, when the session expires. You will need to provide more info as to how you have your radius setup if that doesnt work Regards Tim ----- Original Message ----- From: "Jeremy Tregunna" To: Sent: Thursday, December 21, 2006 1:14 AM Subject: RADIUS/PPPoE Dead Connections > > I've got a FreeBSD NAS and a FreeBSD RADIUS server (both running 6.1) > serving up access to a wireless network. In any event, everything seems > to work peachy when a user logs in and disconnects manually. But if for > instance, someone closes the lid on their laptop and their wireless card > powers off due to standby mode, the connection to the NAS is broken and > the disconnect request never makes it from the NAS to the RADIUS server > to inform it that the client went offline. > > Now then, I'm not so much worried about that stale entry staying on the > RADIUS server until the user tries to log in again (I don't care much > about time used, only bandwidth numbers); but ultimately it would be nice > to have one of two solutions: > > (1) A user tries to log in when he's already logged in, have it > disconnect that user and then log in; or > (2) Have the NAS send a Disconnect-Request to the RADIUS server when-- > as in the above example--someone closes the lid on their laptop. > > An idle timeout isn't a workable solution for me, neither is a session > timeout; I need both to have no fixed limit for all clients. > > My ppp.conf file is basically defined as: > > ### ppp.conf begin > > default: > set log Chat Command Phase > enable pap > allow mode direct > enable proxy > disable ipv6cp > set radius /etc/radius.conf > set mru 1492 > set mtu 1492 > accept dns > > ### end ppp.conf > > The relevant users portion is like: > > DEFAULT Auth-Type := System > Service-Type := Framed-User, > Framed-Protocol := PPP, > Framed-IP-Address := 192.168.8.50, > Framed-IP-Netmask := 255.255.255.0, > Framed-Routing := Broadcast-Listen, > Framed-MTU := 1492 > > And the relevant portions of attrs is like: > > DEFAULT > Service-Type == Framed-User, > Framed-Protocol == PPP, > Framed-MTU == 1492, > Framed-Filter-ID =* ANY, > Reply-Message =* ANY, > Session-Timeout == 0, > Idle-Timeout == 0, > Port-Limit <= 2 > > Any assistance would be greatly appreciated. > > Regards, > > Jeremy Tregunna > > > > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" > From owner-freebsd-isp@FreeBSD.ORG Thu Dec 21 16:24:20 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8E20816A412 for ; Thu, 21 Dec 2006 16:24:20 +0000 (UTC) (envelope-from troy@psknet.com) Received: from psknet.com (dns1.psknet.com [12.196.144.2]) by mx1.freebsd.org (Postfix) with ESMTP id 5013813C459 for ; Thu, 21 Dec 2006 16:24:20 +0000 (UTC) (envelope-from troy@psknet.com) Received: from pool-72-66-165-40.ronkva.east.verizon.net ([72.66.165.40] helo=[192.168.0.2]) by psknet.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GxQ6v-0007LE-Em; Thu, 21 Dec 2006 10:45:34 -0500 Message-ID: <458AAC19.3030404@psknet.com> Date: Thu, 21 Dec 2006 10:45:29 -0500 From: Troy Settle User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Jeremy Tregunna References: <2004672F-664F-4331-A09F-D09A0C9DD99E@blurgle.ca> <56245.24.122.21.214.1166649785.squirrel@secure.interplex.ca> <6FA799B6-ED28-47A5-9A45-E90C86280A65@blurgle.ca> <37692.24.122.21.214.1166656631.squirrel@secure.interplex.ca> In-Reply-To: <37692.24.122.21.214.1166656631.squirrel@secure.interplex.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scan: Clear (ClamAV 0.88.6/2366/Thu Dec 21 08:56:02 2006) Cc: freebsd-isp@freebsd.org Subject: Re: RADIUS/PPPoE Dead Connections X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Dec 2006 16:24:20 -0000 Jeremy, I have the same problem with Mikrotik's implementation of pppoe on RouterOS. For whatever reason, I miss more STOP records than I receive. I overcame this by having the MT box send update records every 5 minutes, and since all my accounting data is written to SQL in real time, I can use a view to see who's online. With a little logic, I was able to weed out the stale sessions by excluding records that hadn't been updated within the last 10 minutes. I then use this view to figure out if a user is connected or not for concurrency control. Worst case for me, is that I lose a few minutes of bandwidth data. Worst case for my users, is that they can't log back in for up to 10 minutes. Haven't had any complaints yet. I wish I had some the time and skill to dig into the code for PPP to ensure that a stop record gets sent no matter what. I was going to blame this on the UDP packet getting lost, but after 10 years of using radius, I'm fairly confident that it's the implementation, not the protocol that's to blame for this. -- Troy Settle Pulaski Networks http://www.psknet.com 866.477.5638 Dominic Blais wrote: > If your radius server has an sql backend, change the sql request so that > it accepts the person if it's the same mac address as the last person that > was connected with the same account. This is a good behaviour to avoid > problems but you should keep on finding your solution... this is just a > workaround.. > > > > >> On 20-Dec-06, at 4:23 PM, Dominic Blais wrote: >> >> >>> Try mpd instead of ppp, great performances... we're using it as a >>> pppoe >>> concentrator for more than 100 simultaneous connections.. >>> >> That's fine and dandy, but I've already got this box deployed, and I >> don't like making major changes mid-stream. Unless I can guarantee >> that mpd won't suffer this same issue, I'm not interested in even >> considering changing, I'm more interested in fixing my problem. >> >> Regards; >> >> Jeremy Tregunna >> >> >>> See /usr/ports/net/mpd >>> >>> mpd4 is beta, don't try it for production. >>> >>> >>> >>> >>>> I've got a FreeBSD NAS and a FreeBSD RADIUS server (both running 6.1) >>>> serving up access to a wireless network. In any event, everything >>>> seems to work peachy when a user logs in and disconnects manually. >>>> But if for instance, someone closes the lid on their laptop and their >>>> wireless card powers off due to standby mode, the connection to the >>>> NAS is broken and the disconnect request never makes it from the NAS >>>> to the RADIUS server to inform it that the client went offline. >>>> >>>> Now then, I'm not so much worried about that stale entry staying on >>>> the RADIUS server until the user tries to log in again (I don't care >>>> much about time used, only bandwidth numbers); but ultimately it >>>> would be nice to have one of two solutions: >>>> >>>> (1) A user tries to log in when he's already logged in, have it >>>> disconnect that user and then log in; or >>>> (2) Have the NAS send a Disconnect-Request to the RADIUS server >>>> when-- >>>> as in the above example--someone closes the lid on their laptop. >>>> >>>> An idle timeout isn't a workable solution for me, neither is a >>>> session timeout; I need both to have no fixed limit for all clients. >>>> >>>> My ppp.conf file is basically defined as: >>>> >>>> ### ppp.conf begin >>>> >>>> default: >>>> set log Chat Command Phase >>>> enable pap >>>> allow mode direct >>>> enable proxy >>>> disable ipv6cp >>>> set radius /etc/radius.conf >>>> set mru 1492 >>>> set mtu 1492 >>>> accept dns >>>> >>>> ### end ppp.conf >>>> >>>> The relevant users portion is like: >>>> >>>> DEFAULT Auth-Type := System >>>> Service-Type := Framed-User, >>>> Framed-Protocol := PPP, >>>> Framed-IP-Address := 192.168.8.50, >>>> Framed-IP-Netmask := 255.255.255.0, >>>> Framed-Routing := Broadcast-Listen, >>>> Framed-MTU := 1492 >>>> >>>> And the relevant portions of attrs is like: >>>> >>>> DEFAULT >>>> Service-Type == Framed-User, >>>> Framed-Protocol == PPP, >>>> Framed-MTU == 1492, >>>> Framed-Filter-ID =* ANY, >>>> Reply-Message =* ANY, >>>> Session-Timeout == 0, >>>> Idle-Timeout == 0, >>>> Port-Limit <= 2 >>>> >>>> Any assistance would be greatly appreciated. >>>> >>>> Regards, >>>> >>>> Jeremy Tregunna >>>> >>>> >>>> >>>> _______________________________________________ >>>> freebsd-isp@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-isp >>>> To unsubscribe, send any mail to "freebsd-isp- >>>> unsubscribe@freebsd.org" >>>> >>>> >>> -- >>> Dominic Blais >>> Administrateur réseau >>> Interplex Télécom Inc. >>> http://www.interplex.ca >>> >>> >>> >>> !DSPAM:4589a963678325368818224! >>> >>> >> > > >