[Users] feature request

[Klaus Darilion]

Hi!

In many situations it would be useful to verify the destination IP 
address of a message before sending the message. E.g. I want to make 
sure that accounting and authentication was applied before sending a 
request to a gateway.

loose_route and DNS resolving make it impossible to handle all scenarios 
in the config script. Thinking about the problem I got the following idea:
   The tm module should, after all DNS lookups, verify the dest. IP 
against a blacklist (e.g. the GW table from lcr module). If the dest. IP 
is on the blacklist, the message will only be sent if a certain flag is 
set. This flag will be set in the config script after all checks (acc, 
auth...) has been applied.

What do you think about this idea? Any other ideas for this problem?

regards,
klaus