Juha Heinanen schrieb:
Klaus Darilion writes:
I know there were some changes in ser/sr too, but do not know exactly what was changed.
btw: another strange thing is that sr even tries to open a new TCP connection. There should be already a TCP connection opened to Twinkle - do you call fix_nated_contact() on the 200 OK from Twinkle?
klaus,
something broke badly after andrei's commit where he added support for setting $du in branch route and other stuff. i started to get all kinds of transport related errors yesterday and also remove_hf in route block function stopped working (at least when branch_route block is executed later).
when i went back to a earlier version of sr_3.0, all these weird errors disappeared. so i don't think that using wrong ip address is something inherent in sr, but just a side effect of some bug or bugs introduced by the commit.
To make it clear, going back to old version also solves the TCP problem?
regards klaus