{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
8/14/2016 11:14:47 PM
4
FIX MARIONBERRY
I have a netduma R1 router with a Tplink switch connected I have factory defaulted all equipment and contacted my ISP my NAT is open and I cannot connect to Destiny on a wired connection. Fix this now.
-
Help! I have the same error :c
-
Same here with Netduma. Marionberry every time. Powercycling may fix it.
-
6 RepliesEdited by KannibalKlown: 8/15/2016 12:00:30 AMYou won't like to hear this ONE cause of marionberry. ONE. Is the router having a small NAT table. This sometimes happens with the free routers, and occurs with some p2p apps (not just destiny) I'm not saying this is your cause, as there are multiple triggers, but it could be the cause Some marionberry victims, and I stress SOME, got it to go away by getting a solid router. [u][b]Edit[/b][/u]. I didn't notice you saying you have netduma. I would hope that has a normal NAT table size. Netduma has awesome software but mediocre hardware, and I don't see any info about NAT tables posted anywhere on its merger hardware. Is there another piece of hardware in front of it?
-
2 RepliesAlso i have all ports used by Destiny already being forwarded
