We will be making a new server release once we get Naali 0.1 out. The features in the next server release aren't yet finalized.
2010/1/8 Mark Malewski <[email protected]> > One a sidenote, are there any plans to release a RealXtend 0.6 release > (with the latest updated OpenSim 0.7 stable + ModRex, and with all the > latest OpenSim bug fixes, and with Mega Region support, and with a working > multi-region support behind NAT?) > > I believe RealXtend 0.5 is already 6+ months old, it really would be great > to just see a RealXtend 0.6 release with the latest OpenSim bug fixes, and > working Mega region support and working multi-region support behind NAT. > > Multi-region support behind NAT would be one of the more important > features, but a working Grid mode would be nice as well. ;-) > > > > On Fri, Jan 8, 2010 at 8:26 AM, Mark Malewski <[email protected]>wrote: > >> Ates, >> >> > Well my region external hostnames are already set to my lan ip which >> > is 192.168.0.2 atm. Internal ip should be set to 0.0.0.0 by default am >> > I right? though I have tried lan ip for it as well and it didnt >> > work... >> >> Are you using Windows or Linux on your local machine? >> >> If you are using windows, and you do a "ping" for that host name, what IP >> address are you getting as a response? (an internal local LAN IP address, >> or an external WAN IP address?) >> >> If you are switching back and forth (using the same machine) between LAN >> and WAN, there is a possibility that the WAN IP address may be stored in >> your local DNS cache. >> >> Try doing an "ipconfig /flushdns" command (from the command line), and see >> if flushing your local DNS cache entries will help fix the issue. >> >> There may be a problem with you switching back and forth between LAN and >> WAN (and the incorrect DNS entry may be stored in your DNS cache). >> >> By flushing your local DNS cache, it may fix the issue. Give it a try, >> and let me know. (Also try a simple ping on that host name and see what IP >> address you are getting as a resolved response for that host name entry). >> The problem could be with your local DNS cache. Try doing a ping on that >> host name, just to see whether you are getting an internal IP or external >> (WAN) IP address resolved. You may need to flush your DNS cache if you are >> switching back and forth between LAN and WAN on the same machine (a >> laptop?). >> >> Thanks, >> >> Mark >> >> >> On Fri, Jan 8, 2010 at 3:58 AM, akaydin <[email protected]> wrote: >> >>> Well my region external hostnames are already set to my lan ip which >>> is 192.168.0.2 atm. Internal ip should be set to 0.0.0.0 by default am >>> I right? though I have tried lan ip for it as well and it didnt >>> work... >>> >>> The problem still persists though :(... >>> >>> On 8 Ocak, 12:44, Jeroen van Veen <[email protected]> wrote: >>> > handshake phase hangs often occur when you have the external hostname >>> of your >>> > regions set to your wan ip, and you try to connect to opensim from the >>> lan. An >>> > easy fix is to set your lan-ip for external hostname, or on linux you >>> could try >>> > to use the iptables script on the wiki. >>> > >>> > Jeroen >>> > >>> > Op vrijdag 08 januari 2010 10:36:05 schreef akaydin: >>> > >>> > > Cheeeersss!!!!! >>> > >>> > > Mikko you are the best :D... it works! >>> > >>> > > I registered a hostname from dyndns for my wan ip and added my <local >>> > > server ip - dns hostname> reference to my hosts file as you said. >>> > >>> > > Now I can pass authentication on client screen. However this time my >>> > > connection drops during handshaking phase... I get an "Unable to >>> > > connect. Login message never received by the server" message... >>> > >>> > > It may be a time out issue as my adsl connection on both server and >>> > > client is slow. Or there is a problem with my region xml >>> > > configuration. I ll check it out. >>> > >>> > > Any other reasons which may cause this message? >>> > >>> > > And Mikko thanks a lot... I was about to lose hope :) >>> > >>> > > Best, >>> > >>> > > Ates >>> > >>> > > On 8 Ocak, 09:48, Mikko Pallari <[email protected]> wrote: >>> > > > That message is inside ModreX AuthenticationService class. >>> > >>> > > > It occurs when something goes wrong when making a XMLRPC-request to >>> > > > remote server. Most likely reason for failed XMLRPC-request is that >>> the >>> > > > network location can't be accessed from the simulator. And in this >>> case >>> > > > the remote location is your authentication server address. >>> > >>> > > > BTW, do you have both simulator and authentication server running >>> on same >>> > > > machine? And the error occurs when you try to log in from external >>> > > > computer to server behind NAT? In this case the simulator tries to >>> > > > connect to your WAN IP and can't connect to it. This is usually >>> because >>> > > > the routers option "NAT loopback" isn't enabled or isn't supported. >>> > >>> > > > If your router doesn't support the NAT loopback, then one option to >>> > > > enable it would be to create DNS name for your servers WAN address >>> and >>> > > > add that DNS entry to your hosts file with local IP address. >>> > >>> > > > Cheers, >>> > > > Mikko >>> > >>> > > > On Fri, Jan 8, 2010 at 9:29 AM, akaydin <[email protected]> >>> wrote: >>> > > > > Thanks a lot Mikko... >>> > >>> > > > > I ll check it out today(when I solve my compilation problems :D) >>> > >>> > > > > I had the server and the client downloaded from >>> > > > >http://www.realxtend.org/page.php?pg=downloads >>> > >>> > > > > And one more question... I know I asked a lot already ;) >>> > >>> > > > > Do you know what may generate a "18:41:49 - [AUTHENTICATION >>> SERVICE]: >>> > > > > Failed creating XmlRpcRequest" message? Having tried a dozen of >>> > > > > methods to fix it I still have doubts about the location of the >>> > > > > problem. I cant decide whether if it is OpenSim server which >>> causes >>> > > > > this error or it is Authentication server. Because that message >>> states >>> > > > > that it is OpenSim server which fails at creating an >>> XmlRpcRequest >>> > > > > message am I right? What may cause this message? Is it >>> Authentication >>> > > > > server returning an invalid response or an internal failure at >>> OpenSim >>> > > > > Server(auth server works correct for instance)... I have searched >>> for >>> > > > > the text "Failed Creating XmlRpcRequest" or its variations in >>> opensim >>> > > > > code but couldnt find a reference :(. >>> > >>> > > > > Cheers, >>> > >>> > > > > Ates >>> > >>> > > > > On 8 Ocak, 08:43, Mikko Pallari <[email protected]> >>> wrote: >>> > > > > > Hi, >>> > >>> > > > > > On Thu, Jan 7, 2010 at 7:14 PM, akaydin <[email protected]> >>> wrote: >>> > > > > > > Thanks again Ryan and Jonne >>> > >>> > > > > > > I have indeed found a mail which explains my problem: >>> > >>> > > > > > > >>> http://www.mail-archive.com/[email protected]/msg00979.html >>> > >>> > > > > > > The problem is the same. I guess Mikko Pallari has added a >>> switch >>> > > > > > > somewhere to check server ip upon an authentication request >>> > > > > > > (server_check_ip). >>> > >>> > > > > > This configuration option is in modrex.ini in >>> > > > > > directory bin/addon-modules/ModreX/config. You can read more >>> about >>> > > > > > ModreX configuration options athttp:// >>> > >>> > > > > wiki.realxtend.org/index.php/Configuring_ModreX >>> > >>> > > > > > However you shouldn't use that option in production >>> environments, >>> > > > > > because >>> > >>> > > > > it >>> > >>> > > > > > disables the check which confirms that the client logging in is >>> who >>> > > > > > it claims to be. >>> > >>> > > > > > Cheers, >>> > > > > > Mikko >>> > >>> > > > > > > The only relevant switch I have found though is in >>> > > > > > > AuthenticationSettings.xml which is: >>> > >>> > > > > > > <check_server_ip>True</check_server_ip> >>> > >>> > > > > > > I had already tried setting this to false but the problem >>> still >>> > > > > > > persists. >>> > >>> > > > > > > Also as Jonne suggested I have tried setting my WAN IP for my >>> three >>> > > > > > > servers in xml configuration files. My viewer cant even >>> connect to >>> > > > > > > the opensim server that way... I tried all combinations of >>> > > > > > > these(like setting opensim to internal ip and authentication >>> to >>> > > > > > > external, vice versa etc etc)... still I couldnt solve it. >>> > >>> > > > > > > Do you know how I can contact Mikko Pallari? Perhaps an >>> e-mail >>> > > > > > > adress or something like that? He seems to know a lot about >>> this >>> > > > > > > issue. >>> > >>> > > > > > > Also I could not find the source code of the application at: >>> > >>> > > > > > > http://sourceforge.net/projects/realxtendserver/ >>> > >>> > > > > > > Only binaries are there... >>> > >>> > > > > > > I have already checked-out source code of the latest version >>> of >>> > > > > > > OpenSim and Modrex Modules however these dont include the >>> source >>> > > > > > > code for the authentication server... >>> > >>> > > > > > > I cannot find the source code of the authentication server >>> anywhere >>> > > > > > > at the moment. The binary exists(authenticationserver-0.5) >>> but no >>> > > > > > > source code. And I still think the problem occurs due to a >>> bug in >>> > > > > > > this server. >>> > >>> > > > > > > Is there anyone who actually managed to deploy a server which >>> can >>> > > > > > > be connected through WAN? Or any tutorials around? LAN and >>> Local >>> > > > > > > connection is easily done... but there should be someone who >>> had >>> > > > > > > connected through WAN via DSL connection. >>> > >>> > > > > > > And finally I get the following error when I try to connect >>> with >>> > > > > > > login_name@<wan ip> perhaps it helps to debug it further: >>> > >>> > > > > > > OpenSim server console: >>> > >>> > > > > > > 18:41:48 - [REXLOGIN]: XMLRPC Client is realXtend >>> 1.20.13.91224, >>> > > > > > > start location >>> > > > > > > is last >>> > > > > > > 18:41:48 - [AUTHENTICATIONSERVICE]: SimAuthenticationAccount >>> with >>> > > > > > > account >>> > > > > > > 18:41:49 - [AUTHENTICATION SERVICE]: Failed creating >>> XmlRpcRequest >>> > > > > > > 18:41:49 - [AUTHENTICATIONSERVICE]: SimAuthenticationAccount: >>> > > > > > > Response is null. >>> > > > > > > 18:41:49 - [LOGIN END]: XMLRPC User testuser@<WAN IP>:10001 >>> ( >>> > > > > > > 444dc39e712276580b40647a9f1807d60b481a4a) failed >>> authentication >>> > >>> > > > > > > Authentication server console: >>> > >>> > > > > > > 18:37:42 - Authentication# : >>> > > > > > > 18:41:44 - [LOGIN]: Authenticating Test User >>> > > > > > > 18:41:44 - ------------------------------------------- >>> > > > > > > 18:41:44 - CLIENT LOGGIN IN TO SIM: testuser@<WAN IP>:9000 >>> > > > > > > 18:41:44 - ------------------------------------------- >>> > >>> > > > > > > And the error message I see on my viewer's screen: >>> > >>> > > > > > > Login Failed: >>> > >>> > > > > > > Could not authenticate your avatar. Please check your user >>> name and >>> > > > > > > password, and check the grid if problem persists. >>> > >>> > > > > > > <WAN IP> I've mentioned in above error outputs is actually my >>> WAN >>> > > > > > > IP I wrote it like that due to security issues :D. >>> > >>> > > > > > > Anyway... >>> > >>> > > > > > > I have tried hacking client code a bit especially >>> llstartup.cpp and >>> > > > > > > lluserauth.cpp in case I can generate an XMLRPC login message >>> where >>> > > > > > > authentication ip is set same as the internal ip of the >>> server. But >>> > > > > > > it didnt work either :(:(:(... Perhaps there is some other >>> way of >>> > > > > > > doing it from client code with a hack. Something I havent >>> realized >>> > > > > > > yet. >>> > >>> > > > > > > I again thank you all for your care in this subject. >>> > >>> > > > > > > Best, >>> > >>> > > > > > > Ateş Akaydın >>> > >>> > > > > > > On 7 Ocak, 09:35, Ryan McDougall <[email protected]> wrote: >>> > > > > > > > The source can be found here: >>> > >>> > > > > > >http://sourceforge.net/projects/realxtendserver/ >>> > >>> > > > > > > > I seem to recall a discussion about this issue before. >>> Perhaps >>> > > > > > > > you >>> > >>> > > > > can >>> > >>> > > > > > > > look at the mailing list archives for an answer. >>> Unfortunately, >>> > > > > > > > 0.5 isn't being actively worked on any more, as we are >>> focusing >>> > > > > > > > on Naali and Taiga: >>> > >>> > > > > >>> http://wiki.realxtend.org/index.php/Main_Page#Developer_Preview_Releases >>> > >>> > > > > > > > Cheers, >>> > >>> > > > > > > > On Wed, Jan 6, 2010 at 6:28 PM, akaydin < >>> [email protected]> >>> > >>> > > > > wrote: >>> > > > > > > > > Ryan thanks a lot for your answer. >>> > >>> > > > > > > > > Unfortunately [email protected] does not work from >>> outside >>> > >>> > > > > network. >>> > >>> > > > > > > > > Nothing happens if I use internal ip here(192.168.0.2) >>> however >>> > > > > > > > > if I use WAN IP then I can connect to the authentication >>> > > > > > > > > server(from >>> > >>> > > > > what I >>> > >>> > > > > > > > > see on authentication server console) but login operation >>> > > > > > > > > fails. >>> > >>> > > > > And >>> > >>> > > > > > > > > if I can connect to the authentication server(althought >>> login >>> > > > > > > > > operation fails) then I believe that should mean that the >>> WAN >>> > > > > > > > > ip resolves correctly and redirected through my NAT. >>> > >>> > > > > > > > > I may be wrong but it seems like" testuser@<wan_ip>" is >>> also >>> > > > > > > > > sent >>> > >>> > > > > as a >>> > >>> > > > > > > > > complete string in some part of an xml message to the >>> > >>> > > > > authentication >>> > >>> > > > > > > > > server. I believe only the left part before "@" sign - >>> that is >>> > > > > > > > > "testuser" - and user password should be >>> > >>> > ... >>> > >>> > tamamını oku » >>> >>> -- >>> http://groups.google.com/group/realxtend >>> http://www.realxtend.org >>> >> >> > > -- > http://groups.google.com/group/realxtend > http://www.realxtend.org >
-- http://groups.google.com/group/realxtend http://www.realxtend.org
