Can't teleport with 1.13.3

I installed the linux 1.13.3 and can't teleport anymore.
When I do a teleport I get disconnected.
I had the same problem when 1.13.2 was released but then it was fixed.
Please fix it in this version also.


Gr. Richard

Yep, same here, New release -> no teleport. Teleported fine until a while ago.

I'd really like to hear Tofu's opinion - is this a linux problem or a firewall problem, what's your impression?

Is that the same firewall problem? Does anybody have a fast way to test "If your firewall is blocking outbound TCP port 12043"? Because at this point I'm not so sure..

Thanks for any help..

PS: last update same problem:

/263/d8/161239/1.html

Thanks for the report. I strongly doubt it's a Linux problem, but you never know...

Could you try removing ALL attachments and then teleporting - does that help?

Thanks Tofu, I've tested all the known methods: fly and teleport, teleport naked (my! lucky it didnt work), and several other that are listed in the web support. No avail.

My best bet is the firewall again. I'm trying to talk with a tech at the net group. But if it is so, how come that Richard says "it was fixed"? Is it possible that the restriction on port 12043 was lifted after a couple of says in the previous version?

And how do we account that Windows people do not have the problem?

With a pointer from a LiveHelper I eventually tracked down that we need to open TCP port 12043 to get TP and region crossing working. The main firewall knowledgebase page at

http://secondlife.com/knowledgebase/article.php?id=029

needs to be updated to reflect this.

The first 1.13.2 that came out had the problem of no teleport, then maby one day later there came a newer 1.13.2 and then the problem was fixed for me..

Yes, I agree - finally I tried a conf where I was really sure of having all ports open, and I could finally teleport.

This does not explain, however

- why the problem seems confined to mac-linux clients (true?)
- what happened with last release, where after a first update we could again tp (perhaps a workaround was added and forgotten in this version?)

And the problem is that I cannot change my network configuration from my main connection.. so it's out of SL until I find a way.. Or I'll just play in a single sim..

I'm having this kind of trouble exactly since yesterday. Can't teleport across sims, only within one. But - I'm working with this client version already for several days, and until ~24 hrs ago it worked fine! This has me doubt whether this is really a client issue.

I'll double check the mentioned firewall issue, but I can't imagine that anything has changed in its configuration just a day ago. (Working on SuSE Linux 10.1, residential shared connection via Apple Airlink.)

Ok I checked... nobody changed any settings of our firewall here. So if it has worked before, it should work now. This is no 100% guarantee that we haven't overlooked anything, but it seems unlikely from this angle.

I don't want to appear impatient, but is anyone aware that they're working on it, is there some Linden feedback on this issue that I've missed? I don't see this listed in the known issues or anywhere else. But it is urgent! The experience is absolutely horrible.

Thanks

Ok, I've waited for the latest problems to sort out... but still no joy here on this front. I heard from a Mac user that they can teleport again, but it still won't work for me on Linux. No indication either that LL is aware of this. Going to try all available channels to get this through...

At this point I don't really have any great insight to add, I fear.
Some data points:
* Teleporting works for most people on the Linux client
* A small number of people on all client platforms started seeing teleporting issues in 1.13.3
* 1.13.{2,3} did introduce some probably-not-documented-enough changes to viewer<->backend communication which requires more open ports or you'll experience the symptoms described
* We've been turning these changes on and off at the backend for various reasons, which means that some days you will or won't be able to teleport if you are over-firewalled, even with the same viewer...
* We've been having a few network issues on and off over the last couple of weeks which really haven't helped.

In conclusion, if you think you're not firewalled or port-filtered, I think the best advice is to look again! Failing that, it would be interesting to hear whether you have any *PROXY variables set in your environment.

For more info on the new firewall requirements,
http://secondlife.com/knowledgebase/article.php?id=355

I can now affirm that this is not a Linux client issue. I found an old harddisk with a previous Windows installation on this same machine, tried it, and the result is the same. So it definitely must be a network/firewall issue that was overlooked before. I am going to check back with the person who has access to the router configuration and will thoroughly go through the requirements as pointed out.

Thank you Tofu for responding!

Cheers

Still no luck...

- Talked to the person who owns the router: Says it's not blocking any outgoing ports. Only if I would run a server that needs to listen to a specific port, a port forwarding needs to be specified. We've done that now for 12043, to forward to my local address. No success.

- Checked local software firewalls. Suse firewall was running on my Linux box. Set it to accept 12043 TCP. No change. Switched it off completely. No change.

I'm at a loss as to what to try next. Maybe we need to know, is the SL client acting as a server as well? Does it need more incoming ports? In the firewall configuration article in your knowledge base, it is said 'and related inbound traffic', what exactly does that mean? If I need to get inbound traffic on certain ports, then we need to setup forwarding for all of them. But I'm not sure actually what I'm talking about here, not really being a savvy network admin. I'm just trying to repeat what I've been told.

Fact is, up until a week ago it worked, even a day after the 1.13.3 update was installed, and no more since then. Teleporting (and flying) across region borders is the only function which is affected. I have no other difficulties like map display or IM issues etc., as other users have reported.

What can I do next to try and resolve this? I found how to bring up the 'secret' Client and Server menus, and there are some logging switches under Client > Network. Would this help? Where do I find the logfiles created this way, and where would I send them?

Thanks for any support

Edit: Checked for the PROXY environment variable, nothing. I even grep'ed the entire output of 'export', nothing that even contains the word. (Or do I need to look elsewhere? Not sure if this was correct.)