From owner-freebsd-isp Mon Oct 9 4:26:24 2000 Delivered-To: freebsd-isp@freebsd.org Received: from beta.root-servers.ch (beta.root-servers.ch [195.49.33.19]) by hub.freebsd.org (Postfix) with SMTP id 2230037B66C for ; Mon, 9 Oct 2000 04:26:22 -0700 (PDT) Received: (qmail 99594 invoked from network); 9 Oct 2000 11:26:20 -0000 Received: from client75-185.hispeed.ch (HELO work.root.li) (62.2.75.185) by beta.root-servers.ch with SMTP; 9 Oct 2000 11:26:20 -0000 Date: Mon, 9 Oct 2000 13:29:50 +0200 From: Gabriel Ambuehl X-Mailer: The Bat! (v1.46c) UNREG / CD5BF9353B3B7091 Organization: BUZ Internet Services X-Priority: 3 (Normal) Message-ID: <137180637703.20001009132950@buz.ch> To: isp@freebsd.org Subject: Management CGI Script for .htaccess protection 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, I'm desperately seeking a nice, if possible GPL or similar licensed, CGI script to control .htaccess/.htpasswd protection on virtual Apache webservers through an easy web based GUI. I looked at quite a lot of script from cgi-resources.com but either found the licence inacceptable (I need to customize the whole thing at least to some degree) or the scripts had so broken UIs that I didn't want them because explaining the users how they work would require way more work than doing the setup of the protection my self... I can't be the only one with such a need, so any suggestions would greatly be appreciated. Best regards, Gabriel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Oct 9 6: 0:53 2000 Delivered-To: freebsd-isp@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id CEF3837B502 for ; Mon, 9 Oct 2000 06:00:37 -0700 (PDT) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id TAA05668; Mon, 9 Oct 2000 19:56:05 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Mon, 9 Oct 2000 19:56:05 +0700 (NSS) From: Max Khon To: Gabriel Ambuehl Cc: isp@FreeBSD.ORG Subject: Re: Management CGI Script for .htaccess protection In-Reply-To: <137180637703.20001009132950@buz.ch> 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 hi, there! On Mon, 9 Oct 2000, Gabriel Ambuehl wrote: > I'm desperately seeking a nice, if possible GPL or similar licensed, > CGI script to control .htaccess/.htpasswd protection on virtual Apache > webservers through an easy web based GUI. http://www.webmin.com/ (BSD-style licence) /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Oct 9 13:21:41 2000 Delivered-To: freebsd-isp@freebsd.org Received: from riga.nu (riga.nu [195.62.138.40]) by hub.freebsd.org (Postfix) with SMTP id 8DF1D37B66C for ; Mon, 9 Oct 2000 13:21:36 -0700 (PDT) Received: (qmail 64361 invoked from network); 9 Oct 2000 20:21:24 -0000 Received: from unknown (HELO running.riga.nu) (213.182.202.72) by ns.riga.nu with SMTP; 9 Oct 2000 20:21:24 -0000 Received: (qmail 31454 invoked from network); 9 Oct 2000 20:21:23 -0000 Received: from unknown (HELO viktors.riga.nu) (10.0.0.2) by 213.182.202.72 with SMTP; 9 Oct 2000 20:21:23 -0000 From: Viktors Rotanovs To: freebsd-isp@freebsd.org Subject: slightly OT Date: Mon, 9 Oct 2000 22:18:27 +0200 X-Mailer: KMail [version 1.1.94.2] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00100922182703.24723@viktors.riga.nu> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, maybe not exact mailing list for the question, but I guess you know the answer :) What is the best procedure for upgrading _remotely_ _production_ 3.2 server to 4.1.1? When I tried this thing last time, it was almost OK except that I was unable to reboot with new /sbin/reboot - "Invalid system call". Now the problem is that network card uses non-default port/irq, so I should do userconfig remotely somehow (or it's safer to just put pre-compiled 4.1.1 kernel?) -- Best Wishes, Viktors Rotanovs I create websites that attract more clients. http://riga.nu/ Riga Latvia +371, Phone/Fax 7377-472, GSM 9173-000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Oct 9 13:26:43 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 369E637B503 for ; Mon, 9 Oct 2000 13:26:41 -0700 (PDT) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id E6D406A907 for ; Mon, 9 Oct 2000 22:26:33 +0200 (CEST) Received: from sv.Go2France.com [212.73.210.79] by mail.Go2France.com with ESMTP (SMTPD32-6.04) id AB19D2E0150; Mon, 09 Oct 2000 22:31:21 +0200 Message-Id: <5.0.0.25.0.20001009222453.04313a20@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Mon, 09 Oct 2000 22:26:31 +0200 To: freebsd-isp@freebsd.org From: Len Conrad Subject: FreeBSD for RAS? In-Reply-To: <00100922182703.24723@viktors.riga.nu> 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 suppose the answer will be "go buy a Portmaster, etc" but is anybody using FreeBSD + PRI card for RAS? Len To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Oct 9 14:55: 5 2000 Delivered-To: freebsd-isp@freebsd.org Received: from hotmail.com (f240.law8.hotmail.com [216.33.241.240]) by hub.freebsd.org (Postfix) with ESMTP id D5D1C37B502 for ; Mon, 9 Oct 2000 14:55:03 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 9 Oct 2000 14:55:03 -0700 Received: from 63.207.125.156 by lw8fd.law8.hotmail.msn.com with HTTP; Mon, 09 Oct 2000 21:55:03 GMT X-Originating-IP: [63.207.125.156] From: "Terje Oseberg" To: freebsd-isp@freebsd.org Subject: Re: Fw: webcam solution Date: Mon, 09 Oct 2000 21:55:03 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 09 Oct 2000 21:55:03.0681 (UTC) FILETIME=[942CFF10:01C0323B] Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Your frame rate that you're asking for is incredibly slow. Have you thought about live video? Check out this camera. http://www.giveusabuck.com/livecam4.shtml Does it look good? The one I'm showing there is 320x240 I can make it 640x240 for wide angle. I can get the frame rate to slow down if you want, but why? I can also rebroadcast it for you and allow you control of the frame rate, or maximum bandwidth or whatever you want. My pricing is really cheap. (I charge about the same for bandwidth usage as the current DSL prices.) That means that if you had a 56k modem on your webcam, I could rebroadcast it for you on a 1Mbit, 10Mbit, 100Mbit or more depending on what you're willing to pay. Basically, you've got full control of everything. Terje _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Oct 9 20:21:18 2000 Delivered-To: freebsd-isp@freebsd.org Received: from longsword.omniti.com (longsword.omniti.com [216.0.51.134]) by hub.freebsd.org (Postfix) with ESMTP id 1CCFB37B66D for ; Mon, 9 Oct 2000 20:21:16 -0700 (PDT) Received: from bardiche.omniti.com ([216.0.51.149] helo=cnds.jhu.edu ident=jesus) by longsword.omniti.com with esmtp (Exim 3.14 #3) id 13ipyb-0001tN-00; Mon, 09 Oct 2000 23:21:13 -0400 Message-ID: <39E28B29.2F8480F9@cnds.jhu.edu> Date: Mon, 09 Oct 2000 23:21:13 -0400 From: "Theo E. Schlossnagle" Organization: Center for Networking and Distributed Systems X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.2.16 i686) X-Accept-Language: en MIME-Version: 1.0 To: kstone@win.net Cc: freebsd-isp@FreeBSD.ORG, backhand-users@lists.backhand.org Subject: Re: [mod_backhand-users] Mod_Backhand and Frontpage extentions. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, first off, let me confess my ignorance of how FrontPage works. Now, I will talk about what I do know. Maybe someone with a little knowledge of FrontPage will be able to piece together why this doesn't work. mod_backhand actually plays "man-in-the-middle" wth regards to proxying HTTP requests. It takes the liberty of upgrading non-persistent HTTP sessions to persistent sessions during proxying. This allows mod_backhand to maintain open TCP/IP sessions and pipeline the HTTP requests/responses between itself and another server, while the client never knows the difference. Client -> HTTP/1.0 no keepalive -> mod_backhand -> upgrades to keepalive -> selected server -> HTTP/1.0 with keepalive -> mod_backhand -> HTTP/1.0 no keepalive -> Client. Because of this, mod_backhand must know the internals of HTTP and counts on the request and response being valid HTTP/1.0 requests... If frontpage requires a "change" to the HTTP protocol, that would completely break mod_backhand's ability to HTTP redirect the request. But, perhaps the HTTP redirection methods will work for you: http://www.backhand.org/mod_backhand/FAQ.shtml#question7 Hope this helps some :-) kstone@win.net wrote: > Has anyone tried this combination and gotten it to work successfully? > > I'm attempting to use backhand with Apacke/SuExec/FP2K extentions.. If the > request is not being handed to another machine the request to open a site > with the Frontpage 98/2K client works properly. If it is redirected > to another box by "byAge, byCost" then the client get rather confused and > spits out strange error messages. The FP2k services have been verified > as working on either machine as long as no redirs take place. > > It seems to me that when mod_backhand is redirecting the data from a > frontpage request, some of the data is getting munged and is considered > malformed when it reaches the server it was internally proxy redirected > to. > > Has anyone else experienced this or seen possible work arounds? I'd > like to have my Frontpage client requests balnced with backhand as well, > rahter then shoved off to it's own box just for FP clients. -- Theo Schlossnagle 1024D/A8EBCF8F/13BD 8C08 6BE2 629A 527E 2DC2 72C2 AD05 A8EB CF8F 2047R/33131B65/71 F7 95 64 49 76 5D BA 3D 90 B9 9F BE 27 24 E7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon Oct 9 20:29:39 2000 Delivered-To: freebsd-isp@freebsd.org Received: from servizi.padova.com (servizi.padova.com [212.131.155.42]) by hub.freebsd.org (Postfix) with ESMTP id B6EFD37B503; Mon, 9 Oct 2000 20:29:22 -0700 (PDT) Received: from padova08 (unverified [212.131.155.4]) by servizi.padova.com (Rockliffe SMTPRA 4.2.2) with SMTP id for ; Tue, 10 Oct 2000 01:56:53 +0200 Message-ID: <006f01c0324d$3d232d40$049b83d4@pol.it> Reply-To: "Emma Bonino" From: "Emma Bonino" To: Subject: Toc toc. Sono Emma Bonino e la prego... Date: Tue, 10 Oct 2000 02:01:28 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Toc toc. Mi scusi, sono Emma Bonino e la prego di partecipare al gioco online che stiamo organizzando perche' anche cittadini come lei (che non votino affatto radicale o che lo facciano, che non votino o non intendano piu' votare) possano partecipare alle nostre decisioni, essere presenti o rappresentati nei nostri organi dirigenti. In vista delle elezioni politiche occorre tentare di allearsi con il Polo o con l'Ulivo? O combattere da soli? O organizzare il boicottaggio di elezioni non democratiche? Quali Riforme istituzionali, politiche, del lavoro, dell'impresa: "americane" o "tedesche", o nessuna? Quali politiche sulle liberta' individuali e sulla scienza, oltre che sulle droghe: proibizioniste o antiproibizioniste, come gia' sul divorzio e sull'aborto? E i partiti devono aprirsi a tutti i cittadini attraverso Internet, o restare "chiusi" come finora? Dal 27 novembre al 3 dicembre si votera' online per eleggere 25 nuovi membri del Comitato Radicale. Se, come vivamente spero, lei intende partecipare a questo gioco, lo preannunci e registri cliccando qui: http://www.radicali.it/p_register/ Mi scusi ancora. A presto. Emma Bonino PS Questa email e' stata inviata nel rispetto della legge sulla privacy; se desidera maggiori informazioni o se intende cancellarsi, puo' cliccare qui: http://www.radicali.it/p_privacy_org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Oct 10 8:41:37 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mail03.rapidsite.net (mail03.rapidsite.net [207.158.192.52]) by hub.freebsd.org (Postfix) with SMTP id 07E0B37B502 for ; Tue, 10 Oct 2000 08:41:35 -0700 (PDT) Received: from www.itechusa.net (209.238.96.96) by mail03.rapidsite.net (RS ver 1.0.58s) with SMTP id 018644752 for ; Tue, 10 Oct 2000 11:41:14 -0400 (EDT) Subject: Kernel Messaage: bad gateway value From: ITECHUSA FreeBSD Support Reply-To: ITECHUSA FreeBSD Support Message-ID: <0003734b6eaf6f56_mailit@smtp.itechusa.net> Date: Tue, 10 Oct 2000 10:45:46 -0500 X-Mailer: BeatWare Mail-It 2.0.4 X-BeOS-Platform: Intel or clone X-Priority: 3 (Normal) To: freebsd-isp@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Loop-Detect: 1 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I could use a little help. My system has been sending kernel messages to the console displaying: "/kernel: arp_rtrequest: bad gateway value" I am concerned this may be a security problem? My current setup for the machine relaying the message is as follows: OS: FreeBSD4.1.1-STABLE NIC: 2 xl 3COM adapters on interfaces xl0 and xl1 KERNEL: IPFIREWALL, IPDIVERT, using NATD. xl0 is my internal private network using 192.168.1.0 network and xl1 is my interface to the CABLE Modem. Here are the rc.conf values: router_flag="-s" router="router" router_enable="YES" gateway_enable="YES" natd_enable="YES" natd_interface="xl1" firewall_enable="YES" firewall_type="open" Maybe I'm just paranoid, but I've been running these servers for a while, and this is the first time I've seen this message appear. Any suggestions? - Chris Tusa alaska@itechusa.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Oct 10 11:43:39 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mx1.thebiz.net (mx1.thebiz.net [216.238.0.20]) by hub.freebsd.org (Postfix) with SMTP id EDAE037B503 for ; Tue, 10 Oct 2000 11:43:32 -0700 (PDT) Received: (qmail 11633 invoked from network); 10 Oct 2000 14:43:26 -0400 Received: from mail1.backend.thebiz.net (HELO mail1.thebiz.net) (172.16.0.179) by mx1.backend.thebiz.net with SMTP; 10 Oct 2000 14:43:26 -0400 Received: (qmail 17675 invoked by uid 0); 10 Oct 2000 14:43:26 -0400 Received: from unknown (HELO shell1.thebiz.net) (216.238.35.75) by mail.thebiz.net with SMTP; 10 Oct 2000 14:43:26 -0400 Date: Tue, 10 Oct 2000 14:43:28 -0400 (EDT) From: X-Sender: tom@shell1.thebiz.net To: freebsd-isp@freebsd.org Subject: Mysterious Lockups (fwd) 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 No one bit on this on the questions group or the alpha group so maybe you guys may have some insite for me. Thanks. ---------- Forwarded message ---------- Hello All, We have a couple of webservers that are in production that are getting hosed on a regular basis and I'm at a loss right now on what the problem is. At first we thought it was the way that our logserver was dealing with the logging but we started logging locally and that did not fix the issue. This is a compaq Alpha DS10 doing diskless booting. The apache setup is basically right out of the box other then the option for mass virtual hosting and a patch to deal with our hashed style of user directories. I've included the output of the netstat right after it got hosed as well as the kernel and apache information. Some other info is that this machine has a few aliased IP adresses to support other ISPs on the local loopback device. These machines sit behind a Foundry ServerIron / FastIron for load balancing. Public side goes through the Foundry and the private side goes through a Cisco Catalyst 4000. Any help or thoughts on this would be great. Thanks a bunch! Server version: Apache/1.3.12 Ben-SSL/1.39 (Unix) Server built: May 31 2000 10:07:41 FreeBSD web2.thebiz.net 4.0-RELEASE FreeBSD 4.0-RELEASE #0: Tue Jul 11 13:35:02 EDT 2000 maz@web1.thebiz.net:/usr/src/sys/compile/DISKLESS-DS10 alpha Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp4 0 4 172.16.0.70.23 172.16.0.20.45984 ESTABLISHED tcp4 481 0 216.238.35.206.80 205.188.209.204.60080 CLOSE_WAIT tcp4 378 0 216.238.35.204.80 24.95.170.63.1088 ESTABLISHED tcp4 261 0 216.238.35.204.80 137.165.14.30.1068 ESTABLISHED tcp4 0 0 216.238.35.204.80 63.166.164.200.61407 CLOSE_WAIT tcp4 0 0 216.238.35.204.80 209.185.143.138.44638 CLOSE_WAIT tcp4 166 0 216.238.35.204.80 209.185.143.138.63642 CLOSE_WAIT tcp4 0 0 216.238.35.204.80 63.21.189.209.1093 CLOSE_WAIT tcp4 355 0 216.238.35.204.80 63.99.105.163.8847 ESTABLISHED tcp4 188 0 216.238.35.206.80 216.35.103.51.52629 CLOSE_WAIT tcp4 332 0 216.238.35.204.80 63.99.105.163.9335 ESTABLISHED tcp4 335 0 216.238.35.204.80 63.99.105.163.9334 ESTABLISHED tcp4 340 0 216.238.35.204.80 63.99.105.163.9333 ESTABLISHED tcp4 335 0 216.238.35.204.80 63.99.105.163.9320 ESTABLISHED tcp4 335 0 216.238.35.204.80 63.99.105.163.9319 ESTABLISHED tcp4 347 0 216.238.35.204.80 63.99.105.163.9317 ESTABLISHED tcp4 148 0 216.238.35.206.80 208.171.252.37.4659 CLOSE_WAIT tcp4 296 0 216.238.35.204.80 24.29.59.89.2119 CLOSE_WAIT tcp4 366 0 216.238.35.204.80 12.34.109.82.43747 ESTABLISHED tcp4 221 0 216.238.35.204.80 209.4.252.235.3592 ESTABLISHED tcp4 270 0 216.238.35.206.80 149.106.33.22.1062 CLOSE_WAIT tcp4 335 0 216.238.35.204.80 63.99.105.163.1970 CLOSE_WAIT tcp4 340 0 216.238.35.204.80 63.99.105.163.1968 CLOSE_WAIT tcp4 332 0 216.238.35.204.80 63.99.105.163.1967 CLOSE_WAIT tcp4 197 0 216.238.35.206.80 216.35.103.53.53678 CLOSE_WAIT tcp4 399 0 216.238.35.204.80 212.125.82.57.18666 ESTABLISHED tcp4 316 0 216.238.35.204.80 24.29.59.89.2117 CLOSE_WAIT tcp4 261 0 216.238.35.204.80 208.17.2.40.1033 CLOSE_WAIT tcp4 0 0 216.238.35.70.80 216.238.9.82.2620 CLOSE_WAIT tcp4 0 0 216.238.35.204.80 216.238.9.82.2618 CLOSE_WAIT tcp4 68 0 216.238.35.204.80 216.15.84.168.38018 CLOSE_WAIT tcp4 326 0 216.238.35.204.80 38.151.70.230.5364 CLOSE_WAIT tcp4 270 0 216.238.35.206.80 149.106.33.22.1061 CLOSE_WAIT tcp4 544 0 216.238.35.204.80 202.61.190.5.4021 CLOSE_WAIT tcp4 187 0 216.238.35.206.80 216.35.103.53.52309 CLOSE_WAIT tcp4 565 0 216.238.35.206.80 194.201.24.172.20488 CLOSE_WAIT tcp4 342 0 216.238.35.204.80 63.99.105.163.63617 CLOSE_WAIT tcp4 355 0 216.238.35.204.80 63.99.105.163.63616 CLOSE_WAIT tcp4 341 0 216.238.35.204.80 63.99.105.163.63615 CLOSE_WAIT tcp4 341 0 216.238.35.204.80 63.99.105.163.63613 CLOSE_WAIT tcp4 68 0 216.238.35.204.80 216.15.84.168.38012 CLOSE_WAIT tcp4 273 0 216.238.35.204.80 205.188.208.203.9694 CLOSE_WAIT tcp4 381 0 216.238.35.204.80 207.198.35.37.64434 CLOSE_WAIT tcp4 187 0 216.238.35.206.80 216.35.103.53.50211 CLOSE_WAIT tcp4 273 0 216.238.35.204.80 205.188.208.203.6938 CLOSE_WAIT tcp4 334 0 216.238.35.204.80 216.238.225.56.1403 ESTABLISHED tcp4 68 0 216.238.35.204.80 216.15.84.168.38007 CLOSE_WAIT tcp4 424 0 216.238.35.206.80 24.131.134.76.1213 CLOSE_WAIT tcp4 292 0 216.238.35.204.80 216.238.225.56.1402 CLOSE_WAIT tcp4 434 0 216.238.35.206.80 212.1.141.191.1570 CLOSE_WAIT tcp4 149 0 216.238.35.206.80 212.1.128.63.33288 CLOSE_WAIT tcp4 261 0 216.238.35.204.80 216.175.235.66.1825 CLOSE_WAIT tcp4 315 0 216.238.35.204.80 209.198.114.237.1263 CLOSE_WAIT tcp4 0 0 216.238.35.204.80 209.185.143.138.53172 CLOSE_WAIT tcp4 250 0 216.238.35.204.80 64.41.254.25.1895 CLOSE_WAIT tcp4 381 0 216.238.35.204.80 207.198.35.37.63567 CLOSE_WAIT tcp4 216 0 216.238.35.204.80 216.35.116.93.52489 CLOSE_WAIT tcp4 261 0 216.238.35.204.80 216.238.1.32.2854 CLOSE_WAIT tcp4 170 0 216.238.35.206.80 209.67.206.127.52954 CLOSE_WAIT tcp4 170 0 216.238.35.206.80 209.67.206.126.51861 CLOSE_WAIT tcp4 381 0 216.238.35.204.80 207.198.35.37.63460 CLOSE_WAIT tcp4 274 0 216.238.35.204.80 205.247.157.99.1614 CLOSE_WAIT tcp4 182 0 216.238.35.204.80 209.185.143.138.49748 CLOSE_WAIT tcp4 148 0 216.238.35.206.80 208.171.252.34.4145 CLOSE_WAIT tcp4 255 0 216.238.35.204.80 205.188.208.203.57187 CLOSE_WAIT tcp4 0 0 216.238.35.204.80 209.185.143.138.46399 CLOSE_WAIT tcp4 170 0 216.238.35.204.80 208.184.66.9.1379 CLOSE_WAIT tcp4 155 0 216.238.35.204.80 208.184.66.9.1378 CLOSE_WAIT tcp4 320 0 216.238.35.204.80 213.189.83.100.43578 CLOSE_WAIT tcp4 387 0 216.238.35.204.80 128.119.121.177.1061 CLOSE_WAIT tcp4 155 0 216.238.35.204.80 208.184.66.9.1094 CLOSE_WAIT tcp4 0 0 216.238.35.204.80 209.185.143.138.57149 CLOSE_WAIT tcp4 226 0 216.238.35.204.80 216.35.116.93.51897 CLOSE_WAIT tcp4 182 0 216.238.35.204.80 209.185.143.138.53529 CLOSE_WAIT tcp4 387 0 216.238.35.204.80 128.119.121.177.1031 CLOSE_WAIT tcp4 261 0 216.238.35.204.80 216.175.235.66.1823 CLOSE_WAIT tcp4 375 0 216.238.35.204.80 199.184.22.2.40832 ESTABLISHED tcp4 261 0 216.238.35.204.80 208.48.238.149.3535 CLOSE_WAIT tcp4 261 0 216.238.35.204.80 208.48.238.149.3534 CLOSE_WAIT tcp4 216 0 216.238.35.204.80 216.35.103.62.62755 CLOSE_WAIT tcp4 261 0 216.238.35.204.80 208.48.238.149.3533 CLOSE_WAIT tcp4 180 0 216.238.35.204.80 209.185.143.138.62329 CLOSE_WAIT tcp4 261 0 216.238.35.204.80 216.175.235.66.1821 CLOSE_WAIT tcp4 261 0 216.238.35.204.80 216.175.235.66.1819 CLOSE_WAIT tcp4 261 0 216.238.35.204.80 216.175.235.66.1817 CLOSE_WAIT tcp4 68 0 216.238.35.204.80 209.133.121.160.57333 CLOSE_WAIT tcp4 226 0 216.238.35.204.80 216.35.103.62.62049 CLOSE_WAIT tcp4 0 0 216.238.35.70.80 216.238.9.82.2462 CLOSE_WAIT tcp4 0 0 216.238.35.204.80 216.238.9.82.2460 CLOSE_WAIT tcp4 588 0 216.238.35.206.80 211.117.39.52.18604 CLOSE_WAIT tcp4 0 0 216.238.35.204.80 199.179.123.68.63172 CLOSE_WAIT tcp4 242 0 216.238.35.206.80 64.196.60.70.1130 CLOSE_WAIT tcp4 191 0 216.238.35.206.80 216.35.103.56.50988 CLOSE_WAIT tcp4 357 0 216.238.35.204.80 172.165.74.108.1199 CLOSE_WAIT tcp4 0 17520 216.238.35.206.80 168.221.7.27.1621 CLOSE_WAIT tcp4 0 5950 216.238.35.206.80 216.35.103.56.49103 LAST_ACK tcp4 0 542 216.238.35.204.80 212.7.60.98.1870 LAST_ACK tcp4 0 17520 216.238.35.206.80 209.240.220.150.59419 CLOSE_WAIT tcp4 0 11794 216.238.35.204.80 216.175.235.66.1815 LAST_ACK tcp4 0 307 216.238.35.204.80 208.184.66.9.4700 LAST_ACK tcp4 0 143 216.238.35.204.80 24.131.134.49.4031 LAST_ACK tcp4 0 307 216.238.35.204.80 208.184.66.9.4530 LAST_ACK tcp4 0 2644 216.238.35.206.80 208.171.252.97.2157 LAST_ACK tcp4 0 17520 216.238.35.206.80 216.35.103.71.50336 LAST_ACK tcp4 0 10921 216.238.35.204.80 205.247.157.86.1101 LAST_ACK tcp4 0 4626 216.238.35.206.80 152.163.189.68.34578 LAST_ACK tcp4 0 8319 216.238.35.204.80 216.35.116.103.50498 LAST_ACK tcp4 0 11794 216.238.35.204.80 172.165.74.108.1134 LAST_ACK tcp4 0 4626 216.238.35.206.80 152.163.189.68.31101 LAST_ACK tcp4 0 11794 216.238.35.204.80 24.29.59.89.2104 LAST_ACK tcp4 0 0 216.238.35.204.80 216.238.225.56.1399 LAST_ACK tcp4 0 0 216.238.35.204.80 216.238.225.56.1398 LAST_ACK tcp4 0 0 216.238.35.204.80 216.238.225.56.1397 LAST_ACK tcp4 0 4096 216.238.35.204.80 216.238.225.56.1396 LAST_ACK tcp4 0 458 216.238.35.204.80 216.35.116.103.49617 LAST_ACK tcp4 0 0 216.238.35.204.80 216.77.225.224.24630 FIN_WAIT_2 tcp4 0 170 216.238.35.204.80 209.185.143.138.47035 LAST_ACK tcp4 0 11794 216.238.35.204.80 209.133.121.160.57120 LAST_ACK tcp4 0 11368 216.238.35.204.80 38.240.127.3.1112 LAST_ACK tcp4 0 17520 216.238.35.206.80 216.238.225.156.1402 LAST_ACK tcp4 0 11794 216.238.35.204.80 24.29.59.89.2102 LAST_ACK tcp4 0 4626 216.238.35.206.80 152.163.189.68.27637 LAST_ACK tcp4 0 0 216.238.35.204.80 216.77.225.224.24631 FIN_WAIT_2 tcp4 0 0 216.238.35.206.80 136.215.199.3.3660 LAST_ACK tcp4 0 8196 216.238.35.204.80 63.53.78.178.2246 LAST_ACK tcp4 0 4096 216.238.35.206.80 194.19.141.241.3256 LAST_ACK tcp4 0 4096 216.238.35.206.80 194.19.141.241.3249 LAST_ACK tcp4 0 0 216.238.35.204.80 24.29.72.189.1083 LAST_ACK tcp4 0 540 216.238.35.206.80 216.35.116.108.38090 LAST_ACK tcp4 0 4096 216.238.35.206.80 194.19.141.241.3167 LAST_ACK tcp4 0 0 216.238.35.206.80 128.59.142.35.1038 LAST_ACK tcp4 0 0 216.238.35.206.80 136.215.199.3.1787 LAST_ACK tcp4 0 170 216.238.35.204.80 209.185.143.138.45445 LAST_ACK tcp4 0 4096 216.238.35.206.80 194.19.141.241.3146 LAST_ACK tcp4 0 170 216.238.35.204.80 209.185.143.138.57109 LAST_ACK tcp4 0 11794 216.238.35.204.80 209.133.121.160.57085 LAST_ACK tcp4 0 0 216.238.35.204.80 216.238.9.82.2326 LAST_ACK tcp4 0 0 216.238.35.70.22 *.* LISTEN tcp4 0 0 172.16.0.70.22 *.* LISTEN tcp4 0 0 *.80 *.* LISTEN tcp4 0 0 *.443 *.* LISTEN tcp4 0 0 172.16.0.70.23 *.* LISTEN tcp4 0 0 172.16.0.70.21 *.* LISTEN tcp4 0 0 *.111 *.* LISTEN udp4 0 0 172.16.0.70.985 172.16.0.50.2049 udp4 0 0 172.16.0.70.994 172.16.0.2.2049 udp4 0 0 172.16.0.70.1000 172.16.0.2.2049 udp4 0 0 172.16.0.70.1006 172.16.0.4.2049 udp4 0 0 172.16.0.70.1012 172.16.0.2.2049 udp4 0 0 *.111 *.* udp4 0 0 172.16.0.70.1023 172.16.0.4.2049 Active UNIX domain sockets Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr fffffe000ec89f80 stream 0 0 fffffe000ec0d120 0 0 0 /tmp/gcache_port -- Tom Holmes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" 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 Oct 10 12:54:33 2000 Delivered-To: freebsd-isp@freebsd.org Received: from troi.csw.net (troi.csw.net [209.136.192.23]) by hub.freebsd.org (Postfix) with ESMTP id 69CC037B502 for ; Tue, 10 Oct 2000 12:54:30 -0700 (PDT) Received: from ssaos2 (ssaos2.csw.net [209.136.201.13]) by troi.csw.net (8.9.3/8.9.3) with SMTP id OAA67254 for ; Tue, 10 Oct 2000 14:54:23 -0500 (CDT) (envelope-from lambert@cswnet.com) Message-Id: <200010101954.OAA67254@troi.csw.net> From: lambert@cswnet.com Date: Tue, 10 Oct 2000 14:48:12 -0400 To: freebsd-isp@FreeBSD.ORG In-Reply-To: Subject: Re: Radius and Accounting X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v2.10a c10 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On 7 Oct 2000 15:50:14 -0400, in sentex.lists.freebsd.isp you wrote: >>I did this yes ;-) for two POPs but we're going to have 2 more POPs and I >>am concerned about it. At current we use PortMaster 2E (old stuff!) and >>Radius on FreeBSD. I also use proxy radius. When you have a single radius >>server and you've got to authenticate from more that 3 POPs, I thought >>there would be some concern on authent traffic on the link btn the POPs. Just as a point of reference, I have two radius servers for 14,000 dial-up accounts. Radiusd and named both run on the each of the two boxes. Monitoring the ethernet interface for these units with MRTG for about a year has shown that the combined radius and DNS traffic seldom crosses 56K on either box as an average for the 5 minute sample period. Always have two radius servers. Then you can knock one down for service and not show and outage. -- Scott Lambert lambert@cswnet.com Systems and Security Administrator CSW Net, Inc. ================================================================ Written: Tuesday, October 10, 2000 - 02:48 PM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue Oct 10 14:35:30 2000 Delivered-To: freebsd-isp@freebsd.org Received: from blizzard.lightning.net (blizzard.lightning.net [209.51.160.5]) by hub.freebsd.org (Postfix) with ESMTP id E219937B502 for ; Tue, 10 Oct 2000 14:35:22 -0700 (PDT) Received: from nut.lightning.net (nut.lightning.net [209.51.160.16]) by blizzard.lightning.net (8.11.0/8.11.0) with ESMTP id e9ALVVx18374; Tue, 10 Oct 2000 17:31:31 -0400 (EDT) Message-Id: <4.3.2.7.2.20001010171808.04bab6f0@mail.lightning.net> X-Sender: jreddy@mail.lightning.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 10 Oct 2000 17:31:55 -0400 To: freebsd-isp@FreeBSD.ORG From: John Reddy Subject: 3Com 3C509 - packet dropping In-Reply-To: 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've got a 3Com 3C509 server NIC that every now and then will simply stop working for approximately 10 - 30 minutes. All throughout this period, I receive the error message: xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! The machine averages about 600kbps in and out, with approximately 3000 to 3500 concurrent connections when this occurs. My question is has anyone seen this problem before? If so, do you know of a fix for this? I've seen this problem before on other versions of FreeBSD in other systems. I know it's not the core OS, because we've pushed similar amounts of bandwidth and connections through other NICs without problem. Either it's the card or the driver. I'd try to look at the driver code if I could, but I'm no coder. -John Reddy -- My public PGP key may be found at http://www.lightning.net/~jreddy John Patrick Reddy Sr. System Administrator Lightning Internet Services, LLC. Tel.(516)248-8400x123 327 Sagamore Ave Pag.(888)935-2700 Mineola, NY 11501 Fax.(516)248-8897 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed Oct 11 21:38:25 2000 Delivered-To: freebsd-isp@freebsd.org Received: from reef.island.net.au (reef.island.net.au [203.28.142.4]) by hub.freebsd.org (Postfix) with ESMTP id 32FED37B502 for ; Wed, 11 Oct 2000 21:38:21 -0700 (PDT) Received: from hansolo (solo.island.net.au [203.28.142.5]) by reef.island.net.au (8.11.1/8.11.1) with SMTP id e9C4c1r80771; Thu, 12 Oct 2000 15:38:01 +1100 (EST) Message-ID: <001d01c03406$2df12380$088ea8c0@island.net.au> From: "Hugh Blandford" To: "Gabriel Ambuehl" , References: <137180637703.20001009132950@buz.ch> Subject: Re: Management CGI Script for .htaccess protection Date: Thu, 12 Oct 2000 15:37:50 +1100 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 Hi, I came across the following: http://stein.cshl.org/~lstein/user_manage/ Regards, Hugh Blandford ----- Original Message ----- From: "Gabriel Ambuehl" To: Sent: Monday, October 09, 2000 10:29 PM Subject: Management CGI Script for .htaccess protection > Hello, > I'm desperately seeking a nice, if possible GPL or similar licensed, > CGI script to control .htaccess/.htpasswd protection on virtual Apache > webservers through an easy web based GUI. > I looked at quite a lot of script from cgi-resources.com but either > found the licence inacceptable (I need to customize the whole thing > at least to some degree) or the scripts had so broken UIs that I didn't > want them because explaining the users how they work would require way > more work than doing the setup of the protection my self... > I can't be the only one with such a need, so any suggestions would > greatly be appreciated. > > > > Best regards, > Gabriel > > > > > 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 Thu Oct 12 4: 3:34 2000 Delivered-To: freebsd-isp@freebsd.org Received: from siafu.iconnect.co.ke (upagraha.iconnect.co.ke [209.198.248.2]) by hub.freebsd.org (Postfix) with ESMTP id 6238437B503 for ; Thu, 12 Oct 2000 04:03:29 -0700 (PDT) Received: from [212.22.163.2] (helo=poeza.iconnect.co.ke) by siafu.iconnect.co.ke with esmtp (Exim 2.12 #1) id 13jg7P-000D26-00; Thu, 12 Oct 2000 14:01:47 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.16 #1) id 13jgA6-0009xM-00; Thu, 12 Oct 2000 14:04:34 +0300 Date: Thu, 12 Oct 2000 14:04:34 +0300 From: Odhiambo Washington To: FBSD-ISP Subject: Processing details files Message-ID: <20001012140434.A38247@poeza.iconnect.co.ke> Mail-Followup-To: Odhiambo Washington , FBSD-ISP Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD poeza.iconnect.co.ke 3.5-STABLE FreeBSD 3.5-STABLE X-URL: web.iconnect.co.ke/users/wash X-Accept-Language: en fr X-Editor: Pico http://www.washington.edu/ X-Location: Mombasa, Kenya, East Africa X-Uptime: 1:40PM up 3 days, 16:28, 1 user, load averages: 0.22, 0.20, 0.09 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Kindly advise how I can process such a file: NB: Did I mention to you that I have no idea how to write a script? ;-) Log starts on Tue Aug 1 00:01:15 2000. Date Logout Userid IP Time Term M# Sent(b) Recieved(b) 08/06/20 11:09:23 caacall@mombasa 20 78.45 Idle 27 416836 437705 08/06/20 23:19:01 caacall@mombasa 20 701.3 Lost 27 6369328 5897091 08/07/20 13:40:18 caacall@mombasa 20 316.0 Lost 27 1455872 1472357 08/07/20 16:52:30 caacall@mombasa 20 185.5 Lost 27 740305 462882 08/07/20 22:10:52 caacall@mombasa 20 307.9 Lost 27 2350597 2499529 08/07/20 23:31:28 caacall@mombasa 20 78.65 User 27 144726 300747 08/08/20 09:42:25 caacall@mombasa 20 44.68 Idle 27 502168 520524 I know I may be asking for so much but pls just help me out. I need a small script that will take a file with this date and give me the TOTALS for column5, column8 and column9 If possible, if I can get col5 interpreted into hrs:min:sec Any little help highly appreciated. -Wash -- Odhiambo Washington Inter-Connect Ltd., wash@iconnect.co.ke 5th Flr Furaha Plaza Tel: 254 11 222604 Nkrumah Rd., Fax: 254 11 222636 PO Box 83613 MOMBASA, KENYA. A leading authority is someone lucky who guessed right. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Oct 12 9:24:46 2000 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 D230137B503 for ; Thu, 12 Oct 2000 09:24:42 -0700 (PDT) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 13jkmS-0002vz-00; Thu, 12 Oct 2000 09:00:28 -0700 Date: Thu, 12 Oct 2000 09:00:27 -0700 (PDT) From: Tom Samplonius To: John Reddy Cc: freebsd-isp@FreeBSD.ORG Subject: Re: 3Com 3C509 - packet dropping In-Reply-To: <4.3.2.7.2.20001010171808.04bab6f0@mail.lightning.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, 10 Oct 2000, John Reddy wrote: > I've got a 3Com 3C509 server NIC that every now and then will simply stop ... > xl0: no memory for rx list -- packet dropped! > xl0: no memory for rx list -- packet dropped! 3COM 509 + xl is notoriously troublesome. Use an Intel card (fxp driver) instead. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Oct 12 12:21:54 2000 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 C854B37B503 for ; Thu, 12 Oct 2000 12:21:51 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 5B2B61C41; Thu, 12 Oct 2000 15:21:51 -0400 (EDT) Date: Thu, 12 Oct 2000 15:21:51 -0400 From: Bill Fumerola To: Tom Samplonius Cc: John Reddy , freebsd-isp@FreeBSD.ORG Subject: Re: 3Com 3C509 - packet dropping Message-ID: <20001012152151.I37870@jade.chc-chimes.com> References: <4.3.2.7.2.20001010171808.04bab6f0@mail.lightning.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from tom@sdf.com on Thu, Oct 12, 2000 at 09:00:27AM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Oct 12, 2000 at 09:00:27AM -0700, Tom Samplonius wrote: > > On Tue, 10 Oct 2000, John Reddy wrote: > > > I've got a 3Com 3C509 server NIC that every now and then will simply stop > ... > > xl0: no memory for rx list -- packet dropped! > > xl0: no memory for rx list -- packet dropped! > > > 3COM 509 + xl is notoriously troublesome. Use an Intel card (fxp > driver) instead. Except the 3com 509 and the xl driver are mutually exclusive. The user has a reliable 3c905 actually and simply (as I already said) needs to tune his network buffers more appropriatly. I've already talked to one of his cohorts(hi gersh) off-list so this is a dead issue (as far as this mailing list is concerned). -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Oct 12 18:31:37 2000 Delivered-To: freebsd-isp@freebsd.org Received: from giroc.albury.net.au (giroc.albury.NET.AU [203.15.244.13]) by hub.freebsd.org (Postfix) with ESMTP id 4869837B502 for ; Thu, 12 Oct 2000 18:31:34 -0700 (PDT) Received: (from nicks@localhost) by giroc.albury.net.au (8.9.3/8.9.3) id MAA97367; Fri, 13 Oct 2000 12:31:12 +1100 (EST) Date: Fri, 13 Oct 2000 12:31:12 +1100 From: Nick Slager To: Odhiambo Washington Cc: FBSD-ISP Subject: Re: Processing details files Message-ID: <20001013123112.A88285@albury.net.au> References: <20001012140434.A38247@poeza.iconnect.co.ke> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001012140434.A38247@poeza.iconnect.co.ke>; from wash@iconnect.co.ke on Thu, Oct 12, 2000 at 02:04:34PM +0300 X-Homer: Whoohooooooo! Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thus spake Odhiambo Washington (wash@iconnect.co.ke): > Kindly advise how I can process such a file: > > NB: Did I mention to you that I have no idea how to write a script? ;-) > > Log starts on Tue Aug 1 00:01:15 2000. > Date Logout Userid IP Time Term M# Sent(b) Recieved(b) > 08/06/20 11:09:23 caacall@mombasa 20 78.45 Idle 27 416836 437705 > 08/06/20 23:19:01 caacall@mombasa 20 701.3 Lost 27 6369328 5897091 awk and sed are your friends. Pick up a copy of 'Sed and Awk' (Oreilly). Nick -- From a Sun Microsystems bug report (#4102680): "Workaround: don't pound on the mouse like a wild monkey." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Oct 12 18:47:48 2000 Delivered-To: freebsd-isp@freebsd.org Received: from gatekeeper.viper.net.au (gatekeeper.viper.net.au [203.31.238.1]) by hub.freebsd.org (Postfix) with ESMTP id DEE1C37B503 for ; Thu, 12 Oct 2000 18:47:42 -0700 (PDT) Received: from localhost (mark@localhost) by gatekeeper.viper.net.au (8.9.3/8.9.3) with ESMTP id MAA61089; Fri, 13 Oct 2000 12:47:27 +1100 (EST) (envelope-from mark@viper.net.au) Date: Fri, 13 Oct 2000 12:47:27 +1100 (EST) From: Mark Russell To: Odhiambo Washington Cc: FBSD-ISP Subject: Re: Processing details files In-Reply-To: <20001012140434.A38247@poeza.iconnect.co.ke> 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, 12 Oct 2000, Odhiambo Washington wrote: > Hi > Kindly advise how I can process such a file: /usr/ports/net/radreport > > NB: Did I mention to you that I have no idea how to write a script? ;-) > > Log starts on Tue Aug 1 00:01:15 2000. > Date Logout Userid IP Time Term M# Sent(b) Recieved(b) > 08/06/20 11:09:23 caacall@mombasa 20 78.45 Idle 27 416836 437705 > 08/06/20 23:19:01 caacall@mombasa 20 701.3 Lost 27 6369328 5897091 > 08/07/20 13:40:18 caacall@mombasa 20 316.0 Lost 27 1455872 1472357 > 08/07/20 16:52:30 caacall@mombasa 20 185.5 Lost 27 740305 462882 > 08/07/20 22:10:52 caacall@mombasa 20 307.9 Lost 27 2350597 2499529 > 08/07/20 23:31:28 caacall@mombasa 20 78.65 User 27 144726 300747 > 08/08/20 09:42:25 caacall@mombasa 20 44.68 Idle 27 502168 520524 > > I know I may be asking for so much but pls just help me out. > I need a small script that will take a file with this date and give me the > TOTALS for column5, column8 and column9 > > If possible, if I can get col5 interpreted into hrs:min:sec > Any little help highly appreciated. > > > -Wash > > -- > Odhiambo Washington Inter-Connect Ltd., > wash@iconnect.co.ke 5th Flr Furaha Plaza > Tel: 254 11 222604 Nkrumah Rd., > Fax: 254 11 222636 PO Box 83613 MOMBASA, KENYA. > > A leading authority is someone lucky who guessed right. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ Mark Russell mark@viper.net.au ph 61 + 2 + 9699 3837 viper.net.au http://www.viper.net.au fax 61 + 2 + 9699 3841 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ http://www.google.com/search?q=mark+sux To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Oct 13 4:13: 6 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mail.camelot.de (mailout.camelot.de [195.30.224.18]) by hub.freebsd.org (Postfix) with ESMTP id 96CEF37B503; Fri, 13 Oct 2000 04:13:01 -0700 (PDT) Received: from robin.camelot.de (bofax@robin.camelot.de [195.30.224.3]) by mail.camelot.de (8.11.1/8.11.1) with ESMTP id e9DBCts73155 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Fri, 13 Oct 2000 13:12:56 +0200 (CEST) Received: (from bofax@localhost) by robin.camelot.de (8.11.1/8.11.1) id e9DBCtT73152; Fri, 13 Oct 2000 13:12:55 +0200 (CEST) Date: Fri, 13 Oct 2000 12:59:47 +0200 From: Florian Bofinger To: freebsd-questions@camelot.de, freebsd-isp@camelot.de Subject: NIS/YP getpwnam timeout in 3.5-RELEASE? Message-ID: <20001013125947.C15981@camelot.de> Mail-Followup-To: Florian Bofinger , freebsd-questions@camelot.de, freebsd-isp@camelot.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, since a few days, our NIS shows strange behaviour. When calling getpwnam on a NIS client for a valid, existing, plussed loginname (+user:::::::::), getpwnam->pw_passwd sometimes returns the crypted password (which is the right behaviour) but sometimes returns '*'. Is it possible, that the ypmatch-call in getpwent.c does a timeout? Does if (_yp_enabled == -1) _ypinitdb(); if (_yp_enabled) rval = _getyppass(&_pw_passwd, name, "passwd.byname"); show, that if _ypinitdb() does not work, YP is not used at all? How can it be, that getpwnam->pw_passwd returns "*" instead of getpwnam beeing NULL? Anyone any suggestions? Greetings, Florian -- Florian Bofinger - CameloT e.K. www.camelot.de - Der "sagenhafte" Internet Full-Service Provider 'Can't buy what I want because it's free' - Pearl Jam (FreeBSD rocks) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Oct 13 9:14:42 2000 Delivered-To: freebsd-isp@freebsd.org Received: from hotmail.com (f194.pav1.hotmail.com [64.4.31.194]) by hub.freebsd.org (Postfix) with ESMTP id DD6D437B6A8 for ; Fri, 13 Oct 2000 09:13:02 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 13 Oct 2000 09:12:51 -0700 Received: from 204.120.54.1 by pv1fd.pav1.hotmail.msn.com with HTTP; Fri, 13 Oct 2000 16:12:51 GMT X-Originating-IP: [204.120.54.1] From: "Jonathan M. Slivko" To: freebsd-isp@freebsd.org Subject: Machine not being able to go on the Internet Date: Fri, 13 Oct 2000 12:12:51 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 13 Oct 2000 16:12:51.0446 (UTC) FILETIME=[6FA99160:01C03530] Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a machine running FreeBSD 4.1.1-RELEASE. It installed fine and was working great. However, when I tried to put it on my network, it wouldn't load on the network. Any suggestions for how to bypass the problem? I haven't tried changing the network card or anything like that. -- Jonathan M. Slivko _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Oct 13 10:43:22 2000 Delivered-To: freebsd-isp@freebsd.org Received: from siafu.iconnect.co.ke (upagraha.iconnect.co.ke [209.198.248.2]) by hub.freebsd.org (Postfix) with ESMTP id 2B8BC37B670 for ; Fri, 13 Oct 2000 10:43:17 -0700 (PDT) Received: from [212.22.163.2] (helo=poeza.iconnect.co.ke) by siafu.iconnect.co.ke with esmtp (Exim 2.12 #1) id 13k8po-000Iru-00 for freebsd-isp@freebsd.org; Fri, 13 Oct 2000 20:41:32 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.16 #1) id 13k8sV-000Df4-00 for freebsd-isp@freebsd.org; Fri, 13 Oct 2000 20:44:19 +0300 Date: Fri, 13 Oct 2000 20:44:19 +0300 From: Odhiambo Washington To: freebsd-isp@freebsd.org Subject: Re: Machine not being able to go on the Internet Message-ID: <20001013204419.B52212@poeza.iconnect.co.ke> Mail-Followup-To: Odhiambo Washington , freebsd-isp@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from "Jonathan M. Slivko" on Fri, Oct 13, 2000 at 12:12:51PM -0400 X-Operating-System: FreeBSD poeza.iconnect.co.ke 3.5-STABLE FreeBSD 3.5-STABLE X-Mailer: Mutt http://www.mutt.org/ X-URL: web.iconnect.co.ke/users/wash X-Accept-Language: en fr X-Editor: Pico http://www.washington.edu/ X-Location: Mombasa, Kenya, East Africa X-Uptime: 8:41PM up 4 days, 23:29, 1 user, load averages: 0.00, 0.00, 0.00 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Jonathan M. Slivko [20001013 19:45]: =>I have a machine running FreeBSD 4.1.1-RELEASE. It installed fine and was =>working great. However, when I tried to put it on my network, it wouldn't =>load on the network. Explain what you mean by 'it wouldn't load on the network'. I am running 4.1.1-STABLE. Maybe I can help after you tell exactly what happens. =>Any suggestions for how to bypass the problem? I =>haven't tried changing the network card or anything like that. -- Jonathan I may not be able to guess what the issue is because I haven't quite understood your problem. Hope to hear from you. -Wash -- Odhiambo Washington Inter-Connect Ltd., wash@iconnect.co.ke 5th Flr Furaha Plaza Tel: 254 11 222604 Nkrumah Rd., Fax: 254 11 222636 PO Box 83613 MOMBASA, KENYA. In computing, the mean time to failure keeps getting shorter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Oct 13 11:49:35 2000 Delivered-To: freebsd-isp@freebsd.org Received: from hotmail.com (f315.pav1.hotmail.com [64.4.30.190]) by hub.freebsd.org (Postfix) with ESMTP id 19E2B37B502 for ; Fri, 13 Oct 2000 11:49:33 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 13 Oct 2000 11:49:32 -0700 Received: from 63.68.69.168 by pv1fd.pav1.hotmail.msn.com with HTTP; Fri, 13 Oct 2000 18:49:32 GMT X-Originating-IP: [63.68.69.168] From: "Jonathan M. Slivko" To: wash@iconnect.co.ke, freebsd-isp@freebsd.org Subject: Re: Machine not being able to go on the Internet Date: Fri, 13 Oct 2000 14:49:32 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 13 Oct 2000 18:49:32.0924 (UTC) FILETIME=[536143C0:01C03546] Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What happens is there is total silence on the network from my machine, not one packet even. I can't get my machine to respond to pings/traceroutes/etc. I am starting to think that it might be a network card that failed me. I was wondering if you possibly came to the same conclusion as I did? Just as a side note, i'm already behind on setting up this server so I need to find out exactly what is going on pretty soon. I would appreciate a speedy reply. -- Jonathan M. Slivko >From: Odhiambo Washington >To: freebsd-isp@freebsd.org >Subject: Re: Machine not being able to go on the Internet >Date: Fri, 13 Oct 2000 20:44:19 +0300 > >* Jonathan M. Slivko [20001013 19:45]: >=>I have a machine running FreeBSD 4.1.1-RELEASE. It installed fine and was >=>working great. However, when I tried to put it on my network, it wouldn't >=>load on the network. > >Explain what you mean by 'it wouldn't load on the network'. I am running >4.1.1-STABLE. Maybe I can help after you tell exactly what happens. > > >=>Any suggestions for how to bypass the problem? I >=>haven't tried changing the network card or anything like that. -- >Jonathan > >I may not be able to guess what the issue is because I haven't quite >understood your problem. > >Hope to hear from you. > >-Wash > >-- >Odhiambo Washington Inter-Connect Ltd., >wash@iconnect.co.ke 5th Flr Furaha Plaza >Tel: 254 11 222604 Nkrumah Rd., >Fax: 254 11 222636 PO Box 83613 MOMBASA, KENYA. > >In computing, the mean time to failure keeps getting shorter. > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-isp" in the body of the message _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Oct 13 12: 6:17 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id 8BDA137B502 for ; Fri, 13 Oct 2000 12:06:15 -0700 (PDT) Received: (qmail 22169 invoked by uid 3001); 13 Oct 2000 19:06:08 -0000 Received: from natto.numachi.com (198.175.254.216) by numachi.numachi.com with SMTP; 13 Oct 2000 19:06:08 -0000 Received: (qmail 30096 invoked by uid 1001); 13 Oct 2000 19:06:08 -0000 Date: Fri, 13 Oct 2000 15:06:08 -0400 From: Brian Reichert To: "Jonathan M. Slivko" Cc: wash@iconnect.co.ke, freebsd-isp@freebsd.org Subject: Re: Machine not being able to go on the Internet Message-ID: <20001013150608.E29360@numachi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jmslivko@hotmail.com on Fri, Oct 13, 2000 at 02:49:32PM -0400 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Oct 13, 2000 at 02:49:32PM -0400, Jonathan M. Slivko wrote: > What happens is there is total silence on the network from my machine, not > one packet even. Is there a network card configured in rc.conf? What does 'ifconfig -a' show? 'netstat -rn'? We're groping blind, here... > -- Jonathan M. Slivko -- Brian 'you Bastard' Reichert 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sat Oct 14 0:39: 2 2000 Delivered-To: freebsd-isp@freebsd.org Received: from ren.sasknow.com (ren.sasknow.com [207.195.92.131]) by hub.freebsd.org (Postfix) with ESMTP id 6424E37B66E for ; Sat, 14 Oct 2000 00:38:59 -0700 (PDT) Received: from localhost (ryan@localhost) by ren.sasknow.com (8.9.3/8.9.3) with ESMTP id BAA96815; Sat, 14 Oct 2000 01:43:26 -0600 (CST) (envelope-from ryan@sasknow.com) Date: Sat, 14 Oct 2000 01:43:26 -0600 (CST) From: Ryan Thompson To: Brian Reichert Cc: "Jonathan M. Slivko" , wash@iconnect.co.ke, freebsd-isp@FreeBSD.ORG Subject: Re: Machine not being able to go on the Internet In-Reply-To: <20001013150608.E29360@numachi.com> Message-ID: Organization: SaskNow Technologies [www.sasknow.com] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brian Reichert wrote to Jonathan M. Slivko: > On Fri, Oct 13, 2000 at 02:49:32PM -0400, Jonathan M. Slivko wrote: > > What happens is there is total silence on the network from my machine, not > > one packet even. > > Is there a network card configured in rc.conf? > > What does 'ifconfig -a' show? > > 'netstat -rn'? > > We're groping blind, here... > Good suggestions... I'll expand a bit for Jonathan. Jonathan; As you've said this is a "server", you are probably using static addresses. Ensure that your addresses are properly configured in rc.conf, and that subnetting/routing TO the machine (or local network segment) is configured correctly. Also ensure that your subnet masks are set correctly on your local machine. If you are not up on BSD network administration, routing, subnets or IP in general, this process will probably not go very smoothly ;-) When you say "nothing on the network", I assume you are putting another machine's network card into promiscuous mode (i.e., "packet sniffing"), on the same collision domain? Recall that if your machines are plugged into a switch, they will NOT share the collision domain for broadcast packets, and one machine's traffic will not be visible to other machines on the LAN, unless the packets are destined for the promiscuous host. I may be grasping at straws, but there is very little else to get ahold of given your problem description. I'm hoping for a lucky shot, here ;-) If public addresses don't get you anywhere, assign the NIC a private IP address from an RFC 1918 subnet that isn't in use on your LAN. (I.e, 10.1.0.1), and assign another machine on the same Ethernet segment (this IS an Ethernet we're talking about, right?) an address in the same subnet (10.1.0.2), and try your tests using those addresses. Check cabling (going to switch/router/hub? use standard UTP... going to another NIC? make sure you use crossover). Swap in another nic. Check dmesg output and make sure that your card is probed correctly. Test basic TCP/IP on the machine itself (ping the local IP address(es), and 127.0.0.1). > > -- Jonathan M. Slivko > > -- Ryan Thompson Network Administrator, 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 Sat Oct 14 8:53:14 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mail.camelot.de (mailout.camelot.de [195.30.224.18]) by hub.freebsd.org (Postfix) with ESMTP id D76A937B502; Sat, 14 Oct 2000 08:53:08 -0700 (PDT) Received: from robin.camelot.de (bofax@robin.camelot.de [195.30.224.3]) by mail.camelot.de (8.11.1/8.11.1) with ESMTP id e9EFr6s26516 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Sat, 14 Oct 2000 17:53:07 +0200 (CEST) Received: (from bofax@localhost) by robin.camelot.de (8.11.1/8.11.1) id e9EFr6e26513; Sat, 14 Oct 2000 17:53:06 +0200 (CEST) Date: Sat, 14 Oct 2000 14:52:23 +0200 From: Florian Bofinger To: freebsd-questions@camelot.de, freebsd-isp@camelot.de Subject: Re: NIS/YP getpwnam timeout in 3.5-RELEASE? Message-ID: <20001014145223.B20898@camelot.de> Mail-Followup-To: Florian Bofinger , freebsd-questions@camelot.de, freebsd-isp@camelot.de References: <20001013125947.C15981@camelot.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001013125947.C15981@camelot.de>; from bofax@camelot.de on Fri, Oct 13, 2000 at 12:59:47PM +0200 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, On Fri, Oct 13, 2000 at 12:59:47PM +0200, Florian Bofinger wrote: > Hi, > > since a few days, our NIS shows strange behaviour. > > When calling getpwnam on a NIS client for a valid, existing, plussed loginname > (+user:::::::::), getpwnam->pw_passwd sometimes returns the crypted password > (which is the right behaviour) but sometimes returns '*'. Is it possible, that > the ypmatch-call in getpwent.c does a timeout? > > Does > > if (_yp_enabled == -1) > _ypinitdb(); > if (_yp_enabled) > rval = _getyppass(&_pw_passwd, name, "passwd.byname"); > > show, that if _ypinitdb() does not work, YP is not used at all? > > How can it be, that getpwnam->pw_passwd returns "*" instead of > getpwnam beeing NULL? > > Anyone any suggestions? I should have taken a look into /var/log/messages on the YP server, where it says a few times: Oct 12 16:40:27 hostname ypserv[189]: access to master.passwd.byname denied -- client X.X.X.X:2305 not privileged Why does ypbind use TCP ports > 1023? It is possible, that there are no ports < 1024 free, but ypbind never should use ports above > 1023 or am I wrong? Greetings, Florian -- Florian Bofinger - CameloT e.K. www.camelot.de - Der "sagenhafte" Internet Full-Service Provider 'Can't buy what I want because it's free' - Pearl Jam (FreeBSD rocks) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sat Oct 14 9:22: 1 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mail.punisher.co.uk (six40.gemsoft.co.uk [195.10.224.75]) by hub.freebsd.org (Postfix) with ESMTP id 252CC37B502 for ; Sat, 14 Oct 2000 09:21:57 -0700 (PDT) Received: from lfarr (bka.punisher.co.uk [192.168.10.200]) by mail.punisher.co.uk (8.9.3/8.9.3) with SMTP id RAA00192 for ; Sat, 14 Oct 2000 17:21:41 +0100 (BST) (envelope-from l.farr@epcdirect.co.uk) Reply-To: From: "Lawrence Farr" To: Subject: Log in Vain Date: Sat, 14 Oct 2000 17:22:17 +0100 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.50.4133.2400 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Posted this to questions a while back and got no answer. Can anyone here help? Lawrence Farr EPC Direct Limited mailto:lawrence@epcdirect.co.uk T:01179666123 F:01179666111 M:07970780901 -----Original Message----- From: Lawrence Farr [mailto:l.farr@epcdirect.co.uk] Sent: 14 September 2000 15:11 To: FreeBSD Questions Owner Subject: Log in Vain Hi, I have log in vain set on a server that I am getting paranoid about. I keep getting this as my 2 DNS boxes talk to it, though DNS queries are fine on it. Pretty much everything is blocked in hosts.allow, so what are they trying to talk to? xxx.xxx.xxx.11 is the server in question, .4 and .1 are my DNS boxes. > Connection attempt to UDP xxx.xxx.xxx.11:3227 from xxx.xxx.xxx.1:53 > Connection attempt to UDP xxx.xxx.xxx.11:4019 from xxx.xxx.xxx.1:53 > Connection attempt to UDP xxx.xxx.xxx.11:4414 from xxx.xxx.xxx.1:53 > Connection attempt to UDP xxx.xxx.xxx.11:4416 from xxx.xxx.xxx.4:53 > Connection attempt to UDP xxx.xxx.xxx.11:4417 from xxx.xxx.xxx.1:53 > Connection attempt to UDP xxx.xxx.xxx.11:4418 from xxx.xxx.xxx.4:53 > Connection attempt to UDP xxx.xxx.xxx.11:4419 from xxx.xxx.xxx.4:53 > Connection attempt to UDP xxx.xxx.xxx.11:4472 from xxx.xxx.xxx.1:53 > Connection attempt to UDP xxx.xxx.xxx.11:4682 from xxx.xxx.xxx.1:53 > Connection attempt to UDP xxx.xxx.xxx.11:4691 from xxx.xxx.xxx.4:53 > Connection attempt to UDP xxx.xxx.xxx.11:4694 from xxx.xxx.xxx.1:53 > Connection attempt to UDP xxx.xxx.xxx.11:1277 from xxx.xxx.xxx.1:53 > Connection attempt to UDP xxx.xxx.xxx.11:1278 from xxx.xxx.xxx.4:53 > Connection attempt to UDP xxx.xxx.xxx.11:1279 from xxx.xxx.xxx.4:53 > Connection attempt to UDP xxx.xxx.xxx.11:1623 from xxx.xxx.xxx.1:53 Thanks! Lawrence Farr EPC Direct Limited mailto:lawrence@epcdirect.co.uk T:01179666123 F:01179666111 M:07970780901 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sat Oct 14 10:17:41 2000 Delivered-To: freebsd-isp@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 3D4F337B502 for ; Sat, 14 Oct 2000 10:17:38 -0700 (PDT) Received: (qmail 23986 invoked by uid 1001); 14 Oct 2000 17:17:36 +0000 (GMT) To: lawrence@epcdirect.co.uk, l.farr@epcdirect.co.uk Cc: freebsd-isp@freebsd.org Subject: Re: Log in Vain From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 14 Oct 2000 17:22:17 +0100" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 14 Oct 2000 19:17:35 +0200 Message-ID: <23983.971543855@verdi.nethelp.no> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have log in vain set on a server that I am getting paranoid about. I keep > getting this as my 2 DNS boxes talk to it, though DNS queries are fine on > it. > Pretty much everything is blocked in hosts.allow, so what are they trying to > talk to? The DNS boxes are trying to send replies to the clients - but after the clients have closed the listening socket. Perfectly normal and expected. Steinar Haug, Nethelp consulting, sthaug@nethelp.no > xxx.xxx.xxx.11 is the server in question, .4 and .1 are my DNS boxes. > > > Connection attempt to UDP xxx.xxx.xxx.11:3227 from xxx.xxx.xxx.1:53 > > Connection attempt to UDP xxx.xxx.xxx.11:4019 from xxx.xxx.xxx.1:53 > > Connection attempt to UDP xxx.xxx.xxx.11:4414 from xxx.xxx.xxx.1:53 > > Connection attempt to UDP xxx.xxx.xxx.11:4416 from xxx.xxx.xxx.4:53 > > Connection attempt to UDP xxx.xxx.xxx.11:4417 from xxx.xxx.xxx.1:53 > > Connection attempt to UDP xxx.xxx.xxx.11:4418 from xxx.xxx.xxx.4:53 > > Connection attempt to UDP xxx.xxx.xxx.11:4419 from xxx.xxx.xxx.4:53 > > Connection attempt to UDP xxx.xxx.xxx.11:4472 from xxx.xxx.xxx.1:53 > > Connection attempt to UDP xxx.xxx.xxx.11:4682 from xxx.xxx.xxx.1:53 > > Connection attempt to UDP xxx.xxx.xxx.11:4691 from xxx.xxx.xxx.4:53 > > Connection attempt to UDP xxx.xxx.xxx.11:4694 from xxx.xxx.xxx.1:53 > > Connection attempt to UDP xxx.xxx.xxx.11:1277 from xxx.xxx.xxx.1:53 > > Connection attempt to UDP xxx.xxx.xxx.11:1278 from xxx.xxx.xxx.4:53 > > Connection attempt to UDP xxx.xxx.xxx.11:1279 from xxx.xxx.xxx.4:53 > > Connection attempt to UDP xxx.xxx.xxx.11:1623 from xxx.xxx.xxx.1:53 > > Thanks! > > Lawrence Farr > EPC Direct Limited mailto:lawrence@epcdirect.co.uk > T:01179666123 F:01179666111 M:07970780901 > > > > 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