James,

May I suggest that you configure your mail client to properly quote mail
messages in your replies?  Otherwise, it makes it very difficult to
reply to your messages.

On Wed, 2006-07-19 at 15:16 -0700, James Edele wrote:
> - No it was not streams.  We put our hooks in the ill_g_head interface list.

That is an implementation artifact of the ip module, so it's no surprise
that your module isn't stable.  But, you already know that by now. :-|

> - How do I learn about the packet filtering hooks?  Is there an API?

The code-review was just announced on this very list yesterday
morning. :-)  Take a look at the mail archives for some history.  The
design documentation is also available in the files section of the
Networking community page:

http://www.opensolaris.org/os/community/networking/files/

This is Darren Reed's project, so I'd suggest you contact him is you
need additional information on this.

> - Is it in SOlaris 10?

No, not today.  It is a project that is currently under development in
OpenSolaris.

> - Regarding the Streams, it was viewed as inefficient and has worked this
> way since the
> - late 90's.

I can't comment on whether a STREAMS method would have been less
efficient in this case, as I'm not the one who did the performance
analysis.  In some cases, a STREAMS interface is not less efficient (for
some definition of "efficient"), but one never knows until some analysis
is done.

> - we're looking for the way that will avoid panics.  If Streams is the way
> to
> - go, then does bge and other drivers implement a full Streams interface
> - in Solaris 10 (and future).  I heard a rumor that Sun was moving away
> - from Streams for some implementations.  Is that true?

Not quite; STREAMS/DLPI will always be supported as a means to interact
with link-layer network interfaces.  It's a standard, and Solaris can't
cease support for that without causing great harm to customers.  Parts
of the internal implementation TCP/IP subsystems are using means other
than STREAMS to communicate in Solaris 10, but that doesn't affect how
3rd party software interacts with STREAMS DLPI devices.

> - Maybe this (opensolaris) is the wrong place to look, though a Sun
> escalation
> - engineer refered us to opensolaris when we presented them with our
> dilemma.

Given that your software was previously using private and unsupported
interfaces, I doubt that an escalation would go anywhere.  That doesn't
surprise me.  Luckily, this mailing list contains the right set of
people to help you solve your problem.

> - Having an API that is reliable and will work with Solaris 10 is what we
> need.
> - Where can I find the official API?
> - If Streams is the only answer, then we will look a little further before
> biting
> - that bullet.

For Solaris 10 and prior, I believe a STREAMS module is your best option
(today).  In addition to that, if you're willing to work with
OpenSolaris features that are being developed now, I'd contact Darren
Reed to see if packet filter hooks can meet your requirements.  Darren
is on this mailing list and has led discussions on the hooks framework
on the list.  Take a look at the mail archives for some background.

-Seb


_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to