Assistance with Networking PS2 Tool

[Parris]

I must have been lucky thus far, as it is only now that I have obtained a PS2 Tool that once it boots up displays a completely blank TOOL networking screen.

The usual 192.168.0.10 doesn't work via ProDG and as such I am now at a loss as to how to access the Administration Tool normally accessed via http://192.168.0.10/english/ in order to reset the IP settings etc.

This is definately something I would like to add to the manual, plus right now any advice would be welcome as I am unable to test any further until this unit is networked up.

How do you obtain the Networking Information without the PS2 Tool displaying it?

As it has been a while, did anyone establish how to get the screen to display the information?

[SilverBull]

I must have been lucky thus far, as it is only now that I have obtained a PS2 Tool that once it boots up displays a completely blank TOOL networking screen.

Frankentool?

The usual 192.168.0.10 doesn't work via ProDG and as such I am now at a loss as to how to access the Administration Tool normally accessed via http://192.168.0.10/english/ in order to reset the IP settings etc.

This is definately something I would like to add to the manual, plus right now any advice would be welcome as I am unable to test any further until this unit is networked up.

The network configuration is stored in /etc/sysconfig/network-scripts/ifcfg-eth0. I prefer to use to the following file, but it requires a DHCP server on the LAN:

DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
NETWORK=
NETMASK=
BROADCAST=
IPADDR=

You can configure a static IP like this (untested; based on http://www.linkbyte.com/support/linux_ifcfg_eth0.html, found via Google, but slightly changed):

DEVICE=eth0
IPADDR=192.168.0.10
BOOTPROTO=none
NETMASK=255.255.255.0
NETWORK=192.168.0.0
BROADCAST=255.255.255.255
GATEWAY=192.168.0.1
ONBOOT=yes

After changing the script, run "ifdown eth0" followed by "ifup eth0" (or reboot) to apply changes; if everything works fine, the TOOL will automatically refresh the network information screen.

How do you obtain the Networking Information without the PS2 Tool displaying it?

As root, type ifconfig. Should list two interfaces, lo (loopback/127.0.0.1) and eth0, and their configuration. You are only interested in eth0, as lo is a local (pseudo) interface.

As it has been a while, did anyone establish how to get the screen to display the information?

The screen is displayed by invoking /usr/local/sony/bin/devtool-opening, which automatically fires on boot or when the network interface is activated (e.g., when you reconnect the LAN cable).

The devtool-opening script gathers some information, writes them to the temporary file /tmp/text, then runs /usr/local/sony/bin/gstitle.elf on the PS2; that file is responsible for displaying the TOOL screen, and if it can find a file named text in the current directory, it displays its contents white-on-black before the background. Well, if it can't find the file, it simply displays the background and quits with an error message:

[Parris]

You guessed it : Frankentool ! :evil:

Right, I tried the first option: /etc/sysconfig/network-scripts/ifcfg-eth0

And got the reply

'Permission Denied'

ifconfig under ROOT returned lo / eth0 data

Thanks for that - a case of a little information being dangerous - I was trying ipconfig.... wonder where the hell I got that from ;-)

Thanks!

Will now try again with the newly acquired details!

;-)

[SilverBull]

Right, I tried the first option: /etc/sysconfig/network-scripts/ifcfg-eth0

And got the reply

'Permission Denied'

Not sure whether I understood you correctly, but did you try to execute the file? ifcfg-eth0 is a configuration (definition) file, not an executable or (invokable) script; therefore, you want to open it in a text editor and put the interface's configuration information there. vi is nice for that (and preinstalled on the TOOL :icon_bigg), but if you have never used it before, I strongly recommend testing it on another system or VM first :rolleyes:. Could be cumbersome if you have never used an editor having multiple editing modes (or something like a command mode) before...

Quick start for vi (make sure you know where the colon (:) is located on your keyboard, just in case you are using a non-default keyboard layout):

• vi /etc/sysconfig/network-scripts/ifcfg-eth0
• You start in command mode. To enter text, you will need to go to edit mode. Place the cursor at the right position, then enter either i (for insert) or a (for append). Type whatever you like. To go back to command mode, hit ESC.
• (in command mode) To delete the character at the current cursor position, hit x. To delete the entire line, type dd.
• (in command mode) To save changes, use :w (yes, that command starts with a colon!). To save and quit, use :wq. Typing :q exits without saving, but won't work if you have made any changes to the file. To quit anyway (without saving), use :q!.

