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 <[EMAIL PROTECTED]>, 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 [EMAIL PROTECTED]
>with "unsubscribe freebsd-hackers" in the body of the message
>
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
