This is a long-standing issue, from what I understand. In fact, I've seen videos that are at least four years old. I was under the impression that this was solved.
For what it's worth, there -is- a crude workaround located at http://forums.steamgames.com/forums/showpost.php?s=2c2d2fab3091aae78902a9e6f644bf17&p=23742696&postcount=14
I'd be willing to check to see if it's solved, but like I said... this has been around since at least 2009. As soon as I can find someone on who I feel shares a mutual trust, I'll check it out.
As this isn't a Linux issue this GitHub isn't really the right place for it, the standard Steam bug reporting channels should be used.
@gdrewb-valve True, but its an old issue and is already known to valve afaik. Just checking to see if anything can be done.
@MrSchism Thanks for the link, but how does an average user enable that on the steam client?
Also @MrSchism when my friends tried it, some guys got a valve IP but some people get the destination IP. So I'm thinking its per router? If the destination refuses a direct connection its patched via valve?
If the destination refuses a direct connection its patched via valve?
That may be the case. I'm not certain of the exact technique, however Teamviewer uses a similar trick as a way of handling some issues including NAT.
Nothing extracted yet.
Since it has come to light that initiating a voice call with another person on steam compromises your IP even without the person accepting said call, maybe it should be considered as a bug for the linux port as well.
Maybe an option to disable steam calls?