Skipping the 3.21, 3.42, 3.56 PS3 update

[Barney_Stinson]

hey, thanks for the workaround mates.
is it possible that you post something like a 'guide' in order to do this by ourselves?
i mean if it does not require some great knowledge or skills , would you consider it?
Suit Up!

[job4chris]

Doing a guide could be tricky due to the number of possible fixes. I did my fix on a dedicated Linux server I have running on my home network using BIND 9 DNS server and Apache 2 web server both of which can be a little complicated in themselves to configure. There are Windows alternatives to both of those products of course as well as other options for providing DNS and web services.

[Barney_Stinson]

hmm, i see.
do the alternatives include the Logan5 program?

[job4chris]

hmm, i see.
do the alternatives include the Logan5 program?

For a Windows user that would probably be a simpler solution.

[Bhaal]

Thanks a lot Aaron

Your DNS will not going to be down if too many people use it ? Sony can't do anything ?

job4chris, can you share your bind9's config ? I know how to config apache2 but i have no idea for Bind9.

Thanks

[job4chris]

Thanks a lot Aaron

Your DNS will not going to be down if too many people use it ? Sony can't do anything ?

job4chris, can you share your bind9's config ? I know how to config apache2 but i have no idea for Bind9.

Thanks

This bind configuration will likely require a bit of explanation:

Code: Select all

$ORIGIN .
$TTL 3600       ; 1 hour
ps3.update.playstation.net      IN SOA  ns1.domain.local. ns2.domain.local. (
                                11         ; serial
                                900        ; refresh (15 minutes)
                                600        ; retry (10 minutes)
                                86400      ; expire (1 day)
                                3600       ; minimum (1 hour)
                                )
                        NS      ns1.domain.local.
                        NS      ns2.domain.local.
$ORIGIN ps3.update.playstation.net
*                       A       192.168.153.5
~


I run a mixed environment with a Windows DNS server as primary and BIND as a secondary. The IN SOA clause specifies which DNS server are authoritative for the domain ps3.update.playstation.net. The numeric entries below that are safe defaults. The NS lines specify the names of the name servers. Everything below the $ORIGIN section is where you specify hosts in the ps3.update.playstation.net domain. For simplicity I used a wildcard host "*" to specify that all hosts point to my web server which in this example is running at 192.168.153.5.

The following is the entry in the named.conf file which contains the listing for the zone file above:

Code: Select all

zone "ps3.update.playstation.net" {
        type slave;
        masters { 192.168.153.2; };
        file "/etc/bind/slaves/ps3.update.playstation.net.db";
        allow-transfer { 192.168.153.2; 192.168.153.5; };
        allow-notify { 192.168.153.2;192.168.153.5; };
        check-names ignore;
};


Again, this is a slave server to my Windows primary as specified in the "type" entry. masters simply specifies which DNS server is the primary for this zone. The "file" line points to the file the above zone data is stored in. The "allow-notify" and "allow-transfer" entries simply specify that DNS data can be shared with other DNS servers on the network.

[Bhaal]

thanks a lot job4chris, i will test this weekend

[job4chris]

thanks a lot job4chris, i will test this weekend

I probably should also mention if BIND is going to be the master server for your ps3 update domain. change the "type" from slave to master and you can remove the "masters" line in your named.conf file.

[bsanehi]

Hey Aaron can you make something like this for the PSP??? so that we could also be able to go on psn, without updating???? lots of people have 5.00/5.50 firmwares and they don't want to update to the latest one which is 6.20 ??? would that work>?? thanks in advance

[job4chris]

Hey Aaron can you make something like this for the PSP??? so that we could also be able to go on psn, without updating???? lots of people have 5.00/5.50 firmwares and they don't want to update to the latest one which is 6.20 ??? would that work>?? thanks in advance

I'm not sure if it would work or not but here's your starting point for creating the same setup for PSP. I might even try setting this up this weekend and see how it goes.

http://forums.qj.net/psp-homebrew-hacks ... -hack.html

[Aaron]

job4chris where did you get the updatelist.txt from

Well, to save you some time, here's the one I'm hosting: http://pastie.org/900791
Skips the update for all regions and all versions.

Thanks a lot Aaron

Your DNS will not going to be down if too many people use it ? Sony can't do anything ?
Thanks

