Post Your TRACERT here!

You can easily install Linux on an external disc drive or Flash drive. Ubuntu Linux can even be installed on the same partition as Windows using Wubi.

I don't have an External Drive. At least not yet. I am in the process of shopping for one though. I have a few flash drives though. About how much space would I need to do this?

I also installed & tried using WinDump, but I don't understand how I am supposed to see that last two lines after getting D/C'd, since the program continues to run non stop. Is there a log that is saved someplace? Since it's running in DOS the information only goes back so far & it can't be copied either.

Thanks

I also installed & tried using WinDump, but I don't understand how I am supposed to see that last two lines after getting D/C'd, since the program continues to run non stop. Is there a log that is saved someplace? Since it's running in DOS the information only goes back so far & it can't be copied either.

windump -vn net 128.241.92.0/23 and tcp port 4500

Only works if you're not using a proxy (lowerping/wtfast).

Our ISP is still NTT.

Our ISP is still NTT.

Time to change to another service?

I don't have an External Drive. At least not yet. I am in the process of shopping for one though. I have a few flash drives though. About how much space would I need to do this?

[…]

After doing a little research, I've discovered that, while it's possible to easily install Ubuntu Linux onto a Flash drive, there is no easy way to install it in a manner that both limits the number of writes to the drive (to extend its lifetime) and allows you to install any additional drivers that you may need. I therefore recommend that you use Wubi instead.

Once you've installed Ubuntu, you should do the following:

• Install the proprietary drivers for your GPU if you're prompted to.
• Install the IRO client.
  
  You should be able to save time and hassle by skipping the last step and simply opening the client from the same folder you open it from in Windows. To access your Windows files:
  
  
  • Open Nautilus (press the button on the launcher that has an icon depicting an orange folder, and is labelled "home folder").
  • Choose "file system" from the side pane.
  • Open the folder named host.
• If you're planning to leave the client running overnight, then disable any power saving features that could interfere with the IRO client's operation.

windump -vn net 128.241.92.0/23 and tcp port 4500

Only works if you're not using a proxy (lowerping/wtfast).

I'm not using any of them. When I started windump it automatically ran on it's own. I wasn't given any options or choices at all. The problem was that it didn't ever stop so I wasn't able to see the information when the disconnect occurred.

As I suspected all along, since this past maintenance was done, now I am no longer receiving these errors, or being disconnected multiple times a day, much less even once a day. The finally fixed whatever they did on the 9th on Tuesday.

Our ISP is still NTT.

I would have to agree that your ISP should be changed, & is one of the problems, as I've always thought. Why use an ISP from another Country when the Servers are in the US? IMO you should be using a US ISP but maybe that's just me.

Thank you for replying Oda but I wasn't just asking who your ISP was. I was asking what type of service you had. For example do you have a dedicated line? What type of connection & speed do you have? If you don't know can you please find this out?

I'm not using any of them. When I started windump it automatically ran on it's own.

You know how to use cmd, right?

Thank you for replying Oda but I wasn't just asking who your ISP was.

He's not replying to you.

Edited by Javsy, 18 April 2013 - 11:50 PM.

You know how to use cmd, right?

I'm not sure I understand your question. If I didn't I wouldn't be able to run tracerts. When I start windump it runs in dos not windows. So I'm not sure what that has to do with how to change settings on windump or capture what no longer shows.

He's not replying to you.

Oda does reply to me. I was the one who has been & asked about who they were using for their ISP


I finally did get another Time Gap Error but at least it wasn't after only being connected for a short time. Instead it was after about 24 hours

Edited by Razzez, 19 April 2013 - 04:08 AM.

Well it was nice while it last but once again I am getting Time Gap Errors, in a very short amount of time, ever since they did maintenance again on the 19th

Hmm I thought I would have a response by now Javsy.

Okay, if you don't know how to do what Renouille said, do the below in steps:

1. download winpcap by clicking http://www.winpcap.o...nPcap_4_1_3.exe and install it. You might need to restart after.
2. download windump by clicking http://www.winpcap.o...9_5/WinDump.exe but you don't need to install/double click it.
3. Log in to RO and go to specific map where you know the IP address the map server. For this example let's user Prontera using IP address 128.241.92.101
4. go to cmd and go to where you have saved windump.exe by using the change directory (c:\ cd yourfoldername) and run the below commands

windump -D

