Associating IP ranges (or other objects) to tickets

RT Developers
1

I’d like to associate IP address ranges with tickets. What’s the best
way to do this? Shall a create a separate table (ticket_id, first_ip,
last_ip), or is it better to use the existing links table?

In addition, we maintain a database of contact persons per IP address
range. We would like to track changes of contact persons using RT.
Has anybody tried to use tickets for a similar purpose (the contact
persons would be the requestors, and the address ranges would be
provided by the extension above)? Or are there better ideas to track
changes of something which could be considered an external object with
respect to RT?

Florian Weimer Weimer@CERT.Uni-Stuttgart.DE
University of Stuttgart http://CERT.Uni-Stuttgart.DE/people/fw/
RUS-CERT +49-711-685-5973/fax +49-711-685-5898

2

I’d like to associate IP address ranges with tickets. What’s the best
way to do this? Shall a create a separate table (ticket_id, first_ip,
last_ip), or is it better to use the existing links table?

I’m biased somewhat, and would suggest using (funnily enough) the RIPE
database software (ftp://ftp.ripe.net/ripe/dbase/software) to record who
is a contact for which IP range. It seems to work somewhat for us :wink:

Regards,

                         Bruce Campbell                            RIPE
               Systems/Network Engineer                             NCC
             www.ripe.net - PGP562C8B1B                      Operations