Thanks for that - a case of a little information being dangerous - I was trying ipconfig.... wonder where the hell I got that from ;-)

That's odd, I regularly make the same mistake. To much windows on my end...

[Parris]

Right, a glass of wine later I am sitting with access over LAN. Nice, thanks! Have skipped changing the IP for now as I am not keen on doing anything with Frankentool just yet, just in case.

However, can't access adminstrators tool as the user name and password are not the usual suspects (admin / administrator / root) etc.

Dang!

I have changed the ROOT password for access to Bash, but as the only option I know of for changing the admininstrator tool password is having had it in the first place I am stuck.

This is going well!

[unclejun]

Did you try with a capital A, as in Administrator?

[Parris]

Did you try with a capital A, as in Administrator?

Yeah, tried upper and lower case in all instances.

If anyone wants to establish which company their unit came from, this is a pretty simple way of finding out.

Type in the inet addr into the dev PC as http://192.168.xxx.x/english and have a look at Show Status > Network > Domain Server... often the developers servers will be names to suit ;-) That's how I established where Frankentool originally came from. They went bust sadly...

From the instruction manual I can see that if an Admin user / password is an issue that you have to call the local Sony office... no instructions!

[hl718]

Thanks for that - a case of a little information being dangerous - I was trying ipconfig.... wonder where the hell I got that from ;-)

Windows. ;)

As for the password bits, is the etc/passwd file shadowed? If not, you shouldn't have an issue getting admin. I don't believe Sony bothered modifying standard Linux bits.

-hl718

[Parris]

Windows. ;)

As for the password bits, is the etc/passwd file shadowed? If not, you shouldn't have an issue getting admin. I don't believe Sony bothered modifying standard Linux bits.

-hl718

Let's assume for a minute that I am a total Linux noob (assume away, because I really am) then how would I go about that then <sniff?>

One thing I just noticed in the manual under troubleshooting:

"If the DVD-rom drive of the unit does not function, the battery for the timer function in the unit may be dead..."

All those nights fighting with DVDrom drives! Bah!

[SilverBull]

Yeah, tried upper and lower case in all instances.

If anyone wants to establish which company their unit came from, this is a pretty simple way of finding out.

Type in the inet addr into the dev PC as http://192.168.xxx.x/english and have a look at Show Status > Network > Domain Server... often the developers servers will be names to suit ;-) That's how I established where Frankentool originally came from. They went bust sadly...

From the instruction manual I can see that if an Admin user / password is an issue that you have to call the local Sony office... no instructions!

That's the reason why I always use DHCP. No way to trace that back to my domain, although the name is only used internally... :katamari: Another caveat, especially when sharing dumps of TOOL HDDs: some TOOLs seem to encode their serial number in the host name. Therefore, its no use when you remove the serial number from all your photos, but hand out HDD dumps :evil: :banghead:.

Regarding the admin password: in all cases of TOOLs I have seen so far, it was Administrator for both the username and password. However, Sony uses a standard Apache server for the TOOL's website, so you can change its password database the hard way... Have a look for an application named htpasswd (try something like find / | grep htpasswd to find it), then use that to change the password database of the Apache; a man htpasswd (or, if that doesn't work, a google search) can tell you more. The database is supposed to be somewhere within the apache directory (or a configuration subdirectory), but I can't remember the details of neither its location, file name nor the invokation syntax of htpasswd. Just use a variant of the above find command, I'm sure its out there. :nod:

[Parris]

That's the reason why I always use DHCP. No way to trace that back to my domain, although the name is only used internally... :katamari: Another caveat, especially when sharing dumps of TOOL HDDs: some TOOLs seem to encode their serial number in the host name. Therefore, its no use when you remove the serial number from all your photos, but hand out HDD dumps :evil: :banghead:.

Regarding the admin password: in all cases of TOOLs I have seen so far, it was Administrator for both the username and password. However, Sony uses a standard Apache server for the TOOL's website, so you can change its password database the hard way... Have a look for an application named htpasswd (try something like find / | grep htpasswd to find it), then use that to change the password database of the Apache; a man htpasswd (or, if that doesn't work, a google search) can tell you more. The database is supposed to be somewhere within the apache directory (or a configuration subdirectory), but I can't remember the details of neither its location, file name nor the invokation syntax of htpasswd. Just use a variant of the above find command, I'm sure its out there. :nod:

Thorough and great explination. I can see this user guide being stuffed with tonnes of useful info. If an idiot like me can understand it, then all is well!

:110:

