Quoting Javier Szyszlican <[EMAIL PROTECTED]>: > Alex, > > >>I don"t understand, you want to be able to do a Manual add of TCP ports > >>without doing a port scan? is that it ? > >> > > > > > > Yes that's it. I read a bit more though and will try to see what custom > > discovery scripts can do. > > One could expect a new interface could be added in the > "Administration"->"Hosts > > and Interfaces"->"Interfaces"->(select by host) and then the "Add" link on > the > > top of the interfaces list (like it works for hosts). But that just shows > "No > > Records Found.", showing in place of the interfaces. > > > > I understand, my idea will be a new discovery type, called "Only Manual Add" > that will show you all the interface types available for manual add, but it > wont > actually call the discovery script. > > Will that be ok?
Yes that is what I'm looking for. > > >>Also you could put the "quit" string in the interface types fields. > > > > > > I don't understand what 'interface fields' you are referring to. And what > "quit" > > would do wherever it should be put. > > > > I was thinking that you wanted to add a string somewhere to gracefully close > the > connection. Ie, we connect to port 110, read for a while, then send 'quit' so > the daemon won't complain. Isn't that what you needed? > > Interface Type fields, are per-interface type fields. Yes, depending on the Interface type one would have to do different things. So far I've encountered 3 different behaviours: HTTP: simply close the connection SSH: the sshd sends an identification/version string, it expects an identification string as reply. So here we simply 'bounce' the string the sshd send. Though I guess we could set a hard-copy string here too, depending on the server we connect to. SMTP: the server we use wants a message; sending 'QUIT' here simply works. This all can be different (I assume) for each specific service you connect to. So it has to be set per interface, not per interface type (since it would be a shame to implement it per type and then encounter a new service of that type requiring other behaviour). So simply adding a column for each TCP(/UDP) interface with a message to send before disconnecting should indeed work. I haven't figured out where and how to do that. Though I have the idea it goes all the way to the database. I could put the message to be send in the "Port Description" for now. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ jffnms-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jffnms-users
