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)<div><br></div>
<div>Harri</div><div><br></div><div><br><div class="gmail_quote">On Sat, Nov 27, 2010 at 9:45 PM, iSkye Silverweb <span dir="ltr"><<a href="mailto:iskye.silverweb@gmail.com">iskye.silverweb@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">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.<div>
<div></div><div class="h5"><br>
<br><div class="gmail_quote">On Sat, Nov 27, 2010 at 11:39 AM, iSkye Silverweb <span dir="ltr"><<a href="mailto:iskye.silverweb@gmail.com" target="_blank">iskye.silverweb@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
We're still not getting a breakthrough on getting the inside-network login working while also having external computers able to get in. <br><br>Our current setup is this:<br>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.<br>
<br>On router (Sagem F@ST 2504 firmware version 2.8Sky): <br>Port 9000 for TCP/UDP and ports 9001-9003 for UDP<br><br>Windows firewall disabled on both computers inside the network<br><br>regions.ini file: <br>external IP is <a href="http://our-grid.dyndns-server.com" target="_blank">our-grid.dyndns-server.com</a> (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)<br>internal IP is 0.0.0.0<br><br>hosts file on the client the UK guy is trying to login from:<br>192.168.0.9 <a href="http://our-grid.dyndns-server.com" target="_blank">our-grid.dyndns-server.com</a><br>
<br>uPnP and DMZ are both off, disabled (we've tried both ways)<br><br>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. <br>
<br>Suggestions, anyone? Your help is much appreciated, thanks in advance.<div><div></div><div><br><br><br><div class="gmail_quote">On Fri, Nov 26, 2010 at 3:37 PM, iSkye Silverweb <span dir="ltr"><<a href="mailto:iskye.silverweb@gmail.com" target="_blank">iskye.silverweb@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">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!<br>
<br>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:<br>
<br><i>This method was used and successfully tested using <a href="http://www.dyndns.com" target="_blank">www.dyndns.com</a> (creates a virtual domain for your pc/ip, like <a href="http://yourcomputer.ath.cx" target="_blank">yourcomputer.ath.cx</a>) 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:<br>
<br>Method:<br><br> * 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="<a href="http://yourcomputer.ath.cx" target="_blank">yourcomputer.ath.cx</a>". Leave internal_ip_address "0.0.0.0" and port "9000".<br>
* Set the client (SecondLife Viewer) -loginuri to "<a href="http://yourcomputer.ath.cx:8002" target="_blank">yourcomputer.ath.cx:8002</a>" (the port used was 8002, yours can be different if you configured it that way) - i didnt used the -loginserver flag also.<br>
* 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.<br>
* 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 <a href="http://yourcomputer.ath.cx" target="_blank">yourcomputer.ath.cx</a>. Of course, xxx.xxx.xxx.xxx is your opensim server internal LAN IP. <br>
<br><a href="http://yourcomputer.ath.cx" target="_blank">yourcomputer.ath.cx</a> is now available for everyone to connect and you may login with the client!</i><br><br>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...<div>
<div></div><div><br>
<br><br><div class="gmail_quote">On Wed, Nov 24, 2010 at 3:18 PM, Diva Canto <span dir="ltr"><<a href="mailto:diva@metaverseink.com" target="_blank">diva@metaverseink.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<div text="#000000" bgcolor="#ffffff">
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.<div><div></div><div><br>
<br>
On 11/24/2010 11:13 AM, iSkye Silverweb wrote:
</div></div><blockquote type="cite"><div><div></div><div>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. <br>
<br>
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. <br>
<br>
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.<br>
<br>
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: <a href="https://github.com/diva/d2/wiki/Installation" target="_blank">https://github.com/diva/d2/wiki/Installation</a>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
Can anyone help, please?<br>
<br>
<br>
<br>
<br>
</div></div><pre><fieldset></fieldset>
_______________________________________________
Opensim-users mailing list
<a href="mailto:Opensim-users@lists.berlios.de" target="_blank">Opensim-users@lists.berlios.de</a>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-users" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-users</a>
</pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
Opensim-users mailing list<br>
<a href="mailto:Opensim-users@lists.berlios.de" target="_blank">Opensim-users@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-users" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-users</a><br>
<br></blockquote></div><br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>
</div></div><br>_______________________________________________<br>
Opensim-users mailing list<br>
<a href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-users" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-users</a><br>
<br></blockquote></div><br></div>