From owner-freebsd-isp@FreeBSD.ORG Sun Apr 26 00:09:31 2009 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8CB75106564A for ; Sun, 26 Apr 2009 00:09:31 +0000 (UTC) (envelope-from martes@mgwigglesworth.com) Received: from mail.mgwigglesworth.com (mail.mgwigglesworth.net [75.146.26.81]) by mx1.freebsd.org (Postfix) with ESMTP id 484068FC15 for ; Sun, 26 Apr 2009 00:09:31 +0000 (UTC) (envelope-from martes@mgwigglesworth.com) To: Steve Bertrand Date: Sat, 25 Apr 2009 20:09:15 -0400 References: <1240615371.6029.34.camel@localhost> <20090425022227.GB79909@in-addr.com> <0000054941@mail.mgwigglesworth.com> <20090425201650.GC79909@in-addr.com> <49F3737D.9030704@ibctech.ca> Message-ID: <0000055048@mail.mgwigglesworth.com> From: "martes" Organization: MGW Networks MIME-Version: 1.0 X-Mailer: WebCit 7.37 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-isp@freebsd.org, martes Subject: Re: Spamassassin anyone??? 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, 26 Apr 2009 00:09:31 -0000 >Sat Apr 25 2009 16:33:01 EDT from Steve Bertrand to Gary Palmer =20 >Subject: Re: Spamassassin anyone??? > >Gary Palmer wrote: > >>> On Sat, Apr 25, 2009 at 01:59:48PM -0400, martes wrote: >>>> Sorry if this seems like a blinded assumption, however, whenever som= eone >>asks >>>> about the origin of explicit spam, such as the anti-semetic stuff th= at >>was >>>> posting to the list from an obviously mangled header source, someone= >>always >>>> brings up that the lists are not proctared, as if there is not any >>management >>>> at all, and such obvious garbage is just going to post due to lack o= f >>>> supervision, or spam protocals... >>> >>> 1) Please do not top post >>> >>> 2) There are only two known methods for dropping 100% of spam >>> >>> 2a) Have a human sit and read every single e-mail and make a judgemen= t >>> call that only a human can do as to the messages legitimacy. I a= m >>> not aware of any organization anywhere in the world that has >>> managed to get that system to scale to any volume. >>> >>> 2b) Turn off your SMTP server >>> >>> The lists are not *moderated*, other than the -announce lists and >>> freebsd-security-notifications. Most of the lists are open to >>> all posters and not just list members as not everyone who wants >>> to be involved in the project or who uses FreeBSD in some capacity >>> subscribes to the lists. The exception to that is freebsd-security. >>> >>> However do not take the lack of enforcement at the mailing list >>> level as there being no anti-spam measures. There are a variety >>> of A/S measures in place that protect not only the mailing list >>> servers but all freebsd.org e-mail addresses. >>> >>> If you, or anyone else, feels that they could contribute to the defea= t >>> of spam on the FreeBSD lists (e.g. by being an active moderator with >>> a long-term commitment to minimising delays in posting caused by >>> the moderation system) then please feel free to offer your services >>> to the postmaster team. >> > >Amen to every single point in every single one of your comments. > >I'm sure that you will provide an update with those who respond to your >request, that have both operational qualifications, and the time to >spare, within the coming days... :) > >Steve > >ps. apologies for the sarcasm, but this is an ISP list for ISP >operations people (so I thought). Perhaps the FBSD mail spam system has >a ``qualified admit'' rule or something that they could apply. > >Cheers Gary, keep up the great work. > >I simply wanted to know why every time that a bunch of racist non-sense >comes through the list multiple times every month or so, all everyone ev= er >says is that there is no moderation on the list, almost like there is an= >assumption that there is nothing being done at all. >You guys can personally attack all you want, but I simply wanted to know= >why there seemed to be nothing done about this type of thing. All I ha= ve >ever seen is indications that there is nothing to be done because it is=20= a >free, non-moderated list. No one ever responds with something like this=20= until >there is some intent to put someone in their place, evidently.... =20 >It is quite frustrating actualy. But hey, I have my answer now. =20 >You guys can think what you want to about my qulifications. =20 >I am sure not many of you have had to restore datacenter services while >being shot at, or mortars coming in overhead, etc... So I am sure not >much would impress me either.... >Have a good day.=20 > From owner-freebsd-isp@FreeBSD.ORG Tue Apr 28 19:32:21 2009 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96DC11065745 for ; Tue, 28 Apr 2009 19:32:21 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from flat.berklix.org (flat.berklix.org [83.236.223.115]) by mx1.freebsd.org (Postfix) with ESMTP id 8E9458FC31 for ; Tue, 28 Apr 2009 19:32:20 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A601C.dip.t-dialin.net [84.154.96.28]) (authenticated bits=0) by flat.berklix.org (8.13.8/8.13.8) with ESMTP id n3SJKI2G001028 for ; Tue, 28 Apr 2009 21:20:20 +0200 (CEST) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.8/8.13.8) with ESMTP id n3SJK21d014451 for ; Tue, 28 Apr 2009 21:20:02 +0200 (CEST) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.3/8.14.3) with ESMTP id n3SJK64A023431 for ; Tue, 28 Apr 2009 21:20:11 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200904281920.n3SJK64A023431@fire.js.berklix.net> To: freebsd-isp@freebsd.org From: "Julian Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://berklix.com In-reply-to: Your message "Sat, 25 Apr 2009 16:16:50 EDT." <20090425201650.GC79909@in-addr.com> Date: Tue, 28 Apr 2009 21:20:06 +0200 Sender: jhs@berklix.org Subject: Re: Spamassassin anyone??? 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, 28 Apr 2009 19:32:22 -0000 > If you, or anyone else, feels that they could contribute to the defeat > of spam on the FreeBSD lists (e.g. by being an active moderator with > a long-term commitment to minimising delays in posting caused by > the moderation system) then please feel free to offer your services > to the postmaster team. My 2c: Bad idea: Moderators. Romans knew long before us: "Quis custodes custodiensis?" But others with 2c like moderators, sadly. Moderation is a tedious bike shed argument, comes up on loads of FreeBSD lists periodically, for one compromise idea (just moderate the unsusbscribed), see suggestion found by google from: Rich Kulawiec to hardware list recently: http://groups.google.com/group/muc.lists.freebsd.hardware/browse_thread/thread/c698d9cd3ca2bd9e/f74bcf1e3e95bdd9?lnk=raot However probably all would agree: Volunteer to help postmaster@freebsd.org team on automatic tools if you have skill & time. Cheers, Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com Mail plain ASCII text. HTML & Base64 text are spam. www.asciiribbon.org From owner-freebsd-isp@FreeBSD.ORG Tue Apr 28 20:40:24 2009 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E73F1065678 for ; Tue, 28 Apr 2009 20:40:24 +0000 (UTC) (envelope-from tibor@tibor.org) Received: from alpha.tibor.org (66-230-99-2.static.acsalaska.net [66.230.99.2]) by mx1.freebsd.org (Postfix) with ESMTP id D11F58FC0A for ; Tue, 28 Apr 2009 20:40:23 +0000 (UTC) (envelope-from tibor@tibor.org) Received: from localhost (localhost [127.0.0.1]) by alpha.tibor.org (8.14.2/8.13.8) with ESMTP id n3SKGEoh093506 for ; Tue, 28 Apr 2009 12:16:14 -0800 (AKDT) (envelope-from tibor@tibor.org) Date: Tue, 28 Apr 2009 12:16:14 -0800 (AKDT) From: Mike Tibor To: freebsd-isp@freebsd.org In-Reply-To: <200904281920.n3SJK64A023431@fire.js.berklix.net> Message-ID: <20090428121050.F91785@alpha.tibor.org> References: <200904281920.n3SJK64A023431@fire.js.berklix.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (alpha.tibor.org [127.0.0.1]); Tue, 28 Apr 2009 12:16:14 -0800 (AKDT) Subject: Re: Spamassassin anyone??? 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, 28 Apr 2009 20:40:24 -0000 On Tue, 28 Apr 2009, Julian Stacey wrote: > My 2c: Bad idea: Moderators. > Romans knew long before us: "Quis custodes custodiensis?" > But others with 2c like moderators, sadly. > > Moderation is a tedious bike shed argument, comes up on loads of > FreeBSD lists periodically, for one compromise idea (just moderate > the unsusbscribed), see suggestion found by google from: Rich > Kulawiec to hardware list recently: > http://groups.google.com/group/muc.lists.freebsd.hardware/browse_thread/thread/c698d9cd3ca2bd9e/f74bcf1e3e95bdd9?lnk=raot > > However probably all would agree: > Volunteer to help postmaster@freebsd.org team on automatic tools > if you have skill & time. I can certainly see why moderation wouldn't be practical, but I've always been curious why the -isp list has had an open posting policy. You would think that those using FreeBSD in an ISP environment wouldn't be put off by having to subscribe to the list in order to post a question, but maybe that's a bad assumption. Obviously you wouldn't want that for many of the other lists, but for more specialized lists like this one, I'm genuinely curious why they're open. Mike From owner-freebsd-isp@FreeBSD.ORG Tue Apr 28 21:33:22 2009 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA0FE106566B for ; Tue, 28 Apr 2009 21:33:22 +0000 (UTC) (envelope-from martes@mgwigglesworth.net) Received: from mail.mgwigglesworth.com (mail.mgwigglesworth.net [75.146.26.81]) by mx1.freebsd.org (Postfix) with ESMTP id 6894F8FC13 for ; Tue, 28 Apr 2009 21:33:19 +0000 (UTC) (envelope-from martes@mgwigglesworth.net) To: freebsd-isp@freebsd.org Date: Tue, 28 Apr 2009 17:02:19 -0400 Envelope-To: freebsd-isp@freebsd.org Message-ID: <200904281702.19301.martes@mgwigglesworth.net> From: "Martes G Wigglesworth" Received: from localhost.localnet (192.168.5.12 [192.168.5.12]) by mail.mgwigglesworth.com; Tue, 28 Apr 2009 17:02:30 -0400 Organization: M.G. Wigglesworth Holdings, LLC User-Agent: KMail/1.10.3 (Linux/2.6.27.19-desktop586-1mnb; KDE/4.1.3; i686; ; ) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Temporary Routing/Switching backup with Backplane and multiple switch cards... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: martes@mgwigglesworth.net List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Apr 2009 21:33:23 -0000 I was wondering if anyone else has attempted to compliment their routing devices or switching devices with a back-plane and multiple switch cards or E1/T1 cards with any success? Meaning that it was worth the trouble to build. This seems a bit useless initially, however, I am doing some research into this for quick-fix disaster recovery systems in case the 3800s are down, etc... A bit home-grown, but would like to know if the design idea would be viable and not just a costly home-grown project... Maybe for a small point of present in a wireless environment which has multiple E1/T1 drops to terminate for back-haul transfer central management stations, etc... From owner-freebsd-isp@FreeBSD.ORG Tue Apr 28 22:14:25 2009 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8AB7106567B for ; Tue, 28 Apr 2009 22:14:25 +0000 (UTC) (envelope-from howie@thingy.com) Received: from mail.thingy.com (wotsit.thingy.com [212.21.100.67]) by mx1.freebsd.org (Postfix) with ESMTP id 3CE718FC18 for ; Tue, 28 Apr 2009 22:14:24 +0000 (UTC) (envelope-from howie@thingy.com) Received: (qmail 16208 invoked by uid 0); 28 Apr 2009 22:47:42 +0100 Received: from unknown (HELO Satans-Little-Helper-mkII.local) (howie@thingy.com@212.21.124.49) by wotsit3.thingy.com with AES256-SHA encrypted SMTP; 28 Apr 2009 22:47:42 +0100 Message-ID: <49F7797B.1060306@thingy.com> Date: Tue, 28 Apr 2009 22:47:39 +0100 From: Howard Jones User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: martes@mgwigglesworth.net References: <200904281702.19301.martes@mgwigglesworth.net> In-Reply-To: <200904281702.19301.martes@mgwigglesworth.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-isp@freebsd.org Subject: Re: [freebsd-isp] Temporary Routing/Switching backup with Backplane and multiple switch cards... 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, 28 Apr 2009 22:14:26 -0000 Martes G Wigglesworth wrote: > I was wondering if anyone else has attempted to compliment their routing > devices or switching devices with a back-plane and multiple switch cards or > E1/T1 cards with any success? Meaning that it was worth the trouble to build. > > This seems a bit useless initially, however, I am doing some research into > this for quick-fix disaster recovery systems in case the 3800s are down, > etc... A bit home-grown, but would like to know if the design idea would be > viable and not just a costly home-grown project... Maybe for a small point of > present in a wireless environment which has multiple E1/T1 drops to terminate > for back-haul transfer central management stations, etc... > _______________________________________________ > You mean like these? http://www.vyatta.com/ http://www.xorp.org/ http://www.freesco.org/ All are "software routers" various levels of hardware support for (e.g.) Sangoma E1/T1 cards. Plenty of people use Quagga+Linux or Quagga+FreeBSD (Quagga is the BGP/OSPF component most of these uses) for peering/transit. PC hardware will route over 100Mbit quite happily. From owner-freebsd-isp@FreeBSD.ORG Wed Apr 29 06:51:17 2009 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCCF51065670 for ; Wed, 29 Apr 2009 06:51:17 +0000 (UTC) (envelope-from ml@geoffroy.eu.org) Received: from mail-ew0-f171.google.com (mail-ew0-f171.google.com [209.85.219.171]) by mx1.freebsd.org (Postfix) with ESMTP id 5C2938FC15 for ; Wed, 29 Apr 2009 06:51:16 +0000 (UTC) (envelope-from ml@geoffroy.eu.org) Received: by ewy19 with SMTP id 19so998066ewy.43 for ; Tue, 28 Apr 2009 23:51:16 -0700 (PDT) Received: by 10.210.76.4 with SMTP id y4mr5094756eba.97.1240986509889; Tue, 28 Apr 2009 23:28:29 -0700 (PDT) Received: from tintin.sicfa.net (tintin.sicfa.net [88.191.17.5]) by mx.google.com with ESMTPS id 7sm1145170eyg.27.2009.04.28.23.28.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 28 Apr 2009 23:28:29 -0700 (PDT) Date: Wed, 29 Apr 2009 08:28:27 +0200 From: Geoffroy RIVAT To: freebsd-isp@freebsd.org Message-ID: <20090429062827.GB60404@tintin.sicfa.net> References: <49E3D793.2090008@staff.openaccess.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <49E3D793.2090008@staff.openaccess.org> User-Agent: Mutt/1.5.18 (2008-05-17) Subject: Re: providing web based DNS management to customers 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, 29 Apr 2009 06:51:18 -0000 Hi Michael, Michael DeMan (OA) wrote: > Hi All, > > What are folks doing for providing web based DNS management to customers? > > I've looked at a lot of open source products over time, but never found > one that was enough to say "Thats it, lets integrate it!". > > It always seems that the tricky part is reverse DNS. PowerDNS and other > tools (at least a few years ago) offered reasonable support for forward > DNS management on a per-user basis, but not reverse, or at least not > reverse in the sense that we only want customers to be able to modify > the reverse DNS of say a single IP, or a subnet, etc. for this I'm using powerdns + poweradmin (but you can use another system) for only 1 IP i do 1.0.168.192.in-addr.arpa IN CNAME reverse.custdomain.tld and reverse.custdomain.tld IN PTR coolreverse.domain.tld. for a subnet : 1.0.168.192.in-addr.arpa IN CNAME 1.reverse.custdomain.tld 2.0.168.192.in-addr.arpa IN CNAME 2.reverse.custdomain.tld 3.0.168.192.in-addr.arpa IN CNAME 3.reverse.custdomain.tld it's explained in an rfc but I can't remember the numbre. Regards, Geo From owner-freebsd-isp@FreeBSD.ORG Wed Apr 29 10:24:08 2009 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 955BB1065677 for ; Wed, 29 Apr 2009 10:24:08 +0000 (UTC) (envelope-from michael@staff.openaccess.org) Received: from aristotle.openaccess.org (aristotle.openaccess.org [66.114.32.142]) by mx1.freebsd.org (Postfix) with ESMTP id 544A08FC2B for ; Wed, 29 Apr 2009 10:24:08 +0000 (UTC) (envelope-from michael@staff.openaccess.org) Received: from localhost (localhost [127.0.0.1]) by aristotle.openaccess.org (Postfix) with ESMTP id 058176AD175; Wed, 29 Apr 2009 03:24:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at staff.openaccess.org Received: from aristotle.openaccess.org ([127.0.0.1]) by localhost (aristotle.openaccess.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IGckwdfw6d-W; Wed, 29 Apr 2009 03:24:07 -0700 (PDT) Received: from DeMan.local (mono-sis1.s.bli.openaccess.org [66.114.32.149]) by aristotle.openaccess.org (Postfix) with ESMTP id 8A3746AD167; Wed, 29 Apr 2009 03:24:07 -0700 (PDT) Message-ID: <49F82AC6.2070305@staff.openaccess.org> Date: Wed, 29 Apr 2009 03:24:06 -0700 From: Michael DeMan User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: freebsd-isp@freebsd.org References: <49E3D793.2090008@staff.openaccess.org> <20090429062827.GB60404@tintin.sicfa.net> In-Reply-To: <20090429062827.GB60404@tintin.sicfa.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Geoffroy RIVAT Subject: Re: providing web based DNS management to customers 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, 29 Apr 2009 10:24:09 -0000 Hi, seems close but I'm not sure if it hits the target. What I need is the ability for customers to be able to login and update entries within a zone. More specifically, the ability to allow customers to update their -in-addr.arpa reverses based on us allocating them things like /29.s I may be crusty here too, but to the best of my knowledge, it is impossible break below /24 at the 'zone' level in reverse DNS. Or at least the tools we use do not allow that. Hence the problem. Given a typical /24, which is easy to manage, I need a tool that allows customers to to have maybe a single IP that they can update to 'mail.theircompany.com', or in other cases, folks that have a /29 or bigger that want 'mail.theircompany.com', 'vpn.parentcompany.com', 'somethingelse.someotherdomain.com', etc. I guess what I am for is a kludge, to make DNS map to CIDR, but also a way that it could be done in a user friendly way. Geoffroy RIVAT wrote: > Hi Michael, > > Michael DeMan (OA) wrote: > >> Hi All, >> >> What are folks doing for providing web based DNS management to customers? >> >> I've looked at a lot of open source products over time, but never found >> one that was enough to say "Thats it, lets integrate it!". >> >> It always seems that the tricky part is reverse DNS. PowerDNS and other >> tools (at least a few years ago) offered reasonable support for forward >> DNS management on a per-user basis, but not reverse, or at least not >> reverse in the sense that we only want customers to be able to modify >> the reverse DNS of say a single IP, or a subnet, etc. >> > > for this I'm using powerdns + poweradmin (but you can use another system) > > for only 1 IP i do 1.0.168.192.in-addr.arpa IN CNAME reverse.custdomain.tld > > and reverse.custdomain.tld IN PTR coolreverse.domain.tld. > > for a subnet : > > 1.0.168.192.in-addr.arpa IN CNAME 1.reverse.custdomain.tld > 2.0.168.192.in-addr.arpa IN CNAME 2.reverse.custdomain.tld > 3.0.168.192.in-addr.arpa IN CNAME 3.reverse.custdomain.tld > > it's explained in an rfc but I can't remember the numbre. > > Regards, > > Geo > _______________________________________________ > 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 Apr 29 11:01:33 2009 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C48621065674 for ; Wed, 29 Apr 2009 11:01:33 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0AFE28FC31 for ; Wed, 29 Apr 2009 11:01:32 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from vhoffman.lon.namesco.net (150.117-84-212.staticip.namesco.net [212.84.117.150]) (authenticated bits=0) by unsane.co.uk (8.14.3/8.14.0) with ESMTP id n3TB2bA8060740 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 29 Apr 2009 12:02:39 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <49F83388.80305@unsane.co.uk> Date: Wed, 29 Apr 2009 12:01:28 +0100 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-GB; rv:1.9.1b3pre) Gecko/20081204 Thunderbird/3.0b1 MIME-Version: 1.0 To: Michael DeMan References: <49E3D793.2090008@staff.openaccess.org> <20090429062827.GB60404@tintin.sicfa.net> <49F82AC6.2070305@staff.openaccess.org> In-Reply-To: <49F82AC6.2070305@staff.openaccess.org> X-Enigmail-Version: 0.96a Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-isp@freebsd.org, Geoffroy RIVAT Subject: Re: providing web based DNS management to customers 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, 29 Apr 2009 11:01:34 -0000 On 29/4/09 11:24, Michael DeMan wrote: > Hi, seems close but I'm not sure if it hits the target. > > What I need is the ability for customers to be able to login and > update entries within a zone. More specifically, the ability to allow > customers to update their -in-addr.arpa reverses based on us > allocating them things like /29.s > > I may be crusty here too, but to the best of my knowledge, it is > impossible break below /24 at the 'zone' level in reverse DNS. Or at > least the tools we use do not allow that. > Its possible but a bit of a hack, RFC2317 shows how to do it, basicly CNAME the initial reverse record, then in the domain its pointed to by the cname setup a PTR record. It potentially could solve your problem but would take some setup time. (you have to setup the initial cname, then the customer can have control of the (sub)domain its pointed to and can change the ptr at will.) We used it a fair bit at a previous job to delegate CIDR networks < /24 to customer nameservers. Vince > Hence the problem. > > Given a typical /24, which is easy to manage, I need a tool that > allows customers to to have maybe a single IP that they can update to > 'mail.theircompany.com', or in other cases, folks that have a /29 or > bigger that want 'mail.theircompany.com', 'vpn.parentcompany.com', > 'somethingelse.someotherdomain.com', etc. > > I guess what I am for is a kludge, to make DNS map to CIDR, but also a > way that it could be done in a user friendly way. > > > > Geoffroy RIVAT wrote: >> Hi Michael, >> >> Michael DeMan (OA) wrote: >> >>> Hi All, >>> >>> What are folks doing for providing web based DNS management to >>> customers? >>> >>> I've looked at a lot of open source products over time, but never >>> found one that was enough to say "Thats it, lets integrate it!". >>> >>> It always seems that the tricky part is reverse DNS. PowerDNS and >>> other tools (at least a few years ago) offered reasonable support >>> for forward DNS management on a per-user basis, but not reverse, or >>> at least not reverse in the sense that we only want customers to be >>> able to modify the reverse DNS of say a single IP, or a subnet, etc. >>> >> >> for this I'm using powerdns + poweradmin (but you can use another >> system) >> >> for only 1 IP i do 1.0.168.192.in-addr.arpa IN CNAME >> reverse.custdomain.tld >> >> and reverse.custdomain.tld IN PTR coolreverse.domain.tld. >> >> for a subnet : >> >> 1.0.168.192.in-addr.arpa IN CNAME 1.reverse.custdomain.tld >> 2.0.168.192.in-addr.arpa IN CNAME 2.reverse.custdomain.tld >> 3.0.168.192.in-addr.arpa IN CNAME 3.reverse.custdomain.tld >> >> it's explained in an rfc but I can't remember the numbre. >> >> Regards, >> >> Geo >> _______________________________________________ >> 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 Apr 29 15:02:33 2009 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64D5A1065672 for ; Wed, 29 Apr 2009 15:02:33 +0000 (UTC) (envelope-from martes@mgwigglesworth.net) Received: from mail.mgwigglesworth.com (mail.mgwigglesworth.com [75.146.26.81]) by mx1.freebsd.org (Postfix) with ESMTP id 93D8A8FC1C for ; Wed, 29 Apr 2009 15:02:32 +0000 (UTC) (envelope-from martes@mgwigglesworth.net) To: freebsd-isp@freebsd.org Date: Wed, 29 Apr 2009 11:01:37 -0400 Envelope-To: freebsd-isp@freebsd.org References: <200904281702.19301.martes@mgwigglesworth.net> <49F7797B.1060306@thingy.com> Message-ID: <200904291101.38436.martes@mgwigglesworth.net> From: "Martes G Wigglesworth" Received: from localhost.localnet (192.168.5.12 [192.168.5.12]) by mail.mgwigglesworth.com; Wed, 29 Apr 2009 11:01:55 -0400 Organization: M.G. Wigglesworth Holdings, LLC User-Agent: KMail/1.10.3 (Linux/2.6.27.19-desktop586-1mnb; KDE/4.1.3; i686; ; ) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: [freebsd-isp] Temporary Routing/Switching backup with Backplane and multiple switch cards... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: martes@mgwigglesworth.net List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Apr 2009 15:02:33 -0000 On Tuesday 28 April 2009 17:47:39 Howard Jones wrote: > Martes G Wigglesworth wrote: > > I was wondering if anyone else has attempted to compliment their routing > > devices or switching devices with a back-plane and multiple switch cards > > or E1/T1 cards with any success? Meaning that it was worth the trouble to > > build. > > > > This seems a bit useless initially, however, I am doing some research > > into this for quick-fix disaster recovery systems in case the 3800s are > > down, etc... A bit home-grown, but would like to know if the design > > idea would be viable and not just a costly home-grown project... Maybe > > for a small point of present in a wireless environment which has multiple > > E1/T1 drops to terminate for back-haul transfer central management > > stations, etc... > > _______________________________________________ > > You mean like these? > http://www.vyatta.com/ > http://www.xorp.org/ > http://www.freesco.org/ > All are "software routers" various levels of hardware support for (e.g.) > Sangoma E1/T1 cards. > > Plenty of people use Quagga+Linux or Quagga+FreeBSD (Quagga is the > BGP/OSPF component most of these uses) for peering/transit. PC hardware > will route over 100Mbit quite happily. > _______________________________________________ > 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" Thank you for the new links that I had not come across yet. However, I was not as clear as I should have been. I was more interested in finding out when it became, or would become less cost effective to do this type of setup, due to economies of scale like Cisco and Juniper devices possibly being cheaper than havnig to spend on individual pieces to... More specifically, when is it not cost effective to do such a thing? Assuming a larger, and not smaller network architecture. When does the embedded, specifically designed network processor do a better job than a stripped down server appliance, as described above? From owner-freebsd-isp@FreeBSD.ORG Wed Apr 29 15:09:43 2009 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29D3C106566B for ; Wed, 29 Apr 2009 15:09:43 +0000 (UTC) (envelope-from tonix@interazioni.it) Received: from mx02.interazioni.net (mx02.interazioni.net [80.94.114.204]) by mx1.freebsd.org (Postfix) with ESMTP id 6F4B38FC15 for ; Wed, 29 Apr 2009 15:09:41 +0000 (UTC) (envelope-from tonix@interazioni.it) Received: (qmail 42094 invoked by uid 88); 29 Apr 2009 14:43:00 -0000 Received: from unknown (HELO ?192.168.56.198?) (tonix@interazioni.it@85.18.206.139) by relay.interazioni.net with ESMTPA; 29 Apr 2009 14:42:59 -0000 Message-ID: <49F86774.40002@interazioni.it> Date: Wed, 29 Apr 2009 16:43:00 +0200 From: "Tonix (Antonio Nati)" User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: freebsd-isp@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: Problems with ripmime and OLE 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, 29 Apr 2009 15:09:43 -0000 Is there anyone esperiencing problems with ripmime crashing (chain qmail-smtpd -> simscan -> ripmime)? Server is a FreeBSD 6.1 production server, stable since year. Suddenly, a few weeks ago, ripmime starts to crash with some messages having DOC attaches (only some messages, other with DOC attaches pass without problems). I had to modify simscan and add a "--no-ole" option to ripmime, in order to avoid crashing. Same messages tested on other platforms do not have problems. It looks to be a libc problem, gdb points to memcpy function as the cause of crash. Any hint? Anyone having the same problem? Tonino -- ------------------------------------------------------------ Inter@zioni Interazioni di Antonio Nati http://www.interazioni.it tonix@interazioni.it ------------------------------------------------------------