it turned out that the problems ricardo reported on gw selection in lcr module were due to the fact that he has the same gw (same in terms of ip address) in more than one gw group and in each group the gw has different trip/tag attributes.
load_gws() function tries the same gateway only once, but it is not currently well defined from which group gw's attributes are taken when request is sent to the gateway. currently the attributes are taken from the gw group, which happens to be the first in in-memory gw table.
one could think that this is a feature, i.e., if the same gw is in many gw groups, it must have the same attributes in every group. the other alternative is that this is a bug, i.e., same gw's attributes can differ from group to group and the ones that are used must be the ones of the chosen group.
i have a fix written for sr_3.0 lcr module, but i'm hesitating to introduce the fix also to version 1.5, because the fix has not been tested well yet.
any opinions on what should be done?
-- juha