Page 1 of 1
DMA CLIENT
Posted: Mon Apr 09, 2007 10:17 am
by dspain
my DMA rlogin protocol made a few breakthroughs over the weekend, i successfully connected outbound using DCLIENT.DLL to another wg 3.30 server running DSERVER.DLL and entered the module i sent the param string to connect to.
so we're getting closer, theres still a few bugs but its coming.
im gonna down-port wg3's ICO for wg2 and try and test it using that too.
so when i release it wg3 will talk to wg2 etc...
there will be no majorbbs version of this utility.
Re: DMA CLIENT
Posted: Tue Apr 10, 2007 10:04 am
by ccs
dspain wrote:my DMA rlogin protocol made a few breakthroughs over the weekend, i successfully connected outbound using DCLIENT.DLL to another wg 3.30 server running DSERVER.DLL and entered the module i sent the param string to connect to.
so we're getting closer, theres still a few bugs but its coming.
im gonna down-port wg3's ICO for wg2 and try and test it using that too.
so when i release it wg3 will talk to wg2 etc...
there will be no majorbbs version of this utility.
Can your client connect to a MajorTCP DMA server?
Joe
Re: DMA CLIENT
Posted: Tue Apr 10, 2007 8:08 pm
by dspain
ccs wrote:dspain wrote:my DMA rlogin protocol made a few breakthroughs over the weekend, i successfully connected outbound using DCLIENT.DLL to another wg 3.30 server running DSERVER.DLL and entered the module i sent the param string to connect to.
so we're getting closer, theres still a few bugs but its coming.
im gonna down-port wg3's ICO for wg2 and try and test it using that too.
so when i release it wg3 will talk to wg2 etc...
there will be no majorbbs version of this utility.
Can your client connect to a MajorTCP DMA server?
Joe
wont be no need, you install it on your WG2 set which port to accept incomings ip allowances,etc...
it wont conflict with your current major tcp/ip installation.
Re: DMA CLIENT
Posted: Wed Apr 11, 2007 10:26 am
by ccs
dspain wrote:ccs wrote:dspain wrote:my DMA rlogin protocol made a few breakthroughs over the weekend, i successfully connected outbound using DCLIENT.DLL to another wg 3.30 server running DSERVER.DLL and entered the module i sent the param string to connect to.
so we're getting closer, theres still a few bugs but its coming.
im gonna down-port wg3's ICO for wg2 and try and test it using that too.
so when i release it wg3 will talk to wg2 etc...
there will be no majorbbs version of this utility.
Can your client connect to a MajorTCP DMA server?
Joe
wont be no need, you install it on your WG2 set which port to accept incomings ip allowances,etc...
it wont conflict with your current major tcp/ip installation.
Yea but I want to able to allow other BBS's to connect to my DMA server.
Joe
Posted: Wed Apr 11, 2007 10:59 pm
by Malakai
If Dan is able to pull it off, it would render vircom's dma server obsolete. Good luck
Posted: Wed Apr 11, 2007 11:39 pm
by ccs
Malakai wrote:If Dan is able to pull it off, it would render vircom's dma server obsolete. Good luck
No thats not it.
I just need a client so other BBS's can connect to my DMA server. We just need to pull apart the hand shake that vircom built into its rlogin client. All I think we need to do is sniff the packets and we can see how it works. Then we can tweek the Galcomm rlogin client and it will allow any worldgroup server out there access DMA servers.
Joe
Posted: Thu Apr 12, 2007 12:36 am
by dspain
ccs wrote:Malakai wrote:If Dan is able to pull it off, it would render vircom's dma server obsolete. Good luck
No thats not it.
I just need a client so other BBS's can connect to my DMA server. We just need to pull apart the hand shake that vircom built into its rlogin client. All I think we need to do is sniff the packets and we can see how it works. Then we can tweek the Galcomm rlogin client and it will allow any worldgroup server out there access DMA servers.
Joe
majortcp uses a datastream what needs to be written is a debug module that any connection accepted on port 513/514 sends the param strings.
but as malakai said you would be able to run both majortcp for bbs's still using mtcpip and mine for bbs's using wg3nt
Posted: Thu Apr 12, 2007 12:54 am
by ccs
dspain wrote:ccs wrote:Malakai wrote:If Dan is able to pull it off, it would render vircom's dma server obsolete. Good luck
No thats not it.
I just need a client so other BBS's can connect to my DMA server. We just need to pull apart the hand shake that vircom built into its rlogin client. All I think we need to do is sniff the packets and we can see how it works. Then we can tweek the Galcomm rlogin client and it will allow any worldgroup server out there access DMA servers.
Joe
majortcp uses a datastream what needs to be written is a debug module that any connection accepted on port 513/514 sends the param strings.
but as malakai said you would be able to run both majortcp for bbs's still using mtcpip and mine for bbs's using wg3nt
I think it is only a rlogin connection with a different handshake. I will do a packet capture..
Joe
Posted: Fri Apr 13, 2007 12:22 am
by ccs
dspain wrote:ccs wrote:Malakai wrote:If Dan is able to pull it off, it would render vircom's dma server obsolete. Good luck
No thats not it.
I just need a client so other BBS's can connect to my DMA server. We just need to pull apart the hand shake that vircom built into its rlogin client. All I think we need to do is sniff the packets and we can see how it works. Then we can tweek the Galcomm rlogin client and it will allow any worldgroup server out there access DMA servers.
Joe
majortcp uses a datastream what needs to be written is a debug module that any connection accepted on port 513/514 sends the param strings.
but as malakai said you would be able to run both majortcp for bbs's still using mtcpip and mine for bbs's using wg3nt
I have a wg2.0 server and a WG2.0 DMA server running and would be glad to help test this stuff out.
Joe
Posted: Fri Apr 13, 2007 3:31 am
by dspain
ccs wrote:dspain wrote:ccs wrote:
No thats not it.
I just need a client so other BBS's can connect to my DMA server. We just need to pull apart the hand shake that vircom built into its rlogin client. All I think we need to do is sniff the packets and we can see how it works. Then we can tweek the Galcomm rlogin client and it will allow any worldgroup server out there access DMA servers.
Joe
majortcp uses a datastream what needs to be written is a debug module that any connection accepted on port 513/514 sends the param strings.
but as malakai said you would be able to run both majortcp for bbs's still using mtcpip and mine for bbs's using wg3nt
I have a wg2.0 server and a WG2.0 DMA server running and would be glad to help test this stuff out.
Joe
cool i have a wg 2.0 server with an average of about 27-36 online
problem is they are all playing my tele-arena custom versions they dont ever enter anything else but maybe t-lord on occasion so any DMA testing on my server is absolete.
Posted: Sat Apr 14, 2007 11:17 am
by Malakai
Only thing is - if this will allow us to use it like a DMA server, ya know, to provide other boards with access, it'll need to have some type of authentication feature.
Posted: Sat Apr 14, 2007 3:18 pm
by dspain
Malakai wrote:Only thing is - if this will allow us to use it like a DMA server, ya know, to provide other boards with access, it'll need to have some type of authentication feature.
you mean like security so you can allow/disallow systems?
Posted: Sat Apr 14, 2007 4:00 pm
by Malakai
System logins and passwords...
Posted: Sun Apr 15, 2007 5:14 am
by dspain
Malakai wrote:System logins and passwords...
i agree, right now i gotta learn to crawl before i can walk.
so im taking baby steps.
phase1: this is to get it to connect via rlogin protocol, and pending on the command switches jump to a module page or a module itself.
right now im using name sysop and sysops pw just to get to client negotiations to work.
right now i can type /DMA arcticzone.dyndns.org %s %s -MODULE TA2 and i connect as sysop and enter ta2 asking for no PW
when i do it with an account that doesnt exist i have a return message to prevent a crash that says "user-id does not exist notify sysop"
so i know its communicating right, so my next step will be to creat an account based on the passed info in the background then jump.
its not been easy but then again ive gotten alot further than i thought i would.
guess thats why vircomm charges an arm and a leg cause they know they can, lol
Posted: Tue Apr 17, 2007 2:04 pm
by Malakai
I think something similar could be done for synchronet as well. Of course, you have the normal way to add xternal programs and go to menus, etc in it, but you also have keywords that will move you to such and such door, external program, etc, which is how I setup the menus on my bbs door game server. So, if you could find a way to:
#1: allow multiple systems to gain access without name conflicts
#2: pass along the keyword through rlogin to synchronet and have synchronet translate that keyword to a specific door.
then it shouldn't be too hard to do.