you should see a list of network interfaces, if you're not sure what exactly, try them all later.



5. type the below command to start capturing your traffic

windump -i <interface number> -w filename.log net <ip address> and tcp port <port number>

Using the interface 3 (that's what I'm using which might be different to yours) and prontera map IP address and the default port the map server uses, you should have something like this:

windump -i 3 -w rawfile.log net 128.241.92.101 and tcp port 4500

6. Once done capturing, press ctrl+c and you would see a message like this:

3 packets captured
20 packets received by filter
0 packets dropped by kernel

If you don't see any packets are captured, go back to step 4 and try another interface number.

7. The output will be in raw packet format so you need to convert it in human-readable form. Use the same interface number you used on the previous command.

windump -i 3 -r rawfile.log>converted.log -vn

8. Check the converted.log file and skim the logs. If you have been disconnected to the server, you should be able to capture it with the timestamps and the network handshakes from the moment you got disconnected. Pretty much you will only capture the packet of the map server you have indicated on the above command.

9. Send a ticket to WP support and send them the logs. Fry them if they don't give you a reasonable answer.


If you need more info on the windump commands, you can visit the documentation at http://www.winpcap.o...docs/manual.htm

Credits to Renouille for sharing this. Took me like 10 minutes to grasp the idea of the tool.

Edited by Javsy, 23 April 2013 - 02:28 AM.

9. Send a ticket to WP support and send them the logs. Fry them if they don't give you a reasonable answer.

Will they be able to understand them? It might be better to post the log in this thread instead.

They should. They're not doing their job well if they can't even understand how to read it.

They should. They're not doing their job well if they can't even understand how to read it.

they will give you a "we are getting many tracerts so it will take a really long time" response and then leave the ticket open for over a week. Possibly 2. Possibly more.

Okay, if you don't know how to do what Renouille said, do the below in steps:

1. download winpcap by clicking http://www.winpcap.o...nPcap_4_1_3.exe and install it. You might need to restart after.
2. download windump by clicking http://www.winpcap.o...9_5/WinDump.exe but you don't need to install/double click it.
3. Log in to RO and go to specific map where you know the IP address the map server. For this example let's user Prontera using IP address 128.241.92.101
4. go to cmd and go to where you have saved windump.exe by using the change directory (c:\ cd yourfoldername) and run the below commands

windump -D

you should see a list of network interfaces, if you're not sure what exactly, try them all later.



5. type the below command to start capturing your traffic

windump -i <interface number> -w filename.log net <ip address> and tcp port <port number>

Using the interface 3 (that's what I'm using which might be different to yours) and prontera map IP address and the default port the map server uses, you should have something like this:

windump -i 3 -w rawfile.log net 128.241.92.101 and tcp port 4500

6. Once done capturing, press ctrl+c and you would see a message like this:

3 packets captured
20 packets received by filter
0 packets dropped by kernel

If you don't see any packets are captured, go back to step 4 and try another interface number.

7. The output will be in raw packet format so you need to convert it in human-readable form. Use the same interface number you used on the previous command.

windump -i 3 -r rawfile.log>converted.log -vn

8. Check the converted.log file and skim the logs. If you have been disconnected to the server, you should be able to capture it with the timestamps and the network handshakes from the moment you got disconnected. Pretty much you will only capture the packet of the map server you have indicated on the above command.

9. Send a ticket to WP support and send them the logs. Fry them if they don't give you a reasonable answer.


If you need more info on the windump commands, you can visit the documentation at http://www.winpcap.o...docs/manual.htm

Credits to Renouille for sharing this. Took me like 10 minutes to grasp the idea of the tool.

Thanks for the reply. The problem I had was when I clicked on Windump to run it showed kept running after I got d/c'd from RO.
That's why I was asking how to set it so it would stop & do the one IP only.

they will give you a "we are getting many tracerts so it will take a really long time" response and then leave the ticket open for over a week. Possibly 2. Possibly more.

That's why I stopped sending in Tickets & won't be. Oda want's me to PM him with the information I get.

Thanks for the reply. The problem I had was when I clicked on Windump to run it showed kept running after I got d/c'd from RO.
That's why I was asking how to set it so it would stop & do the one IP only.

that's why i said on step 2 that you don't need to double click it to run as you need to run it in cmd to pass the parameters to it and assign the interface you need to capture.

That's why I stopped sending in Tickets & won't be. Oda want's me to PM him with the information I get.

Whether you like it or not, you have to do your part of reporting issues. Nothing will happen if the two sides (you and the support team) will ignore their own responsibilities. We already know that the support team are having their lapses... Everyone who already has a job knows what I am saying. But for you as a customer, you should also do your part. Whether you like it or not, it's also your responsibility to keep banging their heads when they're not doing well.

You'll understand sooner or later.

Edited by Javsy, 24 April 2013 - 02:08 AM.

that's why i said on step 2 that you don't need to double click it to run as you need to run it in cmd to pass the parameters to it and assign the interface you need to capture.

That's why I said thank you & was asking for the information as to how to run windump with settings so it didn't do that

I've done it the way you said now & once I do all that shows is this:

D:\Downloads>windump -i 1 -w rawfile.log net 128.241.92.98 and tcp port 4500
windump: listening on \Device\NPF_{F831F7C1-65B0-4591-A2F8-DD9855742023}

After being d/c'd nothing else happened or appeared.

Whether you like it or not, you have to do your part of reporting issues. Nothing will happen if the two sides (you and the support team) will ignore their own responsibilities. We already know that the support team are having their lapses... Everyone who already has a job knows what I am saying. But for you as a customer, you should also do your part. Whether you like it or not, it's also your responsibility to keep banging their heads when they're not doing well.

You'll understand sooner or later.

I have done my part in reporting the issues more times then you know. You have no clue as to how many tickets I have sent in about issues however when the person in charge of the Ticket Department, David, actually has the nerve to complain to me about the amount of tickets I have sent in, then there is a problem.

That's why I am still doing my part, as I said, & reporting the information to Oda directly via PM. He is sending the information to the appropriate people so it can be dealt with.

I've already given him the tracerts as he requested & he knows all about my issues. Now I am trying to gather as much information as I can for him like this. That's why he referred me to this thread of yours

I really appreciate the help.

After being d/c'd nothing else happened or appeared.

If you use the -w option which writes the dump in a form of log file, you won't see the actual packets captured in command prompt. It's the limitation of windump so you need to confirm first you're using the correct parameters. To do that you need to do a test run.

1. Launch RO and log in until you're inside a specific map you want to capture the packets
2. run windump with the the parameters mentioned in the previous post
3. go back to the game and interact with it with a few seconds.
4. go back to windump and finish the capturing session by pressing ctrl + c. You should see something like this

3 packets captured
20 packets received by filter
0 packets dropped by kernel

This will be the only way to see if you are capturing any packets while using -w option

