Skip to topic | Skip to bottom
Note: Included topic Gulli.WebTopBar? does not exist yet
Gulli
Gulli.OscSrvr1.1 - 02 Jun 2005 - 21:11 - TWikiGuesttopic end

Start of topic | Skip to actions

OscSrv -- aka OSC_srv

submodules

OscMx? (multiplexer)

port: 5151

a message multiplexer. used for performance degradation, lucidity and message + connection tracking. offers registration of messages in the namespace available for subscription. offers subscription to messages that exist in the namespace and also can do routing.

for the time being, the server returns some kind of responses to the action you can trigger and by default sends them to UDP port 5252 on the message's source host.

the return messages are of form

  • /request/address resultcode(1 success, 0 failure) resulttext(HumanReadable?)

understands the following messages (## means inimplemented):

  • /sub portnumber /message/name (subscribe, assumes the host from the source IP of the subscription message)
  • ## /suba host portnumber /message/name (subscribe alien, i.e. a different host than the one you re sending from)
  • /unsub portnumber /message/name (unsubscribe)
  • /reg /message/name (register this messages (as available for subscription))
  • /unreg /message/name (unregister messages)
  • /version (returns server version, jff)
  • /satan (random response)
  • /route tohost toport /message/name arg1 arg2 ... argn (route a msg to a specific host, you could just as well send it directly, but this way the server may know about you sending to this host)
  • /subscribed hostname (show to what this host is subscribed to, without hostname argument returns the complete subscription array)
  • / (get all messages from the namespace: reserved server messages and all registered messages)

of course you can send any kind of message to the MXer, unregistered messages will be discarded and not forwared to anywhere.

OscData?

port: 5153

this servlet stores the state and history of the system. it carries an to be extensive hostinfo storage-structure that can be queried and information about hosts received much faster than actually looking it up when needed. this is for data like hostname, host distance in terms of route hops, throughput to this host, etc ...

missing:

write data to file and load on startup, schedule rechecks of old data, ...

messages:

  • receive

    • /shutdown (no arguments, experimental, quits server)
    • /host/new (the host/new message from tcpdump2OSC, telling us a new host has been discovered by the sniffer, who carries its own array of known hosts (can be flushed with osc:///flushuhosts -> snifferhost:5154). when this messages is received, a series of lookup requests to OscLkp? are triggered.
    • /map (no arguments. return complete map i.e. state of the system in sequential messages ala /host,/connection,/bla,/blu,...)
    • /traceroute hostip hops (answer from /traceroute hostip query to OscLkp?)
    • /hostname hostip hostname (answer from /hostname hostip query to OscLkp?)

  • sending

    • /traceroute hostaddr (lookup host distance in hops)
    • /hostname hostaddr (lookup host name via DNS)
    • /host id hostname IP-addr hostOS distance/hops band/w age idle localflag packetcount

stores EVERYTHING.

TODO:

  • clean up host list: fix idle checking
  • check map emission

OscLkp? (lookup)

port: 5152

looks up (dynamic) parameters such as routes to hosts, hostnames, bandwidth to host, etc, ...

messages:

  • /hostname hostaddr (return hostname)
  • /traceroute hostaddr (return number of hops to this host)
  • /nmap hostaddr (return remote OS guess, currently suspended because of network load + portscan overflow)
  • /bing $hostaddr (return estimated throughput to this host)

OscChatbot? (self explaining)

port: 5155

makes a forwarder between Osc_Mx and NakenChat?, a telnet chat server. mainly intended jff and maybe debugging reasons. however, at the moment, packets get lost in the current version, so for debugging its maybe not reliable.

Tcpdump2Osc (self explaining)

obsoleted. moved to OscSniff

Http2Osc (cgi module to translate http queries into open sound control)

http2OSC is called like http://localhost/cgi-bin/http2OSC.pl?host=localhost&port=1234&adr=/test/sublevel/hereiam&param1=1&param2=2.34&param3=a+string and echoes (urlencoded) OSC answer.

## OscSrvMrc?

MasterResourceControl? should be some manager script handling all modules above, enabling 1 to more easily start, restart and shutdown the system ... cuzrrently in the making.

we are but packets in the internet of life.

examples

MessaGes

GsrV2

download


to top

I Attachment Action Size Date Who Comment
OSC_srv-2003051701.tgz manage 31.9 K 17 May 2003 - 17:06 JuanChanson OSC servlet package 20030517

You are here: Gulli > OscSrv

to top

Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback