Re: [Opensim-users] Problems with teleporting in grid mode, from simulator instance to another instance? (Ferd)
Hi Fred / et all, My Grid configuration is running behind a company firewall. So all service we provide are serviced by the company firewall. We dont want to advertise our internal IP addresses to the outside world. So we run an internal DNS server with all the internal network and an external DNS server to provide services to users on the internet. The Split DNS concept. In this way we make our Network configuration more secure beside all other security measures we do on the FW of course. By port forwarding we redirect the traffic from Internet to the right ports on the Grid or Region server. When I started to configure OpenSim I first use FQDN (host.domain.nl) and got the same result as mentioned by Tom. After monitoring the network I saw package that could not be resolved. For the internal network users and the users from internet you want the configuration to be transparent without have to use different configuration. The only solution to use OpenSim Grid in combination with split DNS and a FW is to use FQDN. Then the resolving of the internal and external DNS will result respectively in the internal IP address for internal users (for instance an address like 192.168.0.1) and the FW IP address for external users (for instance 47.185.237.187) with forwarding of ports to the internal servers. This configuration works for all services we provide but not for OpenSim's Region.ini. This configuration will only work when you put in the FW IP address. Somehow there is something wrong in the resolving and accepting the FQDN in the Region.ini I think more and more OpenSim network will be behind FW and security system with split DNS and use internal un-routable IP ranges (class A: 10.x.x.x and class B: 192.168.x.x). Normally this configuration can work stand-alone. But when my FW is down the standalone grid will not work because of the external IP address in the Region.ini. When FQDN in the Region.ini are correctly resolved then internal users can work on the grid because it doesn't need the FW to connect to but use the internal DNS that resolve the FQDN to the internal IP address. So the FQDN in the Region.ini does not lead to the right IP (in this case internal IP address) it will result in a TP that is not working because the Regio Server can not be found. with regard, Johan Taal Fred Beckhusen schreef op 2017-05-23 20:36: > Johan Taal: You have an interesting comment that the FQDN should not be used > on regions. Are you saying that the DNS system at the far end may have > issues resolving it to an IP? Or that the LAN user cannot get to the region > because their DNS server is not resolving, thus occasionally leading to > Thomas Ringates flaky tp problem? > > Tom: > > Your region file looks fine.The Outbound Disallow looks correct, too. > That's a good catch - an exception should be made to the use http:// > 'rule'. > > One minor point: I believe Maxprims = 1 is meaningless without an > economy module. It only reports that number to a osSL function for prims can > check parcel limits. And the viewer stops at 45,000 no matter what you type > in. > > I have the same Linksys, too, and it works great for me. > > Fred > > ___ > Opensim-users mailing list > Opensim-users@opensimulator.org > http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users___ Opensim-users mailing list Opensim-users@opensimulator.org http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users
Re: [Opensim-users] Problems with teleporting in grid mode from simulator, instance to another instance? (Ferd)
Hi to All, I have reported this problem before. This version and the version of OpenSim before does NOT allow Full Qualified Domain Name in the Region.ini file. I think it should be. The problem is gone when you fill in the IP address there. Specially for big company networks (schools, businesses etc.) who use Firewall in combination with split DNS it is wonderful if FQDN is supported in Region.ini. On this moment every request will need the firewall external IP address to be in the Region.ini so the Grid is also reachable from the outside. With a forward rule in the Firewall to server that serviced the specific region it will work from the inside campus network and also from the outside (Internet). I have this configuration working on a campus grid with more the 1200 regions and a number of servers in the internal network. I like to reduce traffic so if this problem can be fixed and FQDN addresses are accepted so the combination of split DNS, Firewall and Region.ini works I will great-full! short time solution is to put in the Region.ini the IP address instead of the FQDN for the ExternalHostName. With regards, Johan Taal tring...@gmail.com schreef op 2017-05-23 18:29: > Fred, > > I read your response with great interest. I also have TP problems on a > frequent basis, and I switched away from Frontier and the actionteck modem > and went back to Brighthouse/Spectrum which uses a true pass-through modem > and I use my WRT1200AC V2 modem running standard Linksys firmware. > > Things run much better, but I still have TP problems myself. Visitors have > no issues at all. > > My regions run on four Fedora linux servers here on my local network. > > I have felt the issue was how things are configured as the TP issue is random > like this original post talks about. > > Here is how my region INI files are all set up is this correct? > > InternalAddress = 0.0.0.0 > InternalPort = 9182 > AllowAlternatePorts = False > MaxPrims = 10 > ExternalHostName = tsim.us.to > RegionType = "Archipelago - Tropical" > > I use a dynamic name service for my domain of tsim.us.to > > I have not tried your debug suggestion yet, as I have no idea what I should > be looking for. > > I see different results when I TP sometimes I arrive with no troubles, > sometimes my viewer simply closes, and I have to relog, and sometimes I wait > for a long time and then end up not TP's. Many times if I first go to LBSA > and then back to one of my regions everything usually works, but not always. > > I am convinced it has something to do with loopback, but the WRT1200AC > supports that function. > > Tom > > -Original Message- From: Fred Beckhusen > Sent: Tuesday, May 23, 2017 10:56 AM > To: opensim-users@opensimulator.org > Subject: [Opensim-users] Problems with teleporting in grid mode from > simulator, instance to another instance? (Ferd) > >> 1. Re: Problems with teleporting in grid mode from simulator >> instance to another instance? (Chris) > It appears to me that your LAN dest region did not handshake properly, > somewhere at the Agent creation process, and the CAPS seed process found > the destination socket was not available. > > I wonder how reliable it is in general. Have you been able to bulk > upload a couple dozen textures reliably, or does it crash out partway > through? That's a sure sign that loopback is failing. You xxx'd your > IP addresses, so I believe you are using a Public WAN IP and therefor a > router is involved and loopback is necessary. There are many reasons > loopback can go wrong or be flaky. Perhaps posting your router > brand/model number to us for future reference will help us, and maybe we > can spot something for you. If this turns out to be the router, please > help us update the page on the Opensimulator.org web site that we use to > track which routers work and which do not. It is at > http://opensimulator.org/wiki/NAT_Loopback_Routers > > Troubleshooting: Check that all IP addresses in your INI files start > with http:// and make sure none of the regions have http:// in them. > > Go to the destination region and type into the console "debug http all > 5". This will print out more details of the handshake that you now > cannot see. You can go to level 6, but that's really verbose.The > command "debug http all 0" will turn it off again. > > A good way to find out if it is loopback is to set your Public IP in the > Opensim.INI to be the LAN IP of the server. You will also need to set > your grid parameters to point to it in the viewer to be able to log in. > When all Private LAN IP's are used, your router will not be involved in > anything at the TCP/IP level and all traffic will be > machine-to-machine. This applies to any IP's in the range of > 172.16.*.*, 192.168.*.* or 10.*.*.*. The Ethernet switch is still > involved, though it is unlikely to be the problem as it works with a > totally different protocol that carries the TCP/IP
Re: [Opensim-users] New opensim hosting, at bargain prices
Local accounts at http://www.simvalley.nl get a FREE sim. As free as opensim is... John Marisa Giancarla schreef op 2016-04-19 00:20: Hello! Looking to rent a Opensim region? We have a great deal - for the first month trial you pay just $15 (for basic service and host setup) and $20/month thereafter. If you need more horsepower we also offer expanded hosting. All our servers use SSD drives for speed and reliability. Just take a look at https://OpensimHosting.org [1] and see what we offer! A great deal from a trusted source... Links: -- [1] https://opensimhosting.org ___ Opensim-users mailing list Opensim-users@opensimulator.org http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users ___ Opensim-users mailing list Opensim-users@opensimulator.org http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users
[Opensim-users] default LAND OPTIONS with EDIT TERRAIN OFF...
taalj schreef op 2015-08-23 11:03: Et All, When I setup a few new sims in ABOUT LAND the option EDIT TERRAIN and CREATE OBJECTS: ALL RESIDENTS are always checked / enabled. Is there a way to set those DEFAULT to OFF? Tihs is specially handy when you generate a lot of new sims. With regards, Johan Taal ___ Opensim-users mailing list Opensim-users@opensimulator.org http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users
