From owner-freebsd-current@FreeBSD.ORG Fri Sep 12 05:30:58 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5039D16A4BF for ; Fri, 12 Sep 2003 05:30:58 -0700 (PDT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC8AF44003 for ; Fri, 12 Sep 2003 05:30:56 -0700 (PDT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (localhost [127.0.0.1]) h8CCUsvf002542; Fri, 12 Sep 2003 08:30:54 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)h8CCUrPx002539; Fri, 12 Sep 2003 08:30:54 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Fri, 12 Sep 2003 08:30:53 -0400 (EDT) From: Andre Guibert de Bruet To: song@isot.com In-Reply-To: <1062982242.3f5bd262962a8@webmail.isot.com> Message-ID: <20030912063408.U96745@alpha.siliconlandmark.com> References: <1062982242.3f5bd262962a8@webmail.isot.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: FreeBSD-Current@freebsd.org Subject: Re: sylogd not logging X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2003 12:30:58 -0000 On Sun, 7 Sep 2003, itchibahn wrote: > I used to run 4.6 where syslogd worked fine with cisco 7507, as5300, and > max4048. Eversince I've installed 5.0-RELEASE, I used exact same config as > old, but can't get it working. Please help. The following is configs: I'm currently using current's syslogd for remote logging on a series of Cisco 2650s and 1720s. The rc.conf entries that'll make this work are: syslogd_enable="YES" syslogd_flags="-a 192.168.128.0/24:*" Though I've never done it by domain name, the manpage suggests that you're looking for something like this: syslogd_flags="-a *.isot.com:*" As usual, check for firewalling between the endpoints. Hope this helps... > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ >