GALICO (REVISION)

[dspain]

anyone running wg 3.2/3.3 that wants a newer ICO let me know.

the following changes in my ICO revision applies:


GALTNTD
----------
configure port to initialize telnet server on, now supports up to
port# 65535

/TELNETS sysop command to display all telnet clients connected to your server

added new sysop configurable command to allow only a certain number of connections from the same IP



GALRLGND
------------

configure port to initialize rlogin server on, now supports up to
port# 65535

/RLOGINS sysop command to display all rlogin clients connected to your server

added new sysop configurable command to allow only a certain number of connections from the same IP

SSH support in development
DMA support in BETA

GALRLGN
-----------

added an option to set the outgoing port to connect to via command line interface


GALTCPIP
-----------

several new ansi text variables for displaying certain information on channels

/clients command to display all ico clients connected, what protocol, and how long


this is the final ICO supplement i will be imlementing, only thing left in this family of addons is the DMA and SSH support.

i am moving on to the webserver to implelemnt true CGI/PHP/PERL support i will keep you informed.

[Toyduck]

anyone running wg 3.2/3.3 that wants a newer ICO let me know.

the following changes in my ICO revision applies:


GALTNTD
----------
configure port to initialize telnet server on, now supports up to
port# 65535

/TELNETS sysop command to display all telnet clients connected to your server

added new sysop configurable command to allow only a certain number of connections from the same IP



GALRLGND
------------

configure port to initialize rlogin server on, now supports up to
port# 65535

/RLOGINS sysop command to display all rlogin clients connected to your server

added new sysop configurable command to allow only a certain number of connections from the same IP

SSH support in development
DMA support in BETA

GALRLGN
-----------

added an option to set the outgoing port to connect to via command line interface


GALTCPIP
-----------

several new ansi text variables for displaying certain information on channels

/clients command to display all ico clients connected, what protocol, and how long


this is the final ICO supplement i will be imlementing, only thing left in this family of addons is the DMA and SSH support.

i am moving on to the webserver to implelemnt true CGI/PHP/PERL support i will keep you informed.

Hey Dan;

Is it possible to have WG telnet to the local machine? Right now it wants to resolve anything you enter to an external address. Would be nice to be able to telnet to the same server WG is running on (without using VM or anything like that).

Like, I constantly use "File/Run" telnet localhost 555 to pop into one of my muds from the console to check on something. Right now I have WG and 2 muds running on the same server and still have 1.5gb ram available and plenty of processing power available. But they can't 'talk' to each other.

Curious...

Don

[dspain]

anyone running wg 3.2/3.3 that wants a newer ICO let me know.

the following changes in my ICO revision applies:


GALTNTD
----------
configure port to initialize telnet server on, now supports up to
port# 65535

/TELNETS sysop command to display all telnet clients connected to your server

added new sysop configurable command to allow only a certain number of connections from the same IP



GALRLGND
------------

configure port to initialize rlogin server on, now supports up to
port# 65535

/RLOGINS sysop command to display all rlogin clients connected to your server

added new sysop configurable command to allow only a certain number of connections from the same IP

SSH support in development
DMA support in BETA

GALRLGN
-----------

added an option to set the outgoing port to connect to via command line interface


GALTCPIP
-----------

several new ansi text variables for displaying certain information on channels

/clients command to display all ico clients connected, what protocol, and how long


this is the final ICO supplement i will be imlementing, only thing left in this family of addons is the DMA and SSH support.

i am moving on to the webserver to implelemnt true CGI/PHP/PERL support i will keep you informed.

Hey Dan;

Is it possible to have WG telnet to the local machine? Right now it wants to resolve anything you enter to an external address. Would be nice to be able to telnet to the same server WG is running on (without using VM or anything like that).

Like, I constantly use "File/Run" telnet localhost 555 to pop into one of my muds from the console to check on something. Right now I have WG and 2 muds running on the same server and still have 1.5gb ram available and plenty of processing power available. But they can't 'talk' to each other.

Curious...

Don

yes set your module page to TELNET set command string to 192.168.1.xxx
you could even set module pages to goto each of your muds.

or /telnet 192.168.1.100 5001

if this doesnt work let me know what it does ill look at the ICO source and find a way around it for ya.

[Toyduck]

yes set your module page to TELNET set command string to 192.168.1.xxx
you could even set module pages to goto each of your muds.

or /telnet 192.168.1.100 5001

if this doesnt work let me know what it does ill look at the ICO source and find a way around it for ya.

Yea, on the original telnet module, it doesn't work. If you set the same IP as the one WG is running on, it just sits there.

On my main WG, the server has multiple IP's, with WG specified as one IP (192.168.1.36). When I tried looping back to the other IP on another card (same machine), 192.168.1.35, same thing, it just sits there.

Of course, using 'localhost' WG resolves the IP locations as my main router...or incoming IP from the internet.

I will d/l your module and see what happens.

Don

[Toyduck]

yes set your module page to TELNET set command string to 192.168.1.xxx
you could even set module pages to goto each of your muds.

or /telnet 192.168.1.100 5001

if this doesnt work let me know what it does ill look at the ICO source and find a way around it for ya.

Yea, on the original telnet module, it doesn't work. If you set the same IP as the one WG is running on, it just sits there.

On my main WG, the server has multiple IP's, with WG specified as one IP (192.168.1.36). When I tried looping back to the other IP on another card (same machine), 192.168.1.35, same thing, it just sits there.

Of course, using 'localhost' WG resolves the IP locations as my main router...or incoming IP from the internet.

I will d/l your module and see what happens.

Don

I found out looking the MUD log that the mud does detect the incoming request, but list's it as "unknown"... I'm looking at the MUD code. also

[dspain]

yes set your module page to TELNET set command string to 192.168.1.xxx
you could even set module pages to goto each of your muds.

or /telnet 192.168.1.100 5001

if this doesnt work let me know what it does ill look at the ICO source and find a way around it for ya.

Yea, on the original telnet module, it doesn't work. If you set the same IP as the one WG is running on, it just sits there.

On my main WG, the server has multiple IP's, with WG specified as one IP (192.168.1.36). When I tried looping back to the other IP on another card (same machine), 192.168.1.35, same thing, it just sits there.

Of course, using 'localhost' WG resolves the IP locations as my main router...or incoming IP from the internet.

I will d/l your module and see what happens.

Don

you can specify an alternate port on command line.

[Toyduck]

yes set your module page to TELNET set command string to 192.168.1.xxx
you could even set module pages to goto each of your muds.

or /telnet 192.168.1.100 5001

if this doesnt work let me know what it does ill look at the ICO source and find a way around it for ya.

Yea, on the original telnet module, it doesn't work. If you set the same IP as the one WG is running on, it just sits there.

On my main WG, the server has multiple IP's, with WG specified as one IP (192.168.1.36). When I tried looping back to the other IP on another card (same machine), 192.168.1.35, same thing, it just sits there.

Of course, using 'localhost' WG resolves the IP locations as my main router...or incoming IP from the internet.

I will d/l your module and see what happens.

Don

you can specify an alternate port on command line.

figured it out.. havta use the ascii only option and turn off binary negociations. Jumps right from WG to the MUD. This opens up options..

TD

[dspain]

Yea, on the original telnet module, it doesn't work. If you set the same IP as the one WG is running on, it just sits there.

On my main WG, the server has multiple IP's, with WG specified as one IP (192.168.1.36). When I tried looping back to the other IP on another card (same machine), 192.168.1.35, same thing, it just sits there.

Of course, using 'localhost' WG resolves the IP locations as my main router...or incoming IP from the internet.

I will d/l your module and see what happens.

Don

you can specify an alternate port on command line.

figured it out.. havta use the ascii only option and turn off binary negociations. Jumps right from WG to the MUD. This opens up options..

TD

awesome. yes it does, i try to tell people worldgroup is a powerful turn key piece of software.
from bbs's to corporate web solutions to personal ads sites now to a front end for mudding.

[Toyduck]

awesome. yes it does, i try to tell people worldgroup is a powerful turn key piece of software.
from bbs's to corporate web solutions to personal ads sites now to a front end for mudding.

I recompiled one of my muds to run as a NT service; put it on with the BBS; and it jumps from the BBS to the MUD so fast you don't even realize you are telnetting out. Now I need to set up a test server and see how far I can push it reliably..., it's the closest I'v seen yet to a WG 'door'.

Better yet; if you could use a Win32 Service based MUD with a built in Rlogin server; or figure out a way to modify the telnet to pass paramaters...

TD

[dspain]

awesome. yes it does, i try to tell people worldgroup is a powerful turn key piece of software.
from bbs's to corporate web solutions to personal ads sites now to a front end for mudding.

I recompiled one of my muds to run as a NT service; put it on with the BBS; and it jumps from the BBS to the MUD so fast you don't even realize you are telnetting out. Now I need to set up a test server and see how far I can push it reliably..., it's the closest I'v seen yet to a WG 'door'.

Better yet; if you could use a Win32 Service based MUD with a built in Rlogin server; or figure out a way to modify the telnet to pass paramaters...

TD

i can make GALTNT pass any param you want.

if your mud uses rlogin a true 32bit rlogin server it will catch the name just as synchronet does. then it will look just like a door.

/go darkage

boom boom
in the game aready logged in as whatever userid you were on the bbs.