From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.50) id 1EbJio-00009r-Eo for garchives@archives.gentoo.org; Sun, 13 Nov 2005 15:24:47 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jADFNKNe030106; Sun, 13 Nov 2005 15:23:20 GMT Received: from psmtp03.wxs.nl (psmtp03.wxs.nl [195.121.247.12]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jADFHlmN010379 for ; Sun, 13 Nov 2005 15:17:47 GMT Received: from [10.0.0.150] (ip3e83ab52.speed.planet.nl [62.131.171.82]) by psmtp03.wxs.nl (iPlanet Messaging Server 5.2 HotFix 2.07 (built Jun 24 2005)) with ESMTP id <0IPW005NUFTMHJ@psmtp03.wxs.nl> for gentoo-user@lists.gentoo.org; Sun, 13 Nov 2005 16:17:46 +0100 (MET) Date: Sun, 13 Nov 2005 16:17:32 +0100 From: Holly Bostick Subject: Re: [gentoo-user] Re: [Iptables related] How to make one machine only talk on loc lan In-reply-to: <87veyxf2gt.fsf@newsguy.com> To: gentoo-user@lists.gentoo.org Message-id: <4377590C.80407@planet.nl> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7BIT X-Accept-Language: nl-NL, nl, en User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051029) X-Enigmail-Version: 0.92.0.0 References: <871x1lsamp.fsf@newsguy.com> <200511121717.40496.john@jolet.net> <873bm1gyb5.fsf@newsguy.com> <200511122114.17516.john@jolet.net> <87veyxf2gt.fsf@newsguy.com> X-Archives-Salt: 68b5e713-eb13-40ee-90d0-491d30051922 X-Archives-Hash: 0bd3a4d0038f61ee0065ae68bb56ba6b Harry Putnam schreef: > Apparently you too are not looking at the router I've specified: > NETGEAR FVS318 > Not to mix in (not having a Netgear router), but I wonder if perhaps the reason you are not seeing the ability to block IPs (which several people have said exists) is because you have not enabled it by setting a schedule: > John Jolet writes (twice): >>> >>>> look at the schedule setups. set them up only to be able to >>>> access the internet for, say a second on sunday at 3 am, and >>>> not for the rest of the time.... >>> >> >> here. you set a schedule, then limit certain ip addresses As I said, I'm not familiar with this router, but I am familiar with the concept of options not becoming enable-able (and often even visible) until some precondition has been met (in this case setting a schedule). Certainly it would not seem logical for a high-end router *not* to be able to block IPs (and fairly thoroughly), especially if lower-end models of the same brand are capable of doing so; certainly it seems possible that such a device would not be "interested" in knowing what you want it to do (ip blocks) if it didn't have a category under which to perform the series of actions (the schedule). Just an idea, Holly -- gentoo-user@gentoo.org mailing list