JavaScript is required to use Bungie.net

Service Alert
Destiny 2 will be temporarily offline tomorrow for scheduled maintenance. Please stay tuned to @BungieHelp for updates.

Forums

Edited by RavenousLD3341: 8/26/2016 5:06:59 PM
4
Excellent advice. Just a few caveats I would like to toss in. Gaming consoles have access to your credit/debit card! If you choose to DMZ your consoles, please secure the hell out of your console. No more automatically logging in, require passwords for everything, so not leave it powered on when not in use, do not allow it to be turned on from another source. (Or wake on LAN for IT peoples) For example.. PS4 users. If you're console is in your DMZ I would not allow updates and downloads to wake your console up. Turn on require password for checkout Turn on require password to log into PSN all the time, and do it manually. and..... NO MORE REST MODE! I thoroughly recommend only using your DMZ to troubleshoot connectivity problems where you need to rule out firewall rules/issues. As for static IPs. I do it I use the Manual DHCP method. Where i put the mac addresses of my important devices into DHCP and assign the addresses to them in there. So everytime i connect my console to my network my router will assign it the same address each time. This requires no changes on the console. If you can't figure this feature out, you can just go to the network settings of your console and just type everything in there manually. I would pick an available IP address near the end of your network. For example: (People that don't like changing default settings on routers. This will likely work for 95% of you) IP Address = 192.168.1.250 Subnet Mask = 255.255.255.0 Default gateway = 192.168.1.1 Enjoy!
English

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