(adsbygoogle = window.adsbygoogle || []).push({}); Since I can't reply yet to other related posts I'll start a new.
(Mods, you can move this if you want)

Things I've done so far:

Used own dns to fake following domain names:
cdn.update.playstation.net
np.stun.playstation.net
ps3.update.playstation.net
dl.playstation.net
vo.llnwd.net

They all point to my own server (apache)

Also configured squid to redirect You must login or register to view this content. to my server, since for some reason the ps3 does bypass my dns the 2nd time it tries.

I use following ps3-updatelist.txt:

    

 cat /var/www/update/ps3/list/eu/ps3-updatelist.txt

# EU

Dest=85;CompatibleSystemSoftwareVersion=3.5500-;

Dest=85;ImageVersion=0000b99c;SystemSoftwareVersion=3.5500;CDN=https://xxx.xxx.xxx.xxx/PS3UPDAT.PUP;CDN_Timeout=30;

This is the access.log from squid when I boot the ps3:

    

1297264108.259      0 xxx.xxx.xxx.xxx TCP_DENIED/302 442 GET https://feu01.ps3.update.playstation.net/update/ps3/list/eu/ps3-updatelist.txt - NONE/- text/html

1297264108.268      0 xxx.xxx.xxx.xxx TCP_MEM_HIT/200 630 GET https://xxx.xxx.xxx.xxx/update/ps3/list/eu/ps3-updatelist.txt - NONE/- text/plain

1297264111.669    738 xxx.xxx.xxx.xxx TCP_MISS/200 3455 CONNECT auth.np.ac.playstation.net:443 - DIRECT/199.108.4.73 

This is what happens if you logon manually after boot:

    

1297264214.516      3 xxx.xxx.xxx.xxx TCP_MISS/404 683 GET https://xmb.dl.playstation.net/xmb/ps3/AD..1WSfwnwPwNFaQCpP5bBETOc_/music2/xil.xml - DIRECT/xxx.xxx.xxx.xxx text/html

1297264215.084      2 xxx.xxx.xxx.xxx TCP_MISS/404 683 GET https://xmb.dl.playstation.net/xmb/ps3/AD..1WSfwnwPwNFaQCpP5bBETOc_/video2/xil.xml - DIRECT/10.252.19.1 text/html

1297264215.894      2 xxx.xxx.xxx.xxx TCP_MISS/404 679 GET https://xmb.dl.playstation.net/xmb/ps3/AD..1WSfwnwPwNFaQCpP5bBETOc_/tv/xil.xml - DIRECT/xxx.xxx.xxx.xxx text/html

1297264216.773    731 xxx.xxx.xxx.xxx TCP_MISS/200 3455 CONNECT auth.np.ac.playstation.net:443 - DIRECT/199.108.4.73 -

1297264218.164    740 xxx.xxx.xxx.xxx TCP_MISS/200 3455 CONNECT auth.np.ac.playstation.net:443 - DIRECT/199.108.4.73 -

1297264218.581     23 1xxx.xxx.xxx.xxx TCP_MISS/504 0 CONNECT nsx.sec.np.dl.playstation.net:443 - DIRECT/xxx.xxx.xxx.xxx -

1297264223.784      0 xxx.xxx.xxx.xxx TCP_DENIED/302 442 GET https://feu01.ps3.update.playstation.net/update/ps3/list/eu/ps3-updatelist.txt - NONE/- text/html

1297264223.794      0 xxx.xxx.xxx.xxx TCP_MEM_HIT/200 631 GET https://xxx.xxx.xxx.xxx/update/ps3/list/eu/ps3-updatelist.txt - NONE/- text/plain

PS3 comes up with update message.
When saying yes, it come's back saying my ps3 is up to date.

I also blocked all ports except 80 and 443 for the ps3 before boot, but then nothing works.

Blocking all but 80 and 443 after boot results in a longer attempt to logon, but then fails with error 80710092

So something is communicating over a non standard port with sony.

I'll try to change my network so I sniff the traffic, as now the ps3 is connected over wireless and wireshark runs on the wired part.

BTW:
anyone an idea what this link does:
You must login or register to view this content.

BTW2: As I read in many other posts here, if you don't know what yo are talking about, don't bother reply-ing (Like someone posted an ip address is only in this format xxx.xxx.xx.x /facepalm)

could be the new Cloud System

hey but seems you pretty into this

Read PM

Can't be anything new, since it's on a pre 3.56 system, that doesn't know anything yet new.
Unless it's a redirect.
In that case it's a redirect comming from auth.np.ac.playstation.net since all else is redirected to my server.
And then why would it not redirect all the time?

What annoys me the most is the fact it needs other ports besides 80 and 443 to get online.

Quick update...

It must be something in the ps3-updatelist.txt

As far as I could check, that was the only thing it accessed, even before it accessed the auth. url.
After that the ps3 is not even connecting to the auth url, but prompts directly for an update.

What is stopping you from being complete?

We are working on something similar and I feel we are having a similar hiccup.

How do you mean by complete?
I've posted most things in my first post.

I think thats for PS3 News and maybe PSN Store thumbnails.

Also there must be some different check, not only updatelist. I tried almost everything, even tried to downgrade my PS3 with a fake pup (went to 60% and gave error "File format not supported").

What I could see with port sniffing is, that there are also other tcp connections, not only getting the http file. After checking the updatelist, the ps3 sends a message to a Sony Server. Sony Server responds and PS3 responds again. Then error pops up.

Oh and btw: To port sniff use your computer as proxy and set as source rule the PS3's local ip.

On what port is that tcp connection?

try looking at certifactes ..... ca5

---------- Post added at 08:16 AM ---------- Previous post was at 07:18 AM ----------

or CA34 ..

I think I found out how they check the current fw.
Just thinking out-loud and still needs to be confirmed but I can't do it at current location.

Based on this:


The fw version is in the browser header of the PS3, so all they need to do at the authentication server is read that header.

If this is really the case, we need to change the browser header in the cfw 3.55

Modifying the header via proxy can't be done I think, due to ssl