![]() You may be witnessing what is called NAT loopback. But you come home and try to use those same addresses to access the camera and nothing appears, or worst, You receive an error message. Have you tested your configuration when I was away from home, the external network, and everything worked fine,as expected. Once again, many thanks.Suppose you have configured an IP camera that you want to access from anywhere via the Internet and have an external IP address, or a DDNS address, to access the camera. So, partial success and certainly a step in the right direction. Since 2013 I've run my own servers, initially using a Netgear WNR 2000 with dd-wrt firmware and since late 2017 with my current router, the RT-AC68U, which as I explained in my initial post, worked well with no issues. I've been using this software for the best part of a decade now, and up til now haven't really had these issues, as previously I've either been a mere user of a virtual world, or have had my region hosted. as a standalone or as part of a wider virtual world respectively. Yes, an Open Simulator instance running locally on the same LAN with no connection to the internet does not need NAT Loopback because it's not being accessed from outside the LAN as is the case with it set up in what is called Hypergrid or Grid mode, i.e. I still don't seem to be able to teleport back to my world though, and this will be a router issue for which I'll probably need help from the Open Simulator community as the message I receive in the special browser is a common one that is at best cryptic. I tried your suggestion and it works, and though I can teleport from my world to others (basically move from my 3D website to another through changing the URI (url for Opensim 3D worlds) in the special browser map. If anyone has any ideas for a solution that is relatively easy to implement I'd be happy to read them.Ĭlick to expand.Thank you. I hope there is a solution, otherwise this router is just useless to me. ![]() I've tried to 'roll back' to a previous version of the firmware know to have NAT Loopback ability, but of course the router is set up to not allow this as a 'security feature', which is frustrating to say the least. This post, however seems to suggest that NAT Loopback does still work, (though maybe because the OP there is using 384.17 firmware) and those responding are unaware that the feature has been removed. On upgrading to the 386.5.2 firmware I again revisited the NAT Loopback issue with the router, only to discover that this feature has been removed back in 2018, according to this post: I tired this, and it worked, so I was able to connect to my Open Simulator servers, albeit in a less than ideal manner. I then hit on the idea of trying to connect via a VPN, as this would emulate NAT Loopback, so my thinking went. It didn't so basically I gave up running the Open Simulator server pending further invesigation. I hadn't changed settings, so in theory it should have worked. ![]() Some months go I upgraded the firmware on the router, and thought nothing of it, and when I tried to connect to my Open SImulator server from another PC on my LAN it refused connection. After setting it up, all worked very smoothly, like a dream in fact, and performance was much better than with the Netgear WNR 2000 it replaced. I bought this router on the strength that it would accomodate NAT Loopback, which is a basic requirement for running an Open Simulator server (used for the creation of Second Life like virtual worlds).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |