[Devel] loose_route() incorrectly strict routing locally forwarded messages

[Tavis P]

Replies

I'll make sure to spend some time today to get you some better information

tavis


Bogdan-Andrei Iancu wrote:
> Hi Tavis,
>
> what messages are you referring to? requests or replies? some more
> info? maybe I will be able to help you with..
>
> regards,
> bogdan
>
> Tavis P wrote:
>
>> I've encountered some problems with the suggested workarounds, when the
>> alias' are set to include the server port there seems to be some
>> problems with the tm module "missing" (not realizing they are meant for
>> itself) some messages and forwarding them instead.
>>
>> I havn't had the time to debug this observation properly, i'm hoping to
>> be able too in the coming weeks.  I think right now forwarding messages
>> to another port on the same server is very broken.  I'll a little
>> disclaimer in the wiki section on alias
>>
>>
>> Bogdan-Andrei Iancu wrote:
>>  
>>
>>> Hi Tavi,
>>>
>>> I gave more thinking on the issues, and as you said, is more a problem
>>> of logic than programming. I would say the best solution is to let the
>>> code as it is, as it offer more flexibility, and to document better
>>> the "alias" behaviour to avoid future misunderstandings.
>>>
>>> What changed my mind? here is an example:  you have the proxy
>>> listening on udp and tcp on 2 ports; and it serves the domain
>>> "mysip.net"...if we change the code, we will have to strictly define
>>> the aliases (all proto and port combination -> 4 entries) to be sure
>>> your domain also covers the 2 protos and ports...and it's not natural.
>>>
>>> So, I will add more info in the wiki page for "aliases"....is it
>>> reasonable?
>>>
>>>   
>
>