Jump to content

KarolinaKatt

Resident
  • Content Count

    21
  • Joined

  • Last visited

Community Reputation

1 Neutral

About KarolinaKatt

  • Rank
    Member
  1. KarolinaKatt

    Multiple crashes

    Sorry forgot: The answer is Yes I have. Same result. I have discussed earlier in this thread that pointing to other addresses than that 11.1.0.1 is jumping all the way to target and does not stop at level 4. Here is result for Tracert 4.16.106.5 1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.1.1] 2 <1 ms <1 ms <1 ms 65.99.187.1 3 2 ms 2 ms 2 ms 65.99.185.249 4 16 ms 16 ms 16 ms 94.246.65.94 5 14 ms 15 ms 14 ms 213.212.14.49 6 16 ms 16 ms 16 ms 213.80.86.224 7 16 ms 15 ms 33 ms sesto1024-rc2.ip-only.net [213.80.86.6] 8 18 ms 18 ms 18 ms lag-150.ear2.Stockholm2.Level3.net [212.73.250.253] 9 187 ms 223 ms 187 ms ae55.bar2.SanDiego1.Level3.net [4.16.106.5] This is measured via my problematic Ehternet, not wifi.
  2. KarolinaKatt

    Multiple crashes

    Thank you Nalates! I get the same results with both my PC and laptop with different cables connected to different ports on the router. The hotspot is the same Netgear router that transmits the problematic ethernet. And I am in Sweden so I do not use TelCo. And I get internet via an optical fibre. At home I never use phone as hotspot. It is my HTTP readings at upload that are extremely low. Websockets gives good results. Are you sure there cannot be any problem there?
  3. KarolinaKatt

    Multiple crashes

    I found out that I can check bandwidth in different ways. And I get VERY different readings on the upload. (Now I do not have a clue of what this means but..) On the uploads I get around 3 Mbit/s when testing on the HTTP variant, while I have 113 on the Websockets variant. Downloads are over 100 on both. Can someone please help me understand. 1) Is this something that can produce the crashes in SL? (But both ethernet and wifi shows similar results) 2) What is causing this difference? Can I do or check something on my router? (I have recently reset it fully)
  4. KarolinaKatt

    Multiple crashes

    Thank you Briana. Do you, just like me, notice in advance when SL starting to crash for you? If so, have you tried to TP to another place before the crash? My problem is only when on ethernet cable - not when on my home wifi network,
  5. KarolinaKatt

    Multiple crashes

    Well I crash out from SL if I do NOT TP away. So the TP is making Firestorm to avoid a crash. If I do not TP, then I will crash. By making the TP I can stay in SL until it crash next time. But thats not a way to go, I cannot TP every teo-three minutes, lol. I have also now totally reset the router to factory settings once more and found that it did not help.
  6. KarolinaKatt

    Multiple crashes

    Ohh I dont understand these quote-functions. I think I messed up something for you Rolig... But thank you Linda and Rolig for replys. I should have been thinking of using the cable directly. I have been doing that two years ago when the router was new and there where problem wiht the ISP. But now I did and I have used SLfor at least 15 minutes now without being thrown out. I cant let the router be down much more, we have several items in house depending on it, but I think I have enough to call the ISP and ask for another router (it is the ISP property) No I will reset the router totally once more first, otherwise I will be ordered to do that. Another question just out of curiosity. When running TRACERT on 11.1.0.1 (mygod is it the US DoD I've been pinging???) I always got four jumps before timeout. Now, without the router, I get three. That feels quite understandable. But when using TRACERT on some other address, like one of the Atlanta addresses in Nalatie's TRACERT above, I come all the way to the goal. What is the difference? But for now SL feels very stable and I am very happy. Hopefully all you guys in here have helped me to pinpoint the error. I am soo thankful for all helpful people. Now what about the bug reports to Firestorm and SL? Shoudl I remove them directly or what to do? My question how I could save from crashing by making a TP, still remains. I have problems to see how that can be fixed by the router.
  7. KarolinaKatt

    Multiple crashes

    Thank you Nalates! I will call my ISP up as soon as I can. The 65. etc address is the ISP servers. Obviously their firewalls works well :) I still cant get out of this 65. area, when running TRACERT, so I guess they have a firewall in that direction also. Still I CAN run SL over wifi at both my home router and via mobile hotspot. So that indicates a problem with the router, dosen't it? On the other hand I can prevent SL crashes by simply make a TP when I notice it is coming. This confuses me. By weekend I will reset my router again, if I find time. Turning all stones......
  8. KarolinaKatt

    Multiple crashes

    Short update: Problem persists. ISP have answered that it is "too complicated" to describe the ICMP path over mail. I dont need a description! But I feel they do not see anything wrong so far. Their queues at the phone support are very long, and I have not mucht time free at home with kids and home cores. I will let a friend make a test to play some other games on his laptop via my ethernet connection, and see if there are any problems.
  9. KarolinaKatt

    Multiple crashes

    Thank you Nalates - I did.
  10. KarolinaKatt

    Multiple crashes

    Thank you Natales! I know enough about computers to manage my own and some company stuff when needed, but networking is not a part of that. And I do not understand very much of what you are trying to tell me. But I notice you wanted to see the whole TRACERT result. I tried to tell that it all was similar to the two last hops but here it is: Tracing route to 11.1.0.1 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 <1 ms 1 ms <1 ms 65.99.187.1 3 2 ms 2 ms 2 ms 65.99.185.249 4 14 ms 12 ms 12 ms 94.246.65.94 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. And all TRACERT I have run is pretty much identical. Might differ one or two milliseconds, but it never comes further than to jump 4. I have asked my ISP about this. Will hopfully get resppond in a few days. I have tried an alt account wiht the same result, so thank you Whirly for that info. Now, I have found out that my PC actually have a wifi card, I was not aware of, but it was not working. I installed driverrs for it and made it work . So therefore I could pull the cable and find out that SL is not crashing anymore. And I am getting 114/111 Mb/s even wiht wifi so thats what I need to my RL photo backups that can be really huge. So I do have a cable problem but not wifi problem on the same router. That is obviously pointing the error to the router. On the other hand, the fact that I can save from crashing out by making TPs in SL, is telling me it might be an SL problem anyhow. What I cannot do, I have discovered after multiple failed attempts, is TP back to the place where the crash initiated, until a crash have started on the new place I TPed to. If I try to TP back sooner, it will lock me in TP and kicking me out from SL. Oh and here are the packets summary from the log I sent to Firestorm support after a crash: SendPacket failures: 0 Dropped packets: 1 Resent packets: 435 Failed reliable resends: 13 Off-circuit rejected packets: 0 On-circuit invalid packets: 0 I cannot interpret that. And thank you guys for giving me your time, I appreciate that a lot.
  11. KarolinaKatt

    Multiple crashes

    Ok I will contact ISP. But since SecondLife is running well until the crash occurs, is it really possible that it is a connection problem? And how can I by teleporting "save" me from crashing out and proceed with SL if it is a connection problem. My feeling is that it might be a windows update problem or something in my inventory. The problem have also been very small for a long time but accelerated severely last weeks. Here is my TRACERT, by the way. I excluded step 7 to 30 since they where all similar to 5 and 6 1 <1 ms <1 ms <1 ms 192.168.1.1 2 <1 ms 1 ms <1 ms 65.99.187.1 3 2 ms 2 ms 2 ms 65.99.185.249 4 14 ms 12 ms 12 ms 94.246.65.94 5 * * * Request timed out. 6 * * * Request timed out.
  12. KarolinaKatt

    Multiple crashes

    Whirly - I need to ask you, since this is now a support issue at Firestorm, do you want me to keep reporting what I find out here, or to the issue or both? For now I will put another small observation here, but I can copy it into the support issue if you like. When TP to "save" my precense in SL, I can, unless I have waited too long before trying the TP and get logged out directly, TP to other places. From that place, if I try to TP back to where I experienced the crash, I mostly get stuck in TP and logged out. i CAN sometomes - only sometimes -make a TP directly to the place where I am, but mostly it will logg me out with the text "You have been disconnected..." And first attempt to log in again moslty result in "The region is logging you out, please try again in ...." I have excluded anyting I wear, body, AO etc from causing the problem. I have no idea if there is a possibility to find out if anything in inventory causes these problems. Cache is not the cause, for sure. I add a screen dump on the one of the 3-4 crashes I have had just while writing this message.
  13. KarolinaKatt

    Multiple crashes

    Hi Whirly! No I have never seen that message. I can TP within the region to "restore" my connection and avoid a total crash, when I notice the first signs of a coming crash. But TP witrhin a region is often locking up, so I prefer to TP outside the region and return again within a minute or so. I mostly get the common "Region might have experienced trouble"-message when letting me being kicked out fully. And - this I do not think I have told before - these crashes started long time ago, but from the beginning I only experienced them very rarely, and only at FogBound Blues. Last months they have accelerated in numbers, ending up in the present situation where I crash everytime and everywhere in SL - even my home. Freinds I tell these problems to, often says that they experience the same behaviour when crashing, but I have heard of noone that chrasing this often. And i will ask the next one if they can try to save the crashes by making a TP. It will be interesting to find out.
  14. KarolinaKatt

    Multiple crashes

    Thank you Natales Packet loss is 0% and ping is 190 - 220. I think that is good. Temperatures are fine - I have an almost brand new huge fan after having heat problems. I will check memory as soon as I can. I have 16 gb memory in my PC (intel i5) and ....sufficient on my laptop (i7) I do not understand TRACERT, but running it get time out before i get out of Swedish routers. Now; I CAN run SL as long as it not crashing and by TP I can prolong the session between crashes. Managed today to be in SL over half an hour before logging out - thanks to frequent TPs of course, which not making my SL experience very nice, but I can at least chat. So there is contact obviously. I think that I wouldl have the same problem on wifi but wifi is ok. Wifi okl, ethernet over the same router not ok, point to my equipment for the problem, but the fact that I can avoid the crashes by making a TP when I notice a crash is immedient, makes me think its on the SL side anyhow. I appreciate all hints and helps like this. Thank you again
  15. KarolinaKatt

    Multiple crashes

    Ok I have filed a bug report to Firestorm. But I discovered that when FS is starting the crash procedure, when I cannot see myself walk anymore, if I then TP somewhere, I am unlocked again and do not get thrown out from SL. I have only tried this a few time so far, but it seems like it works. It is definitely a workaround but I think it limits the problem to Firestorm at least.
×