{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by BNGHelp7:
2/14/2020 8:32:41 PM
1
Hi there,
Thanks for your report. We are tracking an issue with players who have Technicolor and Thompson routers and the CABBAGE error. There seems to be an issue with the security configuration on these routers and connecting to Destiny properly.
Some players have found a fix for this issue by following the steps
[url=https://www.bungie.net/en/Forums/Post/231008613]in this thread[/url] or [url=https://www.bungie.net/en/Forums/Post/241743364]in this thread[/url].
English
-
Edited by YeshuaTalmid: 3/5/2020 8:30:36 AMGreeting, So.... I had a further play with the CONE/PORT unbinding command. I ended up having to settle for unbinding the entire port range, as unbinding the individual ports mentioned, in one of the help responses you added links to, weren't recognised. I've now been playing for up to a couple of hours at a time for a few weeks now ,finally completing the Red War campaign (with NO CABBAGE errors) and even trying my hand on GAMBIT PRIME, testing the changes to see if I get any further messages. The only messages I do get are stating that my NAT type is set to strict and may result in diminished gameplay (or something like that). Just wanted to say thanks to all who sent help (I know the Technicolor router is poor... but, it's easier to plod on with that one for now...) and that this thread can now be shown as ANSWERED, if there is a way to do this... I'm not sure if I can do it myself....? Sanity... restored.
