{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
8/10/2016 4:46:32 AM
1
I was thinking of a similar cause.
I came up with a possible fix here:
https://www.bungie.net/en/Forum/Post/210636234/0/0/1
It likely won't work if it's as you say with the public IP address, but perhaps you could try it and see if it works. I don't have a second console to try it for myself, and I'd trust a network savvy person more than a random to try it out.
Thanks
English
-
A simpler way to do this would be to disable upnp, port forward one console manually and then let the other console get stuck with cone Nat. Ive thought about it as the cone nat device *should* get told to use the port forwarded device (as is the case when in a 3 player fire team with an external party) I was kinda hoping that bungie would fix this themselves. I play games to not do more work. Another reason i game on a console and not a pc.
-
Yes, you could try it that way. I went ahead and connected my ps4 to second router wired to my primary router as a test. I expected it to change my NAT to type 3, but it didn't. I stayed Open NAT, type 2, prolly cause I have UPnP enabled on both? In any case, I'm leaving it that way. One's a netduma, which is great for matchmaking, but is horrible for normal networking. Now I can do both. Hopefully, Bungie patches this issue soon. Even if my idea worked as a temporary workaround, some people might not be able to figure out how to do it. A major game should be plug and play networking. Like you said, we play games to relax, not make more work for ourselves.
