| View previous topic :: View next topic |
| Author |
Message |
teleri
Joined: 28 Jan 2005
Posts: 21
|
 Posted: Wed Feb 23, 2005 10:18 Post subject: |
 |
|
ok I have all that working now I find that the Waypoint and portal have been removed from the older SEND format is there a reason? The waypoint is a very useful thing..
Cheers,
teleri |
|
| Back to top |
|
 |
JeroenB
Joined: 31 Dec 2004
Posts: 228
Location: Netherlands
|
| Posted: Wed Feb 23, 2005 10:27 Post subject: |
|
|
What do you mean exactly? It is easily possible to portal to a waypoint, as that must be given as optional parameter to the ActivePortal function in you own script.
The older SEND format is not supported anymore in this new Vaultster plugin. You must use VAULTSTER to access this new functionality. |
|
| Back to top |
|
|
teleri
Joined: 28 Jan 2005
Posts: 21
|
| Posted: Wed Feb 23, 2005 10:31 Post subject: |
|
|
from portal_nwnx_inc
// Name : Portal include file
// Purpose : Misc code for portalling between servers with NWNX Vaultster
// Authors : Ingmar Stieger
// Modified : December 14, 2003
| Code: | | PortalPlayerNWNX(object oPlayer, object oPortal, string sServer, string sWaypoint) |
or is this a wrapper someone wrote? |
|
| Back to top |
|
|
JeroenB
Joined: 31 Dec 2004
Posts: 228
Location: Netherlands
|
| Posted: Wed Feb 23, 2005 10:34 Post subject: |
|
|
| Yes, that as an older wrapper function around the portalling. You can still use that function though, only thing is that you should call the new PortalPC and PortalStatus functions instead of calling SEND functionality. If you can send me the complete body of the function I can look for the parts that should be changed. |
|
| Back to top |
|
|
teleri
Joined: 28 Jan 2005
Posts: 21
|
| Posted: Wed Feb 23, 2005 10:34 Post subject: |
|
|
| JeroenB wrote: | | Yes, that as an older wrapper function around the portalling. You can still use that function though, only thing is that you should call the new PortalPC and PortalStatus functions instead of calling SEND functionality. If you can send me the complete body of the function I can look for the parts that should be changed. |
What is the best way to send it to you? |
|
| Back to top |
|
|
JeroenB
Joined: 31 Dec 2004
Posts: 228
Location: Netherlands
|
| Posted: Wed Feb 23, 2005 10:36 Post subject: |
|
|
| You can send me a PM. |
|
| Back to top |
|
|
WPCWolfe
Joined: 06 Feb 2005
Posts: 7
|
| Posted: Sun Feb 27, 2005 19:31 Post subject: |
|
|
Hello again,
I have tried to work vauslter but to no avail. I made 2 small modules to just get started and test. But I cant port between the 2 at all. The logs say that the odbc, profiler, and vaulster are loaded. The vaulster log says
NWNX2 Vaultster version 1.4.4 for Windows.
Copyright 2004 (C) Jeroen Broekhuizen
o Using WinSock 2.2.
o Loading in 2 known servers.
o Loaded: 192.168.1.103:5123
o Loaded: 192.168.1.100:5125
o Server started on port 5123.
The profiler says
Current statistics
-----------------------------------------------------------------------------------------------
aps_onload 0 msec 1 calls | portalpc 0 msec 7 calls *|
x2_mod_def_aqu 3 msec 239 calls | x2_mod_def_equ 3 msec 12 calls |
-----------------------------------------------------------------------------------------------
Elapsed time : 10234 msec
Runtime delta : 0 msec
Total cumulative runtime : 6 msec
Total number of scriptcalls : 259
so I know the portal is calling portalpc but nothing happens. So everything functions except my scripting. So here is my scripting
portalpc
#include "vaultster_inc"
void main ()
{
object oPC = GetEnteringObject();
int ret = PortalPC (oPC, "192.168.1.100:5125");
if (ret == VAULTSTER_OK) {
SendMessageToPC (oPC, "Portalling...");
DelayCommand (1.0f, ExecuteScript ("CheckStatus", oPC));
}
else
SendMessageToPC (oPC, "Failure with portalling.");
checkstatus
#include "vaultster_inc"
void main ()
{
object oPC = OBJECT_SELF;
int status = PortalStatus (oPC);
if (status == VAULTSTER_STATUS_OK)
// file was transferred successfully, so now portal the player
ActivatePortal (oPC, "192.168.1.100:5125", "password", "", TRUE);
else if (status == VAULTSTER_STATUS_BUSY) {
// vaultster is still busy with the transmission
SendMessageToPC (oPC, "Hold on..");
DelayCommand (1.0f, ExecuteScript ("CheckStatus", oPC));
}
else {
// failure during transmission or not able to connect (see log file)
SendMessageToPC (oPC, "Failed to portal the character file.");
}
}
I can upload both modules for somebody to look at if needed. They are small. I would really appriciate any help here. Thanks.
_________________
WolfePackClan
We are hunting you. |
|
| Back to top |
|
|
JeroenB
Joined: 31 Dec 2004
Posts: 228
Location: Netherlands
|
| Posted: Sat Mar 05, 2005 10:41 Post subject: |
|
|
In you code for initializing the portalling you have the following line:
| Quote: | | int ret = PortalPC (oPC, "192.168.1.100:5125"); |
This is almost correct except the port number. The PortalPC function only accepts an IP address without the port number at the end, as the Vaultster port is already in the ini file. So, remove that part so that it reads:
| Code: | | int ret = PortalPC (oPC, "192.168.1.100"); |
Also I see in the log file that you have set up Vaultster to use port 5123 and also a NWN server on that same port. I recommend you to keep using port 5100 (the default port) as that will not interfere with existing servers (also remove the ports from the known servers listed in the ini file):
| Code: | Server1 = 192.168.1.103
Server2 = 192.168.1.100 |
Hope this help you a bit. |
|
| Back to top |
|
|
twinj
Joined: 11 Feb 2005
Posts: 16
|
| Posted: Mon Mar 07, 2005 17:34 Post subject: |
|
|
WPCWolfe,
I had a similar setup to you and it works to Portal and connect to the Server. Although there is a limitation in Vaultser, at the moment, that will make your bic file download to the same vault if you use the same IP .. ;(
The port which is chosen in the vaulster.ini file is teh port it will use and also try to connect to. So it will therefore connect to itself once you have told it to connect to an IP, which was the same machine.
It will work across different machines with a different IP Address.
I used the same machine for test purposes. I had two NWServers running and two NWNX's running with the plugin setup on different ports. But not being able to specify Server and Client ports is the problem. They are essentailly bot the same ... This aslo means that all servers have to use the same port which is ok.... but maybe not the best option for security. ??
Follow the advice above in the IP connection code for VAULTSER from Jeroen. It WILL connect and work.. and it will also take you to your other server... but you will be booted because you have an invalid character.
Anyway... I hope that'll help your future probs before you stressssssss  |
|
| Back to top |
|
|
twinj
Joined: 11 Feb 2005
Posts: 16
|
| Posted: Mon Mar 07, 2005 18:13 Post subject: |
|
|
This could help you Its similar to the code Ill be using on my servers. This will be handy for many others too. It is generic one use code for connection. A waypoint is used to setup the required data.
| Code: |
/////////////////////////////////////////////////
// Name Generic Server Portal
// FileName _sp_onclick_gen
// Copyright (c) 2001 Bioware Corp.
////////////////////////////////////////////////
/*
Use this script for portalling a character file and player to anotehr server.
Script needs data from a placed waypoint to work.
*/
////////////////////////////////////////////////
// Created By: twinj
////////////////////////////////////////////////
#include "vaultster_inc"
/*
All of the constants below are designed for a data waypoint of the set tag below
"WP_SP_WAYPOINT_"
The strings/variables need to be set on the waypoint. They are "IP_server_to_goto",
"IP_server_to_stream_to", "PASS_to_connect_to_IP", "WP_tag_to_goto".
ATM youll need to create your own waypoint in the pallette with these variables above.
Once created it is as easy as pie to place and add your connection data. Each
serevr could also be prefabricated. :)
*/
// IP address of the other server, can be with port specified otherwise
// it defaults to 5121 in the activate portal command
const string _SP_IP_SERVER_TO_GOTO = "IP_server_to_goto";
// This is the IP teh VAULSTER will connect to AT teh moment it can only
// be a plain address and no port.
const string _SP_IP_SERVER_TO_STREAM_TO = "IP_server_to_stream_to";
// Pass word needed to connect to teh other server
const string _SP_PASS_TO_CONNECT_TO_IP = "PASS_to_connect_to_IP";
//Waypoint the other server will send you to after you reached the starting location
const string _SP_WP_TAG_TO_GOTO = "WP_tag_to_goto";
//Tag of the data waypoint used to hold all above connection data
const string _SP_WAYPOINT = "WP_SP_WAYPOINT_";
//This sets wether or not to use the GUI for accepting login
//Seemless/TRUE means no GUI
const int _SP_SEEMLESS_SERVER_ENTRY = TRUE;
//This is set so you know when a new PC as entered via a portal and can be used
// handle any needs on the Module OnEnter Event or area OnEnter event. Variables travel
//Across the protal.
const string _SP_JUST_PORTALLED = "SP_just_portalled";
/////////*** CheckPortalStatusAndActivate start ///////////////////////////////////////
void CheckPortalStatusAndActivate(object oPC,string sIP="",string sPass="", string sWayPoint="")
{
int iStatus = PortalStatus(oPC);
if ( iStatus == VAULTSTER_STATUS_OK )
{
ActivatePortal(oPC,sIP,sPass,sWayPoint,_SP_SEEMLESS_SERVER_ENTRY);
}
else if ( iStatus == VAULTSTER_STATUS_BUSY)
{
// vaultster is still busy with the transmission
SendMessageToPC (oPC, "Hold on..");
DelayCommand(1.0f,CheckPortalStatusAndActivate(oPC,sIP,sPass,sWayPoint));
}
else {
// failure during transmission or not able to connect (see log file)
SendMessageToPC (oPC, "Failed to portal the character file. Sending you back.");
}
}
////////*** CheckPortalStatusAndActivate end
// This code is designed to work for an area transition trigger.
void main()
{
object oClickerPC = GetClickingObject();
object oDATA_WayPoint = GetNearestObjectByTag(_SP_WAYPOINT,OBJECT_SELF);
string sSP_WayPoint_Goto = GetLocalString(oDATA_WayPoint,_SP_WP_TAG_TO_GOTO);
string sSP_IP_Con = GetLocalString(oDATA_WayPoint,_SP_IP_SERVER_TO_GOTO);
string sSP_PASS_Con = GetLocalString(oDATA_WayPoint,_SP_PASS_TO_CONNECT_TO_IP);
string sSP_IP_Base = GetLocalString(oDATA_WayPoint,_SP_IP_SERVER_TO_STREAM_TO);
SetLocalInt(oClickerPC,_SP_JUST_PORTALLED,TRUE);
int iPortalCheckStatus = PortalPC(oClickerPC,sSP_IP_Base);
if ( iPortalCheckStatus == VAULTSTER_OK )
{
SendMessageToPC (oClickerPC,"Portalling...");
DelayCommand (1.0f,CheckPortalStatusAndActivate(oClickerPC,sSP_IP_Con,sSP_PASS_Con,sSP_WayPoint_Goto));
}
else {
SendMessageToPC(oClickerPC,"Failure with portalling.. Sending you back");
}
}
///////END MAIN |
Ill adjust if it dont work ..... I have already tested it and its nice. I may have reiterated it here incorreclty... |
|
| Back to top |
|
|
Crono Natsuga
Joined: 15 Mar 2005
Posts: 7
|
| Posted: Sat Mar 19, 2005 21:11 Post subject: |
|
|
hi!
i have 2 nwn servers, over 500km, whose servervault is connected by Internet with a VPN system. This system is so ... unstable !
lucky, i'll found your VaulSter plug-in (I used already nwnx2 to profiler it  ) and i implemente it 
well, it functions very quite safe we are obliged to use the same port for the 2 server ... unfortunately, one use the 5121 port, and other the 5122 
It is possible to use different port with two server use VaulSter ? how ? where i specify the port ?
another thing: 2 server use a DNS (like www.dyndns.org ) because a provider deconnecte reconnecte all 24hours and the IP change  (it's a dynamic IP, not a static IP)
when i specify a DNS in nwnx.ini (exemple: "my.dns.org"), no a IP (exemple: 184.250.12.35), the other server response is: * Invalid client tries to connect: 82.124.x.x 
I am obliged of specify a IP in nwnx.ini has each change and thus restart nwnx.exe after each deconnect/change of IP (every 24 hours!)
how to use VaulSter with a DNS ?
is it possible of not specifier of serverDNS ( server1 = xxx.xxx.xxx.xxx in nwnx.ini) ? only a key and password?
Thank's for your response
I'll love your nwnx2
it's a very good so much program
(sorry for my english) |
|
| Back to top |
|
|
JeroenB
Joined: 31 Dec 2004
Posts: 228
Location: Netherlands
|
| Posted: Sat Mar 19, 2005 23:57 Post subject: |
|
|
The port of NWN server doesn't matter for NWNX Vaultster. In the configuration you can setup a port for vaultster, which by default is 5100.
Using a DNS is name works the same way as an IP address. Just fill in your DNS name in the configuration file and it should work. The vaultster software will lookup the current IP address for you.
I hope this helps, otherwise let me know Good luck! |
|
| Back to top |
|
|
Crono Natsuga
Joined: 15 Mar 2005
Posts: 7
|
| Posted: Sun Mar 20, 2005 13:50 Post subject: |
|
|
ok thank's
but it don't works with DNS, see an exemple of my nwnx.ini :
| Code: | [VAULTSTER]
port=5100
path=E:\NeverwinterNights\servervault
startserver=1
key=mykey
password=mypasswd
count=1
server1=212.177.15.102 |
work fine
| nwnx_vaultsert.txt on other client wrote: | o Character: D:\NWN\servervault2 - CronoNatsuga - aral
o Receiving file: D:\NWN\servervault2\CronoNatsuga\aral.bic
o Returning: 0 |
and this:
| Code: | [VAULTSTER]
port=5100
path=E:\NeverwinterNights\servervault
startserver=1
key=mykey
password=mypasswd
count=1
server1=mydns.example.com |
don't work (i see: * Invalid client tries to connect: 212.177.15.102 in nwnx_vaultster.txt log)
whereas mydns.example.com as same 212.177.15.102 (if i "ping" it, it's the same) but dont work if i specifie the DNS
why ?
it is as if it did not resolve the DNS
________
For the port 5100, yes ok, I understood after several test that it acted 
but, for the port of nwserver.exe ?
if one is 5121 and other server is 5122, it's don't work
how to work with one nwserver use 5121 and the other nwserver use 5122 ?
good job
[Editing: replacement DNS with "mydns.example.com" !]
Last edited by Crono Natsuga on Mon Mar 21, 2005 13:12; edited 1 time in total |
|
| Back to top |
|
|
Liberty Valance
Joined: 06 Jan 2005
Posts: 21
Location: A Persistent World West2
|
| Posted: Sun Mar 20, 2005 21:10 Post subject: |
|
|
erm, when i ping mydns.servegame.com, i get 63.215.241.236 - could this be part of your problem? i note that when you connected to the IP address directly, you connected to the 212.177.15.102 IP, but is it possible that was a few days ago, and the server's IP has since changed, and it just took a while to update the DNS data for mydns.servegame.com?
_________________
A Persistent World West2 | APWW2 Forums
Wirehead Studios |
|
| Back to top |
|
|
Crono Natsuga
Joined: 15 Mar 2005
Posts: 7
|
| Posted: Mon Mar 21, 2005 1:40 Post subject: |
|
|
lol sorry !
the DNS and the IP that i said is a EXAMPLE ^^
(my dns is different of this example but the problem is same )
and, my problem is precisely that my IP and the other IP of second server connected CHANGE every 24hours (due of provider)
for this reason we use each one a dynamic DNS with www.dyndns.org
but, if we specify this DNS (see exemple ^^) VaulSter don't work
Thank you as same |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