Nah, I can't imagine a slightly-used nameserver using that much traffic, and it's only serving a small file once per connection. I suppose if a LOT of people use it there might be issues, but I doubt that many will ever use it at one time. As for Sony... I'm sure they could make it required that you have 3.21 to connect to PSN, but maybe not until the next update. I'm not sure what their infrastructure is like right now; this hole has existed for a long time and people have known about it, so dunno why it would change now.

Hey Aaron can you make something like this for the PSP??? so that we could also be able to go on psn, without updating???? lots of people have 5.00/5.50 firmwares and they don't want to update to the latest one which is 6.20 ??? would that work>?? thanks in advance

I don't have a PSP, so I wouldn't know. You can try my DNS server though, it might work. I added a false psp-updatelist.txt to it.

[job4chris]

job4chris where did you get the updatelist.txt from

Well, to save you some time, here's the one I'm hosting: http://pastie.org/900791
Skips the update for all regions and all versions.

Thanks a lot Aaron

Your DNS will not going to be down if too many people use it ? Sony can't do anything ?
Thanks

Nah, I can't imagine a slightly-used nameserver using that much traffic, and it's only serving a small file once per connection. I suppose if a LOT of people use it there might be issues, but I doubt that many will ever use it at one time. As for Sony... I'm sure they could make it required that you have 3.21 to connect to PSN, but maybe not until the next update. I'm not sure what their infrastructure is like right now; this hole has existed for a long time and people have known about it, so dunno why it would change now.

Hey Aaron can you make something like this for the PSP??? so that we could also be able to go on psn, without updating???? lots of people have 5.00/5.50 firmwares and they don't want to update to the latest one which is 6.20 ??? would that work>?? thanks in advance

I don't have a PSP, so I wouldn't know. You can try my DNS server though, it might work. I added a false psp-updatelist.txt to it.

I'm rather surprised that custom updatelist.txt you made actually didn't cause errors but looking at it and thinking about the PSP situation is leading me to believe that I may be over-thinking the PSP's updatelist.txt file format.

And I don't think setting the PSP to use your DNS is going to work as it's configured now. The PSP uses slightly different update url's.

[bsanehi]

here is the update list for the psp this is for the latest
http://fj01.psp.update.playstation.org/ ... telist.txt = 6.20 new firmware

This one is for 2006 update
http://web.archive.org/web/200711160550 ... telist.txt = old firmware

[Aaron]

I'm rather surprised that custom updatelist.txt you made actually didn't cause errors but looking at it and thinking about the PSP situation is leading me to believe that I may be over-thinking the PSP's updatelist.txt file format.

All it does is find the dest line that matches its region, and checks if the installed ImageVersion is lower than the one in the text or not.

And I don't think setting the PSP to use your DNS is going to work as it's configured now. The PSP uses slightly different update url's.

I'm aware, I adjusted for that fact

[bsanehi]

well i'll test it out and tell you if it works on my psp

[Prahotep]

Hi Aaron,

Thanks fo your solution. At least it will give me time to decide what to do with my Linux partition and make a decent backup.

In other hand, I noticed - using your DNS - the links to the PSN Store are broken - the level beyound the store forefront. It's not possible download a demo, for instance. The error is the typical 404 - HTTP not found. Do you have any idea what is causing it? Maybe a different server request?

[job4chris]

here is the update list for the psp this is for the latest
http://fj01.psp.update.playstation.org/ ... telist.txt = 6.20 new firmware

This one is for 2006 update
http://web.archive.org/web/200711160550 ... telist.txt = old firmware

Do you know which friendly version # the 2006 updatelist.txt is for?

[bsanehi]

here is the update list for the psp this is for the latest
http://fj01.psp.update.playstation.org/ ... telist.txt = 6.20 new firmware

This one is for 2006 update
http://web.archive.org/web/200711160550 ... telist.txt = old firmware

Do you know which friendly version # the 2006 updatelist.txt is for?

No but i got it from this site

http://web.archive.org/web/*/http://fj0 ... telist.txt

[Aaron]

Hi Aaron,

Thanks fo your solution. At least it will give me time to decide what to do with my Linux partition and make a decent backup.

In other hand, I noticed - using your DNS - the links to the PSN Store are broken - the level beyound the store forefront. It's not possible download a demo, for instance. The error is the typical 404 - HTTP not found. Do you have any idea what is causing it? Maybe a different server request?

Sorry about that, side-effect of adding the PSP stuff. Thanks for pointing it out, it should be fixed now.

[Prahotep]

Oh yeah, it is working properly now again! Thank you!