From owner-freebsd-net Fri Dec 22 6:33:49 2000 From owner-freebsd-net@FreeBSD.ORG Fri Dec 22 06:33:45 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id DE91A37B402; Fri, 22 Dec 2000 06:33:43 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eBMC4Yb70740; Fri, 22 Dec 2000 13:04:34 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Archie Cobbs Cc: John Smith , freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: New netgraph features? In-Reply-To: Your message of "Thu, 21 Dec 2000 13:57:10 PST." <200012212157.eBLLvAU78207@curve.dellroad.org> Date: Fri, 22 Dec 2000 13:04:34 +0100 Message-ID: <70738.977486674@critter> From: Poul-Henning Kamp Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I may not have caught the drift here, but if you send meta-data across the net, wouldn't some kind of authentication be needed ? Poul-Henning In message <200012212157.eBLLvAU78207@curve.dellroad.org>, Archie Cobbs writes: >John Smith writes: >> Well, may be I didn't said exactly what I wanted to. >> If we use say, ksocket nodes as a tunnel, we will >> transfer the data - ok, but what about metadata? >> May be I should say 'to connect two netgraphs'? >> May be this is a lost cause, but that's why I'm asking. > >Yes, there would need to be some extra stuff. Here are some >quick possibilities.. > >- We'd need to enhace the definition of a netgraph address > to include, say, an IP address, eg.: > > $ ngctl msg 192.168.1.12:foo: blah blah > >- Encode control messsages in their ASCII forms for transit > across the network > >- Pick a well known UDP port to be used for netgraph messages > and data packets > >- Create a node type that could listen on this port (using ng_ksocket) > and do the required encoding/decoding. > >-Archie > >__________________________________________________________________________ >Archie Cobbs * Packet Design * http://www.packetdesign.com > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message