{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Justice XC:
9/21/2014 9:08:17 PM
6
Edit: Moved to post tracking Home users and Centipede issues.
English
-
Hi, just tagging this post to let others know that the user I'm replying to doesn't know what they're talking about and should be ignored. Thanks.
-
Please go troll the other thread tracking home users ill respond to why and how this was proven out. Go back to networking your home "router" before you put on your big boy pants with the enterprise guys. Thanks :D
-
I'm not trolling, your OP is just flat wrong in many regards. Additonally, I have experience with both Cisco and Juniper enterprise equipment (routers, switches, APs). This comes both through my university program's classes (4th year), and my co-op time spent working as a sysadmin. I'll be back in a few hours to continue this discussion.
-
Edited by Justice XC: 9/21/2014 9:44:37 PMI'd love to have this discussion. There is a reason as to why Bungie is in talks and trying to gather ISP info. My co worker reached out to Comcast on the line and they flat out told him they were doing it (Grain of Salt as Tier 2 tech means I know how to refresh a modem). I have the debugs on my ASA to prove this out. Even my L2L back to work dropped to MM_State deleted / idle. The actual connection out was reset. Ive worked primarily Cisco but from Core enterprise to Cisco CTC Fiber backbone. I have also worked with Bradford, Palo, and Forescout for NAC. I understand this might not be the instance for all users was just trying to dumb it down so power users could check and see if they were getting disconnected and if so could pursue other alternatives to resolve the issue.
-
Edited by Emacs: 9/22/2014 12:19:19 AMI can really only speak for North America (Canada and the USA). My main issue with your original OP was that you're suggesting that ISPs are filtering or blocking P2P traffic (denying the service by modem reset, etc), which (depending on your interpretation of recent events involving the SCOTUS and the FCC on net neutrality) they're not allowed to do. There should be no reason for ISPs to be tampering with their user's data (outside of any QoS they're choosing to do), nor should using an ephemeral port for P2P data transfer nessesitate Bungie having to contact ISPs. I know some ISPs do some level of DPI, but it shouldn't be causing these issues. Item 1: Again though, this is how things [b]should[/b] be behaving. If the ISPs are misbehaving, that's a different issue (outside of Bungie's control). As for using well known ports; it shouldn't make the least bit of a difference what port the transport layer is using, it shouldn't be a consideration at all (to the ISPs). It's information that isn't relevant to the network layer and delivering the IP packet. I should be able to send data to any address on any port number without interference from my ISP. Again, see Item 1. If you're interested in the specifics for Destiny, I've examined it.
-
Edited by Justice XC: 9/22/2014 2:03:01 AMSo I agree for the most part. Now reading my OP I do see how that was misconstrued. It was a (2) part message that got jumbled into one on accident. I should of worded it more along the lines to have the end user check and see if when they received this error if they saw a connection reset of lost outbound connectivity from any other device. If so that would explain that this error was caused by the connection drop, not the other way around. I have seen this misconception in previous posts. When stating reset it was more along the lines that upstream the connection was reset due to packet loss or communication failure for whichever reason. Was it a modem disconnect, well sure I'm not going to rule that out. On the same topic there have been partner disconnect from Bungie as well. Now depending on how in depth you would like to go in regards to QoS / Packet Shaping I will say every single Carrier is shaping to some degree or another. Over-saturation is prevalent and your speed is not guaranteed no matter how much you believe your carrier. Common port was more of a request on the NAC side of the house for the colleges just to make it easier on the admins / vendors so that definition updates wouldn't have to be pushed out, but again with specific port numbers this is not required as Bungie has provided them.
