Re: [Jnetstream-users] WebSite

[Mark B. <voy...@ya...>]

> -----Original Message-----
> From: David Deyo [mailto:Dav...@am...]
> Sent: Friday, September 26, 2008 12:19 PM
> To: voy...@ya...; Jon Schewe
> Cc: jne...@li...
> Subject: RE: [Jnetstream-users] WebSite
>
> General question:
> Whenever I try to ping jnetstream.com I get ip 69.64.79.98
> (dns lookup).
> But the ping never replies.
>
> Is jnetstream.com still up?
> Is so, is this the right ip?

The server is completely offline right now. It will be backup later on
tonight I hope. Yes the IP looks right.

>
> API question:
> I'm trying to use 3.0a to capture, filter and decode.
> Specifically, I'm trying get an rtp packet into an object
> that will allow me access the  sequence numbers in rtp
> packets over a time period.  Is this possible?  If so, where
> could I find how to do that, using the 3.0a codebase as a
> starting point?

RTP is not iplemented yet. You'd have to write the protocol yourself and add
it to the Scanner implementation. Eventually this will done automatically
directly from NPL definitions (cross compiled into java).

The idea with the scanner is that it contains some of the most common
protocols hard coded to allow as fast as possible scanning of raw packet
buffers, but then rely on cross-compiled binding objects that are generated
from NPL definitions which are then tried for each protocols (just like they
are in 2.4 right now) until a match is made. Another words, try hard coded
bindings first then NPL compiled bindings as a last resort. This way any
number of standard protocols can be hardcoded into a scanner, but still
retain flexibility to add new protocols on the fly.

>
> Basically I just need to know what would have to take place
> under that API revision, whether it's implemented yet or not.
> (capture, format, decode)

Once the new protocol is written you can add it to the protocol registry and
it will be available for the decoding. The process of writing protocols
manually is a little involved and is not intended for non-advanced users who
absolutely need something. There are 4 files involved with each protocol:

Rtp - pure interface
RtpHeader - a class implimenting the Rtp interface + extends a
AbstractField class
RtpCodec - a factory class for creating and initializing RtpHeader objects

then there is also the binding which is not currently implemented in object
form, but hard coded into the scanner which is implemented by FastScanner
class in one of the modules.

2.4 has Rtp implemented and is also real easy to use in the mean time,
although you won't achieve the speeds near what 3.0 can.

Cheers,
mark....

>
> dwd
>
>
>
> -----Original Message-----
> From: Mark Bednarczyk [mailto:voy...@ya...]
> Sent: Tuesday, September 23, 2008 6:17 PM
> To: 'Jon Schewe'
> Cc: David Deyo; jne...@li...
> Subject: RE: [Jnetstream-users] WebSite
>
> Yes, something is up. But Drupal is not working. I can't get
> in via the shell account to even look at it.
>
> Cheers,
> mark...
>
> > -----Original Message-----
> > From: Jon Schewe [mailto:jps...@mt...]
> > Sent: Tuesday, September 23, 2008 7:01 PM
> > To: voy...@ya...
> > Cc: 'David Deyo'; jne...@li...
> > Subject: Re: [Jnetstream-users] WebSite
> >
> > The site seems up to me, although the content doesn't look
> so good. My
>
> > own sourceforge projects are up also.
> >
> > Mark Bednarczyk wrote:
> > > Hi David.
> > > 	Yes everyone is experiencing problems with
> > jnetstream.sf.net. SF.net
> > > team decided to take all the websites down for a couple of
> > week again.
> > > Therefore I'm moving everything over to a dedicated server
> > > http://jnetstream.com. As soon as I get access back to my
> > old website
> > > I'll copy all the docs and examples.
> > >
> >
> > --
> > Jon Schewe | http://mtu.net/~jpschewe
> > If you see an attachment named signature.asc, this is my digital
> > signature. See http://www.gnupg.org for more information.
> >
> > For I am convinced that neither death nor life, neither angels nor
> > demons, neither the present nor the future, nor any powers, neither
> > height nor depth, nor anything else in all creation, will
> be able to
> > separate us from the love of God that is in Christ Jesus
> our Lord. -
> > Romans 8:38-39
> >
>
>