User User name Password  
   
Sunday 24.11.2024 / 13:45
Search AfterDawn Forums:        In English   Suomeksi   På svenska
afterdawn.com > forums > archived forums > nintendo gamecube - general discussion > pso plus port issue
Show topics
 
Forums
Forums
pso plus port issue
  Jump to:
 
Posted Message
Page:12Next >
twisterco
Newbie
_
23. September 2004 @ 15:23 _ Link to this message    Send private message to this user   
Ive been trying to mess with pso 1 and 2 plus loading dol files. Ive been able to get the memory card save to work.. but psul and psoload always crash when they try to upload the dol. I read a thread where some people claimed the problem was that pso plus connects to the server on port 9103 instead of 9100. The only way at first i could get the gamecube to connect to the loader at all was to write a small app in java that accepted the gc connection on 9103 and just relayed all the packet data to the loader server running locally. I noticed some other people said they were using port forwarding programs. I found a simple easy fix if anyone wants to mess around with it. Just open psul.exe or psoload.exe in HexWorkshop and replace all hex values 8C23 with 8F23... The loader will now accept the gamecube connection on port 9103.. no need to rewrite the app ;-)

Anyways the loaders still crash, so im guessing they probably still will need rewriting to properly load the dol files with pso plus.. I havent gotten any further.. anyone else have any info?
Advertisement
_
__
Fr0d83
Newbie
_
3. October 2004 @ 19:44 _ Link to this message    Send private message to this user   
I tried the modifications you mentioned above however I get an error. This is what I get:

Call to recv(sClient, szInBuffer, sizeof(szInBuffer), 0); failed with: 10054

I found that this is actually a winsock error code. This is what the error means:

WSAECONNRESET (10054) Connection reset by peer.

An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host used a "hard close".

Thought people would be interested in this information. I'm working on fixing this, but it's hard without the source code.

This message has been edited since posting. Last time this message was edited on 3. October 2004 @ 19:45

StoneRain
Junior Member
_
4. October 2004 @ 20:44 _ Link to this message    Send private message to this user   
There is also rumor going around that you cant use a server that is on the same class C IP. So it could be that even though you are fixing one problem the port, you are still using a server with an IP that is invalid. If you run windows, you can configure a second alternate IP. I dont think it has to be the same IP class. Try that if your bored.
Here is a thought. Why doesnt someone packet sniff all the traffic for when the GC actually connects to the real PSO server. Understand what it is saying back and forth, making note of who is saying what and its credentials. Then, hook-up a cross-over cable to the GC and PC. Finally, make a program that will spoof the whole god damn internet. I realize that this is more than a modification of the PSOLoader. But, in many ways this might actually be more easy. IP spoofing and MAC address spoofing are well known.
Fr0d83
Newbie
_
5. October 2004 @ 05:33 _ Link to this message    Send private message to this user   
Unfortunately I don't have a real account to play PSO, nor am I interested in getting one. But that does sound like an interesting idea.
zephyrius
Newbie
_
17. October 2004 @ 16:45 _ Link to this message    Send private message to this user   
Hey, I re-created all of the steps mentioned as well and get the same error message.

I do have a real PSO account, though. If anyone is interested in working on this project with me (or solo), let me know and I can send you a delimited .csv file with all the login traffic.

In the meantime, I'm going to keep trying to hack away at PSOload.exe.
Fr0d83
Newbie
_
18. October 2004 @ 05:25 _ Link to this message    Send private message to this user   
I would absolutely LOVE to have that login traffic. Can you e-mail it to me at [noemailsallowed@afterdawn.com] ? Thanks a lot

This message has been edited since posting. Last time this message was edited on 23. October 2004 @ 23:25

twisterco
Newbie
_
18. October 2004 @ 14:59 _ Link to this message    Send private message to this user   
yeah the CSV data might b helpful.. Sorry for any confusion
most of you seemed to think this fix would make the loaders
work. It doesnt. It just enables PSO to actually connect to PSUL
and PSOLoad, however the gamecube still disconnects. At
least with PSO Plus actually connecting to the PSOLoad server,
we might be able to work some more on a fix.

Source code costis please!

This message has been edited since posting. Last time this message was edited on 18. October 2004 @ 15:00

Fr0d83
Newbie
_
19. October 2004 @ 12:38 _ Link to this message    Send private message to this user   
Can we storm his house with torches and pitchforks and demand the source?
bigwill29
Newbie
_
20. October 2004 @ 17:44 _ Link to this message    Send private message to this user   
I will try to use a linux with ip forwarding between my pc and the gc, forwarding all connection from 192.168.1.32/24 on port 9103 to a class A ip address on port 9100, so it could solve the problem without rewriting or fixing code. I will try this and get back to you guys. If somebody have an idea to complete or replace mine share it I will try to do it.

Thank you everybody for sharing information!
bigwill29
Newbie
_
20. October 2004 @ 18:48 _ Link to this message    Send private message to this user   
By now, when I first try it this night with the normal setup, all I could get from cubesoft was A DNS Query from 192.168.1.32 was served. This was for the Save user data to memcard. But with the setup I told in my last post it's seem to work. My dos window waiting for connection said "connecting" then "saving user data" then close by herself. I've start this evening so I'm really a newbie. If somebody can point me out which port I need to forward for streaming dol files it would help me alot.