Whilst fiddling around I decided to try and run a PS2 retail title and a PS2 Master Disc just to see whether the DVDrom drive was working.

In all instances I got 'This is not a Playstation2 title : Illegal disc medium" (or words to this effect).

Dang this Frankentool...

[SilverBull]

Let's assume for a minute that I am a total Linux noob (assume away, because I really am) then how would I go about that then <sniff?>

I learned the hard way: get an old computer, an old Debian installation and plenty of time, and try to install that thing, using text-mode setup and advanced setup mode (dselect). Then, for every problem you encounter, invoke google. :110: Granted, that was quite some years ago; at times where you couldn't compile a new kernel (who wants to run a single-processor kernel on a two-way P2, anyway?) and enable loadable kernel modules without making your system unbootable... :banghead:

Seriously: there should be plenty of tutorials and introductory books. If you want a nice-looking distribution, try something like Ubuntu. They repackage most if not all of the low-level (esp. text-mode) setup stuff in fairly nice GUIs, so you might never have to use the command line.

One thing I just noticed in the manual under troubleshooting:

"If the DVD-rom drive of the unit does not function, the battery for the timer function in the unit may be dead..."

All those nights fighting with DVDrom drives! Bah!

Nice info, thanks a lot! Come to think of this, I think I should have been able to deduct that myself. The mechacon (mechanics controller, responsible for data transfer to the DVD besides other useful stuff like region lockout and hardware dongling) is somewhat picky at times.

Whilst fiddling around I decided to try and run a PS2 retail title and a PS2 Master Disc just to see whether the DVDrom drive was working.

In all instances I got 'This is not a Playstation2 title : Illegal disc medium" (or words to this effect).

Dang this Frankentool...

I dare to ask: is it a bad laser or a dead battery? I wouldn't wonder about the retail game, though (as the mechacon could be a japanese one, which doesn't like non-japanese retails), but it should play all master disks. Which writing speed and disk media did you use?

Too bad we don't have the pinout of the service mode port, that would make diagnosing such problems much easier. :banghead::banghead::banghead:

[Parris]

Holy cow, 4 year old son strikes again!

I having been fighting with the unit and it has been doing stuff I didn't expect it too, and I decided to check all the dips just to be 100% sure. My 4 year old had flicked the two front switches to down and closed up the little hatch...

Okay, Tool now fully operational! Still reports 'Illegal disc' type for retail PAL, but it's now playing the Master Discs no problem, plus playing Japanese retail titles without a glitch. I have no idea when he got in here and did this, but he clearly did as he looked really sheepish when I asked him about it. Kids huh?!

The laser is in very good working order all things considered. One fully operational Frankentool reporting for duty. :dance:

I really do need to learn about Linux though, you are right. I even have a full PS2 Linux kit in the attic I never bothered to use once I installed the software.

Ubuntu ahoy!

Thanks folks! I'll have to look into this change of Admin / Passwd as I really want to change the IP address and self test.

[Stone]

Regarding the admin password: in all cases of TOOLs I have seen so far, it was Administrator for both the username and password.

I've found all the networked Sony kit that I've tested obeys this :nod:

Stone

[Parris]

Mine must be the only PS2 Tool that doesn't... typical!

I wonder if the previous owner couldn't spell Administrator ? ;-)

[SilverBull]

Tested on DTL-T10000 (running Red Hat Linux 5.2 (Apollo), Kernel 2.0.36)

First of all, verify the location of the Apache password database, as you don't want to modify the wrong file. To do this:

1. less /usr/local/apache/conf/httpd.conf
2. Type "/AuthUserFile" (without quotes, but including the slash), followed by ENTER, to search for AuthUserFile.
3. The AuthUserFile entry should be present in a block like this (some entries from the real file have been omitted here):

<Directory "/usr/local/sony/www/setup-bin">
AuthType Basic
AuthUserFile /var/sony/devtool-pass
require user Administrator
</Directory>

1. Remember the file name immediately following AuthUserFile. In the example, its /var/sony/devtool-pass
2. Quit less by typing the single letter q (for quit).

To change the password:

1. Enter /usr/local/apache/bin/htpasswd /var/sony/devtool-pass Administrator; if your TOOL uses a different apache password database file, be sure to specify its name instead of "/var/sony/devtool-pass"!
2. When prompted, enter the new password. Recommended is "Administrator" (without quotes). As is the case with the regular unix passwd, you are prompted twice and expected to type in the same password each time :rolleyes:.
3. You should now be able to access the TOOL's website by specifying "Administrator" for the user name and the password you just entered.