5. If you get zeros then you have to try the other interface numbers and start again.
6. If you have tried all the interface and still getting zeros, review the parameters (eg. you're using prontera IP address in windump but your character is not in prontera)
7. Once you have packets successfully captured, proceed with your normal session and convert the raw log file once done with the actual captures (pls refer to the previous posts)

Edited by Javsy, 25 April 2013 - 12:39 AM.

If you use the -w option which writes the dump in a form of log file, you won't see the actual packets captured in command prompt. It's the limitation of windump so you need to confirm first you're using the correct parameters. To do that you need to do a test run.

1. Launch RO and log in until you're inside a specific map you want to capture the packets
2. run windump with the the parameters mentioned in the previous post
3. go back to the game and interact with it with a few seconds.
4. go back to windump and finish the capturing session by pressing ctrl + c. You should see something like this

3 packets captured
20 packets received by filter
0 packets dropped by kernel

This will be the only way to see if you are capturing any packets while using -w option

5. If you get zeros then you have to try the other interface numbers and start again.
6. If you have tried all the interface and still getting zeros, review the parameters (eg. you're using prontera IP address in windump but your character is not in prontera)
7. Once you have packets successfully captured, proceed with your normal session and convert the raw log file once done with the actual captures (pls refer to the previous posts)

I used the exact command you posted for me to use which had the -w option included in it. I also posted above, in my quote, a copy of the command I used. I even tried to open the log file to see if I could get the information from it but it's not readable.

So does that mean instead of running, the original command you posted, which was this:

windump -i 1 -w rawfile.log net 128.241.92.98 and tcp port 4500

I should be running it this way instead?

windump -i 1 net 128.241.92.98 and tcp port 4500

Edited by Razzez, 25 April 2013 - 01:46 AM.

that second one with no -w option will print the captured packets but won't be saved in a file. If you use -w it won't be printed in the screen but it will be saved in the file which can be troublesome if you let it run for like 8 hours while you're sleeping. I assume you have captured some if you see unreadable text in the file. That is why you need to use the convert command to translate it to readeable form.

windump -i 1 -r rawfile.log>converted.log -vn

And I see you use interface 1. Make sure it's the right interface your computer or using. If not, try using the others and see how it goes. You can try doing it without -w just to check if you are capturing any data.

Edited by Javsy, 25 April 2013 - 02:01 AM.

that second one with no -w option will print the captured packets but won't be saved in a file. If you use -w it won't be printed in the screen but it will be saved in the file which can be troublesome if you let it run for like 8 hours while you're sleeping. I assume you have captured some if you see unreadable text in the file. That is why you need to use the convert command to translate it to readeable form.

windump -i 1 -r rawfile.log>converted.log -vn

And I see you use interface 1. Make sure it's the right interface your computer or using. If not, try using the others and see how it goes. You can try doing it without -w just to check if you are capturing any data.

I only have the one device.

I just ran it without the -w option like this

windump -i 1 net 128.241.92.98 and tcp port 4500

After being d/c'd once again it still shows that it is listening on the Device & isn't showing the results.

What am I missing?

I only have the one device.

Having one physical interface doesn't really mean you will only have one. Logical interfaces created by setting a bridge, hotspot, etc will create a logical network interface. To confirm this, you need to use the -D option just like what i said on my previous post.

windump -D

you should see a list of network interfaces, if you're not sure what exactly, try them all later.

It would really help if you show a screenshot of the problem.

After being d/c'd once again it still shows that it is listening on the Device & isn't showing the results.

What am I missing?

Windump won't stop on its own unless you set a timer/packet counter (which is useless based on your purpose). What you can do is stop windump and convert logs and check the handshakes.

To make it short, it's not noob-friendly. It will not tell you "hey you got disconnected because of this and that". It's a tool to capture the data needed for you to make your own personal analysis.

Edited by Javsy, 25 April 2013 - 04:16 AM.

Having one physical interface doesn't really mean you will only have one. Logical interfaces created by setting a bridge, hotspot, etc will create a logical network interface. To confirm this, you need to use the -D option just like what i said on my previous post.



It would really help if you show a screenshot of the problem.



Windump won't stop on its own unless you set a timer/packet counter (which is useless based on your purpose). What you can do is stop windump and convert logs and check the handshakes.

I've done every command you said to do. I can't help it if when I did windump -d only one device showed up instead of 3 like you have but that's all I have. Due to this I am not able to run windump with the parameter set to anything other then 1.

I don't know what screenshot of what problem you are talking about. I've already posted in the quote previously the command I ran & the windump message I got.

Now you're confusing me. "Windump won't stop on it's own unless you set a timer/packet counter (which is useless based on your purpose)." Then exactly how am I supposed to see the packet information on the last 3 lines that you keep showing me?
I've said that all that happens when I run windump now is that the one line appears showing it is listening on the Device. Nothing else happens. It stays like this even after I've been disconnected. I converted the log file & it has no packet information in it either.

I would appreciate it if you could clarify which way I need to run this, in order to get the packet info to show up, whether it be in the log file or within the command prompt screen. I don't care which one.

To make it short, it's not noob-friendly. It will not tell you "hey you got disconnected because of this and that". It's a tool to capture the data needed for you to make your own personal analysis.

I've already told you once I'm not a noob when it comes to computers. I've probably been working on them longer then you have. We just have different experience with things is all

I know this isn't going to tell me anything about why I was disconnected. Just like a tracert doesn't tell you anything however RO is telling me why I am being disconnected. I've said it's due to "Time Gap Errors".

I'm not the one that needs to make my own personal analysis though. I am trying to gather information so that Gravity can fix the problem on their end hopefully. I can't fix something when there isn't anything wrong on my side

Then exactly how am I supposed to see the packet information on the last 3 lines that you keep showing me?

Press ctrl+C.

6. Once done capturing, press ctrl+C

You have to manually stop the capturing with that keystroke. Basically you will see something that looks like this:



It's expected you only see the first line while it's runnning as the actual packets captured will be written in the file. As for the last 3 lines, those will appear when you terminate the program by pressing ctrl+C.

Edited by Javsy, 25 April 2013 - 05:00 AM.