• telnet_gate

    From Hemo@VERT to All on Mon Sep 11 14:02:00 2000
    I'm trying to setup a telnet into another system on my *internal* network and not getting anywhere.

    I have added an entry for this system and the command line is duped from the other telnet entries, I just modified the hostname to reflect what I have in my \windows\hosts file. I have even tried just using the IP address.

    It just hangs.....

    I can telnet to the system in question from my SBBS system with a regular telnet program, both to the hostname and to the IP.

    Any ideas why I can telnet to the world within Synchronet but not to my internal network ?


    ---
    Synchronet ... Running madly into the wind and screaming ...
  • From Amcleod@VERT to Hemo on Tue Sep 12 00:44:31 2000
    RE: telnet_gate
    BY: Hemo to All on Mon Sep 11 2000 09:02 pm

    Any ideas why I can telnet to the world within Synchronet but not to my internal network ?

    You have not really given us a lot of information on the physical topology of the network. You have an internal network and internet connectivity, and an SBBS box, but how are they hooked together?

    Can you ping the system in question? Does it actually have a telnet daemon running? Do you have a multi-homed box functioning as a gateway? Is there any firewalling going on? Maybe you need to put an entry in your routing table(s).

    Tell me more and I will try to help.
    ---
    Synchronet Vertrauen Home of Synchronet telnet://vert.synchro.net
  • From Digital Man@VERT to Hemo on Tue Sep 12 03:40:36 2000
    RE: telnet_gate
    BY: Hemo to All on Mon Sep 11 2000 09:02 pm

    I'm trying to setup a telnet into another system on my *internal* network an not getting anywhere.

    I have added an entry for this system and the command line is duped from the other telnet entries, I just modified the hostname to reflect what I have in \windows\hosts file. I have even tried just using the IP address.

    It just hangs.....

    You mean it never returns an error message? You have to close down SBBSCTRL?

    I can telnet to the system in question from my SBBS system with a regular telnet program, both to the hostname and to the IP.

    Any ideas why I can telnet to the world within Synchronet but not to my internal network ?

    It might be the interface you have the telnet server bound to (outbound telnet connections use the same interface) can not reach this other machine. If you have multiple network interfaces (cards) in your computer, then may need to change your bound Interface in SBBSCTRL->Telnet->Configure to "<ANY>".

    Rob
    ---
    Synchronet Vertrauen Home of Synchronet telnet://vert.synchro.net
  • From Hemo@VERT to Amcleod on Tue Sep 12 04:15:00 2000
    RE: telnet_gate
    BY: Amcleod to Hemo on Tue Sep 12 2000 07:44 am

    Any ideas why I can telnet to the world within Synchronet but not to my internal network ?

    You have not really given us a lot of information on the physical topology o the network. You have an internal network and internet connectivity, and an SBBS box, but how are they hooked together?

    Can you ping the system in question? Does it actually have a telnet daemon running? Do you have a multi-homed box functioning as a gateway? Is there firewalling going on? Maybe you need to put an entry in your routing table(

    Tell me more and I will try to help.

    ouch. ok.. I thought I briefly covered most of what you are asking me.

    I have two computers, A & B.
    A & B are networked through a hub.
    A & B are on the same subnet ( 192.168.1.* )
    A is Windows 98 and runs SBBS (SBBS box)
    B is SCO OpenServer 5.0.4

    I have both A & B entered in the hosts file on both A & B

    I can telnet from A to B, both by IP and by hostname
    I can telnet from B to A, both by IP and by hostname
    I can telnet from A to the world, since any external IP or hostname goes through my router. The same goes for Computer B.

    Did I mention I do Network administration as my real job?

    I use a firewall for my *incoming* traffic, and port 23 (telnet) is fixed to forward to my SBBS box ( A ).

    When logged in to Synchronet, and choosing the external doors, and picking the 'other BBS systems', Synchronet successfully telnets out to the ones that are up.

    When I duplicate one of the entries that is working, and put my the IP or hostname of my Computer B in, save, shutdown SBBS and restart SBBS, log in and try to connect... it goes through the motions but does not connect. When monitoring port 23 from Computer B, nobody ever knocks.. yet I can open a telnet window and connect immediately without problems....

    Sooo... what is Sychronet doing differently than my telnet program?


    I guess I could try adding the route command, but should not have to since we are on the same class c network. I'll drop to ;dos and see if it helps....

    ---
    Synchronet ... Running madly into the wind and screaming ...
  • From Hemo@VERT to Digital Man on Tue Sep 12 13:00:00 2000
    RE: telnet_gate
    BY: Digital Man to Hemo on Tue Sep 12 2000 10:40 am

    It just hangs.....

    You mean it never returns an error message? You have to close down SBBSCTRL?

    No errors. It says 'Press Ctrl-]for a control menu anytime'. Then it says '[Hit a key]'

    I hit a key......

    it says 'Connecting to: myopia'

    and then nothing happens. I can hit Ctrl-] and tell it to disconnect and get back to the BBS.


    I already have the Interface IP bound to <ANY>, but maybe I'll bind it to my NIC and see happens.








    ---
    Synchronet ... Running madly into the wind and screaming ...
  • From Hemo@VERT to Digital Man on Tue Sep 12 13:06:00 2000
    RE: telnet_gate
    BY: Digital Man to Hemo on Tue Sep 12 2000 10:40 am

    Any ideas why I can telnet to the world within Synchronet but not to my internal network ?

    It might be the interface you have the telnet server bound to (outbound teln connections use the same interface) can not reach this other machine. If you have multiple network interfaces (cards) in your computer, then may need to change your bound Interface in SBBSCTRL->Telnet->Configure to "<ANY>".

    Already configured like that.

    Here's the error I get in the log file AFTER I hit Ctrl-D to disconnect from the hung telnet attempt:

    9/12 09:03:24p Node 1 Ran external: Myopia
    9/12 09:03:26p Node 1 Telnet gate to myopia.ujoint.org port 23 on socket 404
    9/12 09:03:42p !TELGATE ERROR 10038 sending on socket 404
    9/12 09:03:42p !ERROR 10038 closing socket 404
    9/12 09:03:42p Node 1 Telnet gate to myopia.ujoint.org finished

    Again, I can telnet to myopia from this machine just fine, but not via Synchronet.. ?

    ---
    Synchronet ... Running madly into the wind and screaming ...
  • From Digital Man@VERT to Hemo on Tue Sep 12 15:22:16 2000
    RE: telnet_gate
    BY: Hemo to Digital Man on Tue Sep 12 2000 08:00 pm

    It just hangs.....

    You mean it never returns an error message? You have to close down SBBSCT

    No errors. It says 'Press Ctrl-]for a control menu anytime'. Then it says '[Hit a key]'

    I hit a key......

    it says 'Connecting to: myopia'

    and then nothing happens. I can hit Ctrl-] and tell it to disconnect and ge back to the BBS.

    Have you tried _waiting_? It will return an error if the connection fails (eventually),

    I already have the Interface IP bound to <ANY>, but maybe I'll bind it to my NIC and see happens.

    Do you have more than one NIC in your BBS machine?

    Rob
    ---
    Synchronet Vertrauen Home of Synchronet telnet://vert.synchro.net
  • From Digital Man@VERT to Hemo on Tue Sep 12 15:23:46 2000
    RE: telnet_gate
    BY: Hemo to Digital Man on Tue Sep 12 2000 08:06 pm

    Any ideas why I can telnet to the world within Synchronet but not to m internal network ?

    It might be the interface you have the telnet server bound to (outbound t connections use the same interface) can not reach this other machine. If have multiple network interfaces (cards) in your computer, then may need change your bound Interface in SBBSCTRL->Telnet->Configure to "<ANY>".

    Already configured like that.

    Here's the error I get in the log file AFTER I hit Ctrl-D to disconnect from the hung telnet attempt:

    9/12 09:03:24p Node 1 Ran external: Myopia
    9/12 09:03:26p Node 1 Telnet gate to myopia.ujoint.org port 23 on socket 404
    9/12 09:03:42p !TELGATE ERROR 10038 sending on socket 404
    9/12 09:03:42p !ERROR 10038 closing socket 404
    9/12 09:03:42p Node 1 Telnet gate to myopia.ujoint.org finished

    This error simply means you aborted the connection attempt. Try being patient and waiting for the real connection failure message.

    Again, I can telnet to myopia from this machine just fine, but not via Synchronet.. ?

    Yes, I gathered that. :-)

    Rob
    ---
    Synchronet Vertrauen Home of Synchronet telnet://vert.synchro.net
  • From TommyKnocker@VERT to Hemo on Tue Sep 12 12:21:00 2000
    RE: telnet_gate
    BY: Hemo to All on Mon Sep 11 2000 09:02 pm

    Any ideas why I can telnet to the world within Synchronet but not to my internal network ?

    Do you have tcp/ip networking setup and IP numbers assigned on your lan?
    TK

    ---
    Synchronet telnet://talamasca-bbs.com http://talamasca-bbs.com
  • From Hemo@VERT to Digital Man on Sun Sep 17 07:51:00 2000
    RE: telnet_gate
    BY: Digital Man to Hemo on Tue Sep 12 2000 10:23 pm

    9/12 09:03:24p Node 1 Ran external: Myopia
    9/12 09:03:26p Node 1 Telnet gate to myopia.ujoint.org port 23 on soc 404
    9/12 09:03:42p !TELGATE ERROR 10038 sending on socket 404
    9/12 09:03:42p !ERROR 10038 closing socket 404
    9/12 09:03:42p Node 1 Telnet gate to myopia.ujoint.org finished

    This error simply means you aborted the connection attempt. Try being patien and waiting for the real connection failure message.

    OK, got my unix machine back up and running and started trying all this stuff again.

    Still don't work. I let it sit for 133 minutes ( I went shopping ) and I still got no error, it just sat there.

    I have a LinkSys broadband router that links my internal network to the outside world. My internal network is 192.168.1. I have connectivity between my
    BBS machine (internal network 192.168.1.100 or delta.ujoint.org) and my unix computer (internal network 192.168.1.50 or myopia.ujoint.org). I tested my connectivity by using ping, ftp, and telnet. These all work fine from either machine to either machine.

    Try running '*telgate myopia.ujoint.org' causes you to just hang there with no connection. running '*telgate delta.ujoint.org' works. Now I am really confusinededed...ded.

    This behavior is identical if I am telneted into my BBS from inside my network or from an outside (other side of my router) host.

    my 'hosts' file( same on both my systems ):
    192.168.1.100 delta delta.ujoint.org
    192.168.1.50 myopia myopia.ujoint.org


    Since I do networking support as part of my real job, this is one of those things that I am determined to figure out why it doesn't work, and I am stumped. I don;t know what's ahppening inside of the baja code for 'telnet_gate', but that's the only place I can figure this is going wrong...

    I have only one NIC on both systems, the IP's are static, SBBS has been bound to <ANY> and is now bound to 192.168.1.100 and all results are the same.

    Help?

    ---
    Synchronet The Universal JoiNT - bbs.ujoint.org - under seda..construction
  • From Hemo@VERT to TommyKnocker on Sun Sep 17 07:54:00 2000
    RE: telnet_gate
    BY: TommyKnocker to Hemo on Tue Sep 12 2000 07:21 pm

    Any ideas why I can telnet to the world within Synchronet but not to my internal network ?

    Do you have tcp/ip networking setup and IP numbers assigned on you lan?

    yuppers. If I didn't, I wouldn't be able to telnet to those other systems. It's just through BAJA's telnet_gate that it _doesn't_ work. Oddly enough, I can telnet into the same system, but not into another sysem on my internal network....


    ---
    Synchronet The Universal JoiNT - bbs.ujoint.org - under seda..construction
  • From Digital Man@VERT to Hemo on Sun Sep 17 09:15:19 2000
    RE: telnet_gate
    BY: Hemo to Digital Man on Sun Sep 17 2000 02:51 pm

    9/12 09:03:42p !TELGATE ERROR 10038 sending on socket 404
    9/12 09:03:42p !ERROR 10038 closing socket 404
    9/12 09:03:42p Node 1 Telnet gate to myopia.ujoint.org finished

    This error simply means you aborted the connection attempt. Try being pat and waiting for the real connection failure message.

    OK, got my unix machine back up and running and started trying all this stuf again.

    Still don't work. I let it sit for 133 minutes ( I went shopping ) and I st got no error, it just sat there.

    I have a LinkSys broadband router that links my internal network to the outs world. My internal network is 192.168.1. I have connectivity between my BBS machine (internal network 192.168.1.100 or delta.ujoint.org) and my unix computer (internal network 192.168.1.50 or myopia.ujoint.org). I tested my connectivity by using ping, ftp, and telnet. These all work fine from either machine to either machine.

    Try running '*telgate myopia.ujoint.org' causes you to just hang there with connection. running '*telgate delta.ujoint.org' works. Now I am really confusinededed...ded.

    This behavior is identical if I am telneted into my BBS from inside my netwo or from an outside (other side of my router) host.

    my 'hosts' file( same on both my systems ):
    192.168.1.100 delta delta.ujoint.org
    192.168.1.50 myopia myopia.ujoint.org


    Since I do networking support as part of my real job, this is one of those things that I am determined to figure out why it doesn't work, and I am stumped. I don;t know what's ahppening inside of the baja code for 'telnet_gate', but that's the only place I can figure this is going wrong...

    I have only one NIC on both systems, the IP's are static, SBBS has been boun to <ANY> and is now bound to 192.168.1.100 and all results are the same.

    Help?

    I really don't have a clue as to why it isn't working. The telnet_gate function simply opens a socket, binds it, and attempts a connect to the address (and port) specified. Nothing complex. Here is the actual code:

    void sbbs_t::telnet_gate(char* destaddr, ulong mode)
    {
    char* p;
    char str[128];
    uchar buf[512];
    int i;
    int rd;
    ulong l;
    bool gotline;
    ushort port=IPPORT_TELNET;
    ulong ip_addr;
    ulong save_console;
    SOCKET remote_socket;
    SOCKADDR_IN addr;

    p=strchr(destaddr,':');
    if(p!=NULL) {
    *p=0;
    port=atoi(p+1);
    }

    if((remote_socket = open_socket(SOCK_STREAM)) == INVALID_SOCKET) {
    errormsg(WHERE,ERR_OPEN,"socket",0);
    return;
    }

    memset(&addr,0,sizeof(addr));
    addr.sin_addr.S_un.S_addr = htonl(cfg.startup->interface_addr);
    addr.sin_family = AF_INET;

    if((i=bind(remote_socket, (struct sockaddr *) &addr, sizeof (addr)))!=0) {
    close_socket(remote_socket);
    lprintf("!ERROR %d (%d) binding to socket %d",i, ERROR_VALUE, socket);
    return;
    }

    ip_addr=resolve_ip(destaddr);
    if(!ip_addr) {
    close_socket(remote_socket);
    lprintf("Failed to resolve addres: %s",destaddr);
    return;
    }

    memset(&addr,0,sizeof(addr));
    addr.sin_addr.S_un.S_addr = ip_addr;
    addr.sin_family = AF_INET;
    addr.sin_port = htons(port);

    if((i=connect(remote_socket, (struct sockaddr *)&addr, sizeof(addr)))!=0) {
    close_socket(remote_socket);
    lprintf("!ERROR %d (%d) connecting to server: %s"
    ,i,ERROR_VALUE, destaddr);
    return;
    }

    l=1;

    if((i = ioctlsocket(remote_socket, FIONBIO, &l))!=0) {
    close_socket(remote_socket);
    lprintf("!ERROR %d (%d) disabling socket blocking"
    ,i, ERROR_VALUE);
    return;
    }

    lprintf("Node %d Telnet gate to %s port %d on socket %d"
    ,cfg.node_num,destaddr,port,remote_socket);

    if(!(mode&TG_CTRLKEYS))
    console|=CON_RAW_IN;
    while(online) {
    gettimeleft();
    rd=RingBufRead(&inbuf,buf,sizeof(buf));
    if(rd) {
    if(!(telnet_mode&TELNET_MODE_BIN_RX)) {
    if(*buf==0x1d) { // ^]
    save_console=console;
    console&=~CON_RAW_IN; // Allow Ctrl-U/Ctrl-P
    CRLF;
    while(online) {
    SYNC;
    mnemonics("\1n\r\n\1h\1bTelnet Gate: \1y~D\1wisconnect, "
    "\1y~E\1wcho toggle, \1y~L\1wist Users, \1y~P\1wrivate message, "
    "\1y~Q\1wuit: ");
    switch(getkeys("DELPQ",0)) {
    case 'D':

    closesocket(remote_socket);
    break;
    case 'E':
    mode^=TG_ECHO;

    bprintf(text[EchoIsNow]

    ,mode&TG_ECHO
    ? text[ON]:text[OFF]);
    continue;
    case 'L':

    whos_online(true);
    continue;
    case 'P':
    nodemsg();
    continue;
    }
    break;
    }
    attr(LIGHTGRAY);
    console=save_console;
    }
    gotline=false;
    if(mode&TG_LINEMODE && buf[0]!='\r') {
    ungetkey(buf[0]);
    l=K_CHAT;
    if(!(mode&TG_ECHO))
    l|=K_NOECHO;
    rd=getstr((char*)buf,sizeof(buf)-1,l);
    if(!rd)
    continue;
    strcat((char*)buf,crlf);
    rd+=2;
    gotline=true;
    }
    if(mode&TG_CRLF && buf[rd-1]=='\r')
    buf[rd++]='\n';
    if(!gotline && mode&TG_ECHO) {
    RingBufWrite(&outbuf,buf,rd);
    SetEvent(output_event);
    }
    }
    if((i=send(remote_socket,(char*)buf,rd,0))<0) {
    lprintf("!TELGATE ERROR %d sending on socket %d",ERROR_VALUE,remote_socket);
    break;
    }
    }
    rd=recv(remote_socket,(char*)buf,sizeof(buf),0);
    if(rd<0) {
    if(ERROR_VALUE==WSAEWOULDBLOCK) {
    if(mode&TG_NODESYNC) {
    SYNC;
    }
    mswait(1);
    continue;
    }
    lprintf("!TELGATE ERROR %d receiving on socket %d",ERROR_VALUE,remote_socket);
    break;
    }
    if(!rd) {
    lprintf("Node %d Telnet gate disconnected",cfg.node_num);
    break;
    }
    RingBufWrite(&outbuf,buf,rd);
    SetEvent(output_event);
    }
    console&=~CON_RAW_IN;

    /* Disable Telnet Terminal Echo */
    sprintf(str,"%c%c%c",TELNET_IAC,TELNET_WILL,TELNET_ECHO);
    putcom(str,3);

    close_socket(remote_socket);

    lprintf("Node %d Telnet gate to %s finished",cfg.node_num,destaddr);
    }

    (if that's of any help)

    Rob
    ---
    Synchronet Vertrauen Home of Synchronet telnet://vert.synchro.net
  • From Amcleod@VERT to Hemo on Sun Sep 17 11:02:43 2000
    RE: telnet_gate
    BY: Hemo to Digital Man on Sun Sep 17 2000 02:51 pm

    I have a LinkSys broadband router that links my internal network to the outs world. My internal network is 192.168.1. I have connectivity between my BBS machine (internal network 192.168.1.100 or delta.ujoint.org) and my unix computer (internal network 192.168.1.50 or myopia.ujoint.org). I tested my connectivity by using ping, ftp, and telnet. These all work fine from either machine to either machine.

    Try running '*telgate myopia.ujoint.org' causes you to just hang there with connection. running '*telgate delta.ujoint.org' works. Now I am really confusinededed...ded.

    'delta' is a Windows machine running SBBS and 'myopia' is a Linux box. You can telnet/ftp/ping the Linux box from Windows, & vice versa. You can 'telgate' from the Windows box to itself. But you can't 'telgate' from the Windows box to the Linux box, even though "regular" telnet works?

    Weird!

    Is the LinkSys router doing any firewalling between the two boxes? Or just to the outside world? Is all the telnet/telgate action taking place on port 23? I don't know if telgate does/can use some alternate port...

    Can you see if anything is knocking on the door when you try to telgate to myopia? Use a packet sniffer to see if delta is sending the packets and myopia ignoring them or if delta doesn't even send them in the first place? What about name resolution? Does SBBS use the 'hosts' file or only DNS? Does IP address 24.160.244.151 belong to you? Try a traceroute (don't know Windows spelling) to myopia and myopia.ujoint.org and see if it is OK. Try using the IP address of myopia directly in the telgate command.

    I dunno what your problem is, but it is an interesting one. I dunno if Windows has anything similar to "/etc/nsswitch.conf". Are you running a DNS server for the domain? Can you add delta and myopia to the DNS config rasther than rely on the hosts file?
    ---
    Synchronet Vertrauen Home of Synchronet telnet://vert.synchro.net
  • From Hemo@VERT to Digital Man on Sun Sep 17 12:29:00 2000
    RE: telnet_gate
    BY: Digital Man to Hemo on Sun Sep 17 2000 04:15 pm

    I really don't have a clue as to why it isn't working. The telnet_gate funct simply opens a socket, binds it, and attempts a connect to the address (and port) specified. Nothing complex. Here is the actual code:

    I'll take a closer gander at the code a bit later, right now I'm going to go grab a packet sniffer and see what I can get from that..

    My router/hub is not in direct eye contact with my system, but with the help of a mirror or another person ( I used another person in this test) I can see the lights on the front. When Synchronet goes off and calls *telgate myopia.ujoint.org, I have verified activity between the nodes, based on the lights. If I bang away at the keyboard, the lights go nuts, as though I _am_ connected to the other server, just can't see anything on my local screen! I tried toggling echo a few times but still can't see anything. Hmmm...

    A little later I'm gonna get a telnet server ( perhaps SBBS ) running an a Win 9x machine and see if I can connect to that. I wouldn't think there is anything different with telnetd under SCO OpenServer 5.0.5 from telnetd on any other system... (refering to receiving data and sending data/echoing commands back)

    This one just stumps me... I hope it isn't going to be on of those simple stupid things like is it plugged in or anything ....


    ---
    Synchronet The Universal JoiNT - bbs.ujoint.org - under seda..construction
  • From Hemo@VERT to Digital Man on Sun Sep 17 14:13:00 2000
    RE: telnet_gate
    BY: Digital Man to Hemo on Sun Sep 17 2000 04:15 pm

    well, I think I have found the problem. This problem can actually be dupliacted if you try using telnet_gate into just about any *nix telnetd server, and the problem may be simple or not so simple to correct.

    I'm just thinking out loud here, so don't take this as gospel, and correct me where I am wrong, please. (Rob)

    Synchronet's telnet server is not doing some of the telnet-protocol communications between server and client that most *nix based telnet server are doing. telnet_gate just opens a pass-thru port to a new IP, and the code you posted looks like it is doing just that. The telnetd on the *nix side, however, is sending some control questions out to the terminal, expecting to get answers and it is not getting answers. I am assuming my terminal software is not sending any answers because it is not listening for those control questions since it _already_ is in a session ( with Synchronet ).

    I enabled debugging ( to the screen ) on my unix teletd daemon and made a connection with my telnet client:
    ----- begin screen paste -----
    td: send do AUTHENTICATION
    td: recv wont AUTHENTICATION
    td: send do TERMINAL TYPE
    td: send do TSPEED
    td: send do XDISPLOC
    td: send do NEW-ENVIRON
    td: send do OLD-ENVIRON
    td: recv will TERMINAL TYPE
    td: recv wont TSPEED
    td: recv wont XDISPLOC
    td: recv wont NEW-ENVIRON
    td: recv wont OLD-ENVIRON
    td: recv suboption TERMINAL-TYPE IS "ansi"
    td: send will SUPPRESS GO AHEAD
    td: send do ECHO
    td: send do NAWS
    td: send will STATUS
    td: send do LFLOW
    td: recv do SUPPRESS GO AHEAD
    td: recv wont ECHO
    td: recv will NAWS
    td: recv suboption NAWS 0 80 (80) 0 25 (25)
    td: recv dont STATUS
    td: recv wont LFLOW
    td: send will ECHO

    SCO OpenServer(TM) Release 5 (myopia.ujoint.org) (ttyp0)

    login: td: recv do ECHO
    ----- End Screen Paste -----

    Wow. That's a lot of crap these two sides are trying to find out. Leaving debugging on and trying to connect through my Synchonet door:

    ----- Begin Screen Paste -----
    Which or Quit: 7

    Press Ctrl-] for a control menu anytime.

    Connecting to: myopia.ujoint.org
    td: send do AUTHENTICATION
    ----- End Screen Paste -----

    Ahah. So, telnetd is waiting for an answer and never gets it. Synchronet won't do it because it is not a telnet client, it's just acting as pass-thru. My telnet client ain't gonna answer because it is already in a session with Synchronet!

    I am not a C or C++ programmer, but I understand enough to read code and get a fair idea. I generally do bourne or bash scripting on unix, work with SQL, and program in Visual Basic. This means I know what kind of work could be involved to add code to Synchronet to act as a psuedo-telnet-client and anser the pre-connecting requests, and then drop into a pass-through mode. I know it ain't pretty. If I could suggest something like this happening, then let's say I just did.

    I've got some C/C++ source here for a telnet client and if I can find the snippets in question, I'll send them your way...
    ... if you are interested. I'm off finding other telnet clients and testing them to see if it is just my (2) clients acting this way or do they all do this to me...


    ---
    Synchronet The Universal JoiNT - bbs.ujoint.org - under seda..construction
  • From Beta@VERT to Digital Man on Sun Sep 17 14:49:00 2000
    RE: telnet_gate
    BY: Digital Man to Hemo on Sun Sep 17 2000 04:15 pm

    I really don't have a clue as to why it isn't working. The telnet_gate funct simply opens a socket, binds it, and attempts a connect to the address (and port) specified. Nothing complex. Here is the actual code:

    1) Oh yeah, reall simple code... <G> 2) I've run into a similar problem here, only when connecting on the local subnet tho, I can connect to TAlamasca, Vert ect from Telgate, but if I try to connect to my firewall (192.168.1.1) it just sits there...
    Beta


    ---
    Synchronet Rover Central, Kenora Ontario, Canada
  • From Hemo@VERT to Amcleod on Tue Sep 19 00:39:00 2000
    RE: telnet_gate
    BY: Amcleod to Hemo on Sun Sep 17 2000 06:02 pm

    I've found the source of my problem, and the problem is the negotiations that take place between a telnet server and a telnet client before a login prompt is displayed. When using telnet_gate to connect to a telnetd or RFC telnet server, the telnet server attempts to do negotiations with the client to establish some things before a login propmpt gets thrown out. Since telnet_gate is not a telnet client, those negotiations are not getting answered and the telnet server never gives a login prompt. I have verified I _am_ connecting to the system in question, but these negotiations are not getting completed. The telnet client I am using to connect to Synchronet does not respond to these negotiations becuase it is programmed to do the negotiation during a connect attempt, not while a connect is already done!

    The RFC's for telnet are about as bad (reading wise) for any RFC, but I have found that reading these in their entirety either gives me a headache or leaves me

    ---
    Synchronet The Universal JoiNT - bbs.ujoint.org - under seda..construction
  • From Digital Man@VERT to Hemo on Tue Sep 19 14:09:54 2000
    RE: telnet_gate
    BY: Hemo to Amcleod on Tue Sep 19 2000 07:39 am

    I've found the source of my problem, and the problem is the negotiations tha take place between a telnet server and a telnet client before a login prompt displayed. When using telnet_gate to connect to a telnetd or RFC telnet server, the telnet server attempts to do negotiations with the client to establish some things before a login propmpt gets thrown out. Since telnet_gate is not a telnet client, those negotiations are not getting answe and the telnet server never gives a login prompt. I have verified I _am_ connecting to the system in question, but these negotiations are not getting completed. The telnet client I am using to connect to Synchronet does not respond to these negotiations becuase it is programmed to do the negotiation during a connect attempt, not while a connect is already done!

    Then your telnet client is broken or misconfigured. Telnet clients are
    required to be able to receive telnet option negotiation sequences at ANY TIME.

    The RFC's for telnet are about as bad (reading wise) for any RFC, but I have found that reading these in their entirety either gives me a headache or lea me

    Maybe so, but RFC 854 does state pretty clearly:

    "Option requests are likely to flurry back and forth when a TELNET
    connection is first established, as each party attempts to get the
    best possible service from the other party. Beyond that, however,
    options can be used to dynamically modify the characteristics of the
    connection to suit changing local conditions."

    I suggest trying a different telnet client.

    Rob
    ---
    Synchronet Vertrauen Home of Synchronet telnet://vert.synchro.net
  • From Digital Man@VERT to Hemo on Tue Sep 19 14:28:42 2000
    RE: telnet_gate
    BY: Hemo to Digital Man on Sun Sep 17 2000 09:13 pm

    well, I think I have found the problem. This problem can actually be dupliacted if you try using telnet_gate into just about any *nix telnetd server, and the problem may be simple or not so simple to correct.

    I have used telnet_gate to connect to my Linux box, and did _not_ have the problem mentioned.

    I'm just thinking out loud here, so don't take this as gospel, and correct m where I am wrong, please. (Rob)

    Synchronet's telnet server is not doing some of the telnet-protocol communications between server and client that most *nix based telnet server doing.

    Not from my research. Synchronet's telnet server does all the necessary configuration and supports ALL telnet negotiation options. Simply turn on Telnet->Configure->Received Logged Commands in SBBSCTRL and you'll see all received telnet commands (which are responded to by Synchronet's telnet server).

    telnet_gate just opens a pass-thru port to a new IP, and the code yo
    posted looks like it is doing just that.

    Well, you can't see the input (from the telnet client) routines, which do the option processing/negotiation. That is where the problem (if there is one) is probably located.

    The telnetd on the *nix side,
    however, is sending some control questions out to the terminal, expecting to get answers and it is not getting answers. I am assuming my terminal softwa is not sending any answers because it is not listening for those control questions since it _already_ is in a session ( with Synchronet ).

    If it's a properly written telnet client, that is probably NOT the case. What's more likely is that the response from the telnet client is getting sucked up (inadvertently) by Synchronet's telnet server.

    I enabled debugging ( to the screen ) on my unix teletd daemon and made a connection with my telnet client:
    ----- begin screen paste -----
    td: send do AUTHENTICATION
    td: recv wont AUTHENTICATION
    td: send do TERMINAL TYPE
    td: send do TSPEED
    td: send do XDISPLOC
    td: send do NEW-ENVIRON
    td: send do OLD-ENVIRON
    td: recv will TERMINAL TYPE
    td: recv wont TSPEED
    td: recv wont XDISPLOC
    td: recv wont NEW-ENVIRON
    td: recv wont OLD-ENVIRON
    td: recv suboption TERMINAL-TYPE IS "ansi"
    td: send will SUPPRESS GO AHEAD
    td: send do ECHO
    td: send do NAWS
    td: send will STATUS
    td: send do LFLOW
    td: recv do SUPPRESS GO AHEAD
    td: recv wont ECHO
    td: recv will NAWS
    td: recv suboption NAWS 0 80 (80) 0 25 (25)
    td: recv dont STATUS
    td: recv wont LFLOW
    td: send will ECHO

    SCO OpenServer(TM) Release 5 (myopia.ujoint.org) (ttyp0)

    login: td: recv do ECHO
    ----- End Screen Paste -----

    Wow. That's a lot of crap these two sides are trying to find out. Leaving debugging on and trying to connect through my Synchonet door:

    ----- Begin Screen Paste -----
    Which or Quit: 7

    Press Ctrl-] for a control menu anytime.

    Connecting to: myopia.ujoint.org
    td: send do AUTHENTICATION
    ----- End Screen Paste -----

    Ahah. So, telnetd is waiting for an answer and never gets it. Synchronet won't do it because it is not a telnet client, it's just acting as pass-thru My telnet client ain't gonna answer because it is already in a session with Synchronet!

    I don't think that's what is happening. I think your telnet client probably IS responding, but the response it getting "eaten" by Synchronet.

    I am not a C or C++ programmer, but I understand enough to read code and get fair idea. I generally do bourne or bash scripting on unix, work with SQL, program in Visual Basic. This means I know what kind of work could be invol to add code to Synchronet to act as a psuedo-telnet-client and anser the pre-connecting requests, and then drop into a pass-through mode. I know it ain't pretty. If I could suggest something like this happening, then let's I just did.

    I've got some C/C++ source here for a telnet client and if I can find the snippets in question, I'll send them your way...

    Thanks, but I do have working option processing code (enable the logging of received Telnet options in SBBSCTRL to see them work).

    ... if you are interested. I'm off finding other telnet clients and testing them to see if it is just my (2) clients acting this way or do they all do t to me...

    Try this too: modify telgate.src, and add 16 to the end of the telnet_gate
    line (and recompile with Baja). Should look like this:

    printf "\r\n\1h\1hPress \1yCtrl-]\1w for a control menu anytime.\r\n\r\n"
    pause
    printf "\1h\1yConnecting to: \1w%s\1n\r\n" str
    telnet_gate str 16
    cls

    This should disable Synchronet's telnet option processing (temporarily, just for the gate session).

    Rob
    ---
    Synchronet Vertrauen Home of Synchronet telnet://vert.synchro.net
  • From Hemo@VERT to Digital Man on Wed Sep 20 12:03:00 2000
    RE: telnet_gate
    BY: Digital Man to Hemo on Tue Sep 19 2000 09:28 pm

    I am now bald and have a flat spot on my forehead.

    I've tried this so many ways I'm still spinning.

    What telnet client are you using? I've tried the Windows 98 included telnet, PowerTerm, and am now going out for others.

    I can connect out to vert and talamasca just fine, but if I try to connect to either my internal unix box ( SCO OpenServer 5.0.5 ) or a box on the net where I have a shell account ( some Red Hat.. uname -a reports version 2.0.38 ) I just hang. netstat -a shows a connection to the system, but my telnet clients hangs there.

    I'll keep trying things, but it's getting to the point I'm thinking of putting my unix box up front and have the bbs as a doorway from there.


    ---
    Synchronet The Universal JoiNT - bbs.ujoint.org - under seda..construction
  • From Digital Man@VERT to Hemo on Wed Sep 20 16:57:14 2000
    RE: telnet_gate
    BY: Hemo to Digital Man on Wed Sep 20 2000 07:03 pm

    I am now bald and have a flat spot on my forehead.

    I've tried this so many ways I'm still spinning.

    What telnet client are you using?

    HyperTerminal PE 5.0

    I've tried the Windows 98 included telnet
    PowerTerm, and am now going out for others.

    I can connect out to vert and talamasca just fine, but if I try to connect t either my internal unix box ( SCO OpenServer 5.0.5 ) or a box on the net whe I have a shell account ( some Red Hat.. uname -a reports version 2.0.38 ) I just hang. netstat -a shows a connection to the system, but my telnet clien hangs there.

    Did you try modifying telgate.src like I suggested?

    I'll keep trying things, but it's getting to the point I'm thinking of putti my unix box up front and have the bbs as a doorway from there.

    I don't think that will be necessary.

    Rob
    ---
    Synchronet Vertrauen Home of Synchronet telnet://vert.synchro.net
  • From Hemo@VERT to Digital Man on Thu Sep 21 12:30:00 2000
    RE: telnet_gate
    BY: Digital Man to Hemo on Wed Sep 20 2000 11:57 pm

    RE: telnet_gate
    BY: Hemo to Digital Man on Wed Sep 20 2000 07:03 pm

    I am now bald and have a flat spot on my forehead.

    I've tried this so many ways I'm still spinning.

    What telnet client are you using?

    HyperTerminal PE 5.0

    I've tried the Windows 98 included telnet
    PowerTerm, and am now going out for others.

    I can connect out to vert and talamasca just fine, but if I try to connec either my internal unix box ( SCO OpenServer 5.0.5 ) or a box on the net I have a shell account ( some Red Hat.. uname -a reports version 2.0.38 ) just hang. netstat -a shows a connection to the system, but my telnet cl hangs there.

    Did you try modifying telgate.src like I suggested?

    I'll keep trying things, but it's getting to the point I'm thinking of pu my unix box up front and have the bbs as a doorway from there.

    I don't think that will be necessary.

    Rob

    I have modified talgate.src, I now have the 'telnet_gate str' line reading 'telnet_gate str 16'

    err.. telgate.src ... too lazy to edit that line. did a 'baja telgate' and tried it again. Made no difference.. I don't understand why I can telnet into vert and talamasca but not into my shell account or local unix box.

    I have also tried Eric's Telnet98, and Tera Term Pro, with no differences. I'll go to Hilgraeve's site later and grab Hyperterm PE and then cross my fingers.

    ---
    Synchronet The Universal JoiNT - bbs.ujoint.org - under seda..construction
  • From Digital Man@VERT to Hemo on Sun Sep 24 00:07:06 2000
    RE: telnet_gate
    BY: Hemo to Digital Man on Thu Sep 21 2000 07:30 pm

    I am now bald and have a flat spot on my forehead.

    I've tried this so many ways I'm still spinning.

    What telnet client are you using?

    HyperTerminal PE 5.0

    I've tried the Windows 98 included telnet
    PowerTerm, and am now going out for others.

    I can connect out to vert and talamasca just fine, but if I try to con either my internal unix box ( SCO OpenServer 5.0.5 ) or a box on the n I have a shell account ( some Red Hat.. uname -a reports version 2.0.3 just hang. netstat -a shows a connection to the system, but my telnet hangs there.

    Did you try modifying telgate.src like I suggested?

    I'll keep trying things, but it's getting to the point I'm thinking of my unix box up front and have the bbs as a doorway from there.

    I don't think that will be necessary.

    Rob

    I have modified talgate.src, I now have the 'telnet_gate str' line reading 'telnet_gate str 16'

    err.. telgate.src ... too lazy to edit that line. did a 'baja telgate' and tried it again. Made no difference.. I don't understand why I can telnet i vert and talamasca but not into my shell account or local unix box.

    I have also tried Eric's Telnet98, and Tera Term Pro, with no differences. I'll go to Hilgraeve's site later and grab Hyperterm PE and then cross my fingers.

    I've put some updated DLLs and TELGATE.SRC/BIN in your .OUT directory. These should fix the problem you're having with Synchronet sucking-up the telnet commands and responses (put these files in your EXEC directory).

    Rob
    ---
    Synchronet Vertrauen Home of Synchronet telnet://vert.synchro.net
  • From PistolGrip@VERT to Digital Man on Sun Sep 24 02:57:00 2000
    RE: telnet_gate
    BY: Digital Man to Hemo on Sun Sep 24 2000 07:07 am

    I've put some updated DLLs and TELGATE.SRC/BIN in your .OUT directory. These should fix the problem you're having with Synchronet sucking-up the telnet commands and responses (put these files in your EXEC directory).

    Oh man... ain't it nice to be using software that's 'actively' being developed :)

    PG

    ---
    Synchronet WasteLand BBS telnet://wasteland.darktech.org
  • From Hemo@VERT to Digital Man on Sun Sep 24 06:29:00 2000
    RE: telnet_gate
    BY: Digital Man to Hemo on Sun Sep 24 2000 07:07 am

    I've put some updated DLLs and TELGATE.SRC/BIN in your .OUT directory. These should fix the problem you're having with Synchronet sucking-up the telnet commands and responses (put these files in your EXEC directory).

    Woo Hoo! Thank you Rob sooo very much. It works great!

    What can I say.... thanks a mil, your changes are going to make my life sooo much easier with the plans I have for Synchronet on my system.


    ---
    Synchronet The Universal JoiNT - bbs.ujoint.org - under seda..construction
  • From Beta@VERT to PistolGrip on Mon Sep 25 14:08:00 2000
    RE: telnet_gate
    BY: PistolGrip to Digital Man on Sun Sep 24 2000 09:57 am

    Oh man... ain't it nice to be using software that's 'actively' being develop

    You said it! :)
    Beta


    ---
    Synchronet Rover Central, Kenora Ontario, Canada