136w ago - A few months back it was first
reported that a Sony ban wave was imminent, and today
DJLO over at PSX-Scene reiterated the fact that it's only a matter of time until Sony begins banning PS3 JailBroken consoles.
To quote: Folks,
Sniffynose pointed me to this. Since we are all
updating now, you ALL need to read this and pay attention
On boot the system contacts the server and uploads the play list etc. this list alone is enought to get anyone that goes online banned as it shows the bootmanger etc. has been running. Here is the list and what they do, I port sniffed this a while ago before I went online with a retail unit >.> because I am not stupid hehe.
All these need to be blocked, web access will still work, updates will still work, but psn and any system messages/ads/communication will be blocked completely. For other areas someone would have to sniff the addresses again to compare. North American Servers are listed.
fus01.ps3.update.playstation.net > Update Server (sys updates)
mercury.dl.playstation.net > What's new ads
nsx.np.dl.playstation.net > playstation store preview
nsx-e.np.dl.playstation.net > ads
(main file exchange connections)
us.np.stun.playstation.net > on boot initiates connection
ena.net.playstation.net > SSLv3 connection after above connection
dus01.ps3.update.playstation.net > secondary update attempt (could force updates)
auth.np.ac.playstation.net > SSLv3 authentication server
(destination servers)
service.playstation.net (has multiple IPs if only the ip address is blocked)
(Error Reporting)
creepo.ww.hl.playstation.net (uploads crash reports etc.)
Almost all connections cannot just be port blocked, the port will continue to increment until it connects, you have to block the entire domains. Also a big point is that ALL computers on your network need to have these blocked not just the PS3's MAC because if you are running a proxy for example to get patches, the computer you proxy to will just allow the connections right out to the open unless all local IPs are blocked from these sites as well."
Wrong gateway doesn't give you a problem in local network. I highly recommend put wrong gateway instead of dns change.
This would be correct in case PS3 / Sony always uses the URLs / web addresses to "call home" rather then directly fixed IPs (which I believe is the case so far). If you want be even more secure, set the Default gateway to some invalid IP as well but then most probably you'll be not able to use it even internally for ftp transfers or media streaming - just try it and you'll see. As an alternative to setting invalid DNS / Gateway simply set your PS3 with fix IP address (which you probably have already anyway) and then block this address from accessing internet completely in your router.
What about because:
1. You might want to update your PS3 on the future and use it online again
2. You might want to sell your PS3 in the future and somene else would like to update / use it online
3. There might be way to go online or JB the higher FWs later on
4. You might (or plan to) have multiply PS3 and as your JB-en PS3 is linked to your PSN ID(s) having it banned can ban your PSN ID(s) on all other PS3s as well losing hence all the paid for PSN content
5. Sony could even start activelly looking up the users using JB and try to sue them etc. (although I doubt that but you never know).
So - if you don't care of any of above - then go ahead and have your fun.
Problem solved.
Where do you get these pkgs? I'm interested. I'm really looking for roster updates for nhl11. To be honest, I'm not really sure why it's essential to update any games, but some guidance to updating through pkgs (and where to get them) is appreciated.
Could you explain how to do this with a linksys router. I can't figure out how to block anything other than numeric ports.
I can't fit the addresses into the "Website Blocking by URL address" windows. Those windows seem to restrict the number of characters you can type in there. So in some instances I try to copy and paste (or even type) in the words "xxxxx.playstation.net" but I can only fit "xxxxx.playstatio" I'm sure this would prove ineffective. Any suggestions?