JavaScript is required to use Bungie.net

Forums

8/23/2018 1:58:45 PM
4
The network vlan IPs should only be valid in so far as the host network is concerned; as soon as it leaves that home net (Bungie systems), it will encounter additional layer 1 / 2 items, and the IP address will be managed by them instead. Additionally, the outgoing IP will be determined by the lan / wan interface and management of the host switch / router / modem. Even in a tunnel connection, which I don't believe we are seeing in the capacity you originally suggested (as that would imply a VPN connection), you are connecting to a domain most of the time, not an IP. The reason for this is IP addresses don't have to be unique by their nature. Ask anyone ever accused of pirating, the primary defense is always that an IP address is not a concrete indicator of any one computer). Are you 100% certain that what you are seeing isn't either an IP conflict between your modem and routting equipment (which is a common issue, typified by failed connections, constant resets on lease renew attempts, etc.), or that you aren't seeing the ISPs hardware as the incoming connection IP? I'm not saying you're wrong, please don't misunderstand me, but I am applying the knowledge I use in my work every day to further analyze the issue.
English

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Edited by seFraggle: 8/23/2018 3:18:41 PM
    I aggree with your points and I´m familiar with IP stuff, it´s my daily work. I guess that Bungie is using GRE to tunnel traffic, no classic VPN connection is established between PS4 and Bungie. GRE btw is also used for DOS prevention. Let my explain the situation a bit further: Your homenetwork is setup with 2 vlans, 192.168.0.x/24 and 192.168.2.x/24 (Standard ISP hardware/router) Bungie tunnels 192.168.0.x host-addresses to your PS4. As soon as these networks are directly connected to your router (which is in our example), your router won´t ever use the WAN interface as gateway for returning the connection to the bungie host, the traffic is routed locally. I´m 100% sure that there´s no IP conflict, I don´t own the host-addresses. The host-addresses were directly attached to the PS4 flow. My public IP is directly sitting on my edge device, no ISP equipment in between. No layer 8 problem here ;)

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • All makes sense, and my level of understanding your understanding (for lack of a better term) is more complete: you'd be surprised how many people in a code factory don't understand any level of networking, so I always have to make assumptions round that. In my case, I have a much different internal vlan setup, -but- I am one of the people that understand it well enough to know why it's a good / not good thing to do; most people are in the plug and play category. Depending on your ISP and equipment, this is a very real issue. I wish I could give everyone the advice I would give myself, which is manually manage your vlan (and all the rest of your network infrastructure), but it's not realistic. Perhaps a solution until Bungie gets their networking protocols in order (release dat e is currently slated for the 5th of Never) would be for people like yourself and me to work on a barebones level guide to setting up networks at home for the average user: I know there is no one and done guide, due to the different end-use devices and ISP equipment, but it might make some difference. On the other hand, if you're like me, I'll sit down to outline something like that, and then immediately have 15 IP phones deposited on my desk for provisioning to a new office location, before the VPN and tunneling are even worked out...and Mitel 53xx series going back to a Mitel 5000 ICP at that...it's gross.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • coding vs networking - these are 2 different scopes. I have basic knowledge of some languages, but wouldn´t be able to write large code. :) I guess we have a non-standard deployment at home. :D Plug & Play is for users without - or minimal knowledge, so nearly everyone can setup a small network at home. Manually desgining and configuring the whole network would assume some basic knowledge about networking, which the majority of all the internet users doesn´t have - therefore plug&play. Writing a guide would be a good start, but as you stated, this is not an easy task, as different needs, devices, and so on. Maybe one time ... :) Back to the problem, it can affect anyone here, as those private IP ranges bungie is using, are pretty common on default configurations - not only in ISP default configs. I hope we will get some official response here...

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • In depth networking I get, but it's the people that don't get the joke, 'There's no place like 127.0.0.1' at my work that shock me. I don't expect everyone to be a network god, by any means, but some of them can't tell you the difference between an IPv4 and an IPv6. I get no less than 3 tickets a week asking me to help someone find there machine IP or MAC address...'nuff said. I'm one of the rare ones that does both programming and network admin...I guess I simply assume everyone in the software work should have -some- basic understanding of how a theoretical deliver model network functions, if only layer 1 and layer 7. I am constantly surprised at how many of our programmers lack basic computer knowledge.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon