From owner-freebsd-isp Sun Dec 5 7:55:50 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mail.fil.net (mail.fil.net [202.57.102.7]) by hub.freebsd.org (Postfix) with ESMTP id A01E414BD0 for ; Sun, 5 Dec 1999 07:55:45 -0800 (PST) (envelope-from aLan@fil.net) Received: from fil.net ([202.57.102.6]) by mail.fil.net (Netscape Messaging Server 3.62) with ESMTP id 251 for ; Sun, 5 Dec 1999 23:55:38 +0800 Message-ID: <384A8AF9.3287B947@fil.net> Date: Sun, 05 Dec 1999 23:55:37 +0800 From: "aLan Tait" X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-isp@FreeBSD.ORG" Subject: IPFilter and xntpd Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I got IPFilter running in the gateway computer. Likewise, xntpd was working fine... until I switched it online and over to the RFC 1918 addresses between the router and the Gateway. Below is basically the rc.conf file (xl0's IP was changed for security). If I am on gw and try to ping, traceroute, or xntpd to the outside world, it fails... I think because it is passing the 192.186.1.2 address as the return. That, of course, also makes xntpd fail for other servers pointed at gw. If I point an inside server at outside our network, it works fine. Everything inside to the outside works as far as I can tell. I was just thinking it would be good if the gw was also our system clock... Can this be? Am I missing something that would allow the return packets to return to "123.45.102.1" instead of "192.168.1.2"??? Or should I just use a different server inside (like ftp), and then point gw at it? network_interfaces="ed1 xl0 lo0" ifconfig_ed1="inet 192.168.1.2 netmask 255.255.255.0" defaultrouter="192.168.1.1" ifconfig_xl0="inet 123.45.102.1 netmask 255.255.254.0" gateway_enable="YES" hostname="gw.fil.net" moused_type="NO" xntpd_enable="YES" xntpd_flags="-c /etc/ntp.conf" Outside | Provider link Router | 192.168.1.1 | | 192.168.1.2 GateWay | x.x.102.1 | | Hub aLan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Dec 5 8:30:50 1999 Delivered-To: freebsd-isp@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 36D5A151F0 for ; Sun, 5 Dec 1999 08:30:47 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id QAA61953; Sun, 5 Dec 1999 16:30:25 GMT (envelope-from joe) Date: Sun, 5 Dec 1999 16:30:25 +0000 From: Josef Karthauser To: Dennis Cc: Julian Elischer , Kurt Jaeger , Tom , "Jean M. Vandette" , freebsd-isp@FreeBSD.ORG Subject: Re: IP or packet Accounting Software for burst connections. Message-ID: <19991205163025.B60129@florence.pavilion.net> References: <199911261715.MAA10373@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199911261715.MAA10373@etinc.com> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Nov 26, 1999 at 12:11:42PM -0500, Dennis wrote: > Try the ET/BWMGR for FreeBSD...our hashed rule indexing can handle > thousands of IP addresses or traffic type measurements with integrated > graphing and bandwidth management. HTML management interface also. > > > www.etinc.com/bwmgr.htm > > Dennis I'm not looking for a commercial solution, unless you've changed your licence since I last looked? Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Dec 5 8:46:54 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mars.aspenworks.net (mars.aspenworks.net [208.44.82.253]) by hub.freebsd.org (Postfix) with ESMTP id 4B09F152FB for ; Sun, 5 Dec 1999 08:46:53 -0800 (PST) (envelope-from alex@aspenworks.com) Received: from aspenworks.com (s31-g-lv3.sopris.net [208.47.129.138]) by mars.aspenworks.net (8.9.3/8.9.3) with ESMTP id JAA40825 for ; Sun, 5 Dec 1999 09:51:25 -0700 (MST) (envelope-from alex@aspenworks.com) Message-ID: <384A96F9.197897A3@aspenworks.com> Date: Sun, 05 Dec 1999 09:46:49 -0700 From: Alex Huppenthal Reply-To: alex@aspenworks.com Organization: Aspenworks.com X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-isp@freebsd.org Subject: Scalable web server - ServeRAID 8640/330-ESS IBM gear Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm building an applications server and this IBM system is a test platform. Everything we've cooked up for our ISP in Aspen is FreeBSD based, and I'd like to keep it that way. I've purchased an IBM system with a "ServeRAID" scsi controller. Three channels, on board cache, powerPC processor etc. etc.. Pretty snappy. I've found Linux and NT drivers, and recently IBM announced the sources are available for the ServerRAID driver. (GNU) Man, have times changed. IBM = open software... purely amazing to me.. wonderful! I've searched the FreeBSD website, but no hits there for ServeRAID support. Does anyone know of a way to get the ServeRAID controller working with FreeBSD? I'm not qualified to port the sources IBM released for their controller, so I'll have to use a canned solution. Anyone working on the port of the drivers? Cheers, -Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Dec 5 10:50:54 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mail.wzrd.com (mail.wzrd.com [206.99.165.3]) by hub.freebsd.org (Postfix) with ESMTP id B69B315420 for ; Sun, 5 Dec 1999 10:50:52 -0800 (PST) (envelope-from danh@wzrd.com) Received: by mail.wzrd.com (Postfix, from userid 91) id ACD495D064; Sun, 5 Dec 1999 13:50:51 -0500 (EST) Subject: Re: IPFilter and xntpd In-Reply-To: <384A8AF9.3287B947@fil.net> from aLan Tait at "Dec 5, 1999 11:55:37 pm" To: aLan@fil.net (aLan Tait) Date: Sun, 5 Dec 1999 13:50:51 -0500 (EST) Cc: freebsd-isp@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 506 Message-Id: <19991205185051.ACD495D064@mail.wzrd.com> From: danh@wzrd.com (Dan Harnett) Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Can this be? Am I missing something that would allow the > return packets to return to "123.45.102.1" instead of > "192.168.1.2"??? > What you need to do here is enable IPNAT. This will translate the internal addresses to the 123.45.102.1 address. Some simple rules to allow most of the basic services are: map xl0 192.168.0.0/16 -> 123.45.102.1/32 proxy port ftp ftp/tcp map xl0 192.168.0.0/16 -> 123.45.102.1/32 portmap tcp/udp 10000:60000 map xl0 192.168.0.0/16 -> 123.45.102.1/32 Dan Harnett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Dec 5 13:14:16 1999 Delivered-To: freebsd-isp@freebsd.org Received: from dns.sonntag.org (dns.sonntag.org [216.140.186.114]) by hub.freebsd.org (Postfix) with ESMTP id 2E79A14CE2 for ; Sun, 5 Dec 1999 13:14:12 -0800 (PST) (envelope-from aaron@sonntag.org) Received: from aaron (cs2744-250.austin.rr.com [24.27.44.250]) by dns.sonntag.org (8.9.3/8.9.3) with SMTP id PAA99901 for ; Sun, 5 Dec 1999 15:14:20 -0600 (CST) (envelope-from aaron@sonntag.org) From: "Aaron Sonntag" To: Subject: Shell shocked / a shell for every season? Date: Sun, 5 Dec 1999 15:32:05 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: <19991205185051.ACD495D064@mail.wzrd.com> Importance: Normal Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a variety of users I need to accommodate/limit By editing vipw myself I have been able to create mail only accounts using /noexistent for home directory and /usr/bin/passwd for the shell... Is there a better solution? I heard this solution is a security issue. How can I do something similar and limit certain accounts to ftp only? How can I do something similar and limit certain accounts to ftp and mail only? How do I keep users from leaving the /home partition? I don't want them to be able to cd to / or /etc or /root for example. I saw something about 'chmod 700 $HOME /home/averageuser' I really don't know. I have done the usual searching of deja and freebsd mail archives and did not get much in the way of specific answers. Thank you, Aaron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Dec 5 15:19:18 1999 Delivered-To: freebsd-isp@freebsd.org Received: from cliff.i-plus.net (cliff.i-plus.net [209.100.20.42]) by hub.freebsd.org (Postfix) with ESMTP id 4D4DE14CEC for ; Sun, 5 Dec 1999 15:19:07 -0800 (PST) (envelope-from st@i-plus.net) Received: from abyss (is.dashit.net [209.100.22.250]) by cliff.i-plus.net (8.9.3/8.9.3) with SMTP id SAA81858; Sun, 5 Dec 1999 18:19:04 -0500 (EST) From: "Troy Settle" To: "Aaron Sonntag" , Subject: RE: Shell shocked / a shell for every season? Date: Sun, 5 Dec 1999 18:18:01 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 In-Reply-To: Importance: Normal Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org For us, every account has email and a home directory (actually, mail is delivered to $HOME/.mail for every user). Everyone's shell is set to /sbin/nologin by default. We enable regular shell access on a case-by-case basis. Dialup users are assigned to a group called 'dialup', non dialup are assigned to group 'email.' Radius rejects dialup access to people in the 'email' group. For FTP, we use ncftpd, which restricts users in those groups to their home directories. If you want to limit FTP, you can do so by group (email only accounts don't have ftp access on our network). I believe you might be able to do it by giving users a shell not listed in /etc/shells (assuming that your FTP server looks for a valid shell, which I believe ncftpd does). I'm not sure how you would restrict people from using mail, or if you'd even want to. Most ISPs make use of email to make announcements to their users. With proper use of gid assignments and system configuration, you can have a very flexable set of services: dialup = dialup, email, ftp mlppp = 2 channel dialup, email, ftp email = email only ftp = email and ftp ftponly = ftp only (might require some hackery to prevent mail) You can create any number of groups, and use each to control access to the combination of services you want. Hell, now that I think about it, you're supposed to be able to use the class field in the passwd file to limit things as well. HTH, Troy ** -----Original Message----- ** From: owner-freebsd-isp@FreeBSD.ORG ** [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of Aaron Sonntag ** Sent: Sunday, December 05, 1999 4:32 PM ** To: freebsd-isp@FreeBSD.ORG ** Subject: Shell shocked / a shell for every season? ** ** ** I have a variety of users I need to accommodate/limit ** ** By editing vipw myself I have been able to create mail only ** accounts using ** /noexistent for home directory and /usr/bin/passwd for the shell... ** Is there a better solution? ** I heard this solution is a security issue. ** ** How can I do something similar and limit certain accounts to ftp only? ** ** How can I do something similar and limit certain accounts to ftp and mail ** only? ** ** How do I keep users from leaving the /home partition? I don't ** want them to ** be able to cd to / or /etc or /root for example. ** I saw something about 'chmod 700 $HOME /home/averageuser' I really don't ** know. ** ** I have done the usual searching of deja and freebsd mail archives and did ** not get much in the way of specific answers. ** ** Thank you, ** ** Aaron ** ** ** ** ** ** To Unsubscribe: send mail to majordomo@FreeBSD.org ** with "unsubscribe freebsd-isp" in the body of the message ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Dec 5 16: 0:35 1999 Delivered-To: freebsd-isp@freebsd.org Received: from dns.sonntag.org (dns.sonntag.org [216.140.186.114]) by hub.freebsd.org (Postfix) with ESMTP id 03A9D14CFF for ; Sun, 5 Dec 1999 16:00:32 -0800 (PST) (envelope-from aaron@sonntag.org) Received: from aaron (cs2744-250.austin.rr.com [24.27.44.250]) by dns.sonntag.org (8.9.3/8.9.3) with SMTP id SAA01573 for ; Sun, 5 Dec 1999 18:00:41 -0600 (CST) (envelope-from aaron@sonntag.org) From: "Aaron Sonntag" To: Subject: apache vhost question Date: Sun, 5 Dec 1999 18:18:25 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When I goto the following VHOST I have no problems www.terraneclipse.com ServerName www.terraneclipse.com ServerAdmin hostmaster@sonntag.org DocumentRoot /home/tec_www/public_html CustomLog /home/tec_www/logs/access_log common ErrorLog /home/tec_www/logs/error_log ScriptLog /home/tec_www/logs/script_log TransferLog /home/tec_www/logs/transfer_log ScriptAlias /cgi-bin/ /home/tec_www/cgi-bin/ but when I goto another VHOST that I want to use the same directories as the .com version I get the error below www.terraneclipse.net ServerName *.terraneclipse.net ServerAdmin hostmaster@sonntag.org DocumentRoot /home/tec_www/public_html CustomLog /home/tec_www/logs/access_log common ErrorLog /home/tec_www/logs/error_log ScriptLog /home/tec_www/logs/script_log TransferLog /home/tec_www/logs/transfer_log ScriptAlias /cgi-bin/ /home/tec_www/cgi-bin/ [error] Forbidden You don't have permission to access / on this server. Apache/1.3.9 Server at www.sonntag.org Port 80 [error] any ideas? Thank you, Aaron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Dec 5 16:23:20 1999 Delivered-To: freebsd-isp@freebsd.org Received: from richard2.pil.net (richard2.pil.net [207.8.164.9]) by hub.freebsd.org (Postfix) with SMTP id C852614D90 for ; Sun, 5 Dec 1999 16:23:16 -0800 (PST) (envelope-from up@3.am) Received: (qmail 10943 invoked by uid 1825); 6 Dec 1999 00:23:09 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Dec 1999 00:23:09 -0000 Date: Sun, 5 Dec 1999 19:23:09 -0500 (EST) From: X-Sender: up@richard2.pil.net To: Aaron Sonntag Cc: freebsd-isp@FreeBSD.ORG Subject: Re: apache vhost question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It looks like you don't have an index.html page in ~tec_www/public_html On Sun, 5 Dec 1999, Aaron Sonntag wrote: > When I goto the following VHOST I have no problems > www.terraneclipse.com > > ServerName www.terraneclipse.com > ServerAdmin hostmaster@sonntag.org > DocumentRoot /home/tec_www/public_html > CustomLog /home/tec_www/logs/access_log common > ErrorLog /home/tec_www/logs/error_log > ScriptLog /home/tec_www/logs/script_log > TransferLog /home/tec_www/logs/transfer_log > ScriptAlias /cgi-bin/ /home/tec_www/cgi-bin/ > > but when I goto another VHOST that I want to use the same directories as the > .com version I get the error below > www.terraneclipse.net > > ServerName *.terraneclipse.net > ServerAdmin hostmaster@sonntag.org > DocumentRoot /home/tec_www/public_html > CustomLog /home/tec_www/logs/access_log common > ErrorLog /home/tec_www/logs/error_log > ScriptLog /home/tec_www/logs/script_log > TransferLog /home/tec_www/logs/transfer_log > ScriptAlias /cgi-bin/ /home/tec_www/cgi-bin/ > > [error] > Forbidden > You don't have permission to access / on this server. > > Apache/1.3.9 Server at www.sonntag.org Port 80 > [error] > > any ideas? > Thank you, > Aaron > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= ISPF 3 - The Forum for ISPs by ISPs(tm) || Nov 15-17, 1999, New Orleans 3 days of clues, news, and views from the industry's best and brightest. Visit for information and registration. ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Dec 5 17:14:22 1999 Delivered-To: freebsd-isp@freebsd.org Received: from web3005.mail.yahoo.com (web3005.mail.yahoo.com [204.71.202.168]) by hub.freebsd.org (Postfix) with SMTP id 1406014D03 for ; Sun, 5 Dec 1999 17:14:10 -0800 (PST) (envelope-from galluccib@yahoo.ie) Received: (qmail 10982 invoked by uid 60001); 6 Dec 1999 01:14:09 -0000 Message-ID: <19991206011409.10981.qmail@web3005.mail.yahoo.com> Received: from [216.174.90.43] by web3005.mail.yahoo.com; Sun, 05 Dec 1999 17:14:09 PST Date: Sun, 5 Dec 1999 17:14:09 -0800 (PST) From: Brian Gallucci Subject: IPFW established To: freebsd-ipfw@freebsd.org Cc: freebsd-isp@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just have one question about the established command in rc.firewall. I have heard that if we add -> $fwcmd add pass tcp from any to any established $fwcmd add pass tcp from any to any 20 setup $fwcmd add pass tcp from any to any 21 setup $fwcmd add pass tcp from any to any 80 setup vs $fwcmd add pass tcp from any 20 to any $fwcmd add pass tcp from any to any 20 $fwcmd add pass tcp from any 21 to any $fwcmd add pass tcp from any to any 21 Using the established command will give us better performance on the firewall, is this correct ? Can you email me back at briang@expnet.net because I'm not on the mailing list. Thanks Brian Gallucci Sr. Network Engineer Network Operations Center Express Networks, Inc. briang@expnet.net ____________________________________________________________ Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Dec 5 18: 9:33 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mail.fil.net (mail.fil.net [202.57.102.7]) by hub.freebsd.org (Postfix) with ESMTP id 47E3114E16 for ; Sun, 5 Dec 1999 18:09:25 -0800 (PST) (envelope-from aLan@fil.net) Received: from fil.net ([202.57.102.6]) by mail.fil.net (Netscape Messaging Server 3.62) with ESMTP id 233; Mon, 6 Dec 1999 10:09:14 +0800 Message-ID: <384B1AC5.B84D93BA@fil.net> Date: Mon, 06 Dec 1999 10:09:09 +0800 From: "aLan Tait" X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Warren Welch Cc: Glen Foster , danh@wzrd.com, "freebsd-isp@FreeBSD.ORG" Subject: Re: IPFilter and xntpd References: <199912051652.LAA18462@rr.gfoster.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Warren! Can you (or anybody on the ISP list) help me with this... I posted the below questions about IPFilter and xntpd following your suggestion to use the RFC-1918 addresses BETWEEN the outside addresses and the inside addresses (ALL of which are globally routable). I only have two RFC-1918 addresses, one at each end of the router - gateway crossover cable. The problem is, I can't get gateway to xntpd to a public server on the other side of the router (I think because it uses a RFC-1918 address on the outgoing link - per your wonderful suggestion). Is there a way to let gateway be my network time server, or do I have to setup a different time server on the inside and point gateway back into it? Jaz, on the inside network, has no problem getting the time from tick.usno.navy.mil (all the way to the USA and back!). I just can't get gateway to get the tick. The answers I've received so far have assumed my "inside" network was using RFC-1918 addresses - which it is not. Everything is global addresses except the gateway - router link. Maybe IPNAT would work, but I cannot think how to map the routable "inside" address of the gateway to be the return IP for packets sent via the non routable "outside" address of gateway. I know this looks "backward" to most people - it did to me until I tried it. It works great - except for the xntpd tick problem. Do you run a system clock in your gateway? Hope someone can tell me the work around (if there is one!). Blessings, aLan Glen Foster wrote: > > What you want is NAT (Network Address Translation). This maps your > RFC-1918 addresses "inside" to one or more routable IP addresses on > the external interface of the router connecting the RFC-1918 network. > > NAT functionality is paired with ipfilter filtering functionality with > the ipnat program just as ipfw has natd as a companion. All of the > relevant man pages are required reading. > > The ipfilter home, , > has pointers to a FAQ, a how-to, and example uses as does the > directory /usr/src/contrib/ipfilter/rules/. > > Good luck, if you have specific questions about your configuration I'd > be happy to try and help you out. > > Glen Foster > > >Date: Sun, 05 Dec 1999 23:55:37 +0800 > >From: "aLan Tait" > > > >I got IPFilter running in the gateway computer. Likewise, > >xntpd was working fine... until I switched it online and > >over to the RFC 1918 addresses between the router and the > >Gateway. > > > >Below is basically the rc.conf file (xl0's IP was changed > >for security). > > > >If I am on gw and try to ping, traceroute, or xntpd to the > >outside world, it fails... I think because it is passing > >the 192.186.1.2 address as the return. That, of course, > >also makes xntpd fail for other servers pointed at gw. If I > >point an inside server at outside our network, it works > >fine. Everything inside to the outside works as far as I > >can tell. I was just thinking it would be good if the gw > >was also our system clock... > > > >Can this be? Am I missing something that would allow the > >return packets to return to "123.45.102.1" instead of > >"192.168.1.2"??? > > > >Or should I just use a different server inside (like ftp), > >and then point gw at it? > > > >network_interfaces="ed1 xl0 lo0" > >ifconfig_ed1="inet 192.168.1.2 netmask 255.255.255.0" > >defaultrouter="192.168.1.1" > >ifconfig_xl0="inet 123.45.102.1 netmask 255.255.254.0" > >gateway_enable="YES" > >hostname="gw.fil.net" > >moused_type="NO" > >xntpd_enable="YES" > >xntpd_flags="-c /etc/ntp.conf" > > > >Outside > > | Provider link > >Router > > | 192.168.1.1 > > | > > | 192.168.1.2 > >GateWay > > | x.x.102.1 > > | > > | > > Hub > > > >aLan > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-isp" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Dec 5 19:16:21 1999 Delivered-To: freebsd-isp@freebsd.org Received: from sasknow.com (h139-142-245-96.ss.fiberone.net [139.142.245.96]) by hub.freebsd.org (Postfix) with ESMTP id 4368814DF5 for ; Sun, 5 Dec 1999 19:16:15 -0800 (PST) (envelope-from freebsd@sasknow.com) Received: from localhost (freebsd@localhost) by sasknow.com (8.9.3/8.9.3) with ESMTP id VAA93870 for ; Sun, 5 Dec 1999 21:16:30 -0600 (CST) (envelope-from freebsd@sasknow.com) Date: Sun, 5 Dec 1999 21:16:30 -0600 (CST) From: Ryan Thompson To: freebsd-isp@freebsd.org Subject: Cyrus imapd/pop3d not talking to sendmail? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hey all; Get ready for a long one... I'm including all of this history to a) let you all know what I did... and b) Avoid responses telling me to do something I've already done or checked :-) In the midst of some hardware upgrades, here, I'm also testing some new software for possible use in production. One such piece of software is the Cyrus mailer found in -STABLE ports. I scoured the included documentation, their websites, and, of course, the FreeBSD mailing list archives... To no avail. So, RTFM replies would be appreciated, if you could point me to TFM. :-) Cyrus compiled fine, installed fine, and runs without a hitch. For testing, I compiled it with the pwcheck_unix option (plaintext passwords), and logins via cyradm work correctly. In imapd.conf, I have added a username for admin, and have verified that this user can log into cyradm and see all mailboxes. With the admin user, I issued: my.host.com> cm user.testuser my.host.com> sq user.testuser 10240 my.host.com> lq user.testuser STORAGE 0% (0/10240) I then modified the freebsd.m4 sendmail config to include MAILER(cyrus), and with that, made and installed a new sendmail.cf in /etc/sendmail.cf I checked the new sendmail.cf and adjusted the default path to /usr/local/cyrus/bin/deliver (now correct), and changed the user/group for cyrus to cyrus:cyrus instead of cyrus:mail. After all was changed here, I HUPped sendmail. (And later tried rebooting, just in case :-). So, I sent mail to testuser, then ran Pine from testuser's account (configured for IMAP, successfully logged in on port 143 with name and password. pwcheck logs a successful login by the same user). However, even though that user can create and delete folders under his control, the user can't view mail... And presumably isn't RECEIVING mail through IMAP, although local mail works as normal. I also tried telnetting in on port 110 (POP3). I can successfully log in as testuser, but stat returns 0 messages/0 octets. So, while they are both running, imapd and pop3d don't fetch mail... Presumably because sendmail isn't communicating with cyrus. When I log into cyradm as the admin user, lm shows that testuser did, in fact, create some folders (shown as user.testuser.personal, etc...) But, lq user.testuser still shows that 0 bytes (or K) are being used for storage (even after some fairly large attachments are sent to the address). /var/spool/imap/user/testuser has some short or zero length files... But nothing to indicate any mail was ever received. --- Snippet of sendmail.cf; /etc/sendmail.cf (last few lines, where Cyrus info is kept): << SNIP!! >> ################################################## ### Cyrus Mailer specification ### ################################################## ##### @(#)cyrus.m4 8.9 (Carnegie Mellon) 5/19/1998 ##### Mcyrus, P=/usr/local/cyrus/bin/deliver, F=lsDFMnPqA5@/:|, S=10, R=20/40, T=X-Unix, U=cyrus:cyrus, A=deliver -e -m $h -- $u Mcyrusbb, P=/usr/local/cyrus/bin/deliver, F=lsDFMnP, S=10, R=20/40, T=X-Unix, U=cyrus:cyrus, A=deliver -e -m $u -- EOF If I can include any other information, let me know... I think I've been pretty exhaustive, so far :-) I haven't included any other config files, as most are just one-line edits, and most of THOSE are taken care of by make all install for the Cyrus port. /usr/local/cyrus/bin/deliver exists, and has permissions 4750 (-rwsr-x---). Owned by cyrus:cyrus. daemon is a member of the cyrus group in /etc/group So, to anyone who has successfully installed Cyrus... What have I done wrong? I'd really like to give Cyrus a shot.. Ryan Thompson 50% Owner, Technical and Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Dec 5 20:55:39 1999 Delivered-To: freebsd-isp@freebsd.org Received: from dns.sonntag.org (dns.sonntag.org [216.140.186.114]) by hub.freebsd.org (Postfix) with ESMTP id C8D8D14DF1 for ; Sun, 5 Dec 1999 20:55:33 -0800 (PST) (envelope-from aaron@sonntag.org) Received: from aaron (cs2744-250.austin.rr.com [24.27.44.250]) by dns.sonntag.org (8.9.3/8.9.3) with SMTP id WAA03399; Sun, 5 Dec 1999 22:55:41 -0600 (CST) (envelope-from aaron@sonntag.org) From: "Aaron Sonntag" To: Cc: Subject: RE: apache vhost question Date: Sun, 5 Dec 1999 23:13:27 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yes I do... interesting idea though... but if you goto www.terraneclipse.com you can see the index.html... You can type in www.terraneclipse.com/index.html as well... The idea I was trying to accomplish is having any requests for *.terraneclipse.net point to the directory for www.terraneclipse.com and as you can see both of my virtual host sections specify the same /home/tec_www/public_html directory. -rw-r--r-- 1 tec_www tec_www 356 Dec 5 17:08 index.html -rw-r--r-- 1 tec_www tec_www 34683 Dec 5 17:08 placeholder.jpg I think it has to do with me trying to go about accomplishing the aliasing of *.terraneclipse.net on to www.terraneclipse.com I saw something about a ServerAlias directive... would that go int the www.terraneclipse.com vhost section of the *.terraneclipse.net setcion? Is that my solution? Aaron -----Original Message----- From: owner-freebsd-isp@FreeBSD.ORG [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of up@3.am Sent: Sunday, December 05, 1999 6:23 PM To: Aaron Sonntag Cc: freebsd-isp@FreeBSD.ORG Subject: Re: apache vhost question It looks like you don't have an index.html page in ~tec_www/public_html On Sun, 5 Dec 1999, Aaron Sonntag wrote: > When I goto the following VHOST I have no problems > www.terraneclipse.com > > ServerName www.terraneclipse.com > ServerAdmin hostmaster@sonntag.org > DocumentRoot /home/tec_www/public_html > CustomLog /home/tec_www/logs/access_log common > ErrorLog /home/tec_www/logs/error_log > ScriptLog /home/tec_www/logs/script_log > TransferLog /home/tec_www/logs/transfer_log > ScriptAlias /cgi-bin/ /home/tec_www/cgi-bin/ > > but when I goto another VHOST that I want to use the same directories as the > .com version I get the error below > www.terraneclipse.net > > ServerName *.terraneclipse.net > ServerAdmin hostmaster@sonntag.org > DocumentRoot /home/tec_www/public_html > CustomLog /home/tec_www/logs/access_log common > ErrorLog /home/tec_www/logs/error_log > ScriptLog /home/tec_www/logs/script_log > TransferLog /home/tec_www/logs/transfer_log > ScriptAlias /cgi-bin/ /home/tec_www/cgi-bin/ > > [error] > Forbidden > You don't have permission to access / on this server. > > Apache/1.3.9 Server at www.sonntag.org Port 80 > [error] > > any ideas? > Thank you, > Aaron > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= ISPF 3 - The Forum for ISPs by ISPs(tm) || Nov 15-17, 1999, New Orleans 3 days of clues, news, and views from the industry's best and brightest. Visit for information and registration. ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Dec 5 22: 0:31 1999 Delivered-To: freebsd-isp@freebsd.org Received: from rowdy.panther.net (rowdy.panther.net [209.197.223.18]) by hub.freebsd.org (Postfix) with ESMTP id 77A6214ED1 for ; Sun, 5 Dec 1999 22:00:00 -0800 (PST) (envelope-from kward@panther.net) Received: from localhost (2555 bytes) by rowdy.panther.net (Smail-3.2.0.104 1998-Nov-20 #3) via sendmail with P:stdio/R:inet_hosts/T:smtp (sender: ) (ident using unix) id for ; Sun, 5 Dec 1999 23:53:53 -0600 (CST) Message-Id: From: kward@panther.net (Keith Ward) Subject: Re: apache vhost question To: aaron@sonntag.org (Aaron Sonntag) Date: Sun, 5 Dec 1999 23:53:52 -0600 (CST) Cc: freebsd-isp@FreeBSD.ORG In-Reply-To: from "Aaron Sonntag" at Dec 5, 99 06:18:25 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2051 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You need a FQDN for the ServerName on the second virtual host. As far as I know, the wildcard can only be used for the ServerAlias directive. i.e.: ServerName www.terraneclipse.net ServerAlias *.terraneclipse.net ... Keith According to the writings of Aaron Sonntag > > When I goto the following VHOST I have no problems > www.terraneclipse.com > > ServerName www.terraneclipse.com > ServerAdmin hostmaster@sonntag.org > DocumentRoot /home/tec_www/public_html > CustomLog /home/tec_www/logs/access_log common > ErrorLog /home/tec_www/logs/error_log > ScriptLog /home/tec_www/logs/script_log > TransferLog /home/tec_www/logs/transfer_log > ScriptAlias /cgi-bin/ /home/tec_www/cgi-bin/ > > but when I goto another VHOST that I want to use the same directories as the > .com version I get the error below > www.terraneclipse.net > > ServerName *.terraneclipse.net > ServerAdmin hostmaster@sonntag.org > DocumentRoot /home/tec_www/public_html > CustomLog /home/tec_www/logs/access_log common > ErrorLog /home/tec_www/logs/error_log > ScriptLog /home/tec_www/logs/script_log > TransferLog /home/tec_www/logs/transfer_log > ScriptAlias /cgi-bin/ /home/tec_www/cgi-bin/ > > [error] > Forbidden > You don't have permission to access / on this server. > > Apache/1.3.9 Server at www.sonntag.org Port 80 > [error] > > any ideas? > Thank you, > Aaron > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > -- Keith Ward N5OOD kward@Panther.net ...!rwsys!rowdy!kward =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= I don't suffer from insanity, I enjoy every minute of it. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun Dec 5 22:13:38 1999 Delivered-To: freebsd-isp@freebsd.org Received: from sasknow.com (h139-142-245-96.ss.fiberone.net [139.142.245.96]) by hub.freebsd.org (Postfix) with ESMTP id DA65C1506A for ; Sun, 5 Dec 1999 22:13:33 -0800 (PST) (envelope-from freebsd@sasknow.com) Received: from localhost (freebsd@localhost) by sasknow.com (8.9.3/8.9.3) with ESMTP id AAA94872 for ; Mon, 6 Dec 1999 00:13:48 -0600 (CST) (envelope-from freebsd@sasknow.com) Date: Mon, 6 Dec 1999 00:13:48 -0600 (CST) From: Ryan Thompson To: freebsd-isp@FreeBSD.ORG Subject: Re: Cyrus imapd/pop3d not talking to sendmail? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Previous message included in full. When I invoke /usr/local/cyrus/bin/deliver and supply it with some standard headers, I discovered that I CAN in fact send messages successfully, and view with an IMAP or POP client. However, sendmail still refuses to call deliver, despite great amounts of my time spent mucking with sendmail.cf and restarting sendmail. I looked through just about every system log I could find, didn't find any sign of error or confusion when sending mail or starting sendmail. I also tried renaming deliver and replacing it with a short perl script that outputs to a file in /tmp/ when invoked. (Kept permissions and ownerships the same as the old deliver). Sendmail wouldn't run that, either (I thought perhaps Sendmail was sending deliver a bad option, causing it to silently abort). Sooooo... it appears as though Sendmail isn't finding, or isn't even attempting to find the deliver program. Is there something else I have to enable for sendmail to invoke Cyrus, or do I have to compile sendmail with different options? (This is sendmail 8.9.3 we're talking about... stock in 3.3-STABLE). Sendmail's documentation seemed to suggest that all I need to was generate a new sendmail.cf, as I have done. Ryan Thompson 50% Owner, Technical and Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 On Sun, 5 Dec 1999, Ryan Thompson wrote: > Hey all; > > Get ready for a long one... I'm including all of this history to a) let > you all know what I did... and b) Avoid responses telling me to do > something I've already done or checked :-) > > In the midst of some hardware upgrades, here, I'm also testing some new > software for possible use in production. One such piece of software is > the Cyrus mailer found in -STABLE ports. > > I scoured the included documentation, their websites, and, of course, the > FreeBSD mailing list archives... To no avail. So, RTFM replies would be > appreciated, if you could point me to TFM. :-) > > Cyrus compiled fine, installed fine, and runs without a hitch. For > testing, I compiled it with the pwcheck_unix option (plaintext passwords), > and logins via cyradm work correctly. In imapd.conf, I have added a > username for admin, and have verified that this user can log into cyradm > and see all mailboxes. With the admin user, I issued: > > my.host.com> cm user.testuser > my.host.com> sq user.testuser 10240 > my.host.com> lq user.testuser > STORAGE 0% (0/10240) > > I then modified the freebsd.m4 sendmail config to include MAILER(cyrus), > and with that, made and installed a new sendmail.cf in /etc/sendmail.cf > > I checked the new sendmail.cf and adjusted the default path to > /usr/local/cyrus/bin/deliver (now correct), and changed the user/group for > cyrus to cyrus:cyrus instead of cyrus:mail. After all was changed here, I > HUPped sendmail. (And later tried rebooting, just in case :-). > > So, I sent mail to testuser, then ran Pine from testuser's account > (configured for IMAP, successfully logged in on port 143 with name and > password. pwcheck logs a successful login by the same user). > > However, even though that user can create and delete folders under his > control, the user can't view mail... And presumably isn't RECEIVING mail > through IMAP, although local mail works as normal. > > I also tried telnetting in on port 110 (POP3). I can successfully log in > as testuser, but stat returns 0 messages/0 octets. So, while they are > both running, imapd and pop3d don't fetch mail... Presumably because > sendmail isn't communicating with cyrus. > > When I log into cyradm as the admin user, lm shows that testuser did, in > fact, create some folders (shown as user.testuser.personal, etc...) > > But, lq user.testuser still shows that 0 bytes (or K) are being used for > storage (even after some fairly large attachments are sent to the > address). > > /var/spool/imap/user/testuser has some short or zero length files... But > nothing to indicate any mail was ever received. > > --- Snippet of sendmail.cf; > > /etc/sendmail.cf (last few lines, where Cyrus info is kept): > > << SNIP!! >> > > ################################################## > ### Cyrus Mailer specification ### > ################################################## > > ##### @(#)cyrus.m4 8.9 (Carnegie Mellon) 5/19/1998 ##### > > Mcyrus, P=/usr/local/cyrus/bin/deliver, F=lsDFMnPqA5@/:|, S=10, R=20/40, T=X-Unix, > U=cyrus:cyrus, > A=deliver -e -m $h -- $u > > Mcyrusbb, P=/usr/local/cyrus/bin/deliver, F=lsDFMnP, S=10, R=20/40, T=X-Unix, > U=cyrus:cyrus, > A=deliver -e -m $u > > -- EOF > > If I can include any other information, let me know... I think I've been > pretty exhaustive, so far :-) I haven't included any other config files, > as most are just one-line edits, and most of THOSE are taken care of by > make all install for the Cyrus port. > > /usr/local/cyrus/bin/deliver exists, and has permissions 4750 > (-rwsr-x---). Owned by cyrus:cyrus. > > daemon is a member of the cyrus group in /etc/group > > So, to anyone who has successfully installed Cyrus... What have I done > wrong? I'd really like to give Cyrus a shot.. > > Ryan Thompson > 50% Owner, Technical and Accounts > Phone: +1 (306) 664-1161 > > SaskNow Technologies http://www.sasknow.com > #106-380 3120 8th St E Saskatoon, SK S7H 0W2 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Dec 6 4:41:45 1999 Delivered-To: freebsd-isp@freebsd.org Received: from cronus.medianetwork.se (cronus.medianetwork.se [193.14.204.1]) by hub.freebsd.org (Postfix) with ESMTP id D6F9915285 for ; Mon, 6 Dec 1999 04:41:34 -0800 (PST) (envelope-from dl@tyfon.net) Received: from junglenote.com (digital15.medianetwork.se [193.14.204.233]) by cronus.medianetwork.se (8.9.3/8.7) with ESMTP id NAA14010 for ; Mon, 6 Dec 1999 13:41:34 +0100 Received: from enigmatic [127.0.0.1] by junglenote.com [localhost] with SMTP (MDaemon.v2.84.R) for ; Mon, 06 Dec 1999 13:47:35 +0100 Received: by localhost with Microsoft MAPI; Mon, 6 Dec 1999 13:47:29 +0100 Message-ID: <01BF3FF0.704F4F50.dl@tyfon.net> From: Dan Larsson To: "[FreeBSD-ISP-List] (E-post)" , "[FreeBSD-Questions-List] (E-post)" Subject: uucpd problem Date: Mon, 6 Dec 1999 13:47:28 +0100 Organization: Tyfon Internet Services [ http://tyfon.net ] X-Mailer: Microsoft Internet-e-post/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-MDaemon-Deliver-To: freebsd-isp@freebsd.org X-Return-Path: dl@tyfon.net Reply-To: dl@tyfon.net Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm having problems 'activating' the uucp daemon. Are there any tutorials on FreeBSD <--> Taylor UUCP? Regards ------------ Dan Larsson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Dec 6 7: 5:58 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131]) by hub.freebsd.org (Postfix) with ESMTP id A612314FB4 for ; Mon, 6 Dec 1999 07:05:52 -0800 (PST) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [209.224.254.141]) by mail.westbend.net (8.9.3/8.9.3) with SMTP id JAA44212; Mon, 6 Dec 1999 09:05:50 -0600 (CST) (envelope-from hetzels@westbend.net) Message-ID: <009e01bf3ffb$61ee1f80$8dfee0d1@westbend.net> From: "Scot W. Hetzel" To: "Ryan Thompson" Cc: References: Subject: Re: Cyrus imapd/pop3d not talking to sendmail? Date: Mon, 6 Dec 1999 09:05:49 -0600 Organization: West Bend Internet MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6000 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: "Ryan Thompson" > When I invoke /usr/local/cyrus/bin/deliver and supply it with > some standard headers, I discovered that I CAN in fact send messages > successfully, and view with an IMAP or POP client. > > However, sendmail still refuses to call deliver, despite great amounts of > my time spent mucking with sendmail.cf and restarting sendmail. I looked > through just about every system log I could find, didn't find any sign of > error or confusion when sending mail or starting sendmail. > What does your sendmail.mc file look like? It should have: define(`CYRUS_MAILER_FLAGS',`SA5@|:/')dnl define(`CYRUS_MAILER_PATH',`/usr/local/cyrus/bin/deliver')dnl define(`CYRUS_MAILER_ARGS',`deliver -e -m $h -- $u')dnl define(`CYRUS_MAILER_MAX',`eval(5*1024*1024)')dnl define(`CYRUS_MAILER_USER',`cyrus:cyrus')dnl define(`CYRUS_BB_MAILER_FLAGS',`')dnl define(`CYRUS_BB_MAILER_ARGS',`deliver -e -m $u')dnl MAILER(cyrus)dnl define(`confLOCAL_MAILER',`cyrus')dnl LOCAL_RULE_0 R$=N $: $#local $: $1 R$=N < @ $=w . > $: $#local $: $1 Rbb + $+ < @ $=w . > $#cyrusbb $: $1 LOCAL_CONFIG dnl list of users not to deliver messages to IMAP server FN /etc/mail/sendmail.cN Also, make sure that user/group cyrus exist. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Dec 6 7:37:46 1999 Delivered-To: freebsd-isp@freebsd.org Received: from bsdie.rwsystems.net (bsdie.rwsystems.net [209.197.223.2]) by hub.freebsd.org (Postfix) with ESMTP id 8BB3914DA6; Mon, 6 Dec 1999 07:37:34 -0800 (PST) (envelope-from jwyatt@rwsystems.net) Received: from bsdie.rwsystems.net([209.197.223.2]) (1569 bytes) by bsdie.rwsystems.net via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Mon, 6 Dec 1999 09:31:22 -0600 (CST) (Smail-3.2.0.106 1999-Mar-31 #1 built 1999-Aug-7) Date: Mon, 6 Dec 1999 09:31:22 -0600 (CST) From: James Wyatt To: Dan Larsson Cc: "[FreeBSD-ISP-List] (E-post)" , "[FreeBSD-Questions-List] (E-post)" Subject: Re: uucpd problem In-Reply-To: <01BF3FF0.704F4F50.dl@tyfon.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 6 Dec 1999, Dan Larsson wrote: > I'm having problems 'activating' the uucp daemon. > Are there any tutorials on FreeBSD <--> Taylor UUCP? I am sure that FreeBSD UUCP *IS* Taylor UUCP. The original UUCP from Bazerkly was pretty simple, thus most UUCP shops I worked at used HDB (HoneyDanBer) UUCP. (incl: SCO and Tandy RS/6000) It had a *lot* more (useful even!) features, logging, and performance. To see for yourself, try 'strings -a /usr/libexec/uucp/uucico | grep -i Taylor'... Taylor UUCP can be compiled several ways, though, to use different format config files (easier upgrade from HDB). Thus, if you have an existing Taylor UUCP (SunOS, HPUX, etc...) that was compiled to use existing config files, the FreeBSD format (native Taylor, I think) may look strange. If you can give us more detail, there are several folks around here that still use UUCP for commercial purposes. - Jy@ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Dec 6 8: 6:46 1999 Delivered-To: freebsd-isp@freebsd.org Received: from iohost.com (io001.iohost.com [209.189.124.99]) by hub.freebsd.org (Postfix) with ESMTP id 89D7214D3F for ; Mon, 6 Dec 1999 08:06:41 -0800 (PST) (envelope-from randyk@ccsales.com) Received: from rknt2 (w146.z206111055.lax-ca.dsl.cnc.net [206.111.55.146]) by iohost.com (8.9.3/8.9.3) with SMTP id IAA22983 for ; Mon, 6 Dec 1999 08:07:25 -0800 Message-Id: <3.0.5.32.19991206080611.0356bab0@ccsales.com> X-Sender: randyk@ccsales.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 06 Dec 1999 08:06:11 -0800 To: From: "Randy A. Katz" Subject: Rotate httpd logs Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Just trying to get a clue about how I should rotate httpd logs, how frequently, and whether to use rotatelogs (included in Apache) or something else. If any of you could share your methods I'd appreciate it. Thank you, Randy Katz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Dec 6 11:21:47 1999 Delivered-To: freebsd-isp@freebsd.org Received: from post.mail.areti.net (meteora.areti.com [193.118.189.10]) by hub.freebsd.org (Postfix) with ESMTP id 78BCD157A9 for ; Mon, 6 Dec 1999 11:21:27 -0800 (PST) (envelope-from ndear@areti.net) Received: from acropolis (acropolis.noc.areti.net [193.118.189.102]) by post.mail.areti.net (8.9.3/8.9.3/Areti-2.0.0) with ESMTP id QAA32337; Mon, 6 Dec 1999 16:27:59 GMT Message-Id: <199912061627.QAA32337@post.mail.areti.net> From: "Nicholas J. Dear" Organization: Areti Internet Ltd. To: "Randy A. Katz" Date: Mon, 6 Dec 1999 16:26:41 -0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Rotate httpd logs Reply-To: ndear@areti.net Cc: freebsd-isp@FreeBSD.ORG In-reply-to: <3.0.5.32.19991206080611.0356bab0@ccsales.com> X-mailer: Pegasus Mail for Win32 (v3.12b) Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 6 Dec 99, at 8:06, Randy A. Katz wrote: > Hi, > > Just trying to get a clue about how I should rotate httpd logs, how > frequently, and whether to use rotatelogs (included in Apache) or something > else. If any of you could share your methods I'd appreciate it. I did try using rotatelogs and it went kinda wild, so I wrote my own simple script to do this via crontab. #!/bin/sh TODAY=`date +%Y-%m-%d` for x in `/bin/cat /var/log/www/rotate.monthly.txt` ; do cd /usr/local/apache/logs/$x ; gzip access_log ; mv access_log.gz access_log.$TODAY.gz ; done /usr/local/apache/bin/apachectl restart > /dev/null Our logging is set up so each virtual server has its own directory for logging, but the script could easily be modified if you don't follow this: /usr/local/apache/logs/www.domainame/ rotate.monthly.txt then simply contains a list of "www.domainame" which reflects the directory structure, one on each line. then just bung it into crontab for however often you want it to run. N. -- Nicholas J. Dear Mail: ndear@areti.net Tel: +44 (0)20-8402-4041 Areti Internet Ltd., http://www.areti.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Dec 6 12:33:27 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id 0CCAA15800; Mon, 6 Dec 1999 12:33:21 -0800 (PST) (envelope-from jataylor@xmission.com) Received: from www by mail.xmission.com with local (Exim 3.03 #3) id 11v4oz-0004TS-00; Mon, 06 Dec 1999 13:33:21 -0700 Content-Length: 1654 Date: Mon, 06 Dec 1999 13:33:21 -700 Subject: user ppp, getty and automatic baud rate detection From: James A.Taylor To: freebsd-questions@FreeBSD.org MIME-Version: 1.0 Cc: freebsd-isp@FreeBSD.org Content-Type: text/plain; charset=iso-8859-1 X-Mailer: IMHO for Roxen Content-Transfer-Encoding: 8bit X-Originating-IP: [166.70.12.185] Message-Id: Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have configured a FreeBSD server to provide dial-in access using getty and user ppp. In order to accomplish this I followed method two in the user ppp man page for receiving incoming calls. I set :pp for the defaut profile in the /etc/gettytab file. As long as I use std.19200 as the profile setting for the ttyd in /etc/ttys then I can connect from a remote (Win98) computer using ppp. If I use a different profile such as std.9600 or std.38400 then ppp is never started by getty. It would appear that getty doesn`t recognize that ppp is needed at other speeds. I just tried logging in via a regular dial-up terminal application rather than ppp and found that at 19200 I get a login prompt however at other speeds all I get is garbage characters. This would explain why the ppp transmisions from the win98 box are not noticed. I have an Echo Communications 56K fax modem attaced to the FreeBSD server answering the incoming calls. Typically I would like to use the std.115200 profile and then have the modem accept calls from modems of all speeds (14.4, 19.2, 28.8, 33.6 & 56.8) automatically adjusting the baud rate as needed. I have tried using two different computers to dial in both of which work with our ISP. One computer has a SupraExpress 33.6k modem the other is a Xircom 56T 56.8K modem. Are their any suggestions on how I can get this to work in such a manner that I can automatically detect the baud rate and use that rate be it 14.4k, 56.8k or anything in between. I have FreeBSD 3.1-Release installed on a Pentium 333Mhz system. Thanks for your assistance James A. Taylor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Dec 6 13:29: 4 1999 Delivered-To: freebsd-isp@freebsd.org Received: from naiad.eclipse.net.uk (naiad.eclipse.net.uk [195.188.32.29]) by hub.freebsd.org (Postfix) with ESMTP id 1A0B615380; Mon, 6 Dec 1999 13:28:55 -0800 (PST) (envelope-from sh@eclipse.net.uk) Received: from eclipse.net.uk (elara.eclipse.net.uk [195.188.32.31]) by naiad.eclipse.net.uk (Postfix) with ESMTP id 76B8F13478; Mon, 06 Dec 1999 21:28:51 +0000 (GMT) Message-ID: <384C2AC8.946F3238@eclipse.net.uk> Date: Mon, 06 Dec 1999 21:29:44 +0000 From: Stuart Henderson Organization: Eclipse Networking X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en-GB MIME-Version: 1.0 To: "James A.Taylor" Cc: freebsd-questions@FreeBSD.org, freebsd-isp@FreeBSD.org Subject: Re: user ppp, getty and automatic baud rate detection References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I just tried logging in via a regular dial-up > terminal application rather than ppp and found > that at 19200 I get a login prompt however at > other speeds all I get is garbage characters. okay, your modem is set to switch com port speed to the actual line speed. I would take a wild guess that it may have been used in a wildcat or pcboard bbs before to have been set in that way :) You'll need to play with the nonvolatile ram settings in the modem and get it to use the more standard "fixed com port speed" config and then std.115200 should be fine. Until you do this, I think the only speeds you'll ever see are 300/1200/2400/4800/9600/19200. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Dec 6 13:36:35 1999 Delivered-To: freebsd-isp@freebsd.org Received: from dns.sonntag.org (dns.sonntag.org [216.140.186.114]) by hub.freebsd.org (Postfix) with ESMTP id 6329A14D1F for ; Mon, 6 Dec 1999 13:36:29 -0800 (PST) (envelope-from aaron@sonntag.org) Received: from WIN2K1 (st84042.nobell.com [216.140.184.42]) by dns.sonntag.org (8.9.3/8.9.3) with SMTP id PAA09624; Mon, 6 Dec 1999 15:36:38 -0600 (CST) (envelope-from aaron@sonntag.org) From: "Aaron Sonntag" To: "Keith Ward" , "Aaron Sonntag" Cc: Subject: RE: apache vhost question Date: Mon, 6 Dec 1999 15:37:54 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600 Importance: Normal In-Reply-To: Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org thank you keith, based upon what you said and the apache documentation the following vhost entry worked for me and should work for anyone else too ;-) note the ServerAlias line... that was the key. Also note the wildcard for the ServerName was not a problem and allows Apache to handle anything.terraneclipse.net thanks again for the help everyone! Aaron Sonntag ServerName *.terraneclipse.net ServerAlias www.terraneclipse.com *.terraneclipse.net ServerAdmin hostmaster@sonntag.org DocumentRoot /home/tec_www/public_html CustomLog /home/tec_www/logs/access_log common ErrorLog /home/tec_www/logs/error_log ScriptLog /home/tec_www/logs/script_log TransferLog /home/tec_www/logs/transfer_log -----Original Message----- From: owner-freebsd-isp@FreeBSD.ORG [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of Keith Ward Sent: Sunday, December 05, 1999 11:54 PM To: Aaron Sonntag Cc: freebsd-isp@FreeBSD.ORG Subject: Re: apache vhost question You need a FQDN for the ServerName on the second virtual host. As far as I know, the wildcard can only be used for the ServerAlias directive. i.e.: ServerName www.terraneclipse.net ServerAlias *.terraneclipse.net ... Keith According to the writings of Aaron Sonntag > > When I goto the following VHOST I have no problems > www.terraneclipse.com > > ServerName www.terraneclipse.com > ServerAdmin hostmaster@sonntag.org > DocumentRoot /home/tec_www/public_html > CustomLog /home/tec_www/logs/access_log common > ErrorLog /home/tec_www/logs/error_log > ScriptLog /home/tec_www/logs/script_log > TransferLog /home/tec_www/logs/transfer_log > ScriptAlias /cgi-bin/ /home/tec_www/cgi-bin/ > > but when I goto another VHOST that I want to use the same directories as the > .com version I get the error below > www.terraneclipse.net > > ServerName *.terraneclipse.net > ServerAdmin hostmaster@sonntag.org > DocumentRoot /home/tec_www/public_html > CustomLog /home/tec_www/logs/access_log common > ErrorLog /home/tec_www/logs/error_log > ScriptLog /home/tec_www/logs/script_log > TransferLog /home/tec_www/logs/transfer_log > ScriptAlias /cgi-bin/ /home/tec_www/cgi-bin/ > > [error] > Forbidden > You don't have permission to access / on this server. > > Apache/1.3.9 Server at www.sonntag.org Port 80 > [error] > > any ideas? > Thank you, > Aaron > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > -- Keith Ward N5OOD kward@Panther.net ...!rwsys!rowdy!kward =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= I don't suffer from insanity, I enjoy every minute of it. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Dec 6 13:42:44 1999 Delivered-To: freebsd-isp@freebsd.org Received: from roble.com (roble.com [206.40.34.50]) by hub.freebsd.org (Postfix) with ESMTP id CC86F14D37 for ; Mon, 6 Dec 1999 13:42:40 -0800 (PST) (envelope-from sendmail@roble.com) Received: from roble2.roble.com (roble2.roble.com [206.40.34.52]) by roble.com (Roble1b) with SMTP id NAA07362 for ; Mon, 6 Dec 1999 13:42:42 -0800 (PST) Date: Mon, 6 Dec 1999 13:42:37 -0800 (PST) From: Roger Marquis To: freebsd-isp@FreeBSD.ORG Subject: Re: Rotate httpd logs In-Reply-To: <3.0.5.32.19991206080611.0356bab0@ccsales.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 6 Dec 1999, Randy A. Katz wrote: > Just trying to get a clue about how I should rotate httpd logs, how > frequently, and whether to use rotatelogs (included in Apache) or something > else. If any of you could share your methods I'd appreciate it. Unlike syslogd Apache httpd keeps the logfile open as long as the daemon's running. This eliminates the need to rotate logfiles larger than a certain size, unless you have a very small log partition. For most sites you can rotate the logs monthly. We do that here and then run reports on the previous month. Try this in your /etc/periodic/monthly or /etc/crontab: /bin/sh - # Assume all logs are in the $LOGDIR LOGDIR=/var/log # # rotate OLD logs, keep 4 {month}'s worth in $LOGDIR/OLD # (in addition to the compressed archives created previously) # cd $LOGDIR for file in `ls OLD/*messages*.2` ; do cp $file "` echo $file|sed 's/.2$/.3/' `" done for file in `ls OLD/*messages*.1` ; do cp $file "` echo $file|sed 's/.1$/.2/' `" done for file in `ls OLD/*messages*.0` ; do cp $file "` echo $file|sed 's/.0$/.1/' `" done # # archive this {month}'s and # clean up for next {month} # cd $LOGDIR for file in `ls *messages` ; do ## combine up to 10 previously rotated logs for i in 9 8 7 6 5 4 3 2 1 0 ; do if [ -s ${file}.${i} ]; then cat ${file}.${i} >> ${file}.tmp fi rm -f ${file}.${i} done if [ -s ${file} ]; then cat ${file} >> ${file}.tmp # null out open logfiles cp /dev/null ${file} fi if [ -s ${file}.tmp ]; then # archive unless empty cp ${file}.tmp OLD/${file}.0 fi rm -f ${file}.tmp ls -ltgF OLD/${file}.0 ${file} done chown -R 0.0 /var/log/OLD chown -R 0.0 /var/log/*messages* chown nobody.nogroup /var/log/http*messages 2>&1 >/dev/null chmod 750 /var/log/OLD chmod 640 /var/log/OLD/* -- Roger Marquis Roble Systems Consulting http://www.roble.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Dec 6 14:11:57 1999 Delivered-To: freebsd-isp@freebsd.org Received: from loki.intrepid.net (intrepid.net [204.71.127.3]) by hub.freebsd.org (Postfix) with ESMTP id 0A4A414A05 for ; Mon, 6 Dec 1999 14:11:50 -0800 (PST) (envelope-from mark@loki.intrepid.net) Received: (from mark@localhost) by loki.intrepid.net (8.8.5/8.8.5) id RAA21228; Mon, 6 Dec 1999 17:11:34 -0500 Date: Mon, 6 Dec 1999 17:11:34 -0500 From: Mark Conway Wirt To: "Nicholas J. Dear" Cc: "Randy A. Katz" , freebsd-isp@FreeBSD.ORG Subject: Re: Rotate httpd logs Message-ID: <19991206171134.G8478@intrepid.net> References: <3.0.5.32.19991206080611.0356bab0@ccsales.com> <199912061627.QAA32337@post.mail.areti.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912061627.QAA32337@post.mail.areti.net>; from ndear@areti.net on Mon, Dec 06, 1999 at 04:26:41PM -0000 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Dec 06, 1999 at 04:26:41PM -0000, Nicholas J. Dear wrote: > On 6 Dec 99, at 8:06, Randy A. Katz wrote: > > > Hi, > > > > Just trying to get a clue about how I should rotate httpd logs, how > > frequently, and whether to use rotatelogs (included in Apache) or something > > else. If any of you could share your methods I'd appreciate it. > > I did try using rotatelogs and it went kinda wild, so I wrote my own simple script to do this via crontab. > > #!/bin/sh > TODAY=`date +%Y-%m-%d` > for x in `/bin/cat /var/log/www/rotate.monthly.txt` ; do cd /usr/local/apache/logs/$x ; gzip access_log ; mv access_log.gz access_log.$TODAY.gz ; done > /usr/local/apache/bin/apachectl restart > /dev/null However you so it, it's important to HUP apache or "restart" the server (as above) after you've zeroed the files. --mark -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Dec 6 14:24: 2 1999 Delivered-To: freebsd-isp@freebsd.org Received: from sasknow.com (h139-142-245-96.ss.fiberone.net [139.142.245.96]) by hub.freebsd.org (Postfix) with ESMTP id 38346150CB for ; Mon, 6 Dec 1999 14:23:59 -0800 (PST) (envelope-from freebsd@sasknow.com) Received: from localhost (freebsd@localhost) by sasknow.com (8.9.3/8.9.3) with ESMTP id QAA00895 for ; Mon, 6 Dec 1999 16:24:16 -0600 (CST) (envelope-from freebsd@sasknow.com) Date: Mon, 6 Dec 1999 16:24:16 -0600 (CST) From: Ryan Thompson To: freebsd-isp@freebsd.org Subject: Re: Cyrus imapd/pop3d not talking to sendmail? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks to everyone for the valuable help with Cyrus/sendmail. As pointed out by more than one individual, I was missing the define: define(`confLOCAL_MAILER', `cyrus') (Which I never did see in any of the docmentation that I read! What's this, an IQ test for sendmail administrators? :-) Also, when all was said and done, I also had to create a /usr/etc/imap/deliverdb directory and change the owner to cyrus:cyrus, to avoid complaints about lockfiles from sendmail. Scot Hetzel also suggested the following: LOCAL_CONFIG FN /etc/mail/sendmail.cN ... which appears to be the way to prevent messages from going through cyrus (and, thus, not into local mail). For example, I added root to this file so that root can receive his messages from /var/mail once again. I'll likely add a few more important ones to the list. Now I'm off to set up some group mailboxes for my staff role accounts. QPopper is going to stay in the ports tree this time around :-) Ryan Thompson 50% Owner, Technical and Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Dec 6 16:47:39 1999 Delivered-To: freebsd-isp@freebsd.org Received: from bsdie.rwsystems.net (bsdie.rwsystems.net [209.197.223.2]) by hub.freebsd.org (Postfix) with ESMTP id 3B8A9150E1; Mon, 6 Dec 1999 16:47:33 -0800 (PST) (envelope-from jwyatt@rwsystems.net) Received: from bsdie.rwsystems.net([209.197.223.2]) (2310 bytes) by bsdie.rwsystems.net via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Mon, 6 Dec 1999 18:42:28 -0600 (CST) (Smail-3.2.0.106 1999-Mar-31 #1 built 1999-Aug-7) Date: Mon, 6 Dec 1999 18:42:28 -0600 (CST) From: James Wyatt To: "James A.Taylor" Cc: freebsd-questions@FreeBSD.org, freebsd-isp@FreeBSD.org Subject: Re: user ppp, getty and automatic baud rate detection In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 6 Dec 1999, James A.Taylor wrote: > I have configured a FreeBSD server to provide > dial-in access using getty and user ppp. [ ... ] > As long as I use std.19200 as the profile setting > for the ttyd in /etc/ttys then I can connect from > a remote (Win98) computer using ppp. If I use a > different profile such as std.9600 or std.38400 > then ppp is never started by getty. It would > appear that getty doesn`t recognize that ppp is > needed at other speeds. It would appear that your modem is autobauding and setting the DTE speed on it's own. Different modem vendors have different ways of fixing the DTE speed of the modem. Some won't let you do it, especially WinModems which lose most of the few brain cells they have without Win32 support. > I have an Echo Communications 56K fax modem > attaced to the FreeBSD server answering the > incoming calls. Typically I would like to use the > std.115200 profile and then have the modem accept > calls from modems of all speeds (14.4, 19.2, 28.8, > 33.6 & 56.8) automatically adjusting the baud rate > as needed. You might be able to kill two birds at one time (one you didn't know was there 8{). If you use mgetty, it can allow FAXes as well as regular getty support and decent auto-ppp support. As it disables auto-answer and issues a 'ATA' command when it sees 'RING', it always reminds the modem of the DTE rate desired. If you have a voicemail modem, it can even be a DTMF-menu-enabled voicemail system. I have a great web script for Apache to be the rest of the answering machine. My wife loves it and the CallerID support is cool. Hope this helps - Jy@ (JWyatt@RWSystems.net) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Dec 6 19:41: 1 1999 Delivered-To: freebsd-isp@freebsd.org Received: from NS4.HELP-DESK.CO.UK (ns4.help-desk.co.uk [212.240.170.26]) by hub.freebsd.org (Postfix) with ESMTP id 1B14A14F3D for ; Mon, 6 Dec 1999 19:40:56 -0800 (PST) (envelope-from pgm@NS4.HELP-DESK.CO.UK) Received: (from root@localhost) by NS4.HELP-DESK.CO.UK (8.9.3/8.9.3) id DAA04253; Tue, 7 Dec 1999 03:46:23 GMT (envelope-from pgm) From: Patrick Mackeown Message-Id: <199912070346.DAA04253@NS4.HELP-DESK.CO.UK> Subject: Re: RADIUS server: current sessions, radcheck In-Reply-To: from "angelko@saw.net" at "Dec 2, 1999 01:54:28 pm" To: angelko@saw.net Date: Tue, 7 Dec 1999 03:46:22 +0000 (GMT) Cc: freebsd-isp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hello, > > Can anyone tell me how to find out the number of current user > sessions, and who those users are on a RADIUS server? > > Also, is there a document explaining in detail the output of > radcheck? The man page I have doesn't explain what the values > are, and I didn't find much info on it on http://www.merit.edu/aaa. > > Thanks, > -angelko > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > Check your radius accounting logging. You may have to write a perl script if you want to keep track of who regulary logs on and when. Patmac To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Dec 6 20: 9:27 1999 Delivered-To: freebsd-isp@freebsd.org Received: from thud.tbe.net (thud.tbe.net [209.123.109.174]) by hub.freebsd.org (Postfix) with ESMTP id 0EA7F14F8D for ; Mon, 6 Dec 1999 20:09:24 -0800 (PST) (envelope-from gary@tbe.net) Received: from localhost (gary@localhost) by thud.tbe.net (8.9.3/8.9.3) with ESMTP id XAA23659 for ; Mon, 6 Dec 1999 23:08:20 -0500 Date: Mon, 6 Dec 1999 23:08:20 -0500 (EST) From: "Gary D. Margiotta" To: freebsd-isp@freebsd.org Subject: xl0 errors Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Heya... Got this on one of our 3.3-RELEASE boxes... xl0: no memory for rx list -- packet dropped! Any ideas? Bad card or maybe a code bug? The machine just starts spitting out those errors, and dissapears from the network for a minute or two, then all of a sudden, the machine reappears and all is fine again like nothing happened. The machine is 3.3-RELEASE, 1xPPro, 128 MB RAM and a DPT card. I can supply a full dmesg output or anything else if needed. -Gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Dec 6 21:48:56 1999 Delivered-To: freebsd-isp@freebsd.org Received: from awfulhak.org (dynamic-7.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.135]) by hub.freebsd.org (Postfix) with ESMTP id 1E2DA14D7D; Mon, 6 Dec 1999 21:48:50 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA01339; Tue, 7 Dec 1999 00:25:05 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA04984; Tue, 7 Dec 1999 00:25:39 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912070025.AAA04984@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Stuart Henderson Cc: "James A.Taylor" , freebsd-questions@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG, brian@hak.lan.awfulhak.org Subject: Re: user ppp, getty and automatic baud rate detection In-Reply-To: Message from Stuart Henderson of "Mon, 06 Dec 1999 21:29:44 GMT." <384C2AC8.946F3238@eclipse.net.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Dec 1999 00:25:38 +0000 From: Brian Somers Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I just tried logging in via a regular dial-up > > terminal application rather than ppp and found > > that at 19200 I get a login prompt however at > > other speeds all I get is garbage characters. > > okay, your modem is set to switch com port speed to the > actual line speed. I would take a wild guess that it may have > been used in a wildcat or pcboard bbs before to have been > set in that way :) You'll need to play with the nonvolatile > ram settings in the modem and get it to use the more > standard "fixed com port speed" config and then std.115200 > should be fine. Until you do this, I think the only speeds > you'll ever see are 300/1200/2400/4800/9600/19200. Once the speed has been put in /etc/ttys (and init HUPd), you also need to connect to the modem (you can use ppp in command mode) at the same speed and do a few ATs to train it to that speed. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Dec 6 22:24:32 1999 Delivered-To: freebsd-isp@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id 5D98B14D7D for ; Mon, 6 Dec 1999 22:24:29 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 11vBPt-0001IS-00; Mon, 6 Dec 1999 19:35:53 -0800 Date: Mon, 6 Dec 1999 19:35:51 -0800 (PST) From: Tom To: "Gary D. Margiotta" Cc: freebsd-isp@freebsd.org Subject: Re: xl0 errors In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 6 Dec 1999, Gary D. Margiotta wrote: > Heya... > > Got this on one of our 3.3-RELEASE boxes... > > xl0: no memory for rx list -- packet dropped! > > Any ideas? Bad card or maybe a code bug? Probably not enough mbufs, so there was no where for the packet(s) to go, so it was dumped. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Dec 7 2: 0:17 1999 Delivered-To: freebsd-isp@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id F2BCA14F92 for ; Tue, 7 Dec 1999 02:00:13 -0800 (PST) (envelope-from netchild@Leidinger.net) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id KAA13830279; Tue, 7 Dec 1999 10:59:15 +0100 (CET) Received: from Magelan.Leidinger.net (maxtnt-259.telip.uni-sb.de [134.96.71.130]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id KAA13120; Tue, 7 Dec 1999 10:59:19 +0100 (CET) Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id KAA00931; Tue, 7 Dec 1999 10:24:37 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <199912070924.KAA00931@Magelan.Leidinger.net> Date: Tue, 7 Dec 1999 10:24:36 +0100 (CET) From: Alexander Leidinger Subject: Re: Rotate httpd logs To: ndear@areti.net Cc: randyk@ccsales.com, freebsd-isp@FreeBSD.ORG In-Reply-To: <199912061627.QAA32337@post.mail.areti.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 6 Dec, Nicholas J. Dear wrote: >> >> Just trying to get a clue about how I should rotate httpd logs, how >> frequently, and whether to use rotatelogs (included in Apache) or something >> else. If any of you could share your methods I'd appreciate it. > > I did try using rotatelogs and it went kinda wild, so I wrote my own simple script to do this via crontab. What do you mean with "it went kinda wild"? > #!/bin/sh > TODAY=`date +%Y-%m-%d` > for x in `/bin/cat /var/log/www/rotate.monthly.txt` ; do cd /usr/local/apache/logs/$x ; gzip access_log ; mv access_log.gz access_log.$TODAY.gz ; done > /usr/local/apache/bin/apachectl restart > /dev/null You loose some lines of logging in the worst case with this script. You should first mv the file, restart apache and then gzip it. Or you could do a mv, apachectl graceful, sleep, gzip (no open connection is closed with "graceful", but you need to wait a little bit to be sure the logs are really closed). And if you have verry big logfiles you may want to use gzip -9 oder bzip2 -9. Bye, Alexander. -- Loose bits sink chips. http://netchild.home.pages.de Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Dec 7 2:47:58 1999 Delivered-To: freebsd-isp@freebsd.org Received: from post.mail.areti.net (meteora.areti.com [193.118.189.10]) by hub.freebsd.org (Postfix) with ESMTP id 1CAB914E2D for ; Tue, 7 Dec 1999 02:47:53 -0800 (PST) (envelope-from ndear@areti.net) Received: from acropolis (acropolis.noc.areti.net [193.118.189.102]) by post.mail.areti.net (8.9.3/8.9.3/Areti-2.0.0) with ESMTP id KAA10785; Tue, 7 Dec 1999 10:47:41 GMT Message-Id: <199912071047.KAA10785@post.mail.areti.net> From: "Nicholas J. Dear" Organization: Areti Internet Ltd. To: Alexander Leidinger Date: Tue, 7 Dec 1999 10:46:19 -0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Rotate httpd logs Reply-To: ndear@areti.net Cc: randyk@ccsales.com, freebsd-isp@FreeBSD.ORG In-reply-to: <199912070924.KAA00931@Magelan.Leidinger.net> References: <199912061627.QAA32337@post.mail.areti.net> X-mailer: Pegasus Mail for Win32 (v3.12b) Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 7 Dec 99, at 10:24, Alexander Leidinger wrote: > What do you mean with "it went kinda wild"? It spawned about 30 copies of itself, and then apache died. > > #!/bin/sh > > TODAY=`date +%Y-%m-%d` > > for x in `/bin/cat /var/log/www/rotate.monthly.txt` ; do cd /usr/local/apache/logs/$x ; gzip access_log ; mv access_log.gz access_log.$TODAY.gz ; done > > /usr/local/apache/bin/apachectl restart > /dev/null > > You loose some lines of logging in the worst case with this script. > You should first mv the file, restart apache and then gzip it. > Or you could do a mv, apachectl graceful, sleep, gzip (no open > connection is closed with "graceful", but you need to wait a little bit > to be sure the logs are really closed). Very true. I've modified my script. Thanks, N. -- Nicholas J. Dear Mail: ndear@areti.net Tel: +44 (0)20-8402-4041 Areti Internet Ltd., http://www.areti.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Dec 7 9:52:13 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mars.aspenworks.net (mars.aspenworks.net [208.44.82.253]) by hub.freebsd.org (Postfix) with ESMTP id 895F014C99 for ; Tue, 7 Dec 1999 09:52:11 -0800 (PST) (envelope-from alex@aspenworks.com) Received: from aspenworks.com (s43-g-lv4.sopris.net [208.47.129.198]) by mars.aspenworks.net (8.9.3/8.9.3) with ESMTP id KAA62151; Tue, 7 Dec 1999 10:56:31 -0700 (MST) (envelope-from alex@aspenworks.com) Message-ID: <384D48DB.EC32FE71@aspenworks.com> Date: Tue, 07 Dec 1999 10:50:19 -0700 From: Alex Huppenthal Reply-To: alex@aspenworks.com Organization: Aspenworks.com X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Patrick Mackeown Cc: angelko@saw.net, freebsd-isp@FreeBSD.ORG Subject: Re: RADIUS server: current sessions, radcheck References: <199912070346.DAA04253@NS4.HELP-DESK.CO.UK> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Try this. Use freeradius, run 'radwho' to find out who is on. Run radwho | wc -l to get a count of the current users. Alternatively, use snmpget to fetch the appropriate MIB variable in your portconcentrator (livingston or otherwise). Patrick Mackeown wrote: > > > Hello, > > > > Can anyone tell me how to find out the number of current user > > sessions, and who those users are on a RADIUS server? > > > > Also, is there a document explaining in detail the output of > > radcheck? The man page I have doesn't explain what the values > > are, and I didn't find much info on it on http://www.merit.edu/aaa. > > > > Thanks, > > -angelko > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-isp" in the body of the message > > > Check your radius accounting logging. You may have to write a perl script > if you want to keep track of who regulary logs on and when. > > Patmac > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Dec 7 10:28:27 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mail2.gmx.net (mail2.gmx.net [194.221.183.62]) by hub.freebsd.org (Postfix) with SMTP id BD3A014DC5 for ; Tue, 7 Dec 1999 10:28:24 -0800 (PST) (envelope-from pons@gmx.li) Received: (qmail 7892 invoked by uid 0); 7 Dec 1999 18:28:18 -0000 Received: from unknown (HELO gmx.li) (212.38.131.194) by mail2.gmx.net with SMTP; 7 Dec 1999 18:28:18 -0000 Message-ID: <384D50BA.16A69627@gmx.li> Date: Tue, 07 Dec 1999 20:23:54 +0200 From: pons X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,arabic MIME-Version: 1.0 To: freebsd-isp@FreeBSD.org Subject: Central Server Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi I would like to setup a central server for our Banking system (huge dyn. data). The 2x machines contain the following: . 2 Motorola 604e RISC CPU . 1 MB of level 2 cache memory . 256 MB central memory . 1x 2GB SCSI disk, designed to serve as a boot disk and hold the OS . 6x 4GB SCSI disks, designed to hold database and other data requred by the Company . 3x SCSI host adapters, 2x of which are ultra-Wide SCSI3 adapters 40MB/s and the third a Wide SCSI 2 adapters 20MB/s . 1x 8mm VDAT tape, 12/24 GB tape capacity, to be used for back up and software installation and updates . 2x full duplex Fast Ethernet adapters 100Mbps The 2 sets of 6x 4GB disks are shared between the 2 machines using RAID 1. Would the 2 servers do the task, or should i rewrite the Hardware application of the 2 machines? -- pons@gmx.li To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Dec 7 10:43:31 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id C5DFD1552F; Tue, 7 Dec 1999 10:43:16 -0800 (PST) (envelope-from jataylor@xmission.com) Received: from www by mail.xmission.com with local (Exim 3.03 #3) id 11vPZs-0002WL-00; Tue, 07 Dec 1999 11:43:08 -0700 Content-Length: 1340 X-Originating-IP: [166.70.12.185] Date: Tue, 07 Dec 1999 11:43:08 -700 Subject: Re: user ppp, getty and automatic baud rate detection From: James A.Taylor X-Mailer: IMHO for Roxen MIME-Version: 1.0 Cc: Stuart Henderson , freebsd-questions@freebsd.org, freebsd-isp@freebsd.org Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit To: Brian Somers Message-Id: Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > I just tried logging in via a regular dial-up > > > terminal application rather than ppp and found > > > that at 19200 I get a login prompt however at > > > other speeds all I get is garbage characters. > > > > okay, your modem is set to switch com port speed to the > > actual line speed. I would take a wild guess that it may have > > been used in a wildcat or pcboard bbs before to have been > > set in that way :) You'll need to play with the nonvolatile > > ram settings in the modem and get it to use the more > > standard "fixed com port speed" config and then std.115200 > > should be fine. Until you do this, I think the only speeds > > you'll ever see are 300/1200/2400/4800/9600/19200. > > Once the speed has been put in /etc/ttys (and init HUPd), you also > need to connect to the modem (you can use ppp in command mode) at > the same speed and do a few ATs to train it to that speed. > > -- > Brian Brian's suggestion to train the modem to the new speed was most helpful. The only problem I have is that if the modem loses power you have to re-train it before it will answer. Is their a way to get around this need to re-train or automatically train it before the modem answers each caller? Thanks all for your help James A. Taylor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Dec 7 11:19:19 1999 Delivered-To: freebsd-isp@freebsd.org Received: from bsdie.rwsystems.net (bsdie.rwsystems.net [209.197.223.2]) by hub.freebsd.org (Postfix) with ESMTP id 4B06314DF3; Tue, 7 Dec 1999 11:18:04 -0800 (PST) (envelope-from jwyatt@rwsystems.net) Received: from bsdie.rwsystems.net([209.197.223.2]) (1959 bytes) by bsdie.rwsystems.net via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Tue, 7 Dec 1999 13:12:04 -0600 (CST) (Smail-3.2.0.106 1999-Mar-31 #1 built 1999-Aug-7) Date: Tue, 7 Dec 1999 13:12:04 -0600 (CST) From: James Wyatt To: "James A.Taylor" Cc: Brian Somers , Stuart Henderson , freebsd-questions@freebsd.org, freebsd-isp@freebsd.org Subject: Re: user ppp, getty and automatic baud rate detection In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 7 Dec 1999, James A.Taylor wrote: > > > > I just tried logging in via a regular dial-up > > > > terminal application rather than ppp and found > > > > that at 19200 I get a login prompt however at > > > > other speeds all I get is garbage characters. > > > > > > okay, your modem is set to switch com port speed to the > > > actual line speed. I would take a wild guess that it may have [ ... ] > > Once the speed has been put in /etc/ttys (and init HUPd), you also > > need to connect to the modem (you can use ppp in command mode) at > > the same speed and do a few ATs to train it to that speed. [ ... ] > Brian's suggestion to train the modem to the new speed was most > helpful. The only problem I have is that if the modem loses power > you have to re-train it before it will answer. Is their a way to get > around this need to re-train or automatically train it before the > modem answers each caller? mgetty will do this when init loads it after a power up and after every call. It will also log it so you can be sure it was done. Look at your modem manual as some modems (Codex, MultiTech, ZyXEL, etc...) allow you to lock the DTE speed in EEROM. - Jy@ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Dec 7 12:12:41 1999 Delivered-To: freebsd-isp@freebsd.org Received: from naiad.eclipse.net.uk (naiad.eclipse.net.uk [195.188.32.29]) by hub.freebsd.org (Postfix) with ESMTP id 6BA73154A7; Tue, 7 Dec 1999 12:12:35 -0800 (PST) (envelope-from sh@eclipse.net.uk) Received: from eclipse.net.uk (elara.eclipse.net.uk [195.188.32.31]) by naiad.eclipse.net.uk (Postfix) with ESMTP id ED9B21364E; Tue, 07 Dec 1999 20:12:33 +0000 (GMT) Message-ID: <384D6A67.6794E206@eclipse.net.uk> Date: Tue, 07 Dec 1999 20:13:27 +0000 From: Stuart Henderson Organization: Eclipse Networking X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en-GB MIME-Version: 1.0 To: James Wyatt Cc: "James A.Taylor" , Brian Somers , freebsd-questions@freebsd.org, freebsd-isp@freebsd.org Subject: Re: user ppp, getty and automatic baud rate detection References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Brian's suggestion to train the modem to the new speed was most > > helpful. The only problem I have is that if the modem loses power > > you have to re-train it before it will answer. Is their a way to get > > around this need to re-train or automatically train it before the > > modem answers each caller? Probably, at&w To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Dec 7 12:36:18 1999 Delivered-To: freebsd-isp@freebsd.org Received: from kerouac.deepwell.com (deepwell.com [209.63.174.12]) by hub.freebsd.org (Postfix) with SMTP id B231C14D27 for ; Tue, 7 Dec 1999 12:36:17 -0800 (PST) (envelope-from freebsd@deepwell.com) Received: (qmail 20730 invoked from network); 7 Dec 1999 21:28:02 -0000 Received: from proxy.dcomm.net (HELO terry) (209.63.175.10) by deepwell.com with SMTP; 7 Dec 1999 21:28:02 -0000 Message-Id: <4.2.0.58.19991207122932.03552d90@mail1.dcomm.net> X-Sender: freebsd@mail.deepwell.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Tue, 07 Dec 1999 12:32:47 -0800 To: freebsd-isp@freebsd.org From: Deepwell Internet Subject: httpd log rotate Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm looking for something slightly different. I'm looking to use a daily cron script to append each log file to a compressed logfile, and then resume logging to a new uncompressed log. Many of the logfile analyzers have the ability to read compressed logs. Is there a simple way of doing this that will ensure I don't miss any data? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Dec 7 12:53:12 1999 Delivered-To: freebsd-isp@freebsd.org Received: from dominik.saargate.de (p3E9D37E9.dip0.t-ipconnect.de [62.157.55.233]) by hub.freebsd.org (Postfix) with ESMTP id E11BD14D49 for ; Tue, 7 Dec 1999 12:52:44 -0800 (PST) (envelope-from domi@saargate.de) Received: from localhost (localhost [127.0.0.1]) by dominik.saargate.de (8.9.3/8.9.3) with ESMTP id VAA38406; Tue, 7 Dec 1999 21:51:28 +0100 (CET) (envelope-from domi@saargate.de) Date: Tue, 7 Dec 1999 21:51:28 +0100 (CET) From: Dominik Brettnacher To: "freebsd@deepwell.com" Cc: freebsd-isp@freebsd.org Subject: Re: httpd log rotate In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 7 Dec 1999, freebsd@deepwell.com wrote: > I'm looking for something slightly different. I'm looking to use a daily > cron script to append each log file to a compressed logfile, and then > resume logging to a new uncompressed log. Many of the logfile analyzers > have the ability to read compressed logs. Is there a simple way of doing > this that will ensure I don't miss any data? Firstly, move all logfiles to another directory (on the same partition), then do an apachectl graceful (or something similar). Apache will use the old files until it gets the signal. -- Dominik - http://www.saargate.de/~domi/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Dec 7 13:44:35 1999 Delivered-To: freebsd-isp@freebsd.org Received: from roble.com (roble.com [206.40.34.50]) by hub.freebsd.org (Postfix) with ESMTP id E57C414E0C for ; Tue, 7 Dec 1999 13:44:31 -0800 (PST) (envelope-from sendmail@roble.com) Received: from roble2.roble.com (roble2.roble.com [206.40.34.52]) by roble.com (Roble1b) with SMTP id NAA18661 for ; Tue, 7 Dec 1999 13:44:34 -0800 (PST) Date: Tue, 7 Dec 1999 13:44:31 -0800 (PST) From: Roger Marquis To: freebsd-isp@FreeBSD.ORG Subject: Re: httpd log rotate In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Firstly, move all logfiles to another directory (on the same partition), > then do an apachectl graceful (or something similar). Apache will use the > old files until it gets the signal. This will work as long as you're able to do an `apachectl graceful` without interrupting any downloads in progress or other persistent connections. Otherwise copying (instead of moving) the log files and clearing the originals will accomplish what you need. The later method does have a small windows where log entries could be lost but in practice this doesn't occur except on _very_ heavily loaded servers with slow filesystems. -- Roger Marquis Roble Systems Consulting http://www.roble.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Dec 7 14:32:21 1999 Delivered-To: freebsd-isp@freebsd.org Received: from gamera.comnetcom.net (ns1.comnetcom.net [209.100.247.254]) by hub.freebsd.org (Postfix) with ESMTP id 3072A14E4A for ; Tue, 7 Dec 1999 14:32:19 -0800 (PST) (envelope-from jeff@comnetcom.net) Received: from jeff (laptop.comnetcom.net [209.100.247.124]) by gamera.comnetcom.net (8.9.1/8.9.1) with SMTP id QAA09935 for ; Tue, 7 Dec 1999 16:53:47 -0600 (CST) Message-ID: <012301bf4102$f23bab40$7cf764d1@comnetcom.net> From: "Jeff Tolley" To: Subject: quick question on passwd file. Date: Tue, 7 Dec 1999 16:32:29 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I hope this in the right place. We are currently in the process of migrating our webserver to a better machine. What is the best way to move the users from the old machine to the new machine? Is simply copying over the passwd and master.passwd file's enough? Obviously I'd have to check home directories and shells. Both machines are running FreeBSD. The old machine is running 2.2.6-RELEASE, the newer one is running 3.3-RELEASE. Thanks, Jeff Tolley - jeff@comnetcom.net Senior Systems Adminstrator Com Net Communication Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Dec 7 15:39:37 1999 Delivered-To: freebsd-isp@freebsd.org Received: from awfulhak.org (dynamic-56.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.184]) by hub.freebsd.org (Postfix) with ESMTP id CCE3914F22; Tue, 7 Dec 1999 15:39:28 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA15302; Tue, 7 Dec 1999 23:38:09 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA00597; Tue, 7 Dec 1999 23:24:48 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912072324.XAA00597@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: "James A.Taylor" Cc: Brian Somers , Stuart Henderson , freebsd-questions@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG, brian@hak.lan.awfulhak.org Subject: Re: user ppp, getty and automatic baud rate detection In-Reply-To: Message from "James A.Taylor" of "Tue, 07 Dec 1999 11:43:08." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Dec 1999 23:24:48 +0000 From: Brian Somers Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [.....] > Brian's suggestion to train the modem to the new speed was most > helpful. The only problem I have is that if the modem loses power > you have to re-train it before it will answer. Is their a way to get > around this need to re-train or automatically train it before the > modem answers each caller? There should be something in your modems command set to lock DTR. I can't remember it off the top of my head though :-/ My USR Sportster is certainly smart enough to remember the last DTR speed despite power loss though.... > Thanks all for your help > > James A. Taylor -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Dec 7 15:49: 4 1999 Delivered-To: freebsd-isp@freebsd.org Received: from moat.teksupport.net.au (moat.teksupport.net.au [203.17.1.98]) by hub.freebsd.org (Postfix) with ESMTP id 7F02E14F22; Tue, 7 Dec 1999 15:48:55 -0800 (PST) (envelope-from robseco@wizard.teksupport.net.au) Received: from magician.teksupport.net.au (magician.teksupport.net.au [192.168.1.2]) by moat.teksupport.net.au (8.8.8/8.8.8) with SMTP id KAA25840; Wed, 8 Dec 1999 10:45:52 +1100 (EST) (envelope-from robseco@wizard.teksupport.net.au) Message-Id: <3.0.5.32.19991208094552.00ad3b70@moat-gw.teksupport.net.au> X-Sender: robseco@moat-gw.teksupport.net.au X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 08 Dec 1999 09:45:52 +1000 To: Brian Somers , "James A.Taylor" From: Rob Secombe Subject: Re: user ppp, getty and automatic baud rate detection Cc: Stuart Henderson , freebsd-questions@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG In-Reply-To: <199912072324.XAA00597@hak.lan.Awfulhak.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I believe most modems store the current DTR speed when the config is written to NVRAM (eg at&W0) When they power up they default to the last saved speed. Cheers Rob. At 23:24 07-12-99 +0000, Brian Somers wrote: >[.....] >> Brian's suggestion to train the modem to the new speed was most >> helpful. The only problem I have is that if the modem loses power >> you have to re-train it before it will answer. Is their a way to get >> around this need to re-train or automatically train it before the >> modem answers each caller? > >There should be something in your modems command set to lock DTR. I >can't remember it off the top of my head though :-/ My USR Sportster >is certainly smart enough to remember the last DTR speed despite power >loss though.... > >> Thanks all for your help >> >> James A. Taylor > >-- >Brian > >Don't _EVER_ lose your sense of humour ! > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-isp" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Dec 7 17:24:16 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mercury.jorsm.com (mercury.jorsm.com [207.112.128.9]) by hub.freebsd.org (Postfix) with ESMTP id 4A6BF14F72 for ; Tue, 7 Dec 1999 17:24:05 -0800 (PST) (envelope-from jeff@mercury.jorsm.com) Received: by mercury.jorsm.com (Postfix, from userid 101) id 60849E4A13; Tue, 7 Dec 1999 19:24:01 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by mercury.jorsm.com (Postfix) with ESMTP id 57945E0C01; Tue, 7 Dec 1999 19:24:01 -0600 (CST) Date: Tue, 7 Dec 1999 19:24:01 -0600 (CST) From: Jeff Lynch To: Jeff Tolley Cc: freebsd-isp@FreeBSD.ORG Subject: Re: quick question on passwd file. In-Reply-To: <012301bf4102$f23bab40$7cf764d1@comnetcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 7 Dec 1999, Jeff Tolley wrote: > I hope this in the right place. > We are currently in the process of migrating our webserver to a better > machine. What is the best way to move the users from the old machine to the > new machine? Is simply copying over the passwd and master.passwd file's > enough? Obviously I'd have to check home directories and shells. > Both machines are running FreeBSD. The old machine is running 2.2.6-RELEASE, > the newer one is running 3.3-RELEASE. Jeff, You'll find some differences in the installation password and group files though. Better to merge the old versions with the new on the old system first. There were system usernames and UID/GID changes between 2.2.x and 3.x. Copy over /etc/master.passwd and /etc/group and do a /usr/sbin/pwd_mkdb -p /etc/master.passwd to recreate /etc/passwd, /etc/spwd.db, and /etc/pwd.db on the new machine. Also make sure you're consistent with your use of either DES or MD5 encryption on the old and new machines. libdescrypt will work with MD5 encrypted passwords but not vice versa. Also check for .htaccess and .htpasswd type files. Note the same dependency (DES/MD5) on .htpasswd files as master.passwd. Regards, --jeff ============================================================================ Jeffrey A. Lynch | JORSM Internet, Regional Internet Services email: jeff@jorsm.com | 7 Area Codes in Chicagoland and NW Indiana Voice: (219)322-2180 | 100Mbps+ Connectivity, 56K-DS3, V.90, ISDN Autoresponse: info@jorsm.com | Quality Service, Affordable Prices http://www.jorsm.com | Serving Gov, Biz, Indivds Since 1995 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Dec 8 6:44:34 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 54682150D5 for ; Wed, 8 Dec 1999 06:44:28 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991207213305.48768@mojave.sitaranetworks.com> Date: Tue, 7 Dec 1999 21:33:05 -0500 From: Greg Lehey To: Jeff Tolley , freebsd-isp@FreeBSD.ORG Subject: Re: quick question on passwd file. Reply-To: Greg Lehey References: <012301bf4102$f23bab40$7cf764d1@comnetcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <012301bf4102$f23bab40$7cf764d1@comnetcom.net>; from Jeff Tolley on Tue, Dec 07, 1999 at 04:32:29PM -0600 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tuesday, 7 December 1999 at 16:32:29 -0600, Jeff Tolley wrote: > I hope this in the right place. You're probabbly better off in -questions, since this isn't a specifically ISP issue. > We are currently in the process of migrating our webserver to a > better machine. What is the best way to move the users from the old > machine to the new machine? Is simply copying over the passwd and > master.passwd file's enough? There are in fact two other files, /etc/pwd.db and /etc/spwd.db as well. But you can generate them and /etc/passwd from /etc/master.passwd (thus the name). The "correct" way to do it is with pwd_mkdb(8), which has a reasonable man page. The "easy" way do to it is with vipw(8). You'll have to change something and write it back to fool vipw to start pwd_mkdb, but that's about all you need to do. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Dec 8 7:56:54 1999 Delivered-To: freebsd-isp@freebsd.org Received: from dumbo.familyinet.net (dumbo.familyinet.net [206.105.51.10]) by hub.freebsd.org (Postfix) with ESMTP id F007B14C10 for ; Wed, 8 Dec 1999 07:56:51 -0800 (PST) (envelope-from phill@freebsd.org) Received: from localhost (phill@localhost) by dumbo.familyinet.net (8.9.1/8.9.1) with ESMTP id LAA22447; Wed, 8 Dec 1999 11:10:42 GMT X-Authentication-Warning: dumbo.familyinet.net: phill owned process doing -bs Date: Wed, 8 Dec 1999 11:10:42 +0000 (GMT) From: Phillip Salzman X-Sender: phill@dumbo.familyinet.net To: Jeff Tolley Cc: freebsd-isp@freebsd.org Subject: Re: quick question on passwd file. In-Reply-To: <012301bf4102$f23bab40$7cf764d1@comnetcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Basically. After that, just make sure you run pwd_mkdb to rebuild the password database. -- Phillip Salzman On Tue, 7 Dec 1999, Jeff Tolley wrote: > I hope this in the right place. > We are currently in the process of migrating our webserver to a better > machine. What is the best way to move the users from the old machine to the > new machine? Is simply copying over the passwd and master.passwd file's > enough? Obviously I'd have to check home directories and shells. > Both machines are running FreeBSD. The old machine is running 2.2.6-RELEASE, > the newer one is running 3.3-RELEASE. > > Thanks, > Jeff Tolley - jeff@comnetcom.net > Senior Systems Adminstrator > Com Net Communication Systems, Inc. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Dec 8 10: 3:39 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mail.foznet.com.br (forum.foznet.com.br [200.250.6.4]) by hub.freebsd.org (Postfix) with ESMTP id 270C4156A8 for ; Wed, 8 Dec 1999 10:03:32 -0800 (PST) (envelope-from cybersrs@mail.com) Received: from cybersrs.foz.net (cybersrs.foz.net [200.250.6.32]) by mail.foznet.com.br (8.9.3/8.8.7) with ESMTP id PAA15763 for ; Mon, 6 Dec 1999 15:35:01 -0200 Message-Id: <4.2.0.58.19991206152630.00be61a0@pop.foznet.com.br> X-Sender: lucifer@pop.foznet.com.br X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 06 Dec 1999 15:26:36 -0200 To: freebsd-isp@freebsd.org From: "Sergio Rodrigo Schulte. (CyberSRS)." Subject: subscribe Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Dec 8 10: 3:52 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mail.foznet.com.br (forum.foznet.com.br [200.250.6.4]) by hub.freebsd.org (Postfix) with ESMTP id 85CC0156B9 for ; Wed, 8 Dec 1999 10:03:44 -0800 (PST) (envelope-from cybersrs@mail.com) Received: from cybersrs.foz.net (cybersrs.foz.net [200.250.6.32]) by mail.foznet.com.br (8.9.3/8.8.7) with ESMTP id PAA15737 for ; Mon, 6 Dec 1999 15:34:29 -0200 Message-Id: <4.2.0.58.19991206152552.00c1aa30@pop.foznet.com.br> X-Sender: lucifer@pop.foznet.com.br X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 06 Dec 1999 15:26:04 -0200 To: freebsd-isp@freebsd.org From: "Sergio Rodrigo Schulte. (CyberSRS)." Subject: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Dec 8 11:19:10 1999 Delivered-To: freebsd-isp@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 017FD15BCA for ; Wed, 8 Dec 1999 11:17:10 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id UAA34547 for ; Wed, 8 Dec 1999 20:16:52 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: isp@freebsd.org Subject: portscan detector... From: Poul-Henning Kamp Date: Wed, 08 Dec 1999 20:16:52 +0100 Message-ID: <34545.944680612@critter.freebsd.dk> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a little port-scan detector gadget for FreeBSD which begs to be polished up and turned into a port. I don't have the time however, so I am looking for a volounteer to adopt this baby. The way it works is this: A FreeBSD machine is setup to do packet forwarding and using gated it participates in the routing exchange internal to the ISP. A few selected subnets are routed to this machine, which routes them into a discard interface (if_disc.c). These subnets are not used for "real trafic", and should be inserted between subnets used for dial-in ports, servers etc etc, so that portscans will hit them. A special process listens on the discard interface with BPF and sorts the packets based on to/from IP numbers. Once a trigger level is reached for a certain source IP a host route for that IP is added to the discard interface. The host route is propagated by gated to the ISP's entire network and any host which the attacker tries to scan will send the packets to the this machine rather than back to the attacker, where the special process will catch and log it along with packets received directly. An email report is sent to the admin with the details (see below). The net effect of this is that brute force scans are stopped very quickly after they are detected, and while the attacker can still send packets into the network he will not get his responses back, which protects customers from the attack. If somebody out there wants to explore and extend this idea please drop me an email. Poul-Henning Sample report: REPORT Ass-944657703.990428-212.12.228.18.txt From: Portscan detector Subject: Portscan 1062 packets from 212.12.228.18 Start time (CET): Wed Dec 8 13:55:03 1999 Start time (GMT): Wed Dec 8 12:55:03 1999 End time (CET): Wed Dec 8 13:55:44 1999 End time (GMT): Wed Dec 8 12:55:44 1999 Nslookup reports: Server: ns1.cybercity.dk Address: 212.242.40.3 Name: async-1-16.wayout.net Address: 212.12.228.18 RIPE reports: % Rights restricted by copyright. See http://www.ripe.net/db/dbcopyright.html inetnum: 212.12.224.0 - 212.12.228.255 netname: WAYOUT-NET descr: Wayout Internet Solutions descr: Cairo country: EG admin-c: OA56 tech-c: OA56 status: ASSIGNED PA notify: osama@wayout.net changed: hostmaster@ripe.net 19990924 source: RIPE Direct evidence of portscan: 13:55:03.990428 212.12.228.18.31790 > 212.242.42.20.31789: udp 1 13:55:03.990661 212.12.228.18.31790 > 212.242.42.21.31789: udp 1 13:55:04.127800 212.12.228.18.31790 > 212.242.42.22.31789: udp 1 13:55:04.131398 212.12.228.18.31790 > 212.242.42.23.31789: udp 1 13:55:15.018784 212.12.228.18.31790 > 212.242.49.192.31789: udp 1 13:55:15.018866 212.12.228.18.31790 > 212.242.49.196.31789: udp 1 13:55:15.019237 212.12.228.18.31790 > 212.242.49.193.31789: udp 1 13:55:15.024646 212.12.228.18.31790 > 212.242.49.203.31789: udp 1 13:55:15.025135 212.12.228.18.31790 > 212.242.49.198.31789: udp 1 13:55:15.025627 212.12.228.18.31790 > 212.242.49.197.31789: udp 1 13:55:15.026425 212.12.228.18.31790 > 212.242.49.199.31789: udp 1 13:55:15.026990 212.12.228.18.31790 > 212.242.49.194.31789: udp 1 13:55:15.041194 212.12.228.18.31790 > 212.242.49.204.31789: udp 1 13:55:15.041684 212.12.228.18.31790 > 212.242.49.205.31789: udp 1 13:55:15.044208 212.12.228.18.31790 > 212.242.49.206.31789: udp 1 13:55:15.045131 212.12.228.18.31790 > 212.242.49.207.31789: udp 1 13:55:15.052438 212.12.228.18.31790 > 212.242.49.195.31789: udp 1 13:55:15.240174 212.12.228.18.31790 > 212.242.49.201.31789: udp 1 13:55:15.538129 212.12.228.18.31790 > 212.242.49.202.31789: udp 1 13:55:15.826603 212.12.228.18.31790 > 212.242.49.200.31789: udp 1 Indirect evidence of portscan: 13:55:15.340713 212.242.48.57 > 212.12.228.18: icmp: time exceeded in-transit 13:55:15.461169 146.188.35.50 > 212.12.228.18: icmp: host 212.242.49.242 unreachable 13:55:16.032289 146.188.35.50 > 212.12.228.18: icmp: host 212.242.50.39 unreachable 13:55:16.539245 146.188.35.50 > 212.12.228.18: icmp: host 212.242.50.224 unreachable 13:55:16.916186 212.242.45.67 > 212.12.228.18: icmp: 212.242.45.67 udp port 31789 unreachable 13:55:17.062326 146.188.35.50 > 212.12.228.18: icmp: host 212.242.49.231 unreachable 13:55:17.177550 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.177994 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.189136 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.189462 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.189669 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.236854 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.264502 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.305848 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.306945 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.311862 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.318906 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.332835 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.336927 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.339876 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.342048 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.342825 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.344832 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.376091 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.376904 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.377068 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.381861 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.382842 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.386031 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.386406 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.386902 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.387439 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.396893 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.397396 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.398165 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.398366 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.398858 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.399349 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.401940 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.402339 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.423927 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.430974 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.431298 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.431611 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.431837 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.432014 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.470621 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.493953 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.494874 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.503879 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.510438 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.530612 212.242.51.91 > 212.12.228.18: icmp: 212.242.51.91 udp port 31789 unreachable 13:55:17.600098 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.618790 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.619065 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.619488 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.619589 146.188.35.50 > 212.12.228.18: icmp: host 212.242.51.128 unreachable 13:55:17.619943 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.639704 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.640049 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.642856 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.643961 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.645804 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.646420 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.649859 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.650351 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:17.788966 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.002948 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.133688 146.188.35.50 > 212.12.228.18: icmp: host 212.242.51.207 unreachable 13:55:18.140925 212.242.51.117 > 212.12.228.18: icmp: 212.242.51.117 udp port 31789 unreachable 13:55:18.434339 212.242.48.105 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.435354 212.242.48.105 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.436950 212.242.48.105 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.438097 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.439080 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.445962 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.448186 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.448459 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.448988 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.449442 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.450056 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.450548 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.451191 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.479061 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.480531 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.481023 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.481668 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.501866 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.502486 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.515084 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.515595 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.515920 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.516412 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.516684 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.630941 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:18.657816 146.188.35.50 > 212.12.228.18: icmp: host 212.242.52.66 unreachable 13:55:19.016782 212.242.48.81 > 212.12.228.18: icmp: time exceeded in-transit 13:55:19.117909 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:19.204216 146.188.35.50 > 212.12.228.18: icmp: host 212.242.52.163 unreachable 13:55:19.701806 146.188.35.50 > 212.12.228.18: icmp: host 212.242.52.250 unreachable 13:55:20.207616 146.188.35.50 > 212.12.228.18: icmp: host 212.242.53.70 unreachable 13:55:20.334043 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:20.748088 146.188.35.50 > 212.12.228.18: icmp: host 212.242.53.40 unreachable 13:55:21.260124 146.188.35.50 > 212.12.228.18: icmp: host 212.242.52.228 unreachable 13:55:21.482977 212.242.48.106 > 212.12.228.18: icmp: time exceeded in-transit 13:55:21.776513 146.188.35.50 > 212.12.228.18: icmp: host 212.242.54.101 unreachable 13:55:22.279044 146.188.35.50 > 212.12.228.18: icmp: host 212.242.54.184 unreachable 13:55:22.779377 146.188.35.50 > 212.12.228.18: icmp: host 212.242.55.16 unreachable 13:55:23.289080 146.188.35.50 > 212.12.228.18: icmp: host 212.242.55.112 unreachable 13:55:23.753467 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:23.769457 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:23.769947 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:23.792298 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:23.803373 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:23.807957 212.242.55.194 > 212.12.228.18: icmp: 212.242.55.194 udp port 31789 unreachable 13:55:23.878087 146.188.35.50 > 212.12.228.18: icmp: host 212.242.55.120 unreachable 13:55:23.887256 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:23.968685 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:23.970527 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:23.971798 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:23.972451 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:23.996305 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.019802 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.020008 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.025357 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.025372 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.025700 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.026355 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.026847 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.027338 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.027829 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.042740 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.045524 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.046057 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.046548 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.049129 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.049784 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.050275 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.057492 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.057894 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.064208 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.089803 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.095334 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.098122 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.098648 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.107455 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.107957 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.130386 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.130720 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.249178 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.249995 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.250650 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.252627 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.254427 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.261300 212.242.48.35 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.263252 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.263757 212.242.48.35 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.264257 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.307852 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.310953 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.311158 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.311445 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.311773 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.320620 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.320824 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.321113 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.339793 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.340607 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.341105 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.348515 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.349003 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.349617 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.375675 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.379110 146.188.35.50 > 212.12.228.18: icmp: host 212.242.55.157 unreachable 13:55:24.390416 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.390947 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.416066 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.416301 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.416956 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.417120 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.429613 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.459064 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.478440 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.480239 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.480854 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.489046 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.489539 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.490132 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.524894 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.526236 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.528797 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.545243 212.242.56.85 > 212.12.228.18: icmp: 212.242.56.85 udp port 31789 unreachable 13:55:24.570166 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.581946 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.582433 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.588004 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.588208 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.588510 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.621594 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.622659 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.623106 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.623884 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.624816 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.625267 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.642243 212.242.56.94 > 212.12.228.18: icmp: 212.242.56.94 udp port 31789 unreachable 13:55:24.653445 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.661185 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.662881 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.663698 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.671398 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.692537 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.693844 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.695318 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.695810 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.698759 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.699907 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.700725 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.706300 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.706992 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.707485 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.708630 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.709122 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.709669 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.754629 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.794647 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.796949 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.797463 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.799520 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.802095 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.858216 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.903072 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.912898 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.913387 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.915355 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.919777 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.920924 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.921415 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.921910 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.922241 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.923385 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.923789 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.924078 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.924488 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.924837 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.925253 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.932599 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.935344 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.953735 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.958453 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.979743 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.979950 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.988768 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.989081 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:24.989416 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.008415 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.009438 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.009930 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.011691 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.012183 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.013821 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.014312 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.015623 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.017425 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.018080 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.020089 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.020579 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.022716 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.029221 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.029549 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.043805 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.044415 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.082755 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.084641 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.092464 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.097874 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.098403 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.098894 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.099429 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.112496 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.113040 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.113476 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.113926 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.114418 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.133938 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.144900 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.145384 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.145874 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.149152 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.149808 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.184711 146.188.35.50 > 212.12.228.18: icmp: host 212.242.55.159 unreachable 13:55:25.191599 212.242.56.34 > 212.12.228.18: icmp: 212.242.56.34 udp port 31789 unreachable 13:55:25.196011 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.198304 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.198795 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.199286 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.201332 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.201752 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.202276 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.202727 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.228614 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.235823 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.236315 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.241230 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.246514 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.247133 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.247619 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.248110 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.248601 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.266891 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.267484 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.268917 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.271261 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.271746 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.272537 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.351020 212.242.56.189 > 212.12.228.18: icmp: 212.242.56.189 udp port 31789 unreachable 13:55:25.406726 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.423147 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.423633 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.428015 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.430473 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.435760 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.437069 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.442640 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.446321 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.451262 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.451651 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.454556 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.455191 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.481920 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.484212 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.485072 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.485563 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.486219 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.486833 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.487324 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.487980 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.488348 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.489069 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.491428 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.492896 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.493717 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.494206 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.495354 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.497648 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.500638 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.501088 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.509649 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.511575 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.514237 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.516164 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.516652 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.517963 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.553845 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.554171 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.554505 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.557235 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.557776 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.565640 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.572524 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.573013 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.573504 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.604680 212.242.56.252 > 212.12.228.18: icmp: 212.242.56.252 udp port 31789 unreachable 13:55:25.604964 212.242.56.253 > 212.12.228.18: icmp: 212.242.56.253 udp port 31789 unreachable 13:55:25.612008 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.612171 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.619420 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.623803 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.624294 212.242.48.43 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.653769 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.654155 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.655259 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.657881 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.663657 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.665950 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.677548 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.677869 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.678718 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.680326 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.680893 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.685079 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.724294 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.728168 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.728756 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.756398 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.760939 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.765859 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.773390 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.774022 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.779941 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.786334 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.787478 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.790795 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.791388 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.792701 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.795384 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.795874 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.830282 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.866613 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.874805 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.875296 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.881876 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.883159 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.883652 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.891668 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.892006 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.892854 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.896432 212.242.57.32 > 212.12.228.18: icmp: 212.242.57.32 udp port 31789 unreachable 13:55:25.901550 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.937930 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.938415 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.938917 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.939498 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.939847 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.940503 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.942562 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.943065 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.943762 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.968029 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.994089 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:25.995717 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:26.000344 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:26.002599 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:26.079284 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:26.082061 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:26.096892 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:26.119252 212.242.56.28 > 212.12.228.18: icmp: 212.242.56.28 udp port 31789 unreachable [tos 0xc0] 13:55:26.196592 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:26.236575 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:26.318499 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:26.387024 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:26.439239 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:26.441946 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:26.462182 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:26.478725 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:26.759181 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:26.762167 212.242.48.41 > 212.12.228.18: icmp: time exceeded in-transit 13:55:27.031814 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.043154 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.043639 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.044132 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.045933 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.046431 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.060065 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.060350 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.060735 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.060844 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.061170 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.061376 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.066087 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.090664 212.242.48.33 > 212.12.228.18: icmp: time exceeded in-transit 13:55:27.091092 212.242.56.39 > 212.12.228.18: icmp: 212.242.56.39 udp port 31789 unreachable 13:55:27.174875 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.178314 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.178478 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.179952 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.222061 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.222265 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.222551 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.222879 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.255366 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.255647 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.255973 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.256138 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.256466 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.256670 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.269411 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.270067 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.281044 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.281547 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.281877 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.282026 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.282354 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.325951 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.328765 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.329380 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.331682 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.334500 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.337571 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.338062 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.338554 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.352154 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.357887 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.358378 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.361327 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.398686 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.431944 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.432270 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.432762 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.433091 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.433297 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.433581 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.441815 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.442304 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.474091 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.474703 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.476834 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.522401 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.525332 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.537292 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.548813 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.549347 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.549743 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.567151 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.569965 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.570386 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.570754 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.572682 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.579766 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.580371 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.580707 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.581076 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.588068 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.588573 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.614340 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.617245 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.623144 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.665743 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.666231 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.668566 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.669059 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.674267 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.674911 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.740130 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.740615 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.740984 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.745784 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.748763 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.751427 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.754229 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.758187 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.760203 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.768636 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.769122 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.769613 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.774366 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.842696 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.848306 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.851206 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.905533 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.988013 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.988502 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.990796 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.993745 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.994236 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.994891 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.995055 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.995475 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.995751 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.998797 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:27.999643 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.000134 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.000627 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.000953 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.002429 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.025280 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.025858 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.026349 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.026785 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.027076 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.028521 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.028971 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.029339 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.034585 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.036016 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.036346 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.042572 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.043102 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.065289 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.071118 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.071637 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.072062 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.076811 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.079596 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.080253 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.083899 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.084390 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.091229 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.091680 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.092127 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.092417 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.108269 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.108849 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.111094 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.111754 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.112085 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.112597 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.114251 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.155128 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.158076 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.158567 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.159059 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.160868 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.183636 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.184166 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.184618 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.186680 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.228527 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.234917 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.235408 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.236768 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.238192 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.238684 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.243928 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.244438 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.244910 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.287587 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.290294 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.290464 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.355632 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.376812 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.383531 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.386314 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.389425 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.389917 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.390354 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.390782 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.391064 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.397823 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.403517 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.404007 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.406465 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.406957 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.418837 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.419409 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.419780 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.420227 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.420554 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.420883 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.421251 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.424312 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.427643 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.475772 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.476261 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.477612 146.188.35.50 > 212.12.228.18: icmp: host 212.242.59.6 unreachable 13:55:28.520170 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.685499 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.688310 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.855829 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.861609 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:28.979576 146.188.35.50 > 212.12.228.18: icmp: host 212.242.59.88 unreachable 13:55:29.225032 212.242.48.26 > 212.12.228.18: icmp: source quench 13:55:29.594706 146.188.35.50 > 212.12.228.18: icmp: host 212.242.59.184 unreachable 13:55:30.169062 146.188.35.50 > 212.12.228.18: icmp: host 212.242.59.221 unreachable 13:55:30.754509 146.188.35.50 > 212.12.228.18: icmp: host 212.242.60.139 unreachable 13:55:31.307926 146.188.35.50 > 212.12.228.18: icmp: host 212.242.60.159 unreachable 13:55:31.826242 146.188.35.50 > 212.12.228.18: icmp: host 212.242.61.73 unreachable 13:55:32.384362 146.188.35.50 > 212.12.228.18: icmp: host 212.242.61.160 unreachable 13:55:32.735662 212.242.30.130 > 212.12.228.18: icmp: 212.242.30.130 udp port 31789 unreachable 13:55:32.947962 146.188.35.50 > 212.12.228.18: icmp: host 212.242.61.153 unreachable 13:55:33.455866 146.188.35.50 > 212.12.228.18: icmp: host 212.242.62.100 unreachable 13:55:33.982975 146.188.35.50 > 212.12.228.18: icmp: host 212.242.62.172 unreachable 13:55:34.505961 146.188.35.50 > 212.12.228.18: icmp: host 212.242.63.22 unreachable 13:55:35.032471 146.188.35.50 > 212.12.228.18: icmp: host 212.242.62.200 unreachable 13:55:35.527955 146.188.35.50 > 212.12.228.18: icmp: host 212.242.63.203 unreachable 13:55:35.857744 212.242.64.26 > 212.12.228.18: icmp: 212.242.64.26 udp port 31789 unreachable 13:55:35.890490 212.242.64.27 > 212.12.228.18: icmp: 212.242.64.27 udp port 31789 unreachable 13:55:35.895898 212.242.64.31 > 212.12.228.18: icmp: 212.242.64.31 udp port 31789 unreachable [tos 0xc0] 13:55:35.900722 192.168.70.2 > 212.12.228.18: icmp: 212.242.64.1 udp port 31789 unreachable [tos 0xc0] 13:55:35.967857 212.242.64.17 > 212.12.228.18: icmp: 212.242.64.17 udp port 31789 unreachable 13:55:35.989347 192.168.72.2 > 212.12.228.18: icmp: 212.242.64.24 udp port 31789 unreachable 13:55:36.000887 212.242.64.25 > 212.12.228.18: icmp: 212.242.64.25 udp port 31789 unreachable 13:55:36.025084 212.242.64.35 > 212.12.228.18: icmp: 212.242.64.35 udp port 31789 unreachable 13:55:36.033329 212.242.64.28 > 212.12.228.18: icmp: 212.242.64.28 udp port 31789 unreachable 13:55:36.034615 212.242.64.29 > 212.12.228.18: icmp: 212.242.64.29 udp port 31789 unreachable 13:55:36.065177 212.242.41.113 > 212.12.228.18: icmp: time exceeded in-transit 13:55:36.065501 212.242.41.113 > 212.12.228.18: icmp: time exceeded in-transit 13:55:36.066689 146.188.35.50 > 212.12.228.18: icmp: host 212.242.63.153 unreachable 13:55:36.075176 212.242.64.43 > 212.12.228.18: icmp: 212.242.64.43 udp port 31789 unreachable 13:55:36.077372 192.168.76.6 > 212.12.228.18: icmp: 212.242.64.33 udp port 31789 unreachable 13:55:36.095159 212.242.41.113 > 212.12.228.18: icmp: time exceeded in-transit 13:55:36.121208 212.242.41.114 > 212.12.228.18: icmp: time exceeded in-transit 13:55:36.123173 212.242.41.114 > 212.12.228.18: icmp: time exceeded in-transit 13:55:36.138823 212.242.64.67 > 212.12.228.18: icmp: 212.242.64.67 udp port 31789 unreachable 13:55:36.152675 212.242.64.66 > 212.12.228.18: icmp: 212.242.64.66 udp port 31789 unreachable 13:55:36.165950 192.168.74.2 > 212.12.228.18: icmp: 212.242.64.41 udp port 31789 unreachable 13:55:36.167409 212.242.64.74 > 212.12.228.18: icmp: 212.242.64.74 udp port 31789 unreachable 13:55:36.171834 212.242.64.37 > 212.12.228.18: icmp: 212.242.64.37 udp port 31789 unreachable 13:55:36.199195 212.242.41.113 > 212.12.228.18: icmp: 212.242.64.53 udp port 31789 unreachable 13:55:36.203127 212.242.41.114 > 212.12.228.18: icmp: time exceeded in-transit 13:55:36.203539 212.242.41.114 > 212.12.228.18: icmp: time exceeded in-transit 13:55:36.234133 212.242.41.114 > 212.12.228.18: icmp: time exceeded in-transit 13:55:36.274110 212.242.41.113 > 212.12.228.18: icmp: time exceeded in-transit 13:55:36.274395 212.242.41.113 > 212.12.228.18: icmp: time exceeded in-transit 13:55:36.275214 212.242.41.114 > 212.12.228.18: icmp: time exceeded in-transit 13:55:36.284397 192.168.71.6 > 212.12.228.18: icmp: 212.242.64.65 udp port 31789 unreachable 13:55:36.312631 212.242.64.68 > 212.12.228.18: icmp: 212.242.64.68 udp port 31789 unreachable 13:55:36.315530 212.242.64.76 > 212.12.228.18: icmp: 212.242.64.76 udp port 31789 unreachable 13:55:36.318045 212.242.64.30 > 212.12.228.18: icmp: 212.242.64.30 udp port 31789 unreachable 13:55:36.329803 212.242.64.80 > 212.12.228.18: icmp: 212.242.64.80 udp port 31789 unreachable 13:55:36.329946 212.242.64.81 > 212.12.228.18: icmp: 212.242.64.81 udp port 31789 unreachable 13:55:36.413224 212.242.64.91 > 212.12.228.18: icmp: 212.242.64.91 udp port 31789 unreachable 13:55:36.425507 212.242.64.95 > 212.12.228.18: icmp: 212.242.64.95 udp port 31789 unreachable 13:55:36.433003 212.242.64.94 > 212.12.228.18: icmp: 212.242.64.94 udp port 31789 unreachable [tos 0xc0] 13:55:36.556865 212.242.64.92 > 212.12.228.18: icmp: 212.242.64.92 udp port 31789 unreachable [tos 0xc0] 13:55:36.600232 192.168.70.6 > 212.12.228.18: icmp: host 212.242.64.162 unreachable 13:55:36.651116 212.242.64.170 > 212.12.228.18: icmp: 212.242.64.170 udp port 31789 unreachable (DF) 13:55:36.654846 212.242.64.170 > 212.12.228.18: icmp: 212.242.64.170 udp port 31789 unreachable (DF) 13:55:36.659027 212.242.64.170 > 212.12.228.18: icmp: 212.242.64.170 udp port 31789 unreachable (DF) 13:55:36.689722 212.242.64.148 > 212.12.228.18: icmp: 212.242.64.148 udp port 31789 unreachable 13:55:36.704483 212.242.64.178 > 212.12.228.18: icmp: 212.242.64.178 udp port 31789 unreachable [tos 0xc0] 13:55:36.760557 192.168.76.9 > 212.12.228.18: icmp: time exceeded in-transit 13:55:36.763137 192.168.76.9 > 212.12.228.18: icmp: time exceeded in-transit 13:55:36.802544 192.168.72.6 > 212.12.228.18: icmp: 212.242.64.169 udp port 31789 unreachable 13:55:36.807585 212.242.64.170 > 212.12.228.18: icmp: 212.242.64.170 udp port 31789 unreachable (DF) 13:55:36.811754 212.242.64.170 > 212.12.228.18: icmp: 212.242.64.170 udp port 31789 unreachable (DF) 13:55:36.846779 212.242.64.190 > 212.12.228.18: icmp: 212.242.64.190 udp port 31789 unreachable [tos 0xc0] 13:55:36.856409 212.242.64.177 > 212.12.228.18: icmp: 212.242.64.177 udp port 31789 unreachable [tos 0xc0] 13:55:36.864726 212.242.64.180 > 212.12.228.18: icmp: 212.242.64.180 udp port 31789 unreachable [tos 0xc0] 13:55:36.884378 212.242.64.194 > 212.12.228.18: icmp: 212.242.64.194 udp port 31789 unreachable 13:55:36.885100 212.242.64.195 > 212.12.228.18: icmp: 212.242.64.195 udp port 31789 unreachable 13:55:36.917473 212.242.64.184 > 212.12.228.18: icmp: 212.242.64.184 udp port 31789 unreachable [tos 0xc0] 13:55:36.927140 192.168.76.10 > 212.12.228.18: icmp: time exceeded in-transit [tos 0xc0] 13:55:36.938609 212.242.64.17 > 212.12.228.18: icmp: host 212.242.64.19 unreachable 13:55:36.947294 212.242.64.17 > 212.12.228.18: icmp: host 212.242.64.22 unreachable 13:55:36.948766 212.242.64.210 > 212.12.228.18: icmp: 212.242.64.210 udp port 31789 unreachable [tos 0xc0] 13:55:36.971213 212.242.41.113 > 212.12.228.18: icmp: time exceeded in-transit 13:55:36.991201 212.242.64.189 > 212.12.228.18: icmp: 212.242.64.189 udp port 31789 unreachable [tos 0xc0] 13:55:37.011574 212.242.64.179 > 212.12.228.18: icmp: 212.242.64.179 udp port 31789 unreachable [tos 0xc0] 13:55:37.012868 192.168.75.2 > 212.12.228.18: icmp: 212.242.64.193 udp port 31789 unreachable 13:55:37.018677 192.168.72.14 > 212.12.228.18: icmp: 212.242.64.201 udp port 31789 unreachable [tos 0xc0] 13:55:37.022905 212.242.64.226 > 212.12.228.18: icmp: 212.242.64.226 udp port 31789 unreachable 13:55:37.025811 212.242.64.196 > 212.12.228.18: icmp: 212.242.64.196 udp port 31789 unreachable 13:55:37.028596 212.242.64.214 > 212.12.228.18: icmp: 212.242.64.214 udp port 31789 unreachable 13:55:37.030791 212.242.64.231 > 212.12.228.18: icmp: 212.242.64.231 udp port 31789 unreachable 13:55:37.054777 192.168.70.10 > 212.12.228.18: icmp: 212.242.64.209 udp port 31789 unreachable 13:55:37.134826 212.242.64.243 > 212.12.228.18: icmp: 212.242.64.243 udp port 31789 unreachable 13:55:37.143174 212.242.64.242 > 212.12.228.18: icmp: 212.242.64.242 udp port 31789 unreachable 13:55:37.160566 192.168.72.10 > 212.12.228.18: icmp: 212.242.64.225 udp port 31789 unreachable 13:55:37.176683 212.242.64.220 > 212.12.228.18: icmp: 212.242.64.220 udp port 31789 unreachable [tos 0xc0] 13:55:37.191012 212.242.64.250 > 212.12.228.18: icmp: 212.242.64.250 udp port 31789 unreachable 13:55:37.268918 212.242.64.240 > 212.12.228.18: icmp: 212.242.64.240 udp port 31789 unreachable 13:55:37.281066 212.242.64.244 > 212.12.228.18: icmp: 212.242.64.244 udp port 31789 unreachable 13:55:37.314250 212.242.64.252 > 212.12.228.18: icmp: 212.242.64.252 udp port 31789 unreachable 13:55:37.319583 212.242.64.222 > 212.12.228.18: icmp: 212.242.64.222 udp port 31789 unreachable 13:55:37.368205 192.168.75.6 > 212.12.228.18: icmp: 212.242.65.1 udp port 31789 unreachable 13:55:37.380067 212.242.64.245 > 212.12.228.18: icmp: 212.242.64.245 udp port 31789 unreachable 13:55:37.411471 212.242.65.34 > 212.12.228.18: icmp: 212.242.65.34 udp port 31789 unreachable 13:55:37.415386 212.242.65.35 > 212.12.228.18: icmp: 212.242.65.35 udp port 31789 unreachable 13:55:37.450796 212.242.65.42 > 212.12.228.18: icmp: 212.242.65.42 udp port 31789 unreachable 13:55:37.454784 212.242.65.43 > 212.12.228.18: icmp: 212.242.65.43 udp port 31789 unreachable 13:55:37.478176 212.242.65.51 > 212.12.228.18: icmp: 212.242.65.51 udp port 31789 unreachable 13:55:37.520813 192.168.72.18 > 212.12.228.18: icmp: 212.242.65.33 udp port 31789 unreachable 13:55:37.527040 212.242.64.248 > 212.12.228.18: icmp: 212.242.64.248 udp port 31789 unreachable 13:55:37.550859 212.242.65.37 > 212.12.228.18: icmp: 212.242.65.37 udp port 31789 unreachable 13:55:37.565668 212.242.65.40 > 212.12.228.18: icmp: 212.242.65.40 udp port 31789 unreachable 13:55:37.569114 212.242.65.41 > 212.12.228.18: icmp: 212.242.65.41 udp port 31789 unreachable 13:55:37.576492 212.242.65.34 > 212.12.228.18: icmp: 212.242.65.49 udp port 31789 unreachable 13:55:37.580602 212.242.65.45 > 212.12.228.18: icmp: 212.242.65.45 udp port 31789 unreachable 13:55:37.584661 212.242.65.44 > 212.12.228.18: icmp: 212.242.65.44 udp port 31789 unreachable 13:55:37.607582 212.242.65.75 > 212.12.228.18: icmp: 212.242.65.75 udp port 31789 unreachable 13:55:37.634652 212.242.64.188 > 212.12.228.18: icmp: 212.242.64.188 udp port 31789 unreachable [tos 0xc0] 13:55:37.665028 192.168.74.6 > 212.12.228.18: icmp: 212.242.65.69 udp port 31789 unreachable [tos 0xc0] 13:55:37.667435 212.242.65.82 > 212.12.228.18: icmp: 212.242.65.82 udp port 31789 unreachable 13:55:37.718049 212.242.65.76 > 212.12.228.18: icmp: 212.242.65.76 udp port 31789 unreachable 13:55:37.769248 192.168.72.34 > 212.12.228.18: icmp: 212.242.65.81 udp port 31789 unreachable [tos 0xc0] 13:55:37.922806 195.24.23.18 > 212.12.228.18: icmp: host 212.242.65.100 unreachable 13:55:37.928204 212.242.65.130 > 212.12.228.18: icmp: 212.242.65.130 udp port 31789 unreachable 13:55:37.930569 212.242.64.17 > 212.12.228.18: icmp: host 212.242.64.20 unreachable 13:55:37.936539 212.242.64.17 > 212.12.228.18: icmp: host 212.242.64.21 unreachable 13:55:37.967334 192.168.72.30 > 212.12.228.18: icmp: 212.242.65.113 udp port 31789 unreachable [tos 0xc0] 13:55:38.027828 212.242.65.133 > 212.12.228.18: icmp: 212.242.65.133 udp port 31789 unreachable 13:55:38.101594 212.242.65.135 > 212.12.228.18: icmp: 212.242.65.135 udp port 31789 unreachable 13:55:38.144478 212.242.65.142 > 212.12.228.18: icmp: 212.242.65.142 udp port 31789 unreachable 13:55:38.182856 212.242.65.39 > 212.12.228.18: icmp: 212.242.65.39 udp port 31789 unreachable 13:55:38.202636 192.168.70.14 > 212.12.228.18: icmp: host 212.242.65.162 unreachable - admin prohibited filter 13:55:38.218540 212.242.65.136 > 212.12.228.18: icmp: 212.242.65.136 udp port 31789 unreachable 13:55:38.255924 212.242.65.134 > 212.12.228.18: icmp: 212.242.65.134 udp port 31789 unreachable 13:55:38.314441 212.242.65.178 > 212.12.228.18: icmp: 212.242.65.178 udp port 31789 unreachable 13:55:38.390077 212.242.65.190 > 212.12.228.18: icmp: 212.242.65.190 udp port 31789 unreachable 13:55:38.458451 192.168.78.2 > 212.12.228.18: icmp: 212.242.65.177 udp port 31789 unreachable [tos 0xc0] 13:55:38.466350 212.242.65.180 > 212.12.228.18: icmp: 212.242.65.180 udp port 31789 unreachable 13:55:38.517421 192.168.77.18 > 212.12.228.18: icmp: 212.242.65.185 udp port 31789 unreachable 13:55:38.525081 212.242.65.186 > 212.12.228.18: icmp: 212.242.65.184 udp port 31789 unreachable 13:55:38.533107 212.242.65.188 > 212.12.228.18: icmp: 212.242.65.188 udp port 31789 unreachable 13:55:38.535365 192.168.72.38 > 212.12.228.18: icmp: host 212.242.65.242 unreachable - admin prohibited filter 13:55:38.603820 192.168.72.22 > 212.12.228.18: icmp: 212.242.66.1 udp port 31789 unreachable 13:55:38.606392 212.242.65.181 > 212.12.228.18: icmp: 212.242.65.181 udp port 31789 unreachable 13:55:38.614607 212.242.66.4 > 212.12.228.18: icmp: 212.242.66.4 udp port 31789 unreachable 13:55:38.619549 212.242.66.5 > 212.12.228.18: icmp: 212.242.66.5 udp port 31789 unreachable 13:55:38.715137 212.242.65.187 > 212.12.228.18: icmp: 212.242.65.187 udp port 31789 unreachable 13:55:38.800657 192.168.70.14 > 212.12.228.18: icmp: host 212.242.65.166 unreachable - admin prohibited filter 13:55:38.846438 212.242.65.90 > 212.12.228.18: icmp: 212.242.65.90 udp port 31789 unreachable [tos 0xc0] 13:55:38.884050 212.242.65.189 > 212.12.228.18: icmp: 212.242.65.189 udp port 31789 unreachable 13:55:38.900082 212.242.64.251 > 212.12.228.18: icmp: 212.242.64.251 udp port 31789 unreachable 13:55:38.913999 212.242.66.30 > 212.12.228.18: icmp: 212.242.66.30 udp port 31789 unreachable 13:55:38.919117 212.242.65.186 > 212.12.228.18: icmp: 212.242.65.186 udp port 31789 unreachable 13:55:38.971047 212.242.66.65 > 212.12.228.18: icmp: 212.242.66.65 udp port 31789 unreachable 13:55:39.003448 212.242.66.68 > 212.12.228.18: icmp: 212.242.66.68 udp port 31789 unreachable 13:55:39.019678 212.242.65.114 > 212.12.228.18: icmp: 212.242.65.114 udp port 31789 unreachable [tos 0xc0] 13:55:39.086569 212.242.66.67 > 212.12.228.18: icmp: 212.242.66.67 udp port 31789 unreachable 13:55:39.129808 212.242.66.77 > 212.12.228.18: icmp: 212.242.66.77 udp port 31789 unreachable 13:55:39.315823 212.242.66.90 > 212.12.228.18: icmp: 212.242.66.90 udp port 31789 unreachable 13:55:39.331971 212.242.66.102 > 212.12.228.18: icmp: 212.242.66.102 udp port 31789 unreachable 13:55:39.336107 212.242.66.98 > 212.12.228.18: icmp: 212.242.66.98 udp port 31789 unreachable 13:55:39.498428 192.168.72.38 > 212.12.228.18: icmp: host 212.242.65.250 unreachable - admin prohibited filter 13:55:39.688822 192.168.74.10 > 212.12.228.18: icmp: 212.242.65.145 udp port 31789 unreachable 13:55:39.942670 212.242.65.74 > 212.12.228.18: icmp: 212.242.65.74 udp port 31789 unreachable 13:55:40.106011 212.242.67.1 > 212.12.228.18: icmp: 212.242.67.1 udp port 31789 unreachable 13:55:40.522627 212.242.41.65 > 212.12.228.18: icmp: 212.242.67.65 udp port 31789 unreachable 13:55:40.628788 192.168.75.14 > 212.12.228.18: icmp: 212.242.67.97 udp port 31789 unreachable 13:55:40.689569 212.242.67.105 > 212.12.228.18: icmp: 212.242.67.105 udp port 31789 unreachable 13:55:40.717008 212.242.67.124 > 212.12.228.18: icmp: 212.242.67.124 udp port 31789 unreachable 13:55:40.725121 212.242.67.98 > 212.12.228.18: icmp: 212.242.67.98 udp port 31789 unreachable [tos 0xc0] 13:55:40.786893 212.242.67.106 > 212.12.228.18: icmp: 212.242.67.106 udp port 31789 unreachable 13:55:40.787450 212.242.67.107 > 212.12.228.18: icmp: 212.242.67.107 udp port 31789 unreachable 13:55:40.800538 212.242.67.123 > 212.12.228.18: icmp: 212.242.67.123 udp port 31789 unreachable 13:55:40.803477 212.242.67.74 > 212.12.228.18: icmp: host 212.242.67.128 unreachable 13:55:40.804746 212.242.67.74 > 212.12.228.18: icmp: host 212.242.67.129 unreachable 13:55:40.807040 212.242.67.108 > 212.12.228.18: icmp: 212.242.67.108 udp port 31789 unreachable 13:55:40.829201 212.242.67.74 > 212.12.228.18: icmp: host 212.242.67.132 unreachable 13:55:40.836119 212.242.67.74 > 212.12.228.18: icmp: host 212.242.67.133 unreachable 13:55:40.836209 212.242.67.74 > 212.12.228.18: icmp: host 212.242.67.136 unreachable 13:55:40.836530 212.242.67.74 > 212.12.228.18: icmp: host 212.242.67.137 unreachable 13:55:40.844068 212.242.67.74 > 212.12.228.18: icmp: host 212.242.67.140 unreachable 13:55:40.852014 192.168.72.42 > 212.12.228.18: icmp: host 212.242.67.144 unreachable 13:55:40.876085 212.242.67.126 > 212.12.228.18: icmp: 212.242.67.126 udp port 31789 unreachable 13:55:40.894366 212.242.67.74 > 212.12.228.18: icmp: host 212.242.67.131 unreachable 13:55:40.918779 212.242.67.74 > 212.12.228.18: icmp: host 212.242.67.134 unreachable 13:55:40.919014 212.242.67.74 > 212.12.228.18: icmp: host 212.242.67.135 unreachable 13:55:40.919269 212.242.67.74 > 212.12.228.18: icmp: host 212.242.67.139 unreachable 13:55:40.919598 212.242.67.74 > 212.12.228.18: icmp: host 212.242.67.138 unreachable 13:55:40.944176 212.242.67.74 > 212.12.228.18: icmp: host 212.242.67.130 unreachable 13:55:40.944387 212.242.67.74 > 212.12.228.18: icmp: host 212.242.67.143 unreachable 13:55:40.944869 212.242.67.142 > 212.12.228.18: icmp: 212.242.67.142 udp port 31789 unreachable (DF) 13:55:41.001045 212.242.67.104 > 212.12.228.18: icmp: 212.242.67.104 udp port 31789 unreachable [tos 0xc0] 13:55:41.036710 212.242.67.165 > 212.12.228.18: icmp: 212.242.67.165 udp port 31789 unreachable 13:55:41.040697 212.242.67.168 > 212.12.228.18: icmp: 212.242.67.168 udp port 31789 unreachable 13:55:41.043647 212.242.67.169 > 212.12.228.18: icmp: 212.242.67.169 udp port 31789 unreachable 13:55:41.070344 192.168.72.54 > 212.12.228.18: icmp: 212.242.67.69 udp port 31789 unreachable 13:55:41.074042 212.242.67.70 > 212.12.228.18: icmp: 212.242.67.70 udp port 31789 unreachable [tos 0xc0] 13:55:41.083896 212.242.67.122 > 212.12.228.18: icmp: 212.242.67.122 udp port 31789 unreachable 13:55:41.148587 192.168.72.46 > 212.12.228.18: icmp: 212.242.67.177 udp port 31789 unreachable [tos 0xc0] 13:55:41.190387 212.242.67.167 > 212.12.228.18: icmp: 212.242.67.167 udp port 31789 unreachable 13:55:41.193284 212.242.67.163 > 212.12.228.18: icmp: 212.242.67.163 udp port 31789 unreachable 13:55:41.195248 212.242.67.166 > 212.12.228.18: icmp: 212.242.67.166 udp port 31789 unreachable 13:55:41.197278 212.242.67.170 > 212.12.228.18: icmp: 212.242.67.170 udp port 31789 unreachable 13:55:41.198450 192.168.73.18 > 212.12.228.18: icmp: 212.242.67.193 udp port 31789 unreachable 13:55:41.213361 212.242.67.196 > 212.12.228.18: icmp: 212.242.67.196 udp port 31789 unreachable 13:55:41.268291 212.242.67.213 > 212.12.228.18: icmp: 212.242.67.213 udp port 31789 unreachable 13:55:41.274314 212.242.67.212 > 212.12.228.18: icmp: 212.242.67.212 udp port 31789 unreachable 13:55:41.290465 212.242.67.194 > 212.12.228.18: icmp: 212.242.67.194 udp port 31789 unreachable 13:55:41.341831 212.242.67.211 > 212.12.228.18: icmp: 212.242.67.211 udp port 31789 unreachable 13:55:41.372174 212.242.67.214 > 212.12.228.18: icmp: 212.242.67.214 udp port 31789 unreachable 13:55:41.379994 212.242.67.217 > 212.12.228.18: icmp: 212.242.67.217 udp port 31789 unreachable 13:55:41.380217 212.242.67.216 > 212.12.228.18: icmp: 212.242.67.216 udp port 31789 unreachable 13:55:41.408181 212.242.67.228 > 212.12.228.18: icmp: 212.242.67.228 udp port 31789 unreachable 13:55:41.467322 212.242.67.218 > 212.12.228.18: icmp: 212.242.67.218 udp port 31789 unreachable 13:55:41.498614 212.242.67.226 > 212.12.228.18: icmp: 212.242.67.226 udp port 31789 unreachable 13:55:41.568631 212.242.68.14 > 212.12.228.18: icmp: 212.242.68.14 udp port 31789 unreachable 13:55:41.570679 212.242.68.15 > 212.12.228.18: icmp: 212.242.68.15 udp port 31789 unreachable 13:55:41.601672 212.242.68.19 > 212.12.228.18: icmp: 212.242.68.19 udp port 31789 unreachable 13:55:41.639884 212.242.68.12 > 212.12.228.18: icmp: 212.242.68.12 udp port 31789 unreachable 13:55:41.642628 212.242.68.13 > 212.12.228.18: icmp: 212.242.68.13 udp port 31789 unreachable 13:55:41.652623 212.242.68.16 > 212.12.228.18: icmp: 212.242.68.16 udp port 31789 unreachable 13:55:41.688545 212.242.68.17 > 212.12.228.18: icmp: 212.242.68.17 udp port 31789 unreachable 13:55:41.692599 212.242.68.20 > 212.12.228.18: icmp: 212.242.68.20 udp port 31789 unreachable 13:55:41.700955 212.242.68.22 > 212.12.228.18: icmp: 212.242.68.22 udp port 31789 unreachable 13:55:41.702593 212.242.68.23 > 212.12.228.18: icmp: 212.242.68.23 udp port 31789 unreachable 13:55:41.712588 212.242.68.26 > 212.12.228.18: icmp: 212.242.68.26 udp port 31789 unreachable 13:55:41.717550 212.242.68.27 > 212.12.228.18: icmp: 212.242.68.27 udp port 31789 unreachable 13:55:41.728520 212.242.68.30 > 212.12.228.18: icmp: 212.242.68.30 udp port 31789 unreachable 13:55:41.731591 212.242.68.34 > 212.12.228.18: icmp: 212.242.68.34 udp port 31789 unreachable 13:55:41.736549 212.242.68.35 > 212.12.228.18: icmp: 212.242.68.35 udp port 31789 unreachable 13:55:41.740767 212.242.68.38 > 212.12.228.18: icmp: 212.242.68.38 udp port 31789 unreachable 13:55:41.753425 212.242.68.42 > 212.12.228.18: icmp: 212.242.68.42 udp port 31789 unreachable 13:55:41.753785 212.242.68.43 > 212.12.228.18: icmp: 212.242.68.43 udp port 31789 unreachable 13:55:41.796643 212.242.68.21 > 212.12.228.18: icmp: 212.242.68.21 udp port 31789 unreachable 13:55:41.900519 212.242.68.46 > 212.12.228.18: icmp: 212.242.68.46 udp port 31789 unreachable 13:55:41.905958 212.242.68.47 > 212.12.228.18: icmp: 212.242.68.47 udp port 31789 unreachable 13:55:41.909521 212.242.68.24 > 212.12.228.18: icmp: 212.242.68.24 udp port 31789 unreachable 13:55:41.914600 212.242.68.51 > 212.12.228.18: icmp: 212.242.68.51 udp port 31789 unreachable 13:55:41.918736 212.242.68.50 > 212.12.228.18: icmp: 212.242.68.50 udp port 31789 unreachable 13:55:41.953707 212.242.68.25 > 212.12.228.18: icmp: 212.242.68.25 udp port 31789 unreachable 13:55:41.958508 212.242.68.29 > 212.12.228.18: icmp: 212.242.68.29 udp port 31789 unreachable 13:55:41.963589 212.242.68.33 > 212.12.228.18: icmp: 212.242.68.33 udp port 31789 unreachable 13:55:41.969578 212.242.68.37 > 212.12.228.18: icmp: 212.242.68.37 udp port 31789 unreachable 13:55:41.975057 212.242.68.54 > 212.12.228.18: icmp: 212.242.68.54 udp port 31789 unreachable 13:55:41.978548 212.242.68.55 > 212.12.228.18: icmp: 212.242.68.55 udp port 31789 unreachable 13:55:41.984563 212.242.68.58 > 212.12.228.18: icmp: 212.242.68.58 udp port 31789 unreachable 13:55:41.989735 212.242.68.59 > 212.12.228.18: icmp: 212.242.68.59 udp port 31789 unreachable 13:55:41.994811 212.242.68.62 > 212.12.228.18: icmp: 212.242.68.62 udp port 31789 unreachable 13:55:42.002131 212.242.68.57 > 212.12.228.18: icmp: 212.242.68.57 udp port 31789 unreachable 13:55:42.004875 212.242.68.63 > 212.12.228.18: icmp: 212.242.68.63 udp port 31789 unreachable 13:55:42.008521 212.242.68.44 > 212.12.228.18: icmp: 212.242.68.44 udp port 31789 unreachable 13:55:42.012576 212.242.68.36 > 212.12.228.18: icmp: 212.242.68.36 udp port 31789 unreachable 13:55:42.017712 212.242.68.45 > 212.12.228.18: icmp: 212.242.68.45 udp port 31789 unreachable 13:55:42.022570 212.242.68.48 > 212.12.228.18: icmp: 212.242.68.48 udp port 31789 unreachable 13:55:42.031580 212.242.68.49 > 212.12.228.18: icmp: 212.242.68.49 udp port 31789 unreachable 13:55:42.036537 212.242.68.52 > 212.12.228.18: icmp: 212.242.68.52 udp port 31789 unreachable 13:55:42.045015 212.242.68.28 > 212.12.228.18: icmp: 212.242.68.28 udp port 31789 unreachable 13:55:42.046530 212.242.68.53 > 212.12.228.18: icmp: 212.242.68.53 udp port 31789 unreachable 13:55:42.050586 212.242.68.60 > 212.12.228.18: icmp: 212.242.68.60 udp port 31789 unreachable 13:55:42.055550 212.242.68.56 > 212.12.228.18: icmp: 212.242.68.56 udp port 31789 unreachable 13:55:42.059546 212.242.68.61 > 212.12.228.18: icmp: 212.242.68.61 udp port 31789 unreachable 13:55:42.212632 212.242.68.66 > 212.12.228.18: icmp: 212.242.68.66 udp port 31789 unreachable 13:55:42.218521 212.242.68.67 > 212.12.228.18: icmp: 212.242.68.67 udp port 31789 unreachable 13:55:42.228516 212.242.68.70 > 212.12.228.18: icmp: 212.242.68.70 udp port 31789 unreachable 13:55:42.233594 212.242.68.71 > 212.12.228.18: icmp: 212.242.68.71 udp port 31789 unreachable 13:55:42.237526 212.242.68.74 > 212.12.228.18: icmp: 212.242.68.74 udp port 31789 unreachable 13:55:42.242647 212.242.68.75 > 212.12.228.18: icmp: 212.242.68.75 udp port 31789 unreachable 13:55:42.249984 212.242.68.78 > 212.12.228.18: icmp: 212.242.68.78 udp port 31789 unreachable 13:55:42.252599 212.242.68.99 > 212.12.228.18: icmp: 212.242.68.99 udp port 31789 unreachable 13:55:42.262601 212.242.68.79 > 212.12.228.18: icmp: 212.242.68.79 udp port 31789 unreachable 13:55:42.263579 212.242.68.83 > 212.12.228.18: icmp: 212.242.68.83 udp port 31789 unreachable 13:55:42.268532 212.242.68.82 > 212.12.228.18: icmp: 212.242.68.82 udp port 31789 unreachable 13:55:42.273571 212.242.68.86 > 212.12.228.18: icmp: 212.242.68.86 udp port 31789 unreachable 13:55:42.280615 212.242.68.90 > 212.12.228.18: icmp: 212.242.68.90 udp port 31789 unreachable 13:55:42.285539 212.242.68.91 > 212.12.228.18: icmp: 212.242.68.91 udp port 31789 unreachable 13:55:42.290754 212.242.68.94 > 212.12.228.18: icmp: 212.242.68.94 udp port 31789 unreachable 13:55:42.295543 212.242.68.95 > 212.12.228.18: icmp: 212.242.68.95 udp port 31789 unreachable 13:55:42.300613 212.242.68.98 > 212.12.228.18: icmp: 212.242.68.98 udp port 31789 unreachable 13:55:42.305530 212.242.68.102 > 212.12.228.18: icmp: 212.242.68.102 udp port 31789 unreachable 13:55:42.311591 212.242.68.103 > 212.12.228.18: icmp: 212.242.68.103 udp port 31789 unreachable 13:55:42.315570 212.242.68.106 > 212.12.228.18: icmp: 212.242.68.106 udp port 31789 unreachable 13:55:42.321585 212.242.68.111 > 212.12.228.18: icmp: 212.242.68.111 udp port 31789 unreachable 13:55:42.332399 212.242.68.64 > 212.12.228.18: icmp: 212.242.68.64 udp port 31789 unreachable 13:55:42.334528 212.242.68.114 > 212.12.228.18: icmp: 212.242.68.114 udp port 31789 unreachable 13:55:42.338501 212.242.68.115 > 212.12.228.18: icmp: 212.242.68.115 udp port 31789 unreachable 13:55:42.343540 212.242.68.65 > 212.12.228.18: icmp: 212.242.68.65 udp port 31789 unreachable 13:55:42.347635 212.242.68.68 > 212.12.228.18: icmp: 212.242.68.68 udp port 31789 unreachable 13:55:42.353583 212.242.68.69 > 212.12.228.18: icmp: 212.242.68.69 udp port 31789 unreachable 13:55:42.361562 212.242.68.72 > 212.12.228.18: icmp: 212.242.68.72 udp port 31789 unreachable 13:55:42.362546 212.242.68.73 > 212.12.228.18: icmp: 212.242.68.73 udp port 31789 unreachable 13:55:42.366518 212.242.68.76 > 212.12.228.18: icmp: 212.242.68.76 udp port 31789 unreachable 13:55:42.371563 212.242.68.77 > 212.12.228.18: icmp: 212.242.68.77 udp port 31789 unreachable 13:55:42.377854 212.242.68.80 > 212.12.228.18: icmp: 212.242.68.80 udp port 31789 unreachable 13:55:42.380567 212.242.68.81 > 212.12.228.18: icmp: 212.242.68.81 udp port 31789 unreachable 13:55:42.387941 212.242.68.84 > 212.12.228.18: icmp: 212.242.68.84 udp port 31789 unreachable 13:55:42.389579 212.242.68.85 > 212.12.228.18: icmp: 212.242.68.85 udp port 31789 unreachable 13:55:42.395518 212.242.68.88 > 212.12.228.18: icmp: 212.242.68.88 udp port 31789 unreachable 13:55:42.400556 212.242.68.89 > 212.12.228.18: icmp: 212.242.68.89 udp port 31789 unreachable 13:55:42.404530 212.242.68.92 > 212.12.228.18: icmp: 212.242.68.92 udp port 31789 unreachable 13:55:42.409568 212.242.68.93 > 212.12.228.18: icmp: 212.242.68.93 udp port 31789 unreachable 13:55:42.414646 212.242.68.96 > 212.12.228.18: icmp: 212.242.68.96 udp port 31789 unreachable 13:55:42.418782 212.242.68.97 > 212.12.228.18: icmp: 212.242.68.97 udp port 31789 unreachable 13:55:42.428572 212.242.68.100 > 212.12.228.18: icmp: 212.242.68.100 udp port 31789 unreachable 13:55:42.432670 212.242.68.101 > 212.12.228.18: icmp: 212.242.68.101 udp port 31789 unreachable 13:55:42.437875 212.242.68.104 > 212.12.228.18: icmp: 212.242.68.104 udp port 31789 unreachable 13:55:42.443522 212.242.68.105 > 212.12.228.18: icmp: 212.242.68.105 udp port 31789 unreachable 13:55:42.447905 212.242.68.147 > 212.12.228.18: icmp: 212.242.68.147 udp port 31789 unreachable 13:55:42.450404 212.242.68.109 > 212.12.228.18: icmp: 212.242.68.109 udp port 31789 unreachable 13:55:42.451508 212.242.68.118 > 212.12.228.18: icmp: 212.242.68.118 udp port 31789 unreachable 13:55:42.457450 212.242.68.119 > 212.12.228.18: icmp: 212.242.68.119 udp port 31789 unreachable 13:55:42.460561 212.242.68.108 > 212.12.228.18: icmp: 212.242.68.108 udp port 31789 unreachable 13:55:42.465599 212.242.68.112 > 212.12.228.18: icmp: 212.242.68.112 udp port 31789 unreachable 13:55:42.470514 212.242.68.116 > 212.12.228.18: icmp: 212.242.68.116 udp port 31789 unreachable 13:55:42.482844 212.242.68.150 > 212.12.228.18: icmp: 212.242.68.150 udp port 31789 unreachable 13:55:42.488537 212.242.68.151 > 212.12.228.18: icmp: 212.242.68.151 udp port 31789 unreachable 13:55:42.524420 212.242.68.154 > 212.12.228.18: icmp: 212.242.68.154 udp port 31789 unreachable 13:55:42.537361 212.242.68.155 > 212.12.228.18: icmp: 212.242.68.155 udp port 31789 unreachable 13:55:42.553582 212.242.68.122 > 212.12.228.18: icmp: 212.242.68.122 udp port 31789 unreachable 13:55:42.558537 212.242.68.123 > 212.12.228.18: icmp: 212.242.68.123 udp port 31789 unreachable 13:55:42.559383 212.242.68.195 > 212.12.228.18: icmp: 212.242.68.195 udp port 31789 unreachable 13:55:42.563183 212.242.68.198 > 212.12.228.18: icmp: 212.242.68.198 udp port 31789 unreachable 13:55:42.563576 212.242.68.126 > 212.12.228.18: icmp: 212.242.68.126 udp port 31789 unreachable 13:55:42.568531 212.242.68.120 > 212.12.228.18: icmp: 212.242.68.120 udp port 31789 unreachable 13:55:42.572593 212.242.68.125 > 212.12.228.18: icmp: 212.242.68.125 udp port 31789 unreachable 13:55:42.577543 212.242.68.121 > 212.12.228.18: icmp: 212.242.68.121 udp port 31789 unreachable 13:55:42.582582 212.242.68.124 > 212.12.228.18: icmp: 212.242.68.124 udp port 31789 unreachable 13:55:42.587331 192.168.75.10 > 212.12.228.18: icmp: 212.242.68.145 udp port 31789 unreachable 13:55:42.591962 192.168.77.10 > 212.12.228.18: icmp: time exceeded in-transit [tos 0xc0] 13:55:42.598964 192.168.77.9 > 212.12.228.18: icmp: time exceeded in-transit 13:55:42.599948 192.168.77.9 > 212.12.228.18: icmp: time exceeded in-transit 13:55:42.634358 212.242.68.149 > 212.12.228.18: icmp: 212.242.68.149 udp port 31789 unreachable 13:55:42.645701 212.242.68.153 > 212.12.228.18: icmp: 212.242.68.153 udp port 31789 unreachable 13:55:42.648935 192.168.77.10 > 212.12.228.18: icmp: 212.242.68.161 udp port 31789 unreachable [tos 0xc0] 13:55:42.652704 212.242.68.152 > 212.12.228.18: icmp: 212.242.68.152 udp port 31789 unreachable 13:55:42.716937 192.168.77.9 > 212.12.228.18: icmp: time exceeded in-transit 13:55:42.717031 212.242.68.197 > 212.12.228.18: icmp: 212.242.68.197 udp port 31789 unreachable 13:55:42.721148 212.242.68.207 > 212.12.228.18: icmp: 212.242.68.207 udp port 31789 unreachable 13:55:42.725614 212.242.68.196 > 212.12.228.18: icmp: 212.242.68.196 udp port 31789 unreachable 13:55:42.766948 192.168.77.10 > 212.12.228.18: icmp: time exceeded in-transit [tos 0xc0] 13:55:42.783612 212.242.68.117 > 212.12.228.18: icmp: 212.242.68.117 udp port 31789 unreachable 13:55:42.784143 192.168.77.10 > 212.12.228.18: icmp: time exceeded in-transit [tos 0xc0] 13:55:42.784798 192.168.77.10 > 212.12.228.18: icmp: time exceeded in-transit [tos 0xc0] 13:55:42.785248 192.168.77.10 > 212.12.228.18: icmp: time exceeded in-transit [tos 0xc0] 13:55:42.785648 192.168.77.9 > 212.12.228.18: icmp: time exceeded in-transit 13:55:42.815612 212.242.68.210 > 212.12.228.18: icmp: 212.242.68.210 udp port 31789 unreachable 13:55:42.820162 212.242.68.204 > 212.12.228.18: icmp: 212.242.68.204 udp port 31789 unreachable 13:55:42.824348 212.242.68.205 > 212.12.228.18: icmp: 212.242.68.205 udp port 31789 unreachable 13:55:42.828187 212.242.68.208 > 212.12.228.18: icmp: 212.242.68.208 udp port 31789 unreachable 13:55:42.832334 212.242.68.201 > 212.12.228.18: icmp: 212.242.68.201 udp port 31789 unreachable 13:55:42.836039 212.242.68.227 > 212.12.228.18: icmp: 212.242.68.227 udp port 31789 unreachable 13:55:42.915996 192.168.77.30 > 212.12.228.18: icmp: 212.242.68.225 udp port 31789 unreachable 13:55:42.967212 212.242.68.220 > 212.12.228.18: icmp: 212.242.68.220 udp port 31789 unreachable 13:55:42.975687 212.242.68.250 > 212.12.228.18: icmp: 212.242.68.250 udp port 31789 unreachable 13:55:42.979726 212.242.68.243 > 212.12.228.18: icmp: 212.242.68.243 udp port 31789 unreachable [tos 0xc0] 13:55:42.980141 212.242.68.251 > 212.12.228.18: icmp: 212.242.68.251 udp port 31789 unreachable 13:55:42.988397 212.242.68.254 > 212.12.228.18: icmp: 212.242.68.254 udp port 31789 unreachable 13:55:43.042682 212.242.69.15 > 212.12.228.18: icmp: 212.242.69.15 udp port 31789 unreachable 13:55:43.068864 212.242.69.18 > 212.12.228.18: icmp: 212.242.69.18 udp port 31789 unreachable 13:55:43.078551 192.168.72.58 > 212.12.228.18: icmp: 212.242.68.233 udp port 31789 unreachable [tos 0xc0] 13:55:43.091911 192.168.72.62 > 212.12.228.18: icmp: 212.242.68.249 udp port 31789 unreachable 13:55:43.096399 212.242.68.253 > 212.12.228.18: icmp: 212.242.68.253 udp port 31789 unreachable 13:55:43.106708 192.168.74.14 > 212.12.228.18: icmp: 212.242.68.241 udp port 31789 unreachable 13:55:43.199763 212.242.69.7 > 212.12.228.18: icmp: 212.242.69.7 udp port 31789 unreachable 13:55:43.203694 192.168.74.18 > 212.12.228.18: icmp: 212.242.69.1 udp port 31789 unreachable [tos 0xc0] 13:55:43.206684 212.242.69.11 > 212.12.228.18: icmp: 212.242.69.11 udp port 31789 unreachable 13:55:43.241996 212.242.69.42 > 212.12.228.18: icmp: 212.242.69.42 udp port 31789 unreachable 13:55:43.242068 212.242.69.43 > 212.12.228.18: icmp: 212.242.69.43 udp port 31789 unreachable [tos 0xc0] 13:55:43.268738 212.242.69.17 > 212.12.228.18: icmp: 212.242.69.17 udp port 31789 unreachable 13:55:43.339433 212.242.69.50 > 212.12.228.18: icmp: 212.242.69.50 udp port 31789 unreachable 13:55:43.340017 192.168.76.22 > 212.12.228.18: icmp: 212.242.69.37 udp port 31789 unreachable [tos 0xc0] 13:55:43.379417 192.168.72.70 > 212.12.228.18: icmp: 212.242.69.41 udp port 31789 unreachable [tos 0xc0] 13:55:43.407035 212.242.69.66 > 212.12.228.18: icmp: 212.242.69.66 udp port 31789 unreachable 13:55:43.416525 212.242.69.67 > 212.12.228.18: icmp: 212.242.69.67 udp port 31789 unreachable 13:55:43.420359 192.168.87.2 > 212.12.228.18: icmp: 212.242.69.49 udp port 31789 unreachable 13:55:43.424505 212.242.69.70 > 212.12.228.18: icmp: 212.242.69.70 udp port 31789 unreachable 13:55:43.432520 212.242.69.71 > 212.12.228.18: icmp: 212.242.69.71 udp port 31789 unreachable 13:55:43.457292 212.242.69.74 > 212.12.228.18: icmp: 212.242.69.74 udp port 31789 unreachable 13:55:43.465981 212.242.69.75 > 212.12.228.18: icmp: 212.242.69.75 udp port 31789 unreachable 13:55:43.475743 212.242.69.78 > 212.12.228.18: icmp: 212.242.69.78 udp port 31789 unreachable 13:55:43.495050 212.242.68.87 > 212.12.228.18: icmp: 212.242.68.87 udp port 31789 unreachable 13:55:43.504889 212.242.69.86 > 212.12.228.18: icmp: 212.242.69.86 udp port 31789 unreachable 13:55:43.507433 212.242.69.83 > 212.12.228.18: icmp: 212.242.69.83 udp port 31789 unreachable 13:55:43.517143 212.242.69.65 > 212.12.228.18: icmp: 212.242.69.65 udp port 31789 unreachable 13:55:43.522735 212.242.69.66 > 212.12.228.18: icmp: 212.242.69.64 udp port 31789 unreachable 13:55:43.532796 212.242.69.69 > 212.12.228.18: icmp: 212.242.69.69 udp port 31789 unreachable 13:55:43.540800 212.242.69.68 > 212.12.228.18: icmp: 212.242.69.68 udp port 31789 unreachable 13:55:43.563525 212.242.69.72 > 212.12.228.18: icmp: 212.242.69.72 udp port 31789 unreachable 13:55:43.573255 212.242.69.73 > 212.12.228.18: icmp: 212.242.69.73 udp port 31789 unreachable 13:55:43.581310 212.242.69.76 > 212.12.228.18: icmp: 212.242.69.76 udp port 31789 unreachable 13:55:43.582129 212.242.69.82 > 212.12.228.18: icmp: 212.242.69.82 udp port 31789 unreachable [tos 0xc0] 13:55:43.589125 212.242.69.77 > 212.12.228.18: icmp: 212.242.69.77 udp port 31789 unreachable 13:55:43.589543 212.242.68.107 > 212.12.228.18: icmp: 212.242.68.107 udp port 31789 unreachable 13:55:43.591774 212.242.69.114 > 212.12.228.18: icmp: 212.242.69.114 udp port 31789 unreachable [tos 0xc0] 13:55:43.598741 192.168.72.78 > 212.12.228.18: icmp: 212.242.69.81 udp port 31789 unreachable 13:55:43.605998 212.242.69.85 > 212.12.228.18: icmp: 212.242.69.85 udp port 31789 unreachable 13:55:43.645585 212.242.68.113 > 212.12.228.18: icmp: 212.242.68.113 udp port 31789 unreachable 13:55:43.691692 212.242.69.117 > 212.12.228.18: icmp: 212.242.69.117 udp port 31789 unreachable [tos 0xc0] 13:55:43.703747 212.242.68.242 > 212.12.228.18: icmp: 212.242.68.242 udp port 31789 unreachable [tos 0xc0] 13:55:43.706739 192.168.72.65 > 212.12.228.18: icmp: 212.242.69.33 udp port 31789 unreachable [tos 0xc0] 13:55:43.800489 212.242.69.121 > 212.12.228.18: icmp: 212.242.69.121 udp port 31789 unreachable [tos 0xc0] 13:55:43.802185 212.242.69.84 > 212.12.228.18: icmp: 212.242.69.84 udp port 31789 unreachable 13:55:43.888719 192.168.74.26 > 212.12.228.18: icmp: 212.242.69.129 udp port 31789 unreachable [tos 0xc0] 13:55:43.976267 212.242.69.163 > 212.12.228.18: icmp: 212.242.69.163 udp port 31789 unreachable 13:55:43.980238 212.242.69.162 > 212.12.228.18: icmp: 212.242.69.162 udp port 31789 unreachable 13:55:43.991535 212.242.69.170 > 212.12.228.18: icmp: 212.242.69.170 udp port 31789 unreachable 13:55:44.073259 192.168.88.2 > 212.12.228.18: icmp: 212.242.69.161 udp port 31789 unreachable 13:55:44.086243 212.242.69.165 > 212.12.228.18: icmp: 192.168.15.63 udp port 1441 unreachable (DF) 13:55:44.546282 212.242.69.171 > 212.12.228.18: icmp: 212.242.69.171 udp port 31789 unreachable 13:55:44.833629 192.168.74.26 > 212.12.228.18: icmp: 212.242.69.158 udp port 31789 unreachable [tos 0xc0] END OF REPORT -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Dec 9 10:30: 4 1999 Delivered-To: freebsd-isp@freebsd.org Received: from cronus.medianetwork.se (cronus.medianetwork.se [193.14.204.1]) by hub.freebsd.org (Postfix) with ESMTP id AA7F71565C for ; Thu, 9 Dec 1999 10:30:00 -0800 (PST) (envelope-from dl@tyfon.net) Received: from junglenote.com (digital01.medianetwork.se [193.14.204.219]) by cronus.medianetwork.se (8.9.3/8.7) with ESMTP id TAA32364 for ; Thu, 9 Dec 1999 19:29:56 +0100 Received: from enigmatic [127.0.0.1] by junglenote.com [localhost] with SMTP (MDaemon.v2.84.R) for ; Thu, 09 Dec 1999 19:40:31 +0100 Received: by localhost with Microsoft MAPI; Thu, 9 Dec 1999 19:40:30 +0100 Message-ID: <01BF427D.40521690.dl@tyfon.net> From: Dan Larsson To: "[FreeBSD-ISP-List] (E-post)" , "[FreeBSD-Questions-List] (E-post)" Subject: howto force sendmail Date: Thu, 9 Dec 1999 19:40:29 +0100 Organization: Tyfon Internet Services [ http://tyfon.net ] X-Mailer: Microsoft Internet-e-post/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-MDaemon-Deliver-To: freebsd-isp@freebsd.org X-Return-Path: dl@tyfon.net Reply-To: dl@tyfon.net Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is it possible to force sendmail to use a particular node name when communicating with uucp. If it is, what do I need to do? Regards ------------ Dan Larsson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Dec 9 12:17:55 1999 Delivered-To: freebsd-isp@freebsd.org Received: from bsdie.rwsystems.net (bsdie.rwsystems.net [209.197.223.2]) by hub.freebsd.org (Postfix) with ESMTP id 3A0DE156B4; Thu, 9 Dec 1999 12:17:36 -0800 (PST) (envelope-from jwyatt@rwsystems.net) Received: from bsdie.rwsystems.net([209.197.223.2]) (1043 bytes) by bsdie.rwsystems.net via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Thu, 9 Dec 1999 14:08:54 -0600 (CST) (Smail-3.2.0.106 1999-Mar-31 #1 built 1999-Aug-7) Date: Thu, 9 Dec 1999 14:08:53 -0600 (CST) From: James Wyatt To: Dan Larsson Cc: "[FreeBSD-ISP-List] (E-post)" , "[FreeBSD-Questions-List] (E-post)" Subject: Re: howto force sendmail In-Reply-To: <01BF427D.40521690.dl@tyfon.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 9 Dec 1999, Dan Larsson wrote: > Is it possible to force sendmail to use a particular node name when > communicating with uucp. > > If it is, what do I need to do? A decent resource for UUCP and sendmail is: http://www.sendmail.org/m4/uucp.html Though, to be honest, we've usually converted UUCP gateway machines to use smail for numerous reasons. - Jy@ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Dec 9 14:37:17 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mail.alpha.net.au (mail2.alpha.net.au [203.41.44.8]) by hub.freebsd.org (Postfix) with ESMTP id 6B6F115033; Thu, 9 Dec 1999 14:37:13 -0800 (PST) (envelope-from dannyh@idx.com.au) Received: from psych ([203.41.44.172]) by mail.alpha.net.au (8.9.3/8.9.3) with SMTP id JAA18232; Fri, 10 Dec 1999 09:37:34 +1100 Message-Id: <3.0.32.19991210093828.0073e6e0@idx.com.au> X-Sender: dannyh@idx.com.au X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Fri, 10 Dec 1999 09:38:29 +1100 To: freebsd-isp@freebsd.org From: Danny Subject: Freebsd -> ISP intranet Office Automation Question Cc: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Situation I am planning to develop a intranet that will automate network documentation, some BB to enter phone messages etc. Question I was wondering if anyone can Email me a brief description of what tools you use to automate your ISP office. Anything ideas or web sites will do. thank you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Dec 9 14:46:46 1999 Delivered-To: freebsd-isp@freebsd.org Received: from gamera.comnetcom.net (ns1.comnetcom.net [209.100.247.254]) by hub.freebsd.org (Postfix) with ESMTP id 6B31215206 for ; Thu, 9 Dec 1999 14:46:43 -0800 (PST) (envelope-from jeff@comnetcom.net) Received: from jeff (laptop.comnetcom.net [209.100.247.124]) by gamera.comnetcom.net (8.9.1/8.9.1) with SMTP id RAA05413 for ; Thu, 9 Dec 1999 17:08:22 -0600 (CST) Message-ID: <00a201bf4297$4bc415e0$7cf764d1@comnetcom.net> From: "Jeff Tolley" To: Subject: Re: quick question on passwd file. Date: Thu, 9 Dec 1999 16:46:56 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks for all the help everyone. It shouldn't be much of a problem. Jeff Tolley - jeff@comnetcom.net Senior Systems Engineer Com Net Communication Systems, Inc. ----- Original Message ----- From: "Greg Lehey" To: "Jeff Tolley" ; Sent: Tuesday, December 07, 1999 8:33 PM Subject: Re: quick question on passwd file. > On Tuesday, 7 December 1999 at 16:32:29 -0600, Jeff Tolley wrote: > > I hope this in the right place. > > You're probabbly better off in -questions, since this isn't a > specifically ISP issue. > > > We are currently in the process of migrating our webserver to a > > better machine. What is the best way to move the users from the old > > machine to the new machine? Is simply copying over the passwd and > > master.passwd file's enough? > > There are in fact two other files, /etc/pwd.db and /etc/spwd.db as > well. But you can generate them and /etc/passwd from > /etc/master.passwd (thus the name). The "correct" way to do it is > with pwd_mkdb(8), which has a reasonable man page. The "easy" way do > to it is with vipw(8). You'll have to change something and write it > back to fool vipw to start pwd_mkdb, but that's about all you need to > do. > > Greg > -- > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Dec 10 4:34:50 1999 Delivered-To: freebsd-isp@freebsd.org Received: from post.mail.areti.net (meteora.areti.com [193.118.189.10]) by hub.freebsd.org (Postfix) with ESMTP id 3595D1528F for ; Fri, 10 Dec 1999 04:34:47 -0800 (PST) (envelope-from ndear@areti.net) Received: from acropolis (acropolis.noc.areti.net [193.118.189.102]) by post.mail.areti.net (8.9.3/8.9.3/Areti-2.0.0) with ESMTP id MAA12252 for ; Fri, 10 Dec 1999 12:34:42 GMT Message-Id: <199912101234.MAA12252@post.mail.areti.net> From: "Nicholas J. Dear" Organization: Areti Internet Ltd. To: freebsd-isp@FreeBSD.ORG Date: Fri, 10 Dec 1999 12:31:31 -0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Setting time and date via ntp. Reply-To: ndear@areti.net X-mailer: Pegasus Mail for Win32 (v3.12b) Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, What software can I use via crontab to periodically set the date to that provided by an NTP server? We use netdate on Linux, but was wondering if there is something similar for FreeBSD? Tia. N. -- Nicholas J. Dear Mail: ndear@areti.net Tel: +44 (0)20-8402-4041 Areti Internet Ltd., http://www.areti.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Dec 10 4:39:23 1999 Delivered-To: freebsd-isp@freebsd.org Received: from nathalie.macomnet.ru (nathalie.macomnet.ru [195.128.64.164]) by hub.freebsd.org (Postfix) with ESMTP id A3748152D7 for ; Fri, 10 Dec 1999 04:39:19 -0800 (PST) (envelope-from serg@macomnet.ru) Received: from nathalie.macomnet.ru (nathalie.macomnet.ru [195.128.64.164]) by nathalie.macomnet.ru (8.9.3/8.9.3) with ESMTP id PAA30808; Fri, 10 Dec 1999 15:39:14 +0300 (MSK) (envelope-from serg@macomnet.ru) Date: Fri, 10 Dec 1999 15:39:14 +0300 (MSK) From: "Serg V. Shubenkov" Reply-To: serg@macomnet.ru To: "Nicholas J. Dear" Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Setting time and date via ntp. In-Reply-To: <199912101234.MAA12252@post.mail.areti.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Some like ntpdate clock0.macomnet.ru On Fri, 10 Dec 1999, Nicholas J. Dear wrote: #Hi, # #What software can I use via crontab to periodically set the date to that provided #by an NTP server? We use netdate on Linux, but was wondering if there is #something similar for FreeBSD? # #Tia. #N. #-- #Nicholas J. Dear #Mail: ndear@areti.net Tel: +44 (0)20-8402-4041 #Areti Internet Ltd., http://www.areti.co.uk/ # # #To Unsubscribe: send mail to majordomo@FreeBSD.org #with "unsubscribe freebsd-isp" in the body of the message # Sergey Shubenkov (SVS21-RIPN) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Dec 10 4:44:38 1999 Delivered-To: freebsd-isp@freebsd.org Received: from smtp2.maxim.net (smtp2.maxim.net [206.171.12.25]) by hub.freebsd.org (Postfix) with ESMTP id B8EDB150FD for ; Fri, 10 Dec 1999 04:44:27 -0800 (PST) (envelope-from Arabian@ArabChat.Org) Received: from qatar ([194.133.179.81]) by smtp2.maxim.net (8.8.4/8.6.9) with SMTP id EAA15151; Fri, 10 Dec 1999 04:52:39 -0800 Message-ID: <00f001bf430c$4770b320$51b385c2@net.qa.qatar.net.qa> Reply-To: "Abdullah Bin Hamad" From: "Abdullah Bin Hamad" To: , References: <199912101234.MAA12252@post.mail.areti.net> Subject: Re: Setting time and date via ntp. Date: Fri, 10 Dec 1999 15:44:12 +0300 Organization: ArabChat IRC NetWork MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Nicholas, Check http://www.eecis.udel.edu/~ntp/ Good luck, -Arabian aka Abdullah http://www.ArabChat.Org/ ----- Original Message ----- From: Nicholas J. Dear To: Sent: Friday, December 10, 1999 3:31 PM Subject: Setting time and date via ntp. > Hi, > > What software can I use via crontab to periodically set the date to that provided > by an NTP server? We use netdate on Linux, but was wondering if there is > something similar for FreeBSD? > > Tia. > N. > -- > Nicholas J. Dear > Mail: ndear@areti.net Tel: +44 (0)20-8402-4041 > Areti Internet Ltd., http://www.areti.co.uk/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Dec 10 4:58:48 1999 Delivered-To: freebsd-isp@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 8682D152D7 for ; Fri, 10 Dec 1999 04:58:38 -0800 (PST) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id HAA74891; Fri, 10 Dec 1999 07:58:37 -0500 (EST) (envelope-from mike@sentex.net) Received: from ospf-mdt.sentex.net (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id HAA03355; Fri, 10 Dec 1999 07:58:36 -0500 (EST) From: mike@sentex.net (Mike Tancsa) To: ndear@areti.net ("Nicholas J. Dear") Cc: freebsd-isp@freebsd.org Subject: Re: Setting time and date via ntp. Date: Fri, 10 Dec 1999 12:58:36 GMT Message-ID: <3850f8b8.1251090422@mail.sentex.net> References: In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 10 Dec 1999 07:35:12 -0500, in sentex.lists.freebsd.isp you wrote: >Hi, > >What software can I use via crontab to periodically set the date to that provided >by an NTP server? We use netdate on Linux, but was wondering if there is >something similar for FreeBSD? Try, /usr/sbin/ntpdate tick.usno.navy.mil clock.llnl.gov ntp1.berkeley.edu ---Mike Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Dec 10 5: 0:38 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mail2.one.net (mail2.one.net [206.112.192.100]) by hub.freebsd.org (Postfix) with ESMTP id E3F3F15498 for ; Fri, 10 Dec 1999 05:00:35 -0800 (PST) (envelope-from pboehmer@one.net) Received: from shell.one.net ([206.112.192.106] EHLO shell ident: IDENT-NOT-QUERIED [port 60933]) by mail2.one.net with ESMTP id <25468-138>; Fri, 10 Dec 1999 08:00:23 -0500 Date: Fri, 10 Dec 1999 08:00:12 -0500 (EST) From: Paul Boehmer To: "Nicholas J. Dear" Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Setting time and date via ntp. In-Reply-To: <199912101234.MAA12252@post.mail.areti.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org rdate is probably what you want, works for us. Paul Boehmer pboehmer@one.net On Fri, 10 Dec 1999, Nicholas J. Dear wrote: > Hi, > > What software can I use via crontab to periodically set the date to that provided > by an NTP server? We use netdate on Linux, but was wondering if there is > something similar for FreeBSD? > > Tia. > N. > -- > Nicholas J. Dear > Mail: ndear@areti.net Tel: +44 (0)20-8402-4041 > Areti Internet Ltd., http://www.areti.co.uk/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Dec 10 5:10:32 1999 Delivered-To: freebsd-isp@freebsd.org Received: from naiad.eclipse.net.uk (naiad.eclipse.net.uk [195.188.32.29]) by hub.freebsd.org (Postfix) with ESMTP id 58F0E15298 for ; Fri, 10 Dec 1999 05:10:30 -0800 (PST) (envelope-from sh@eclipse.net.uk) Received: from eclipse.net.uk (elara.eclipse.net.uk [195.188.32.31]) by naiad.eclipse.net.uk (Postfix) with ESMTP id CFAB11313D; Fri, 10 Dec 1999 13:10:23 +0000 (GMT) Message-ID: <3850FBF6.4550F384@eclipse.net.uk> Date: Fri, 10 Dec 1999 13:11:18 +0000 From: Stuart Henderson Organization: Eclipse Networking X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en-GB MIME-Version: 1.0 To: ndear@areti.net Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Setting time and date via ntp. References: <199912101234.MAA12252@post.mail.areti.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > What software can I use via crontab to periodically set the date to that provided > by an NTP server? We use netdate on Linux, but was wondering if there is > something similar for FreeBSD? As others have suggested, ntpdate, but it's better not to run from crontab and instead to use xntpd which keeps a drift file so that if the server can't be contacted, time is still corrected. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Dec 10 7:25: 7 1999 Delivered-To: freebsd-isp@freebsd.org Received: from bogon.kjsl.com (bogon.kjsl.com [206.55.236.201]) by hub.freebsd.org (Postfix) with ESMTP id E7EE01503B for ; Fri, 10 Dec 1999 07:25:04 -0800 (PST) (envelope-from javier@bogon.kjsl.com) Received: (from javier@localhost) by bogon.kjsl.com (8.9.3/8.9.3) id HAA02760; Fri, 10 Dec 1999 07:24:43 -0800 (PST) From: Javier Henderson MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14417.6971.512702.374961@bogon.kjsl.com> Date: Fri, 10 Dec 1999 07:24:43 -0800 (PST) To: ndear@areti.net Cc: freebsd-isp@FreeBSD.ORG Subject: Setting time and date via ntp. In-Reply-To: <199912101234.MAA12252@post.mail.areti.net> References: <199912101234.MAA12252@post.mail.areti.net> X-Mailer: VM 6.63 under Emacs 19.34.1 X-Airplane-of-the-day: Grumman Tiger Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nicholas J. Dear writes: > What software can I use via crontab to periodically set the date to that provided > by an NTP server? We use netdate on Linux, but was wondering if there is > something similar for FreeBSD? Why don't you run xntpd? -jav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Dec 10 9: 3:40 1999 Delivered-To: freebsd-isp@freebsd.org Received: from manor.msen.com (manor.msen.com [148.59.4.13]) by hub.freebsd.org (Postfix) with ESMTP id 231A715175 for ; Fri, 10 Dec 1999 09:03:38 -0800 (PST) (envelope-from wayne@staff.msen.com) Received: (from wayne@localhost) by manor.msen.com (8.8.8/8.8.8) id MAA17094 for freebsd-isp@FreeBSD.ORG; Fri, 10 Dec 1999 12:03:35 -0500 (EST) (envelope-from wayne) Message-ID: <19991210120334.A16989@staff.msen.com> Date: Fri, 10 Dec 1999 12:03:34 -0500 From: "Michael R. Wayne" To: freebsd-isp@FreeBSD.ORG Subject: Re: Setting time and date via ntp. References: <199912101234.MAA12252@post.mail.areti.net> <14417.6971.512702.374961@bogon.kjsl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <14417.6971.512702.374961@bogon.kjsl.com>; from Javier Henderson on Fri, Dec 10, 1999 at 07:24:43AM -0800 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Dec 10, 1999 at 07:24:43AM -0800, Javier Henderson wrote: > > Why don't you run xntpd? Out of curiosity, is anyone running xntpd w/ 250+ virtual domains? On another version of BSD we had problems with xntpd trying to open a channel on every virtual IP address and croaking because it was out of sockets. Typically we just toss a /24 onto each web server and we've taken to installing a custom hack of xntpd that stops after N interfaces regardless of what they are. /\/\ \/\/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Dec 10 9: 6:35 1999 Delivered-To: freebsd-isp@freebsd.org Received: from bogon.kjsl.com (bogon.kjsl.com [206.55.236.201]) by hub.freebsd.org (Postfix) with ESMTP id 21BF615881 for ; Fri, 10 Dec 1999 09:06:31 -0800 (PST) (envelope-from javier@bogon.kjsl.com) Received: (from javier@localhost) by bogon.kjsl.com (8.9.3/8.9.3) id JAA04564; Fri, 10 Dec 1999 09:06:28 -0800 (PST) From: Javier Henderson MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14417.13075.884729.244757@bogon.kjsl.com> Date: Fri, 10 Dec 1999 09:06:27 -0800 (PST) To: "Michael R. Wayne" Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Setting time and date via ntp. In-Reply-To: <19991210120334.A16989@staff.msen.com> References: <199912101234.MAA12252@post.mail.areti.net> <14417.6971.512702.374961@bogon.kjsl.com> <19991210120334.A16989@staff.msen.com> X-Mailer: VM 6.63 under Emacs 19.34.1 X-Airplane-of-the-day: Grumman Tiger Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Michael R. Wayne writes: > Out of curiosity, is anyone running xntpd w/ 250+ virtual domains? > On another version of BSD we had problems with xntpd trying to open > a channel on every virtual IP address and croaking because it was > out of sockets. Typically we just toss a /24 onto each web server > and we've taken to installing a custom hack of xntpd that stops > after N interfaces regardless of what they are. I've xntpd running on a 2.2.8 machine with 35 virtual domains, and I don't see the problem you're seeing. -jav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Dec 10 10:44:47 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mail1.gmx.net (mail1.gmx.net [194.221.183.61]) by hub.freebsd.org (Postfix) with SMTP id 94FD2153A0 for ; Fri, 10 Dec 1999 10:44:25 -0800 (PST) (envelope-from pons@gmx.li) Received: (qmail 29356 invoked by uid 0); 10 Dec 1999 18:43:56 -0000 Received: from unknown (HELO gmx.li) (212.38.131.194) by mail1.gmx.net with SMTP; 10 Dec 1999 18:43:56 -0000 Message-ID: <385148CC.93A8E2D0@gmx.li> Date: Fri, 10 Dec 1999 20:39:08 +0200 From: pons X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,arabic MIME-Version: 1.0 To: freebsd-isp@freebsd.org Subject: Router Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Our Company preforms the MIS for 250x remote locations . We would like to provide a leased line WAN that connects all 250 to main office. 50 of them would have an analog dial-up via 56k modem as a backup. Which Routes would be the best (cost, preformance, security) can be used to provide LAN and WAN connection on the server and client site? Server: 2x machines OS: UNIX Clients: OS : Win9x/NT LAN: Ethernet -- pons@gmx.li pons@arabchat.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Dec 10 12:17: 8 1999 Delivered-To: freebsd-isp@freebsd.org Received: from bigcity.net (mail.bigcity.net [206.222.176.4]) by hub.freebsd.org (Postfix) with ESMTP id 5345D1596F for ; Fri, 10 Dec 1999 12:07:10 -0800 (PST) (envelope-from josh@bigcity.net) Received: from enigma [206.222.176.65] by bigcity.net (SMTPD32-5.05) id AF05C61B0118; Fri, 10 Dec 1999 14:13:57 -0600 Message-ID: <005101bf434a$1ddfa460$41b0dece@bigcity.net> From: "Josh Bell" To: References: <199912101234.MAA12252@post.mail.areti.net><14417.6971.512702.374961@bogon.kjsl.com><19991210120334.A16989@staff.msen.com> <14417.13075.884729.244757@bogon.kjsl.com> Subject: Re: Setting time and date via ntp. Date: Fri, 10 Dec 1999 14:06:59 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can you not use ntpdate? I know that a stock system of FreeBSD comes with ntpdate, even as far back as 2.2.2 if not earlier. I dont see why this isnt possible to be used. What are the advantages on xntpd over ntpdate or vise versa? -Josh ----- Original Message ----- From: "Javier Henderson" To: "Michael R. Wayne" Cc: Sent: Friday, December 10, 1999 11:06 AM Subject: Re: Setting time and date via ntp. > Michael R. Wayne writes: > > > Out of curiosity, is anyone running xntpd w/ 250+ virtual domains? > > On another version of BSD we had problems with xntpd trying to open > > a channel on every virtual IP address and croaking because it was > > out of sockets. Typically we just toss a /24 onto each web server > > and we've taken to installing a custom hack of xntpd that stops > > after N interfaces regardless of what they are. > > I've xntpd running on a 2.2.8 machine with 35 virtual domains, > and I don't see the problem you're seeing. > > -jav > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Dec 10 13:20: 7 1999 Delivered-To: freebsd-isp@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id F28AE14D96 for ; Fri, 10 Dec 1999 13:19:59 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id NAA64672; Fri, 10 Dec 1999 13:19:59 -0800 (PST) Date: Fri, 10 Dec 1999 13:19:59 -0800 (PST) From: David Wolfskill Message-Id: <199912102119.NAA64672@pau-amma.whistle.com> To: freebsd-isp@FreeBSD.org, josh@bigcity.net Subject: Re: Setting time and date via ntp. In-Reply-To: <005101bf434a$1ddfa460$41b0dece@bigcity.net> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >From: "Josh Bell" >Date: Fri, 10 Dec 1999 14:06:59 -0600 >Can you not use ntpdate? I know that a stock system of FreeBSD comes with >ntpdate, even as far back as 2.2.2 if not earlier. I dont see why this isnt >possible to be used. What are the advantages on xntpd over ntpdate or vise >versa? Well, they aren't mutually exclusive. I normally set up a machine to use ntpdate during the /etc/rc stuff just after boot time, to get the date/time correct at first, and then fire off xntpd in order to maintain synchronization. xntpd doesn't tend to perform arbitrarily large changes to the system's notion of the current (date and) time; ntpdate will. I don't recall whether or not xntpd also ensures that any change that it makes still only permits the time to increase monotonically, as it should. Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Dec 10 17:47:35 1999 Delivered-To: freebsd-isp@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 7240214D71 for ; Fri, 10 Dec 1999 17:47:33 -0800 (PST) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id UAA63455; Fri, 10 Dec 1999 20:47:31 -0500 (EST) (envelope-from mike@sentex.net) Received: from ospf-mdt.sentex.net (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id UAA21449; Fri, 10 Dec 1999 20:47:30 -0500 (EST) From: mike@sentex.net (Mike Tancsa) To: pons@gmx.li (pons) Cc: freebsd-isp@freebsd.org Subject: Re: Router Date: Sat, 11 Dec 1999 01:47:30 GMT Message-ID: <3851ac5d.1297084769@mail.sentex.net> References: In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 10 Dec 1999 14:10:06 -0500, in sentex.lists.freebsd.isp you wrote: >Hi > >Our Company preforms the MIS for 250x remote locations . >We would like to provide a leased line WAN that connects >all 250 to main office. 50 of them would have an analog >dial-up via 56k modem as a backup. > > >Which Routes would be the best (cost, preformance, security) >can be used to provide LAN and WAN connection on the >server and client site? Well, have a look at some of the mailing lists and newsgroups devoted to terminal servers. We use Lucent PM3s, and they are OK. We are evaluating a Cisco AS5300, and it has comprable modem performance, but many more features... but it also costs more. Unless you like weekly software updates, I would stay away from Ascend. Some people however really like them, so get a few opinions. www.data.com also has a fairly extensive review, but be read the methodology. To an ISP world, the modem performance is somewhat irrelavant in that ISPs dont see such a homogeneous environment. ---Mike Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Dec 10 21:21:58 1999 Delivered-To: freebsd-isp@freebsd.org Received: from cliff.i-plus.net (cliff.i-plus.net [209.100.20.42]) by hub.freebsd.org (Postfix) with ESMTP id 7924614F4F for ; Fri, 10 Dec 1999 21:21:49 -0800 (PST) (envelope-from st@i-plus.net) Received: from abyss (is.dashit.net [209.100.22.250]) by cliff.i-plus.net (8.9.3/8.9.3) with SMTP id AAA65578; Sat, 11 Dec 1999 00:21:37 -0500 (EST) From: "Troy Settle" To: "pons" , Subject: RE: Router Date: Sat, 11 Dec 1999 00:20:26 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal In-Reply-To: <385148CC.93A8E2D0@gmx.li> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org There are of course, several other solutions to this, but to address the issues of cost, performance, and security, you'll probably want something like a private frame from the telco (they can do this). Connect everyone to the frame via T1 (ala Cisco 1600), then at the main office, have a cisco 3640 or 3660 with modems, PRI, a T3 for the frame cloud, and a T1 (or whatever) for internet. -Troy ** -----Original Message----- ** From: owner-freebsd-isp@FreeBSD.ORG ** [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of pons ** Sent: Friday, December 10, 1999 1:39 PM ** To: freebsd-isp@FreeBSD.ORG ** Subject: Router ** ** ** Hi ** ** Our Company preforms the MIS for 250x remote locations . ** We would like to provide a leased line WAN that connects ** all 250 to main office. 50 of them would have an analog ** dial-up via 56k modem as a backup. ** ** ** Which Routes would be the best (cost, preformance, security) ** can be used to provide LAN and WAN connection on the ** server and client site? ** ** Server: ** 2x machines ** OS: UNIX ** ** Clients: ** OS : Win9x/NT ** LAN: Ethernet ** ** -- ** pons@gmx.li ** pons@arabchat.org ** ** ** To Unsubscribe: send mail to majordomo@FreeBSD.org ** with "unsubscribe freebsd-isp" in the body of the message ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sat Dec 11 6:29: 3 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mail1.gmx.net (mail1.gmx.net [194.221.183.61]) by hub.freebsd.org (Postfix) with SMTP id 3CB8914EB8 for ; Sat, 11 Dec 1999 06:28:44 -0800 (PST) (envelope-from pons@gmx.li) Received: (qmail 7800 invoked by uid 0); 11 Dec 1999 14:28:33 -0000 Received: from unknown (HELO gmx.li) (212.38.131.194) by mail1.gmx.net with SMTP; 11 Dec 1999 14:28:33 -0000 Message-ID: <38525E8B.9CFC8E29@gmx.li> Date: Sat, 11 Dec 1999 16:24:11 +0200 From: pons X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,arabic MIME-Version: 1.0 Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Router References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Troy Settle wrote: > > There are of course, several other solutions to this, but to address the > issues of cost, performance, and security, you'll probably want something > like a private frame from the telco (they can do this). Connect everyone to > the frame via T1 (ala Cisco 1600), then at the main office, have a cisco > 3640 or 3660 with modems, PRI, a T3 for the frame cloud, and a T1 (or > whatever) for internet. > > -Troy I need the list price for Cisco 1600/3660 -Pons > ** > ** Hi > ** > ** Our Company preforms the MIS for 250x remote locations . > ** We would like to provide a leased line WAN that connects > ** all 250 to main office. 50 of them would have an analog > ** dial-up via 56k modem as a backup. > ** > ** > ** Which Routes would be the best (cost, preformance, security) > ** can be used to provide LAN and WAN connection on the > ** server and client site? > ** > ** Server: > ** 2x machines > ** OS: UNIX > ** > ** Clients: > ** OS : Win9x/NT > ** LAN: Ethernet > ** > ** -- > ** pons@gmx.li > ** pons@arabchat.org > ** > ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sat Dec 11 6:58:32 1999 Delivered-To: freebsd-isp@freebsd.org Received: from cliff.i-plus.net (cliff.i-plus.net [209.100.20.42]) by hub.freebsd.org (Postfix) with ESMTP id 8FF3714E9C for ; Sat, 11 Dec 1999 06:58:19 -0800 (PST) (envelope-from st@i-plus.net) Received: from abyss (is.dashit.net [209.100.22.250]) by cliff.i-plus.net (8.9.3/8.9.3) with SMTP id JAA87783 for ; Sat, 11 Dec 1999 09:58:15 -0500 (EST) From: "Troy Settle" To: Subject: RE: Router Date: Sat, 11 Dec 1999 09:57:02 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal In-Reply-To: <38525E8B.9CFC8E29@gmx.li> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org www.starcom.com Or, contact your local hardware vendor ** -----Original Message----- ** From: owner-freebsd-isp@FreeBSD.ORG ** [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of pons ** Sent: Saturday, December 11, 1999 9:24 AM ** Cc: freebsd-isp@FreeBSD.ORG ** Subject: Re: Router ** ** ** ** ** Troy Settle wrote: ** > ** > There are of course, several other solutions to this, but to ** address the ** > issues of cost, performance, and security, you'll probably ** want something ** > like a private frame from the telco (they can do this). ** Connect everyone to ** > the frame via T1 (ala Cisco 1600), then at the main office, ** have a cisco ** > 3640 or 3660 with modems, PRI, a T3 for the frame cloud, and a T1 (or ** > whatever) for internet. ** > ** > -Troy ** ** I need the list price for Cisco 1600/3660 ** ** -Pons ** > ** ** > ** Hi ** > ** ** > ** Our Company preforms the MIS for 250x remote locations . ** > ** We would like to provide a leased line WAN that connects ** > ** all 250 to main office. 50 of them would have an analog ** > ** dial-up via 56k modem as a backup. ** > ** ** > ** ** > ** Which Routes would be the best (cost, preformance, security) ** > ** can be used to provide LAN and WAN connection on the ** > ** server and client site? ** > ** ** > ** Server: ** > ** 2x machines ** > ** OS: UNIX ** > ** ** > ** Clients: ** > ** OS : Win9x/NT ** > ** LAN: Ethernet ** > ** ** > ** -- ** > ** pons@gmx.li ** > ** pons@arabchat.org ** > ** ** > ** ** ** ** To Unsubscribe: send mail to majordomo@FreeBSD.org ** with "unsubscribe freebsd-isp" in the body of the message ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sat Dec 11 7:28: 5 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mail1.gmx.net (mail1.gmx.net [194.221.183.61]) by hub.freebsd.org (Postfix) with SMTP id 8590D14E34 for ; Sat, 11 Dec 1999 07:28:01 -0800 (PST) (envelope-from pons@gmx.li) Received: (qmail 15755 invoked by uid 0); 11 Dec 1999 15:27:58 -0000 Received: from unknown (HELO gmx.li) (212.38.131.194) by mail1.gmx.net with SMTP; 11 Dec 1999 15:27:58 -0000 Message-ID: <38526C76.9074A18E@gmx.li> Date: Sat, 11 Dec 1999 17:23:34 +0200 From: pons X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,arabic MIME-Version: 1.0 Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Router References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What is the Max. no. of remote modem connections of Cisco3600/3660? -Pons Troy Settle wrote: > > www.starcom.com > > Or, contact your local hardware vendor > > ** -----Original Message----- > ** From: owner-freebsd-isp@FreeBSD.ORG > ** [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of pons > ** Sent: Saturday, December 11, 1999 9:24 AM > ** Cc: freebsd-isp@FreeBSD.ORG > ** Subject: Re: Router > ** > ** > ** > ** > ** Troy Settle wrote: > ** > > ** > There are of course, several other solutions to this, but to > ** address the > ** > issues of cost, performance, and security, you'll probably > ** want something > ** > like a private frame from the telco (they can do this). > ** Connect everyone to > ** > the frame via T1 (ala Cisco 1600), then at the main office, > ** have a cisco > ** > 3640 or 3660 with modems, PRI, a T3 for the frame cloud, and a T1 (or > ** > whatever) for internet. > ** > > ** > -Troy > ** > ** I need the list price for Cisco 1600/3660 > ** > ** -Pons > ** > ** > ** > ** Hi > ** > ** > ** > ** Our Company preforms the MIS for 250x remote locations . > ** > ** We would like to provide a leased line WAN that connects > ** > ** all 250 to main office. 50 of them would have an analog > ** > ** dial-up via 56k modem as a backup. > ** > ** > ** > ** > ** > ** Which Routes would be the best (cost, preformance, security) > ** > ** can be used to provide LAN and WAN connection on the > ** > ** server and client site? > ** > ** > ** > ** Server: > ** > ** 2x machines > ** > ** OS: UNIX > ** > ** > ** > ** Clients: > ** > ** OS : Win9x/NT > ** > ** LAN: Ethernet > ** > ** > ** > ** -- > ** > ** pons@gmx.li > ** > ** pons@arabchat.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sat Dec 11 10:56: 8 1999 Delivered-To: freebsd-isp@freebsd.org Received: from continuity.necrosys.net (continuity.necrosys.net [207.229.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 03C8214C98 for ; Sat, 11 Dec 1999 10:56:06 -0800 (PST) (envelope-from root@necrosys.net) Received: from localhost (root@localhost) by continuity.necrosys.net (8.9.3/8.9.3) with ESMTP id LAA45646 for ; Sat, 11 Dec 1999 11:56:02 -0700 (MST) (envelope-from root@necrosys.net) Date: Sat, 11 Dec 1999 11:56:02 -0700 (MST) From: Charlie ROOT To: freebsd-isp@freebsd.org Subject: Admin needed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I run a small co-location and shell server setup, I'm currently having a problem with some of my users. They've all had me install for them freebsd servers, however they're not competent enough unix admins to run their whole show on their own (a couple shell servers, web servers and the like) I'd love to help them out but I haven't got the time. If there are any unix sysadmin people looking to make a little extra money from helping these guys out it would be really great. Most of them can be found on efnet in the channel #necrosys. Or you can contact me and I'll put you in touch with the ones that need the most help. Thanks, (Sorry to anybody who might consider this spam) Barkley To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sat Dec 11 15:48:47 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mail.alpha.net.au (mail2.alpha.net.au [203.41.44.8]) by hub.freebsd.org (Postfix) with ESMTP id D2BBA14A31 for ; Sat, 11 Dec 1999 15:48:43 -0800 (PST) (envelope-from dannyh@idx.com.au) Received: from psych ([203.41.44.211]) by mail.alpha.net.au (8.9.3/8.9.3) with SMTP id KAA26052; Sun, 12 Dec 1999 10:48:52 +1100 Message-Id: <3.0.32.19991212104946.006947f4@idx.com.au> X-Sender: dannyh@idx.com.au X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 12 Dec 1999 10:49:50 +1100 To: Charlie ROOT , freebsd-isp@FreeBSD.ORG From: Danny Subject: Problem with the design phase. Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, Currently the ISP Has no or not enough =B7 Documentation containing licenceings and software support contracts =B7 Map of the network (locations of servers and details about cabling) =B7 A journal of all problems and their symptoms, solutions, dates, outcome =B7 Information about each server =B7Documentation Access Information : -For information on our access numbers= , server details, login-scripts and setup software.=20 =B7 Documentation Technical / Helpdesk : support in the areas of: connecting to the Internet, using Internet-related software, contacting the helpdesk.= =20 =B7 Documentation Accounts: FAQ and pointers about accounts related issues. Phone Messages are taken down by hand. There are no backup for internal documentations As a developer I need a way to=20 centralize the above documentation=20 a easier way to access the documentation (like a search engine on the intranet) a easier way to keep phone messages a backup tool for internal documentation Question: - What tools, solutions, web sites, books can I refer to or look at to find a solution to the above problem? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sat Dec 11 17: 5:25 1999 Delivered-To: freebsd-isp@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 71A311509B for ; Sat, 11 Dec 1999 17:05:23 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id AE2F11C4A; Sat, 11 Dec 1999 20:05:14 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id AB0C8381B; Sat, 11 Dec 1999 20:05:14 -0500 (EST) Date: Sat, 11 Dec 1999 20:05:14 -0500 (EST) From: Bill Fumerola To: pons Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Router In-Reply-To: <38526C76.9074A18E@gmx.li> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 11 Dec 1999, pons wrote: > What is the Max. no. of remote modem connections > of Cisco3600/3660? Like most things, it depends. I have a 3620 and it can max out at 48. (with the configuration I have a 2/DS1 + 1/ethernet and a modem card) The other 36xx series routers can have different amounts of modules. The cisco website really does have the best information on this. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message