Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 39626 invoked from network); 28 Mar 2005 23:04:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Mar 2005 23:04:42 -0000 Received: (qmail 31164 invoked by uid 500); 28 Mar 2005 23:04:41 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 30452 invoked by uid 500); 28 Mar 2005 23:04:39 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 30437 invoked by uid 99); 28 Mar 2005 23:04:39 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from ajax-1.apache.org (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 28 Mar 2005 15:04:34 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 117352B8 for ; Tue, 29 Mar 2005 01:04:32 +0200 (CEST) Message-ID: <1090728438.1112051072070.JavaMail.jira@ajax.apache.org> Date: Tue, 29 Mar 2005 01:04:32 +0200 (CEST) From: "Dain Sundstrom (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Created: (GERONIMO-620) ServiceAccessController does not support ip6address Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ServiceAccessController does not support ip6address --------------------------------------------------- Key: GERONIMO-620 URL: http://issues.apache.org/jira/browse/GERONIMO-620 Project: Geronimo Type: Bug Components: OpenEJB Reporter: Dain Sundstrom Assigned to: Gianny DAMOUR The ServiceAccessController class does not work with ip6 addresses. I have added an if statement that skips ip6 addresses. Also I think we should use the standard ip bit mask filtering rule style for the masks that xinetd uses. I found a ok description of the style here http://www.hn.edu.cn/book/NetWork/NetworkingBookshelf_2ndEd/tcp/ch12_05.htm (look near the bottom of this page) but I bet there are better ones out there. 172.16.12.5 defines a specific host 129.6.0.0 defines all hosts with an address that begins with 129.6 0.0.0.0 matches all addresses 172.16.12.{3,6,8,23} defines four different hosts: 172.16.12.3, 172.16.12.6, 172.16.12.8, and 172.16.12.23 172.16.12.128/25 match every address from 172.16.12.128 to 172.16.12.255 I also think you can do the following which is an address and a mask: 172.16.12.0/255.255.224.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira