From owner-freebsd-net Mon Oct 4 15:24:23 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 330891529E for ; Mon, 4 Oct 1999 15:24:22 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id PAA58534 for ; Mon, 4 Oct 1999 15:24:21 -0700 (PDT) Date: Mon, 4 Oct 1999 15:24:20 -0700 (PDT) From: Julian Elischer To: net@freebsd.org Subject: PPPoE question (repeat) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does ANYONE have any ideas of the expected formats of the AC-Name and Service-Name fields? I'm trying to figure out if it's possible to 'bind' a listenning socket ahead of time (not really, but the analagy works) to a service, so that it gets all teh PADI requests to that service, or whether I'd have to bind using a regexp pattern (e.g. ".+@whistle.com"). Obviously that would require some sort of pattern matching code in the kernel. (We already have similar in the CAM code for QUIRK matching). I don't know however how extensive this needs to be. I can imagine that "*@my-isp.net" might be sufficient. The alternative is to pass ALL PADI service requests to a userland agent that interprets the packets and decides whether or not to offer a service to the requesting client machine. I'd rather have the option of some pre-processing in the kernel so that the the server daemons can be simpler in the case where a server is only selecting simple services to respond to. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message