The external users are fine, we are able to get into the grid without trouble; it's the guy inside the network who can't get into the grid, he gets the handshake problem, even though we thought he had the loopback problem fixed with the hosts file - even with that, he still cannot get into the grid.
On Sun, Nov 28, 2010 at 2:30 AM, Olli Aro <[email protected]> wrote: > Well my experience so far with opensim is that you cannot use domain names > as values for the external_ip property. But have not tested it with 0.7.x > yet. > > > > If you do not have a static IP address you could still try to following: > > > > 1) In the same network find out your current public IP address with > some website like: http://whatismyipaddress.com/ > > 2) Try that IP as the external IP > > 3) Ask your external users to connect using that IP > > > > You might as well try it :) > > > > Olli > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *iSkye Silverweb > *Sent:* 27 November 2010 23:06 > > *To:* [email protected] > *Subject:* Re: [Opensim-users] Diva Distro - Hitting Walls > > > > I'm not clear on why you said that, Olli. We've gone through steps as > recommended on github, and here on this forum, we researched and were told > we needed to use that in order to address problem of having dynamic IP > addresses. Can you explain, please? > > On Sat, Nov 27, 2010 at 4:58 PM, Olli Aro <[email protected]> wrote: > > Don't think it is possible to use dyndns with opensim. > > > > The problem is that external ip still does not support domain names. > > > > So if you want to make the server visible from the Internet you need to put > your Internet ip in as the external ip. > > > > Regards > > > > Olli > > Sent from my iPhone > > > On 27 Nov 2010, at 20:25, iSkye Silverweb <[email protected]> > wrote: > > Yes, we all use the same viewer and the same login url. > > He just went to a different computer (still inside his network) and was > able to get the grid info but still hangs at the handshake. > > When we do the following in the regions.ini file: > > external IP is our-grid.dyndns-server.com and internal IP is 0.0.0.0 > > the computers outside the network are able to get into the grid but the UK > guy's computer hangs on handshake - this is even though he has the hosts > file edited as described previously, on each computer in the network; > > when we set the following in the regions file: > > external IP is 192.168.0.9 > > our UK guy can log in from inside his network, but the 2 outside computers > can't log in. > > On Sat, Nov 27, 2010 at 2:03 PM, Harri Nyman <[email protected]> > wrote: > > One question pops into my mind - are all users connecting to same login > URL? I had similar problems, but it all worked ok when I put same login urls > into every viewer, regardless of the network (intra/internet) > > > > Harri > > > > > > On Sat, Nov 27, 2010 at 9:45 PM, iSkye Silverweb < > [email protected]> wrote: > > An additional note. While our UK guy is able to see the website, when he > opens the viewer and tries to get grid info in the grid manager, it does not > return the information; however when I try it from outside his network, I am > able to get the grid information in the viewer. We all use the Imprudence > viewer. Not sure if this bit of information is helpful. > > > > On Sat, Nov 27, 2010 at 11:39 AM, iSkye Silverweb < > [email protected]> wrote: > > We're still not getting a breakthrough on getting the inside-network login > working while also having external computers able to get in. > > Our current setup is this: > We have a standalone Diva distro 0.7.0 on a Windows XP computer in the UK, > with two other computers inside that network; two external computers outside > the UK. > > On router (Sagem f...@st 2504 firmware version 2.8Sky): > Port 9000 for TCP/UDP and ports 9001-9003 for UDP > > Windows firewall disabled on both computers inside the network > > regions.ini file: > external IP is our-grid.dyndns-server.com (note: when we change the > external IP to the actual internal IP, 192.168.0.9, for the machine running > our grid, our UK guy can log in from inside his network, but the 2 outside > computers can't log in) > internal IP is 0.0.0.0 > > hosts file on the client the UK guy is trying to login from: > 192.168.0.9 our-grid.dyndns-server.com > > uPnP and DMZ are both off, disabled (we've tried both ways) > > All three of us can see the welcome page in the browser. The UK (inside > network) guy, isn't able to log in through the webpage, nor can he get into > the grid. We seem to be missing one small ingredient that will let our UK > guy login from inside his network. > > Suggestions, anyone? Your help is much appreciated, thanks in advance. > > > > On Fri, Nov 26, 2010 at 3:37 PM, iSkye Silverweb < > [email protected]> wrote: > > We're getting closer. We guess! Now, we've got the opposite issue. > External computers can log in; the UK guy can't get in from inside his > network. We did as Diva suggested (9000 only for both TCP & UDP; 9001-9003 > for UDP only - previously all four ports were opened for both UDP & TCP) and > that got us to this point, thank you Diva! > > We're told his router supports NAT loopback (Sagem FAST 2504 from Sky > Broadband). Not sure that's by default? So, we attempted this method, > hoping that would get him able to log in through his viewer from inside the > network: > > *This method was used and successfully tested using www.dyndns.com(creates a > virtual domain for your pc/ip, like > yourcomputer.ath.cx) as loopback for devices on a LAN with three machines > (pentium 2.8ghz running windows xp - internet server , amd opteron running > ubuntu 7.10 64bit - as opensim server - and MacBook with OSX 10.4.11 - as > client), a modem (thomson/alcatel speedtouch 330) and a mini-switch (which > brand no one ever heard of). The connection of these machines is made as > following: Modem -> Win Pc -> Switch -> Mac and Ubuntu. Dyndns is used to > loopback to the Win Pc, and then it forwards the request to the internal LAN > opensim server, which grants everything for the client. As for the client, > if he is inside the private LAN then he is now actually someone on the > internet requesting for access to the opensim server. Thus, if the client is > someone on the internet then he will be treated like that. Tricky ? Further > details ahead: > > Method: > > * Set the simulator listening IP address to your dyndns domain - edit > opensim/bin/Regions/default.xml; and change the external_host_name to > external_host_name="yourcomputer.ath.cx". Leave internal_ip_address > "0.0.0.0" and port "9000". > * Set the client (SecondLife Viewer) -loginuri to " > yourcomputer.ath.cx:8002" (the port used was 8002, yours can be different > if you configured it that way) - i didnt used the -loginserver flag also. > * Port Forward the above ports on the internet server (in this case, > win xp). You do so by creating exceptions in Windows Firewall for the above > mentioned ports, and for both connections: Internet Connection and LAN - > this keeps the ports open for the web requests to travel over the private > network. > * Edit "hosts" file (on windows, this is > C:\Windows\System32\Drivers\etc\hosts and on Unix-type systems, this is > /etc/hosts) entry on your internet server (in this case, win xp box) and add > the following line: xxx.xxx.xxx.xxx yourcomputer.ath.cx. Of course, > xxx.xxx.xxx.xxx is your opensim server internal LAN IP. > > yourcomputer.ath.cx is now available for everyone to connect and you may > login with the client!* > > Now, while he was able to get in, the external computers were locked out > again. He reversed his changes; we're back to external computers being able > to log in, but he can't. Seems we have an either/or situation, but we want > to have our cake and eat it too... > > > > On Wed, Nov 24, 2010 at 3:18 PM, Diva Canto <[email protected]> wrote: > > This sounds like you're hitting exactly that: a firewall. Make sure there > are holes in all the right ports: TCP 9000, and UDP 9000--9003. > > > > On 11/24/2010 11:13 AM, iSkye Silverweb wrote: > > We're a group of 3 people; one in the UK, the other two in the US. The one > in the UK is the one with the system on which we've been trying to get our > Diva distro up and running. > > We have really struggled with getting external access sorted. We haven't > tried hypergate yet - we want the 3 of us to be able to log into the grid > with our viewers first, since we will be building in there, and we want to > set our home to our grid. > > We've tried multiple times, multiple settings, and the closest we got was > to get the registration page on the Web set up and working, and the login > page on the viewer (Imprudence), and the login process started. Our UK guy > was able to log in from within his network; the two of us in the US are not > able to log in from outside. The logs showed that OpenSim saw us logging > in, everything looked great, until we got to the handshake stage; we can't > get past that despite trying numerous different settings in the Regions.ini > file and on the router. Someone in some forum mentioned never seeing > LLUDPSERVER kicking in; we have never seen that either, so if we were > supposed to, that's where our problem seems to lie, but we tried different > fixes, but to no avail. We're incredibly frustrated and demoralised. > > Last night, we decided to start over again on two different computers > (separate times), but now we can't even get the registration page up and the > viewer's grid manager's 'get grid info' can't find our grid address. We > followed the instructions on this page: > https://github.com/diva/d2/wiki/Installation and even tried it with MySQL > Workbench on one of the computers while using the command line on the other > one. Both gave us the same result. NOTE: We did not try to run OpenSim on > both computers simultaneously, and we made sure to port forward correctly > when attempting one or the other computer. > > We even invested in a new router from the ISP with a current firmware > version that supports NAT Loopback, etc. We tried creating a DMZ, not > having one; we tried turning off uPnP and leaving it on; we tried a numeric > IP address for the external address and the FQDN; we tried 0.0.0.0 for > internal IP and using an internal address. Two of us actually worked > through the day and all night yesterday/last night trying to get this > working multiple times. We've seen others successfully getting their grids > up and externally accessible, so we know it's possible, but that apple seems > to be dangling just outside our reach. It's galling for us because two of > us have backgrounds in systems, network, web and database programming > spanning more than a decade each. > > We REALLY could use some help from someone who has done it successfully > (all the way to successful external logins) and maybe wouldn't mind going > thru it with us a bit; a fresh pair of eyes and input from someone who has > succeeded might spot something we've missed or something we've been doing > wrong. > > Can anyone help, please? > > > > > > _______________________________________________ > > Opensim-users mailing list > > [email protected] > > https://lists.berlios.de/mailman/listinfo/opensim-users > > > > > _______________________________________________ > Opensim-users mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/opensim-users > > > > > > > > > _______________________________________________ > Opensim-users mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/opensim-users > > > > > _______________________________________________ > Opensim-users mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/opensim-users > > > > _______________________________________________ > Opensim-users mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/opensim-users > > > _______________________________________________ > Opensim-users mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/opensim-users > > > > _______________________________________________ > Opensim-users mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/opensim-users > >
_______________________________________________ Opensim-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-users