Thank you everybody for sharing information!
npd
Newbie
_
23. October 2004 @ 15:02 _ Link to this message    Send private message to this user   
I tried the modifications suggested at the top of this page (I have PSO 1&2 Plus) and it saved the information to the memory card. However, whenever I try to make a backup off of the gamecube, it waits for a connection, and then connects. (Before the modification, it didn't connect at all) Then the computer window closes, and on the gamecube I'm left with "The line was disconnected. GAME OVER. Press start."
Sorry if I'm repeating questions asked by others, but is there any possible way to make a backup of a game with PSO1&2 plus?

Hi.

This message has been edited since posting. Last time this message was edited on 23. October 2004 @ 15:05

StoneRain
Junior Member
_
23. October 2004 @ 19:17 _ Link to this message    Send private message to this user   
wow, im impressed that someone made progress on this. good work guys. I would really like to know if you get it to work. I dont know much about linux so I cant test this stuff out myself. you might have to check to see if the receiving port on the GC is the same as the old one. If they changed the server port I can only guess they changed the GC port. this will be harder to figure out because you will have to wait to till the exact moment that the port opens and then ping them all before it closes.

or this info should be in a log of an actual log on. much more simple.

just a guess...

This message has been edited since posting. Last time this message was edited on 23. October 2004 @ 19:18

Mr69ways
Suspended due to non-functional email address
_
2. November 2004 @ 15:56 _ Link to this message    Send private message to this user   
You guys still working on this?
twisterco
Newbie
_
6. November 2004 @ 05:31 _ Link to this message    Send private message to this user   
I was messing around with PSO some more, heres what I found out so far, maybe someone can help fill me in.

When the GC first connects to the server, the server sends some information about the server, its viewable in plain text and says something like Dreamcast Port Map... at the end of the packet is an 8 byte key. All further communication between the GC and server are encrypted using this key.

PSOLoad and PSUL have a fixed key that is sent to the GC everytime, so the encrypted data is always the same. They each use a different key though. My guess is that the authors of the program observed the communication between the GC and the actual sega server and just wrote a program to mirror the responses from the sega server. No decrypting is involved. If you hex edit the key in psoload to another 8 byte key, it gives an unexpected client response error or something, so all of the communication is hard coded into the app.

I would love to figure out the encryption so that it is possible to see the actual communcation that is occuring. The people that made the unofficial PSO server software for dreamcast and PC have figured out the encryption http://schtserv.funurl.com/ but they dont release source code because they want people to continue to use sega's servers for gamecube and xbox.

The problem may not actually be with the loaders, as some thought PSO just limited access to certain ip ranges and stuff. Networking isnt my favorite field but I dont know how this kind of protection would be implemented, especially with features such as the proxy server. If someone was able to get a proxy server going, then the GC could actually contact a real DNS server, send out the request for the sega server to the proxy server, then the proxy server could just tunnel the connection to PSUl or PSOload. Any thoughts?
Mr69ways
Suspended due to non-functional email address
_
6. November 2004 @ 06:58 _ Link to this message    Send private message to this user   
Maybe you can shed some light on me.I am getting the "DNS Server Error->Can't bind socket" when tyring to load the testdemo4.dol via PSO ver2.0

Here is my setup.
PSO+ settings:
IP:192.168.0.32 (does it have to be 192.168.1.32)
Subnet:255.255.255.0
Gateway:192.168.0.1
DNS Server:151.196.111.74

Windows XP Computer:
IP:151.196.111.74
Subnet:255.255.255.0
Gateway:192.168.0.1
DNS Server:127.0.0.1

Using Hanewin DNS Server to forward gc01.st-pso.games.sega.net to 151.196.111.74
StoneRain
Junior Member
_
7. November 2004 @ 09:53 _ Link to this message    Send private message to this user   
you are right I think, a proxy would clear up many of the networking problems. I'm not totally sure though. try it and see if you can get all the same successful responces.

So it is encrypted, hmmm. I believe there are programs out there that if you have 20 compinations of "A" & "B" that are encrypted. It can decrypt them, because every A = B regardless of whether you have 2A = 2B or 3A = 3B... I think there used to be some serial # generators that worked of this stuff. So basically what I am saying is if you have 20 logs of the 8 byte key and 20 logs of maybe the first line of the responce you should be able to figure out the algorithem. Honestly, you probably need more like 64-128 combinations (more combinations, more accurate), instead of just 20. Am I right here 8 byte = 64 bit encryption? I think the way most encryption works these days is that (in this case) 1)the server sends an encypted message 2)the GC decrypts it 3)it reads the message 4) in re-encypts it 5) it sends it back to the server which sees if it got the same decrypted message back.

All of this really doesnt explain why PSOload doesnt connect if it is not just a simple port issue or IP filtering, unless the encryption is different. You just need to figure out what new responce to mirror. I think maybe this gives evidence that the Plus version is on a different port is because it connects to a different server software that has slightly different encryption.

I'm still curious to know if the GC is listening for the server (the real one, not psoload) on a different port?

Really wish I had the knowledge to answer more of these questions myself.

mr69ways. PSOLoad v2.0 has a DNS server built in, if you are running an extra DNS server or you didnt reboot your computer after installing it, I have gotten those messages. try disabling PSOLoad's DNS server. It has something to do with all of this...
Mr69ways
Suspended due to non-functional email address
_
7. November 2004 @ 12:13 _ Link to this message    Send private message to this user   
StoneRain, I will try what you said. Anyway to use a "network sniffer" to determine what port PSO+ is using. I don't have a account to go online with PSO+ (would be nice to have a log file of what going on during the log in process).
Morfiuso
Newbie
_
16. November 2004 @ 04:56 _ Link to this message    Send private message to this user   
Is there any news about this issue?
I will sniff the ethernet stuff and look at the packets this week, when i get the time!
But any new info would be great

The great Morfiuso
Mr69ways
Suspended due to non-functional email address
_
16. November 2004 @ 04:58 _ Link to this message    Send private message to this user   
I really have not had time myself to sniff the network.
doood81
Newbie
_
20. November 2004 @ 19:28 _ Link to this message    Send private message to this user   
I've been able to capture all the packets during the DNS query and load process. All traffic aims for port 9103 but I'm seeing two packets with [CHECKSUM INCORRECT] that are replies from psul to the gc. It seems there is some header checksumming going on here or something?

I'm using pso I&II plus on a US gc rev 2.

C:\>psul.exe testdemo4.dol
PSUL 1.1 Copyright (C) 2003, Titanik of Crazy Nation

Starting server on 192.168.0.235...
Waiting for connection...
Served DNS query from 192.168.0.234...
Connected (US)...
Sending file...Error > Communication error 0b...

Has anyone made any progress for pso plus users?

This message has been edited since posting. Last time this message was edited on 20. November 2004 @ 20:34

StoneRain
Junior Member
_
21. November 2004 @ 00:05 _ Link to this message    Send private message to this user   
i dont exactly understand this sum check error.

I think what is more likely going on is what I was talking about before or in a different thread, there is a new encription. could even be that the reply is a different size than PSO version 1.
if you could edit the port PSOLoad uses, which i think someone told us how to do. Then edit the values for "handshake" or login, and there might be 2 corrisponding values... it should work. You should be able to know the values from the legitmate login capture.

I'm glad someone is still working on this.

Just a thought, but i think the best way to test this would be to "reverse engineer the reverse engineering". make a little program that can handshake PSOload and PSUL. If you can make a program like that, you should know what values you need. And, I think you should be able to find those values in the original PSOLoad with an editor and change them. It would also be a good exercise in how the hell the program works.

I realize this is much more simple in text, but I think it makes sense.
doood81
Newbie
_
21. November 2004 @ 09:16 _ Link to this message    Send private message to this user   
I have the packet capture from ethereal if you would like to look at it.
Mr69ways
Suspended due to non-functional email address
_
21. November 2004 @ 09:39 _ Link to this message    Send private message to this user   
yes plz. private message me or if u can copy and paste here
doood81
Newbie
_
21. November 2004 @ 10:05 _ Link to this message    Send private message to this user   
The info is pretty terse so I'll paste the section with the suspect packets... I hope this isn't too long.

I'm using US gc rev 3 with a crossover and pso 1&2 plus.
I'm also using psul.exe v1.1 with the hex modification.
Saving to memory card works fine.

No. Time Source Destination Protocol Info
1 0.000000 64.95.121.95 Broadcast ARP Who has 64.95.121.96? Tell 64.95.121.95

Frame 1 (60 bytes on wire, 60 bytes captured)
Arrival Time: Nov 20, 2004 21:14:17.910920000
Time delta from previous packet: 0.000000000 seconds
Time since reference or first frame: 0.000000000 seconds
Frame Number: 1
Packet Length: 60 bytes
Capture Length: 60 bytes
Ethernet II, Src: 00:09:bf:01:6b:23, Dst: ff:ff:ff:ff:ff:ff
Destination: ff:ff:ff:ff:ff:ff (Broadcast)
Source: 00:09:bf:01:6b:23 (64.95.121.95)
Type: ARP (0x0806)
Trailer: C12C59C650141000253D0000722FD3D6...
Address Resolution Protocol (request)
Hardware type: Ethernet (0x0001)
Protocol type: IP (0x0800)
Hardware size: 6
Protocol size: 4
Opcode: request (0x0001)
Sender MAC address: 00:09:bf:01:6b:23 (64.95.121.95)
Sender IP address: 64.95.121.95 (64.95.121.95)
Target MAC address: 00:00:00:00:00:00 (00:00:00_00:00:00)
Target IP address: 64.95.121.96 (64.95.121.96)

No. Time Source Destination Protocol Info
2 0.000022 64.95.121.96 64.95.121.95 ARP 64.95.121.96 is at 00:0e:0c:50:36:fa

Frame 2 (42 bytes on wire, 42 bytes captured)
Arrival Time: Nov 20, 2004 21:14:17.910942000
Time delta from previous packet: 0.000022000 seconds
Time since reference or first frame: 0.000022000 seconds
Frame Number: 2
Packet Length: 42 bytes
Capture Length: 42 bytes
Ethernet II, Src: 00:0e:0c:50:36:fa, Dst: 00:09:bf:01:6b:23
Destination: 00:09:bf:01:6b:23 (64.95.121.95)
Source: 00:0e:0c:50:36:fa (64.95.121.96)
Type: ARP (0x0806)
Address Resolution Protocol (reply)
Hardware type: Ethernet (0x0001)
Protocol type: IP (0x0800)
Hardware size: 6
Protocol size: 4
Opcode: reply (0x0002)
Sender MAC address: 00:0e:0c:50:36:fa (64.95.121.96)
Sender IP address: 64.95.121.96 (64.95.121.96)
Target MAC address: 00:09:bf:01:6b:23 (64.95.121.95)
Target IP address: 64.95.121.95 (64.95.121.95)

No. Time Source Destination Protocol Info
3 0.000466 64.95.121.95 64.95.121.96 DNS Standard query A game04.st-pso.games.sega.net

Frame 3 (88 bytes on wire, 88 bytes captured)
Arrival Time: Nov 20, 2004 21:14:17.911386000
Time delta from previous packet: 0.000444000 seconds
Time since reference or first frame: 0.000466000 seconds
Frame Number: 3
Packet Length: 88 bytes
Capture Length: 88 bytes
Ethernet II, Src: 00:09:bf:01:6b:23, Dst: 00:0e:0c:50:36:fa
Destination: 00:0e:0c:50:36:fa (64.95.121.96)
Source: 00:09:bf:01:6b:23 (64.95.121.95)
Type: IP (0x0800)
Internet Protocol, Src Addr: 64.95.121.95 (64.95.121.95), Dst Addr: 64.95.121.96 (64.95.121.96)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 74
Identification: 0x0002 (2)
Flags: 0x00
0... = Reserved bit: Not set
.0.. = Don't fragment: Not set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 120
Protocol: UDP (0x11)
Header checksum: 0xcf23 (correct)
Source: 64.95.121.95 (64.95.121.95)
Destination: 64.95.121.96 (64.95.121.96)
User Datagram Protocol, Src Port: 1362 (1362), Dst Port: domain (53)
Source port: 1362 (1362)
Destination port: domain (53)
Length: 54
Checksum: 0xf68f (correct)
Domain Name System (query)
Transaction ID: 0x0000
Flags: 0x0100 (Standard query)
0... .... .... .... = Response: Message is a query
.000 0... .... .... = Opcode: Standard query (0)
.... ..0. .... .... = Truncated: Message is not truncated
.... ...1 .... .... = Recursion desired: Do query recursively
.... .... .0.. .... = Z: reserved (0)
.... .... ...0 .... = Non-authenticated data OK: Non-authenticated data is unacceptable
Questions: 1
Answer RRs: 0
Authority RRs: 0
Additional RRs: 0
Queries
game04.st-pso.games.sega.net: type A, class inet
Name: game04.st-pso.games.sega.net
Type: Host address
Class: inet

No. Time Source Destination Protocol Info
4 0.000590 64.95.121.96 64.95.121.95 DNS Standard query response A 64.95.121.96

Frame 4 (128 bytes on wire, 128 bytes captured)
Arrival Time: Nov 20, 2004 21:14:17.911510000
Time delta from previous packet: 0.000124000 seconds
Time since reference or first frame: 0.000590000 seconds
Frame Number: 4
Packet Length: 128 bytes
Capture Length: 128 bytes
Ethernet II, Src: 00:0e:0c:50:36:fa, Dst: 00:09:bf:01:6b:23
Destination: 00:09:bf:01:6b:23 (64.95.121.95)
Source: 00:0e:0c:50:36:fa (64.95.121.96)
Type: IP (0x0800)
Internet Protocol, Src Addr: 64.95.121.96 (64.95.121.96), Dst Addr: 64.95.121.95 (64.95.121.95)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 114
Identification: 0x19b8 (6584)
Flags: 0x00
0... = Reserved bit: Not set
.0.. = Don't fragment: Not set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 128
Protocol: UDP (0x11)
Header checksum: 0xad45 (correct)
Source: 64.95.121.96 (64.95.121.96)
Destination: 64.95.121.95 (64.95.121.95)
User Datagram Protocol, Src Port: domain (53), Dst Port: 1362 (1362)
Source port: domain (53)
Destination port: 1362 (1362)
Length: 94
Checksum: 0x3b0a (correct)
Domain Name System (response)
Transaction ID: 0x0000
Flags: 0x8580 (Standard query response, No error)
1... .... .... .... = Response: Message is a response
.000 0... .... .... = Opcode: Standard query (0)
.... .1.. .... .... = Authoritative: Server is an authority for domain
.... ..0. .... .... = Truncated: Message is not truncated
.... ...1 .... .... = Recursion desired: Do query recursively
.... .... 1... .... = Recursion available: Server can do recursive queries
.... .... .0.. .... = Z: reserved (0)
.... .... ..0. .... = Answer authenticated: Answer/authority portion was not authenticated by the server
.... .... .... 0000 = Reply code: No error (0)
Questions: 1
Answer RRs: 1
Authority RRs: 1
Additional RRs: 0
Queries
game04.st-pso.games.sega.net: type A, class inet
Name: game04.st-pso.games.sega.net
Type: Host address
Class: inet
Answers
game04.st-pso.games.sega.net: type A, class inet, addr 64.95.121.96
Name: game04.st-pso.games.sega.net
Type: Host address
Class: inet
Time to live: 2 days
Data length: 4
Addr: 64.95.121.96
Authoritative nameservers
game04.st-pso.games.sega.net: type NS, class inet, ns <Unknown extended label>
Name: game04.st-pso.games.sega.net
Type: Authoritative name server
Class: inet
Time to live: 2 days
Data length: 12
Name server: <Unknown extended label>

No. Time Source Destination Protocol Info
5 0.063714 64.95.121.95 64.95.121.96 TCP 1325 > 9103 [SYN] Seq=0 Ack=0 Win=4096 Len=0 MSS=1460

Frame 5 (62 bytes on wire, 62 bytes captured)
Arrival Time: Nov 20, 2004 21:14:17.974634000
Time delta from previous packet: 0.063124000 seconds
Time since reference or first frame: 0.063714000 seconds
Frame Number: 5
Packet Length: 62 bytes
Capture Length: 62 bytes
Ethernet II, Src: 00:09:bf:01:6b:23, Dst: 00:0e:0c:50:36:fa
Destination: 00:0e:0c:50:36:fa (64.95.121.96)
Source: 00:09:bf:01:6b:23 (64.95.121.95)
Type: IP (0x0800)
Internet Protocol, Src Addr: 64.95.121.95 (64.95.121.95), Dst Addr: 64.95.121.96 (64.95.121.96)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 48
Identification: 0x0003 (3)
Flags: 0x00
0... = Reserved bit: Not set
.0.. = Don't fragment: Not set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 120
Protocol: TCP (0x06)
Header checksum: 0xcf47 (correct)
Source: 64.95.121.95 (64.95.121.95)
Destination: 64.95.121.96 (64.95.121.96)
Transmission Control Protocol, Src Port: 1325 (1325), Dst Port: 9103 (9103), Seq: 0, Ack: 0, Len: 0
Source port: 1325 (1325)
Destination port: 9103 (9103)
Sequence number: 0 (relative sequence number)
Header length: 28 bytes
Flags: 0x0002 (SYN)
0... .... = Congestion Window Reduced (CWR): Not set
.0.. .... = ECN-Echo: Not set
..0. .... = Urgent: Not set
...0 .... = Acknowledgment: Not set
.... 0... = Push: Not set
.... .0.. = Reset: Not set
.... ..1. = Syn: Set
.... ...0 = Fin: Not set
Window size: 4096
Checksum: 0x9a3e (correct)
Options: (8 bytes)
Maximum segment size: 1460 bytes
SACK permitted
NOP
NOP

No. Time Source Destination Protocol Info
6 0.063813 64.95.121.96 64.95.121.95 TCP 9103 > 1325 [SYN, ACK] Seq=0 Ack=1 Win=17520 Len=0 MSS=1460

Frame 6 (62 bytes on wire, 62 bytes captured)
Arrival Time: Nov 20, 2004 21:14:17.974733000
Time delta from previous packet: 0.000099000 seconds
Time since reference or first frame: 0.063813000 seconds
Frame Number: 6
Packet Length: 62 bytes
Capture Length: 62 bytes
Ethernet II, Src: 00:0e:0c:50:36:fa, Dst: 00:09:bf:01:6b:23
Destination: 00:09:bf:01:6b:23 (64.95.121.95)
Source: 00:0e:0c:50:36:fa (64.95.121.96)
Type: IP (0x0800)
Internet Protocol, Src Addr: 64.95.121.96 (64.95.121.96), Dst Addr: 64.95.121.95 (64.95.121.95)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 48
Identification: 0x19b9 (6585)
Flags: 0x04 (Don't Fragment)
0... = Reserved bit: Not set
.1.. = Don't fragment: Set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 128
Protocol: TCP (0x06)
Header checksum: 0x6d91 (correct)
Source: 64.95.121.96 (64.95.121.96)
Destination: 64.95.121.95 (64.95.121.95)
Transmission Control Protocol, Src Port: 9103 (9103), Dst Port: 1325 (1325), Seq: 0, Ack: 1, Len: 0
Source port: 9103 (9103)
Destination port: 1325 (1325)
Sequence number: 0 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 28 bytes
Flags: 0x0012 (SYN, ACK)
0... .... = Congestion Window Reduced (CWR): Not set
.0.. .... = ECN-Echo: Not set
..0. .... = Urgent: Not set
...1 .... = Acknowledgment: Set
.... 0... = Push: Not set
.... .0.. = Reset: Not set
.... ..1. = Syn: Set
.... ...0 = Fin: Not set
Window size: 17520
Checksum: 0x9ce5 (correct)
Options: (8 bytes)
Maximum segment size: 1460 bytes
NOP
NOP
SACK permitted
SEQ/ACK analysis
This is an ACK to the segment in frame: 5
The RTT to ACK the segment was: 0.000099000 seconds

No. Time Source Destination Protocol Info
7 0.064428 64.95.121.95 64.95.121.96 TCP 1325 > 9103 [ACK] Seq=1 Ack=1 Win=4096 Len=0

Frame 7 (60 bytes on wire, 60 bytes captured)
Arrival Time: Nov 20, 2004 21:14:17.975348000
Time delta from previous packet: 0.000615000 seconds
Time since reference or first frame: 0.064428000 seconds
Frame Number: 7
Packet Length: 60 bytes
Capture Length: 60 bytes
Ethernet II, Src: 00:09:bf:01:6b:23, Dst: 00:0e:0c:50:36:fa
Destination: 00:0e:0c:50:36:fa (64.95.121.96)
Source: 00:09:bf:01:6b:23 (64.95.121.95)
Type: IP (0x0800)
Trailer: 020405B40402
Internet Protocol, Src Addr: 64.95.121.95 (64.95.121.95), Dst Addr: 64.95.121.96 (64.95.121.96)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 40
Identification: 0x0004 (4)
Flags: 0x00
0... = Reserved bit: Not set
.0.. = Don't fragment: Not set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 120
Protocol: TCP (0x06)
Header checksum: 0xcf4e (correct)
Source: 64.95.121.95 (64.95.121.95)
Destination: 64.95.121.96 (64.95.121.96)
Transmission Control Protocol, Src Port: 1325 (1325), Dst Port: 9103 (9103), Seq: 1, Ack: 1, Len: 0
Source port: 1325 (1325)
Destination port: 9103 (9103)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
0... .... = Congestion Window Reduced (CWR): Not set
.0.. .... = ECN-Echo: Not set
..0. .... = Urgent: Not set
...1 .... = Acknowledgment: Set
.... 0... = Push: Not set
.... .0.. = Reset: Not set
.... ..0. = Syn: Not set
.... ...0 = Fin: Not set
Window size: 4096
Checksum: 0xfe19 (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 6
The RTT to ACK the segment was: 0.000615000 seconds

No. Time Source Destination Protocol Info
8 0.066426 64.95.121.96 64.95.121.95 TCP 9103 > 1325 [PSH, ACK] Seq=1 Ack=1 Win=17520 [CHECKSUM INCORRECT] Len=76

Frame 8 (130 bytes on wire, 130 bytes captured)
Arrival Time: Nov 20, 2004 21:14:17.977346000
Time delta from previous packet: 0.001998000 seconds
Time since reference or first frame: 0.066426000 seconds
Frame Number: 8
Packet Length: 130 bytes
Capture Length: 130 bytes
Ethernet II, Src: 00:0e:0c:50:36:fa, Dst: 00:09:bf:01:6b:23
Destination: 00:09:bf:01:6b:23 (64.95.121.95)
Source: 00:0e:0c:50:36:fa (64.95.121.96)
Type: IP (0x0800)
Internet Protocol, Src Addr: 64.95.121.96 (64.95.121.96), Dst Addr: 64.95.121.95 (64.95.121.95)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 116
Identification: 0x19ba (6586)
Flags: 0x04 (Don't Fragment)
0... = Reserved bit: Not set
.1.. = Don't fragment: Set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 128
Protocol: TCP (0x06)
Header checksum: 0x6d4c (correct)
Source: 64.95.121.96 (64.95.121.96)
Destination: 64.95.121.95 (64.95.121.95)
Transmission Control Protocol, Src Port: 9103 (9103), Dst Port: 1325 (1325), Seq: 1, Ack: 1, Len: 76
Source port: 9103 (9103)
Destination port: 1325 (1325)
Sequence number: 1 (relative sequence number)
Next sequence number: 77 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
0... .... = Congestion Window Reduced (CWR): Not set
.0.. .... = ECN-Echo: Not set
..0. .... = Urgent: Not set
...1 .... = Acknowledgment: Set
.... 1... = Push: Set
.... .0.. = Reset: Not set
.... ..0. = Syn: Not set
.... ...0 = Fin: Not set
Window size: 17520
Checksum: 0x73e4 (incorrect, should be 0x2652)
Data (76 bytes)

0000 9b 00 4c 00 44 72 65 61 6d 43 61 73 74 20 50 6f ..L.DreamCast Po
0010 72 74 20 4d 61 70 2e 20 43 6f 70 79 72 69 67 68 rt Map. Copyrigh
0020 74 20 53 45 47 41 20 45 6e 74 65 72 70 72 69 73 t SEGA Enterpris
0030 65 73 2e 20 31 39 39 39 00 00 00 00 00 00 00 00 es. 1999........
0040 00 00 00 00 43 5a 4e 5f 32 30 30 33 ....CZN_2003

No. Time Source Destination Protocol Info
9 0.067109 64.95.121.95 64.95.121.96 TCP 1325 > 9103 [ACK] Seq=1 Ack=77 Win=4020 Len=0

Frame 9 (60 bytes on wire, 60 bytes captured)
Arrival Time: Nov 20, 2004 21:14:17.978029000
Time delta from previous packet: 0.000683000 seconds
Time since reference or first frame: 0.067109000 seconds
Frame Number: 9
Packet Length: 60 bytes
Capture Length: 60 bytes
Ethernet II, Src: 00:09:bf:01:6b:23, Dst: 00:0e:0c:50:36:fa
Destination: 00:0e:0c:50:36:fa (64.95.121.96)
Source: 00:09:bf:01:6b:23 (64.95.121.95)
Type: IP (0x0800)
Trailer: 020405B40402
Internet Protocol, Src Addr: 64.95.121.95 (64.95.121.95), Dst Addr: 64.95.121.96 (64.95.121.96)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 40
Identification: 0x0005 (5)
Flags: 0x00
0... = Reserved bit: Not set
.0.. = Don't fragment: Not set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 120
Protocol: TCP (0x06)
Header checksum: 0xcf4d (correct)
Source: 64.95.121.95 (64.95.121.95)
Destination: 64.95.121.96 (64.95.121.96)
Transmission Control Protocol, Src Port: 1325 (1325), Dst Port: 9103 (9103), Seq: 1, Ack: 77, Len: 0
Source port: 1325 (1325)
Destination port: 9103 (9103)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 77 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
0... .... = Congestion Window Reduced (CWR): Not set
.0.. .... = ECN-Echo: Not set
..0. .... = Urgent: Not set
...1 .... = Acknowledgment: Set
.... 0... = Push: Not set
.... .0.. = Reset: Not set
.... ..0. = Syn: Not set
.... ...0 = Fin: Not set
Window size: 4020
Checksum: 0xfe19 (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 8
The RTT to ACK the segment was: 0.000683000 seconds

No. Time Source Destination Protocol Info
10 0.131328 64.95.121.95 64.95.121.96 TCP 1325 > 9103 [PSH, ACK] Seq=1 Ack=77 Win=4096 Len=224

Frame 10 (278 bytes on wire, 278 bytes captured)
Arrival Time: Nov 20, 2004 21:14:18.042248000
Time delta from previous packet: 0.064219000 seconds
Time since reference or first frame: 0.131328000 seconds
Frame Number: 10
Packet Length: 278 bytes
Capture Length: 278 bytes
Ethernet II, Src: 00:09:bf:01:6b:23, Dst: 00:0e:0c:50:36:fa
Destination: 00:0e:0c:50:36:fa (64.95.121.96)
Source: 00:09:bf:01:6b:23 (64.95.121.95)
Type: IP (0x0800)
Internet Protocol, Src Addr: 64.95.121.95 (64.95.121.95), Dst Addr: 64.95.121.96 (64.95.121.96)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 264
Identification: 0x0006 (6)
Flags: 0x00
0... = Reserved bit: Not set
.0.. = Don't fragment: Not set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 120
Protocol: TCP (0x06)
Header checksum: 0xce6c (correct)
Source: 64.95.121.95 (64.95.121.95)
Destination: 64.95.121.96 (64.95.121.96)
Transmission Control Protocol, Src Port: 1325 (1325), Dst Port: 9103 (9103), Seq: 1, Ack: 77, Len: 224
Source port: 1325 (1325)
Destination port: 9103 (9103)
Sequence number: 1 (relative sequence number)
Next sequence number: 225 (relative sequence number)
Acknowledgement number: 77 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
0... .... = Congestion Window Reduced (CWR): Not set
.0.. .... = ECN-Echo: Not set
..0. .... = Urgent: Not set
...1 .... = Acknowledgment: Set
.... 1... = Push: Set
.... .0.. = Reset: Not set
.... ..0. = Syn: Not set
.... ...0 = Fin: Not set
Window size: 4096
Checksum: 0x4f5a (correct)
Data (224 bytes)

0000 72 2f d3 d6 69 fc fa 90 a5 79 78 10 b6 ad db b8 r/..i....yx.....
0010 04 29 e6 56 5f 27 a1 77 e5 fb 61 df 96 7d e3 2c .).V_'.w..a..}.,
0020 5a fa 9d 35 21 57 1c b0 b9 3c 2f 39 c3 95 4f 27 Z..5!W...</9..O'
0030 e0 24 da ab ac 19 e8 e4 31 d6 0e c9 a5 1d 9c 08 .$......1.......
0040 04 33 c0 a0 7a 4e 08 74 46 72 80 40 a6 1f 5c 92 .3..zN.tFr.@..\.
0050 c5 59 40 7a 27 8c 75 f3 ea 0c a3 64 54 7d 35 96 .Y@z'.u....dT}5.
0060 a9 b3 2f 5d 18 26 6e 70 1e ad 6e 40 d4 0a fd 04 ../].&np..n@....
0070 c6 e7 28 e5 52 88 46 95 a2 17 b8 5b 37 c2 24 df ..(.R.F....[7.$.
0080 1f 92 c3 ae 31 91 ff 20 06 d1 d9 18 3f c8 a7 0a ....1.. ....?...
0090 89 73 83 c2 d7 d5 e6 80 51 84 54 8b ef 9e 1f fe .s......Q.T.....
00a0 36 09 31 54 25 3e 89 80 73 09 a9 8c f6 77 ab 03 6.1T%>..s....w..
00b0 b4 d2 e8 58 f0 71 a2 bb ca 9c be a3 ab 0e d1 72 ...X.q.........r
00c0 fa 74 1a 69 a9 13 10 7e da e4 84 7a 3e b7 81 62 .t.i...~...z>..b
00d0 87 f6 60 7d ed 85 a0 b9 af 2f 65 52 60 20 9a 7a ..`}...../eR` .z

No. Time Source Destination Protocol Info
11 0.131448 64.95.121.96 64.95.121.95 TCP 9103 > 1325 [PSH, ACK] Seq=77 Ack=225 Win=17296 [CHECKSUM INCORRECT] Len=16

Frame 11 (70 bytes on wire, 70 bytes captured)
Arrival Time: Nov 20, 2004 21:14:18.042368000
Time delta from previous packet: 0.000120000 seconds
Time since reference or first frame: 0.131448000 seconds
Frame Number: 11
Packet Length: 70 bytes
Capture Length: 70 bytes
Ethernet II, Src: 00:0e:0c:50:36:fa, Dst: 00:09:bf:01:6b:23
Destination: 00:09:bf:01:6b:23 (64.95.121.95)
Source: 00:0e:0c:50:36:fa (64.95.121.96)
Type: IP (0x0800)
Internet Protocol, Src Addr: 64.95.121.96 (64.95.121.96), Dst Addr: 64.95.121.95 (64.95.121.95)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 56
Identification: 0x19bb (6587)
Flags: 0x04 (Don't Fragment)
0... = Reserved bit: Not set
.1.. = Don't fragment: Set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 128
Protocol: TCP (0x06)
Header checksum: 0x6d87 (correct)
Source: 64.95.121.96 (64.95.121.96)
Destination: 64.95.121.95 (64.95.121.95)
Transmission Control Protocol, Src Port: 9103 (9103), Dst Port: 1325 (1325), Seq: 77, Ack: 225, Len: 16
Source port: 9103 (9103)
Destination port: 1325 (1325)
Sequence number: 77 (relative sequence number)
Next sequence number: 93 (relative sequence number)
Acknowledgement number: 225 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
0... .... = Congestion Window Reduced (CWR): Not set
.0.. .... = ECN-Echo: Not set
..0. .... = Urgent: Not set
...1 .... = Acknowledgment: Set
.... 1... = Push: Set
.... .0.. = Reset: Not set
.... ..0. = Syn: Not set
.... ...0 = Fin: Not set
Window size: 17296
Checksum: 0x73a8 (incorrect, should be 0xbaef)
SEQ/ACK analysis
This is an ACK to the segment in frame: 10
The RTT to ACK the segment was: 0.000120000 seconds
Data (16 bytes)

0000 bb ed 29 cb e4 51 f1 2a b8 a3 6f d2 2d 2f fd 7a ..)..Q.*..o.-/.z

No. Time Source Destination Protocol Info
12 0.132040 64.95.121.95 64.95.121.96 TCP 1325 > 9103 [ACK] Seq=225 Ack=93 Win=4096 Len=0

Frame 12 (60 bytes on wire, 60 bytes captured)
Arrival Time: Nov 20, 2004 21:14:18.042960000
Time delta from previous packet: 0.000592000 seconds
Time since reference or first frame: 0.132040000 seconds
Frame Number: 12
Packet Length: 60 bytes
Capture Length: 60 bytes
Ethernet II, Src: 00:09:bf:01:6b:23, Dst: 00:0e:0c:50:36:fa
Destination: 00:0e:0c:50:36:fa (64.95.121.96)
Source: 00:09:bf:01:6b:23 (64.95.121.95)
Type: IP (0x0800)
Trailer: 722FD3D669FC
Internet Protocol, Src Addr: 64.95.121.95 (64.95.121.95), Dst Addr: 64.95.121.96 (64.95.121.96)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 40
Identification: 0x0007 (7)
Flags: 0x00
0... = Reserved bit: Not set
.0.. = Don't fragment: Not set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 120
Protocol: TCP (0x06)
Header checksum: 0xcf4b (correct)
Source: 64.95.121.95 (64.95.121.95)
Destination: 64.95.121.96 (64.95.121.96)
Transmission Control Protocol, Src Port: 1325 (1325), Dst Port: 9103 (9103), Seq: 225, Ack: 93, Len: 0
Source port: 1325 (1325)
Destination port: 9103 (9103)
Sequence number: 225 (relative sequence number)
Acknowledgement number: 93 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
0... .... = Congestion Window Reduced (CWR): Not set
.0.. .... = ECN-Echo: Not set
..0. .... = Urgent: Not set
...1 .... = Acknowledgment: Set
.... 0... = Push: Not set
.... .0.. = Reset: Not set
.... ..0. = Syn: Not set
.... ...0 = Fin: Not set
Window size: 4096
Checksum: 0xfcdd (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 11
The RTT to ACK the segment was: 0.000592000 seconds

No. Time Source Destination Protocol Info
13 0.197971 64.95.121.95 64.95.121.96 TCP 1325 > 9103 [RST, ACK] Seq=225 Ack=93 Win=4096 Len=0

Frame 13 (60 bytes on wire, 60 bytes captured)
Arrival Time: Nov 20, 2004 21:14:18.108891000
Time delta from previous packet: 0.065931000 seconds
Time since reference or first frame: 0.197971000 seconds
Frame Number: 13
Packet Length: 60 bytes
Capture Length: 60 bytes
Ethernet II, Src: 00:09:bf:01:6b:23, Dst: 00:0e:0c:50:36:fa
Destination: 00:0e:0c:50:36:fa (64.95.121.96)
Source: 00:09:bf:01:6b:23 (64.95.121.95)
Type: IP (0x0800)
Trailer: 722FD3D669FC
Internet Protocol, Src Addr: 64.95.121.95 (64.95.121.95), Dst Addr: 64.95.121.96 (64.95.121.96)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 40
Identification: 0x0008 (8)
Flags: 0x00
0... = Reserved bit: Not set
.0.. = Don't fragment: Not set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 120
Protocol: TCP (0x06)
Header checksum: 0xcf4a (correct)
Source: 64.95.121.95 (64.95.121.95)
Destination: 64.95.121.96 (64.95.121.96)
Transmission Control Protocol, Src Port: 1325 (1325), Dst Port: 9103 (9103), Seq: 225, Ack: 93, Len: 0
Source port: 1325 (1325)
Destination port: 9103 (9103)
Sequence number: 225 (relative sequence number)
Acknowledgement number: 93 (relative ack number)
Header length: 20 bytes
Flags: 0x0014 (RST, ACK)
0... .... = Congestion Window Reduced (CWR): Not set
.0.. .... = ECN-Echo: Not set
..0. .... = Urgent: Not set
...1 .... = Acknowledgment: Set
.... 0... = Push: Not set
.... .1.. = Reset: Set
.... ..0. = Syn: Not set
.... ...0 = Fin: Not set
Window size: 4096
Checksum: 0xfcd9 (correct)
SEQ/ACK analysis


Advertisement
_
__
 
_
StoneRain
Junior Member
_
21. November 2004 @ 10:06 _ Link to this message    Send private message to this user   
Just to clear things up, which IP is the GC and which is your PC?

It still looks like to me they changed the encryption method. I am also curious if the dreamcast blah blah blah ..2003 shouldnt be 2004 since PSO+ came out then. This is a real long shot.

This message has been edited since posting. Last time this message was edited on 21. November 2004 @ 11:33

 
Page:12Next >
afterdawn.com > forums > archived forums > nintendo gamecube - general discussion > pso plus port issue
 

Digital video: AfterDawn.com | AfterDawn Forums
Music: MP3Lizard.com
Gaming: Blasteroids.com | Blasteroids Forums | Compare game prices
Software: Software downloads
Blogs: User profile pages
RSS feeds: AfterDawn.com News | Software updates | AfterDawn Forums
International: AfterDawn in Finnish | AfterDawn in Swedish | AfterDawn in Norwegian | download.fi
Navigate: Search | Site map
About us: About AfterDawn Ltd | Advertise on our sites | Rules, Restrictions, Legal disclaimer & Privacy policy
Contact us: Send feedback | Contact our media sales team
 
  © 1999-2024 by AfterDawn Ltd.

  IDG TechNetwork