"SfR Fresh" - the SfR Freeware/Shareware Archive

Member "slirp-1.0.16/docs/alt.dcom.slip-emulators.FAQ" of archive slirp-1.0.16.tar.gz:


As a special service "SfR Fresh" has tried to format the requested source page into HTML format using source code syntax highlighting with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file. That can be also achieved for any archive member file by clicking within an archive contents listing on the first character of the file(path) respectively on the according byte size field.
    1 From stevew@netcom.com Wed Aug 16 01:33:24 1995
    2 Return-Path: stevew@netcom.com
    3 Received: from netcom21.netcom.com (stevew@netcom21.netcom.com [192.100.81.135]) by blitzen.canberra.edu.au (8.6.10/8.6.9) with ESMTP id BAA17220 for <danjo@blitzen.canberra.edu.au>; Wed, 16 Aug 1995 01:32:14 +1000
    4 Received: by netcom21.netcom.com (8.6.12/Netcom)
    5 	id IAA29646; Tue, 15 Aug 1995 08:25:30 -0700
    6 From: stevew@netcom.com (Steve Wilson)
    7 Message-Id: <199508151525.IAA29646@netcom21.netcom.com>
    8 Subject: Latest FAQ
    9 To: danjo@BLITZEN.CANBERRA.EDU.AU
   10 Date: Tue, 15 Aug 1995 08:25:30 -0700 (PDT)
   11 X-Mailer: ELM [version 2.4 PL23]
   12 MIME-Version: 1.0
   13 Content-Type: text/plain; charset=US-ASCII
   14 Content-Transfer-Encoding: 7bit
   15 Content-Length: 57991     
   16 Status: RO
   17 X-Status: 
   18 
   19 
   20 Alt.dcom.slip-emulators FAQ  V1.5   Aug 10, 1995
   21 
   22 This has been completely re-organized, i.e. there is a some what
   23 logical organization now with some of the descriptions you'd
   24 asked for!  There is also some meat to the questions relevant to
   25 Windows 95, etc.   
   26 
   27 Steve Wilson
   28 -------------------------------------------------------------------
   29 
   30 Questions:
   31 
   32 1.0 What is a Slip Emulator anyway?
   33    1.  What is a Slip/PPP emulator?
   34    2.  Is Slirp better using  SLIP or PPP?
   35 
   36 2.0 Where to get Slip Emulator Software?:
   37 
   38    1.  Is Slirp Free to Use?  Will I be charged long distance fees for using
   39        this because it uses my modem?
   40    2.  Where can I get slirp?
   41    3.  Where are there precompiled binaries for Slirp for... ?
   42    4.  Where can I get precompiled binaries for TIA?
   43    5.  Where on Netcom is a pre-compiled version of slirp?
   44 
   45    (Need to add stuff about twinsock...anyone want to write this section?)
   46 
   47 3.0 Emulator Configuration, i.e. How do I make this stuff work?
   48 
   49    1. Slirp starts up ok except doesn't display the DNS so I told
   50       it what the DNS was.  However, it won't load my local homepage?
   51    2. What should my network configuration look like for trumpet
   52       winsock for netcom?
   53    3. How do I use slirp to telnet into my linux box?
   54    4. What do the configuration files need to look like for linux?
   55    5. Is it possible to send mail from my Linux box to/thru Netcom while
   56    6. How do I set up slirp for an X connection?
   57    7. What are the new formats for the .slirprc commands in the .95x
   58       release of slirp? What are the new control port commands? 
   59    8. I'm trying to get shell via telnet on slirp, without 
   60       logging in again. What is the configuration?
   61    9. Does anyone have instructions/hints as to how to use Windows 95
   62       with slirp? 
   63 
   64 4.0 Emulator Performance
   65 
   66    1. Tia/Slirp Benchmark (This is slirp .9o vs TAI 1.0 I think..)
   67 
   68 5.0 Miscilaneous Problems/solutions...
   69 
   70    1. The posted solution from Dan(Author of SLIRP) for the .9o 
   71       lockup problem(RWIN adjustments, etc.)
   72    2. 32 bit Netscape on Win95 has DNS problems. Why? 
   73    3. Using OS/2 my baud rate say it's 1200. How do I make this faster for
   74       slirp?
   75    4. How do you login using the slirp.telnetd?
   76    5. Slirp says it's running 9600 baud. How do I make ir run at 14.4?
   77    6. Where can I find nntpd for netcom? How do I configure it for
   78       Netcom?
   79    7. TCPman launches when I try to run Netscape..but netscape never
   80       comes up?
   81    8. I start up a connection under Win95 and I only get a PPP connection?
   82       How do I configure it for slip?
   83    9. Why is using the telnetd better than just logging in twice? 
   84    10. Why doesnt' FTP-PM work with slirp?
   85    11. Will TIA 2.0 support PPP and CSLIP? Why don't they support ICMP?
   86        I'd love to see automagic port redirection as well?
   87    12. Why does rlogin work from the port master I'm dialing into, but
   88        telnet doesn't for setting up slirp between then end points? 
   89    13. Address 10.0.2.0 doesn't work under InterSlip from my Mac. Why not?
   90    14. How do I setup POP mail using slirp?
   91 
   92 (note - I'm still not completely happy with this organization... but it's a start
   93             and it's all I've got time for at this point.  Next release...)
   94 
   95 ----------------------------------------------------------------------------
   96 1.0 What is a Slip Emulator anyway?
   97 
   98 Question 1.1
   99 
  100 What is a SLIP Emulator?
  101 
  102 A slip emulator is a piece of software that runs on the host machine that you 
  103 call into. This software accepts the bits you throw it's way using SLIP  
  104 and then submits these bits to the host computer for transmission on the
  105 internet.
  106  
  107 When bits are received from the internet for the remote system, the emulator
  108 packages them up into the SLIP protocol and send them along to your remote
  109 system.
  110 
  111 Boy...that was terse and to the point ;-)
  112 
  113 Another way of putting this is that the SLIP emulator acts as a middleman 
  114 between the internet and your remote system.  Your remote system speaks SLIP
  115 at the middleman, and he interprets it into the language used by the 
  116 internet.  
  117 
  118 These two languages aren't really that different, and actually, SLIP is the
  119 same language as used on the internet plus some extra packaging to send it
  120 over your phone line.  
  121 
  122 You need to use SLIP (or PPP..explained later) over the phone line because 
  123 you are transferring binary information instead of just text.  If you've used
  124 zmodem or xmodem or kermit...you are using these protocols for the same reason
  125 as you are using SLIP or PPP. The primary difference between these protocols 
  126 and SLIP is that SLIP corresponds(as just mentioned) to the language of 
  127 the internet (TCP/IP...Transport Control Protocol/Internet Protocol...
  128 a real mouthful even as TCP/IP ;-)
  129 
  130 ----------------------------------------------------------------------------
  131 
  132 Question 1.2
  133 
  134 Leo Perez y Perez (perez@csulb.edu) wrote:
  135 : Is SLiRP better as SLIP or PPP?
  136 : or, what is the difference between them anyway?
  137 :
  138 : Leo Perez y Perez    
  139 : perez@csulb.edu      
  140 
  141 There are really three protocols available with slirp.
  142 
  143 They are SLIP, CSLIP, and PPP.
  144 
  145 The protocols have the following properties...
  146 
  147 Slip is merely raw IP frames sent in between two Flag characters, one
  148 indicating start, and the other indicating end of packet.  There is
  149 an escaping method when either of the two flags appears inside the 
  150 actual IP datagram.
  151 
  152 CSLIP is sent via the same basic mechanism over the physical medium(your
  153 phone line) but an added level of compression is applied to the 
  154 header of the IP datagram itself such that the IP header is reduced
  155 in sized from something like 40 bytes to something like 7 bytes.  This
  156 savings happens on EVERY packet.  This is a style of compression that
  157 is beyond the V.42bis compression algorithm used by your modem.  Estimates
  158 give about a 20% increase in performance(give or take 10%).
  159 
  160 PPP (or Point-to-Point Protocol) really might be classified more like
  161 a byte oriented HDLC.  That means that it takes the IP datagram and puts
  162 inside yet another encapsulating packet.  This packet has a CRC across
  163 it so bad packets can be detected at the lowest level.  There are also
  164 security features built into this protocol.  Basically, it is a far more
  165 robust protocol than Slip or CSLIP.  PPP also has the added property that
  166 the Slirp implementation can escape several control characters, so you
  167 are more likely to get a successful link up on a line that isn't 
  168 8 bit clean. (aka a serial line that has some sort of input processing
  169 occuring.) 
  170 
  171 >From previous performance measurements, people have found that CSLIP
  172 is fastest when using Slirp.  Some folks(like me) wind up using PPP
  173 over CSLIP because of the need for the escaping feature. In my case
  174 this allows me to do ftp sessions that don't work under CSLIP.
  175 
  176 Now, that is probably more than you ever wanted to know ;-)
  177 
  178 Steve Wilson
  179 ----------------------------------------------------------------------------
  180 2.0 Where to get Slip Emulator Software?:
  181 
  182 Question 2.1
  183 
  184 In article <waddell.803517481@hercules>, waddell@HERCULES.CS.UREGINA.CA 
  185 says...
  186 >
  187 >Is SLiRP free to use (ie.  will I be charged long distance fees for using
  188 >this because it uses my modem> or does it use the University's (or Unix 
  189 >server's modem>?
  190 >
  191 
  192 Yes. SLiRP is a free copyrighted software.  SLiRP runs on your UNIX shell 
  193 account and let's you connect to the internet.  You need a client PC with a 
  194 TCP stack like Trumpet Winsock which uses your modem to access your shell 
  195 account.  If there is a long distance charge to access your university's 
  196 computer, then you will have to pay those charges, as well as, any usage fees 
  197 that you are now paying.  Otherwise, you don't have to pay for accessing the 
  198 internet.
  199 
  200 Hope this helps,
  201 
  202 Lynn Larrow        
  203 llarrow@netcom.com                                Pacific Grove, CA
  204 http://www.webcom.com/~llarrow/tiarefg.html (SLiRP/TIA/Trumpet Setup)
  205 [Editor's note:  The above is a VERY useful home page, and is packed
  206  with more info than you'll find here!!]
  207 ----------------------------------------------------------------------------
  208 Question 2.2
  209 
  210 In article <DB9Hwz.BDL@agora.rdrop.com>, lucasa@postes.gaylord.org says...
  211 >Could someone please inform me of a FTP site for the 
  212 >updates to slirp?
  213 >
  214 >Lucas
  215 
  216 ftp://peace.wit.com/danjo/slirp/  or
  217 ftp://blitzen.canberra.edu.au/pub/slirp/  or
  218 ftp://ibc.wustl.edu/pub/slirp_bin/
  219 
  220 Lynn Larrow        "When the shoe fits, the foot is forgotten"
  221 llarrow@netcom.com                                Pacific Grove, CA
  222 ----------------------------------------------------------------------------
  223 Question 2.3
  224 
  225 In article <3s35j8$eab@gulfa.kuwait.net>, kcc94td1@access.kuwait.net says...
  226 >Anyone know where there are pre-compiled SLiRP binaries?  This would be 
  227 >very helpful and highly appreciated :-D
  228 >
  229 >Khaled al-Feeli
  230 
  231 Try ftp://ibc.wustl.edu/pub/slirp_bin/USE_AT_OWN_RISK/
  232 
  233 I also have some other links to slirp binary sites at this URL:
  234 
  235 http://www.webcom.com/~llarrow/tiafaqs.html
  236 
  237 Hopefully they are all still active :)
  238 
  239 Lynn Larrow                        
  240 llarrow@netcom.com                                Pacific Grove, CA
  241 ----------------------------------------------------------------------------
  242 Question 2.4
  243 
  244 > Where can I get precompiled binaries for TIA?
  245 
  246 You can get TIA by :
  247 ftp: //marketplace.com/tia
  248 
  249 There is also shareware for different systems under:
  250 
  251 ftp: //marketplace.com/tia/shareware
  252 
  253 ----------------------------------------------------------------------------
  254 Question 2.5
  255 
  256 In article <stew1117DAJ8vy.96s@netcom.com>,
  257 >stew1117@netcom.com (stewart coulter) wrote:
  258 >I am trying to locate the latest version of slirp, the one site that I 
  259 >tried I was unable to locate it any directories, please help me.  I need 
  260 >the FTP site and directory.  Respond via email.
  261 
  262 Folks on Netcom can get the release files and a few other doo-dads from my 
  263 directory:
  264 
  265   ~ldobbs/slirp
  266 
  267 The modified source for tcp_input.c (see other threads) is there, along with 
  268 some simple (and undocumented) scripts to build the binary.
  269 
  270 Lee Dobbs                     Milpitas CA            Voice: 408-946-7860
  271 ldobbs@netcom.com                 USA                Fax:   408-262-9392
  272 ----------------------------------------------------------------------------
  273 3.0 Emulator Configuration, i.e. How do I make this stuff work?
  274 
  275 Question 3.1
  276 
  277 In article <DBD1MG.6J5@zeno.fit.edu>, lkhan@winnie.fit.edu says...
  278 >I have installed the latest version of slirp on the Unix machine.  It
  279 >conplied properly (although I had to erase some files so it won't go over
  280 >disc quota).  Using Trumpet Winsock, I ran it using the command line:
  281 >"slirp -m 552 -c" (I set all the configurations as stated on the slirp home
  282 >page.)  It shows all the messages at the beginning expect for the dns ip
  283 >address.  So I used the "I.P. address of slirp" for the dns.
  284 >
  285 >When running Mosiac (ver. 2beta4), it wouldn't load the homepage.  The 
  286 >messages at the bottom stop at "Waiting..." and sticks there forever, the
  287 >little Mosaic "earth" still moves.
  288 >
  289 >What can be wrong??
  290 >
  291 >On the same machine, I can still run twinsock properly (it works.)
  292 
  293 My best guesses would be one of two things.  The first is that using the IP 
  294 address of the machine slirp is running on as your DNS isn't working.  In many 
  295 university situations, they will have one or two machines which serve as 
  296 nothing more than DNS servers.  You need to find out the address of these 
  297 machines.  The best idea here would be to ask the sysadmin at your site.
  298 
  299 The second good possibility is that a terminal server is interfering.  Using 
  300 SLIP/CSLIP requires an absolutely clean 8-bit line, something that most 
  301 terminal servers in a university setting have trouble with.  Try to find out 
  302 if your terminal server has a 'terminal download' option, or something similar 
  303 to set the connection to 8-bit clean.  Alternatively, try using SLiRPs PPP 
  304 mode as you can escape control characters which may help the problem.  BTW, 
  305 this would explain why twinsock works as it defaults to a 6-bit mode, which 
  306 means it can run over almost any connection.  It also makes it dog slow.
  307 
  308 Hope this helps.
  309 
  310 Matt
  311 mnm@goodnet.com
  312 matt.moore@asu.edu
  313 ----------------------------------------------------------------------------
  314 Question 3.2
  315 
  316 In article <sfbDBtEx8.FCz@netcom.com>, sfb@netcom.com (sfb) wrote:
  317 >I currently have a Netcom Shell Account and am using TIA to emulate slip.
  318 > ...
  319 >What should my settings be under Network Configuration?  I have tried 
  320 >tons of various settings, such as 192.0.2.2 (works for Eudora) and 
  321 >netcom.com
  322 
  323 First, I suggest adding these to the end of your hosts file in the Trumpet 
  324 directory:
  325 
  326 (Editor's note - Should probably change the 192.0.2.x stuff to 10.0.2.x
  327  in the table below ... see the linux configuration info for what I mean..)
  328 
  329 192.100.81.101  netcomsv netcomsv.netcom.com
  330 192.100.81.105  ns.netcom.com
  331 192.100.81.254  netcomgw netcomgw.netcom.com
  332 192.0.2.1       local-pc
  333 192.0.2.2	mail.netcom.com smtp-server pop-server
  334 192.0.2.3	netcom.com news.netcom.com nntp-server
  335 
  336 Then, in any winsock app that needs a POP or SMTP server (such as the Host 
  337 and Relay Host for Pegasus), use mail.netcom.com -- for a news (NNTP) 
  338 server, use netcom.com .
  339 
  340 By the way, in my Trumpet File;Setup Nameserver setting, I've been using
  341 
  342   192.100.81.101 192.100.81.254 192.100.81.105
  343 
  344 and I get very few name lookup delays.
  345 
  346 Lee Dobbs                     Milpitas CA            Voice: 408-946-7860
  347 ldobbs@netcom.com                 USA                Fax:   408-262-9392
  348 ________________________________________________________________________
  349 Question 3.3
  350 
  351 In article <frankDAGH97.Gu6@netcom.com> frank@netcom.com (frank) writes:
  352 >Hi, Slirpers:
  353 >
  354 >How do I telnet into my linux box?  I redir the port 8888 to 192.0.2.0:23
  355 >I am using SLiRP 0.9o.  But when I login to netcom and use
  356 >telnet netcom8(or whatever).netcom.com 8888, nothing happened.
  357 >Do I need to set my IP to 192.0.2.0 instead of 10.0.2.15?  Any help
  358 >will be greatly appreciated.
  359 >
  360 >frank@netcom.com
  361 
  362 
  363 Why don't you try redirecting it to 10.0.2.15:23  ???
  364 ________________________________________________________________________
  365 
  366 Question 3.4
  367 
  368 What do the configuration files need to look like for linux
  369 for basic tcp/ip connetions to work with a slip emulator?
  370 
  371 These files are configured for netcom..but hopefully will
  372 serve as an example as to how to set things up....
  373 
  374 /etc/hosts ----
  375 127.0.0.1       localhost
  376 10.0.2.15       darkstar local-pc
  377 192.100.81.101  netcomsv netcomsv.netcom.com
  378 192.100.81.105  ns.netcom.com
  379 192.100.81.254  netcomgw netcomgw.netcom.com
  380 10.0.2.2	mail.netcom.com smtp-server pop-server
  381 10.0.2.3	netcom.com news.netcom.com nntp-server
  382 /etc/resolv.conf ----
  383 domain netcom.com
  384 nameserver 192.100.81.108   (Editor's note - You might want to have
  385                                               several entries on this line so if one
  386                                              nameserver is down, there are alternatives locally.)
  387 /etc/host.conf -----
  388 order hosts, bind
  389 multi on
  390 
  391 I'm not going to try and explain how to use dip here...that's a bit much.
  392 ________________________________________________________________________
  393 Question 3.5
  394 In article <ekbondDACC0q.DFM@netcom.com>, ekbond@netcom.com (E. Kelly
  395 Bond) wrote:
  396 
  397 > Is it possible to send mail from my Linux box to/through Netcom
  398 > while connected via TIA?
  399 > 
  400 > Any help will be appreciated.
  401 > 
  402 > Kelly
  403 > ekbond@netcom.com
  404 
  405 Yes, I am doing it.  You have to configure your domain name to netcom.com
  406 and use sendmail with the smtp-only script in /usr/src/sendmail/cf, and
  407 all will be great.  There are readmes in the sendmail directory how to use
  408 m4.  It's a one liner.  Use sendmail -q to bump the queue into action when
  409 you connect, or as part of your ppp-on script.
  410 
  411 Oh, actually I am doing it with SLiRP, not TIA, but same thing...
  412 
  413 Cheers,
  414 
  415 -- Grant Bowman     <grantbow@netcom.com> 
  416 
  417 ________________________________________________________________________
  418 Question 3.6
  419 
  420 In article <3vn7vg$8s@seagoon.newcastle.edu.au> you wrote:
  421 : Hi all!
  422 : 	I'm currently trying to get an xterm window from the host machine 
  423 : to my computer. I've tried the -X option and setting the DISPLAY 
  424 : environment. When I type "xterm", I just get the I/O error 32. Broken 
  425 : pipe or something like that on X server. Does anyone know what I'm doing 
  426 : wrong?
  427 :
  428 : | Edmund Lai								|
  429 
  430 Okay...lets review what you have to do.
  431 
  432 First, in the .slirprc you have something like
  433 
  434 redir X IP  (where IP is the number of the system you are typing at, ie
  435              whatever your fake IP address is.  Slirp uses 10.0.2.15 
  436              by default.  That is as good a choice as any unless you
  437              have other reasons to change it.)
  438 
  439 Okay...next. IS YOUR X SERVER UP and ALLOWING REMOTE CONNECTIONS on
  440 your home system?  If you are running linux at home, you need to say
  441 "xhost +"  to allow all hosts to access your screen.  Note - this IS
  442 potentially a security problem! This opens your system wide up to 
  443 intrusion.  On the other hand...do people know you have X and slirp
  444 running?
  445 
  446 Finally, you need to telnet over to the remote host and type what
  447 slirp told you to type in its' log on banner.  Something like
  448 "setenv DISPLAY HOSTIP:offset" where HOSTIP is the host's IP number
  449 and offset is the X socket offset from port 6000 that slirp 
  450 grabbed(see below).   
  451 
  452 Why do you have to do this you might ask...why isn't this number
  453 you home system's IP instead?  Good question, and one I asked the
  454 author before I stared at the code myself, and learned about unix
  455 sockets;-)  What slirp does with ANY port redirection is open
  456 up a unix socket, and start listening for traffic on that socket.
  457 So when you say redir X IP, what you are saying is listen on 
  458 port 6000(or 6000+ some number if 6000 is busy), and any 
  459 connections you see on that number forward over the SLIP link
  460 to the IP address I gave you.  
  461 
  462 That means that you need to tell X clients to look for the X
  463 server at a specific machine IP address:socket number to 
  464 connect to your server that is on the other end of the phone 
  465 line!  You do this by typeing "setenv DISPLAY HOSTIP:offset"
  466 which is a variable, DISPLAY, that all X clients are sensitive
  467 too.  
  468 
  469 Notice the offset.  This might be a little confusing also.  Slirp
  470 tries to grab socket 6000, but if the socket is already in use, 
  471 it'll increment the socket it's trying to listen too until it
  472 finds a free one.  So you might get 6007 as an example, if 6000-6006
  473 are already in use.  To set the display variable correctly you need
  474 to set the address to HOSTIP:7.  The X client is already smart 
  475 enough to add the 6000 base address.  
  476 
  477 Summary.  1) Set the redir X HOMEIP in slirprc
  478           2) Make sure that connecting hosts can access your server
  479              by getting the security right.
  480           3) Telnet to the host and do a setenv DISPLAY HOSTIP:offset
  481              corresponding to the slirp banner.
  482 
  483 That should get you up and running X!
  484 
  485 Good Luck,
  486 
  487 Steve Wilson 
  488 
  489 ________________________________________________________________________
  490 Question 3.7
  491 
  492 : What is  the new format for .slirprc commands?  What commands
  493 : are available on the control port? 
  494 
  495 Note that versions of SLIRP after version "O" have many changes.
  496  
  497 They require you to use a different, new format for [pty]exec in the
  498 "$HOME/.slirprc" file.  Here is the new format:
  499  
  500 SLIRP95c Usage: add ptyexec | ptyexec PROGRAM:[ADDRESS:]PORT
  501  
  502 The new formats, the use of the $HOME/.slirprc-0 file (executed _before_
  503 $HOME/.slirprc), and many other NEW features are clearly described in the
  504 docs/CONFIG file, which is included with the SLIRP95c package.
  505  
  506 There is a new HELP menu, with many options, here is what it looks like:
  507 --= SLIRP 95c help menu =--
  508  
  509 SLiRP command-line ready (type "help" for help).
  510 Valid commands:
  511 prompt               redir X              show X
  512 redir                baudrate             special addr
  513 control addr         host addr            add exec
  514 add ptyexec          add emu              shell
  515 debug                socket               log stats
  516 config               log start            dns
  517 help                 -h                   echo
  518 exec                 ptyexec              unit
  519 wait                 quit                 ppp
  520 -all                 -ac                  -am
  521 asyncmap             debugppp             -ip
  522 -mn                  -mru                 -pc
  523 +ua                  +pap                 -pap
  524 +chap                -chap                -vj
  525 -vjccomp             vj-max-slots         escape
  526 domain               mru                  mtu
  527 initiate-options     name                 user
  528 usehostname          remotename           auth
  529 proxyarp             login                lcp-echo-failure
  530 lcp-echo-interval    lcp-restart          lcp-max-terminate
  531 lcp-max-configure    lcp-max-failure      ipcp-restart
  532 ipcp-max-terminate   ipcp-max-configure   ipcp-max-failure
  533 pap-restart          pap-max-authreq      pap-timeout
  534 chap-restart         chap-max-challenge   chap-interval
  535 ipcp-accept-local    ipcp-accept-remote   bsdcomp
  536 -bsdcomp             papcrypt
  537 For more help type "help COMMAND" where command is either
  538 one of the above commands or a portion of a command.
  539  
  540 (Editors Note - This comes from the slirp .95c change log I believe)
  541 
  542 ________________________________________________________________________
  543 Question 3.8 
  544 
  545 in article <darkmarkDC5LEK.41n@netcom.com>says
  546 >i'm trying to get shell via telnet on slirp, without logging in again.
  547  
  548 1.a) Get the file:
  549  
  550     ftp://blitzen.canberra.edu.au/pub/slirp/extra/slirp.telnetd-b.tar.g
  551  
  552 1.b) extract and compile it like you did with Slirp
  553  
  554 1.c) place the binary into a directory that is in your path
  555  
  556  
  557 [ Note:
  558 [ Can anyone explain in detail what function slirp.telnetd
  559 [ adds to slirp? Does it provide the 'telnet protocol'?
  560 [ If so, what is contained in the telnet protocol - local echo?
  561 [ Xon/Xoff flow control?
  562  
  563  
  564 2) Add the following line to your .slirprc file (you may wish to pick
  565 another shell).  I use:
  566  
  567     shell /usr/local/bin/tcsh
  568  
  569  
  570 3) Add a line to your hosts file so you can telnet to your shell without
  571 having to use the IP number, if you like.  For example, my hosts file
  572 includes:
  573  
  574 #
  575 # Host file for use on winsock pc running TIA or SLiRP on shell account
  576 #
  577  
  578 # -- SLIP emulator names --
  579  
  580 10.0.2.15       PC-name
  581 10.0.2.2        emulator-host
  582 10.0.2.2        pop-server
  583 10.0.2.1        shell        <<<=== Add this line here
  584 10.0.2.1        smtp-server
  585 10.0.2.1        nntp-server news-server
  586  
  587 (Above is just an example - you may wish to call your services by other
  588 names.)
  589  
  590  
  591 [ For you TIA users wondering how to use tia with slirp IP numbers...
  592 [ my .tiarc:
  593 [
  594 [-n10.0.2.2
  595 [-r10.0.2.15:21
  596 [-p10.0.2.1:25 mailit
  597 [-p10.0.2.1:119 nntpd.xover
  598  
  599 4) If running Windows, setup an icon that passess the argument "shell" to
  600 your favorite telnet application.  Double-clicking that icon will connect
  601 you to the host and run a shell program.  I use:
  602  
  603      c:\winsock\ewan\ewan.exe shell
  604  
  605  
  606 5) Running another shell will not execute the commands in your .login
  607 file.  So, on your shell, move the commands alias, set, path, (everything
  608 non-login environment related) from .login to .cshrc (or whatever shell rc
  609 file you are using) so when you start up a new shell you will have things
  610 the way you are used to them.  You could also just put a 'source .login'
  611 in your .cshrc if you like.
  612  
  613 [ I'm don't really understand UNIX enough to know what
  614 [ gets passed in to child processes in UNIX -
  615 [ anyone what to jump in here?
  616  
  617  
  618 And I think you should be in business.  I hope I haven't forgotten
  619 anything.
  620  
  621 Bill                
  622 moseley@netcom.com  
  623 ________________________________________________________________________
  624 Question 3.9
  625 Alex Clamann (aclamann@vcu.edu) wrote:
  626 : Does anyone have instructions/hints as to how to use Windows 95
  627 : with SLiRP?
  628  
  629 Works great!
  630  
  631 1) Install TCP/IP under network in the control panel
  632 2) The numbers 10.0.2.0 is the default gateway under IP settings in the
  633    control panel
  634 3) The number of the local address is 10.0.2.115
  635 4) Set the DNS server to whatever slirp gives you, (the second and
  636    third on netcom as the first seems to change)
  637 5) under the win config the very last box needs to be checked. (note:
  638    this is second hand from a friend, and he can't remember what the box is
  639    called. :( )
  640 6) create a dialup network account, (it's an option in the dialup network
  641    program group)
  642 7) make sure to set the modem setup box and select <bring up dialog box
  643    after dialing>, (that lets you log in and start slirp.
  644 8) then set server type to PPP
  645 9) use the connect button and when the dialog box comes up, type in your
  646    name and password.
  647 10) run slirp with the -P switch (this tells slirp to use PPP)
  648 11) then press continue and win95 should tell you that you are connected.
  649  
  650 once the connection is running you can use the win/95 utils or the win/95
  651 version of the web browsers.  Note: Netscape 32bit is at www.netscape.com
  652 
  653                                                     jtessin@netcom.com
  654 
  655 (Editors Note - Another VERY detailed response to this question  
  656  is found below - I'd love to get feedback as to which I should 
  657  keep!!!!)
  658 
  659 >Are there instructions available on how to configure win95,slirp,Free
  660 >Agent, and Netscape?  And if so would someone post it or its address?
  661  
  662  Note:  The instructions below now accomodate multiple dial-ups by
  663  localizing the IP addresses to each dial-up entry, rather than making
  664  them global throughout the system.  Revisions have also been made for
  665  better clarity.
  666  
  667  The following are comprehensive instructions on getting Win95 to
  668  network over a dial-up using SLIP/PPP, with consideration for TIA &
  669  SLiRP.  These are specific to the CD release version (950r6) of Win95.
  670  These assume that you have a modem, a phone line, and have an Internet
  671  account with an ISP (Internet Service Provider).
  672  
  673  Info needed:  Your IP address (if static IP); your ISP's name, domain
  674  names, and IP addresses.
  675  
  676  Components needed:  Dial-Up Networking; DSCRIPT; TCP/IP.
  677  
  678  **Always select OK to close a settings screen and not the Close (X)
  679    button, or otherwise the changes you made will be ignored.
  680 
  681  ----------
  682  
  683  ADDING NEEDED COMPONENTS:
  684  
  685  To add Dial-Up Networking,
  686     Open Start | Settings | Control Panel | Network | Add | Adapter |
  687        Microsoft | Dial-Up Adapter.  Click OK.
  688     The Dial-Up Adapter should now be present in the Network window.
  689        Win95 will ask to restart system, don't restart just yet.
  690     Delete all other entries in the window (aside from the Dial-Up
  691        Adapter), by selecting them and clicking Remove.
  692  
  693  To add DSCRIPT,
  694     Open Start | Settings | Control Panel | Add/Remove Programs |
  695        Windows Setup | Have Disk.
  696     Enter [CD drive]:\ADMIN\APPTOOLS\DSCRIPT and press OK.
  697     [Note: DSCRIPT may not be present in the Win95 floppy disk version.]
  698  
  699  To add TCP/IP,
  700     Open Start | Settings | Control Panel | Network | Add | Protocol |
  701        Add | Microsoft | TCP/IP.  Click OK.
  702     You should now have the Dial-Up Adapter and TCP/IP icons in the
  703        Network window.  Win95 will ask to restart system.  Press No
  704        to keep on going.
  705     Select TCP/IP, and click on 'Properties'.  Select 'Gateway' tab.
  706        Enter  1.0.0.1, and press the Add button.
  707     Press OK's until you've closed the Network screen.
  708  
  709     After rebuilding its driver database, Win95 will again prompt you to
  710     restart the system.  Select No to keep on going.
  711  
  712 ----------
  713  
  714  MAKING A DIAL-UP ENTRY:
  715  
  716  Open Start | Programs | Accessories | Dial-Up Networking.  Win95 will
  717     activate the Make New Connection wizard.  Press Cancel for now.
  718  Select Connections (in the Dial-Up Networking folder menu) | Settings.
  719     Enable 'Redial' (retry = 99, 0 min 1 sec between retries).
  720     Select 'Don't prompt to use Dial-Up Networking'.  Press OK.
  721  
  722  Double-click on the Make New Connection icon.
  723  Enter name of the ISP for the top box (ex: Eskimo North).
  724  Select your modem from the list, or let Win95 autoselect your modem
  725     (if modem is not already set up).
  726  Select 'Configure' (modem)
  727     [General]
  728        Select max speed (I use 57600 for 28.8K, for typical 2:1
  729           compression ratio).  Click OK.
  730     [Connection]
  731        Enable 'Cancel the call if not connected within _60_ secs'
  732        Enable 'Disconnect a call if idle for more than _15_ mins'
  733  Click Next; enter the ISP's telephone access number when prompted
  734     (no area code, unless it is a long-distance call.)
  735  Click Next; enter a name for the dial-up entry (ex: Eskimo).
  736  Click Finish.  A connect icon for the ISP will appear in the folder.
  737  
  738  Right-click on the connect icon.  Select Properties | Server Type.
  739     Select SLIP, CSLIP, or PPP (use this for SLiRP or TIA 2.x) from
  740        the drop-down menu.
  741     Disable 'Log on to network'.
  742     Disable 'NetBEUI' and 'IPX/SPX Compatible'.
  743        [If you select SLIP or CSLIP, these will already be greyed out.]
  744     Click on 'TCP/IP Settings'.
  745        Select 'Specify name server address'.
  746           Enter the IP address(es) of the various domains of the ISP.
  747           (Ex: for Eskimo, enter 204.122.16.13 for main server,
  748           204.122.16.40 for tia server)
  749        If dynamic IP address, select 'Server assigned IP address'.
  750        If static IP address, select 'Specify an IP address' and enter
  751           your IP address, as provided to you by your ISP.
  752  
  753        If TIA or SLiRP, select 'Specify an IP address' and enter
  754           192.0.2.1 (anything you want, really) for IP address.
  755  
  756  You can drag the ISP icon you've just made out onto the desktop for
  757  quicker access.  Repeat this section for any additional dial-up entry
  758  you want to create.
  759  
  760  ----------
  761  
  762  MAKING A LOGIN SCRIPT:
  763  
  764  You've made a dialing connection icon for the ISP, but you need a
  765  script to get past the login and start SLIP/PPP/TIA.  DSCRIPT will
  766  handle this chore.
  767  
  768  Open Start | Programs | Accessories | Dial-Up Scripting Tool
  769  
  770  The dialing connection you've just made should be presented as an entry
  771  inside the Connections window.  Since it's the only entry, it should
  772  already be highlighted.  Click on 'Browse', and select one of the
  773  sample script (SCP) files for modification.  Then click on 'Edit' to
  774  modify the file to fit your ISP login.  Below is a sample script for
  775  Eskimo North:
  776  
  777  ; Eskimo North login script
  778  proc main
  779     transmit "^M"
  780     waitfor "Selection ==>"
  781     transmit "4^M"
  782     waitfor "login:"
  783     transmit "YourName^M"   ; replace with your login name
  784     waitfor "Password:"
  785     transmit "YourPasswd^M" ; replace with your password
  786     waitfor "bash$"         ; replace with your prompt
  787     transmit "tia -ppp^M"   ; use this for TIA 2.x
  788     ;transmit "slirp -b 57600 -P^M"  ; use this for SLiRP
  789     ;set ipaddr getip 2     ; use this for dynamic IP address
  790  endproc
  791  
  792  Save the script.
  793  Enable 'Start terminal screen minimized'.
  794    [For script debugging purposes, you can elect to disable the 'Start
  795    terminal screen minimized' option and/or enable the 'Step through
  796    Script' option.]
  797  Restart Win95.
  798  
  799  Note:  Accessing the SCRIPTER.HLP file may be problematic, as it has no
  800  accompanying .CNT (contents listing) file.  I wasn't able to access its
  801  Topics List, which means no access to the command syntax listing.  I
  802  ran the help file through an ASCII filter, and reconstructed the syntax
  803  listing after some reformatting.  If there is sufficient interest, I'll
  804  repost it as an addendum.  [The Plus! pack's "Internet Option" has the
  805  identical Dial-Up Scripting Tool as included in the base Win95 CD, but
  806  it has an accompanying SCRIPT.DOC which has the command syntax in it.]
  807  
  808  ----------
  809  
  810  TESTING THE SETUP:
  811  
  812  Double-click on the dialing-connection icon for the ISP, and click
  813  Connect.  (You don't have to enter your name/passwd, since you've
  814  already hardcoded it into the script file.  Be aware, however, that the
  815  scripts are saved in plain ASCII which may pose a security problem for
  816  multi-user setups).  If everything goes smoothly, you will get a
  817  Connect message.  (I've noted that with SLiRP, it takes as long as half
  818  a minute for the TCP/IP connect to be made after the SLiRP command is
  819  given to the host shell.)
  820  
  821  After the Connect message, minimize the window onto the TaskBar, and
  822  open up a DOS box.  Enter 'telnet [ISP domain name]' (ex: telnet
  823  eskimo.com) to connect to your ISP.  If telnet is successful, then the
  824  setup is good, and you are in business.
  825  
  826  Win95 also has some other command-line TCP/IP utils, the most important
  827  of which is FTP.EXE.  Between) telnet and ftp, you have the tools to
  828  acquire other winsock apps from the net to add to your stable.
  829  
  830  hpham@eskimo.com (Hoang Pham) 
  831 
  832 ________________________________________________________________________
  833 
  834 
  835 4.0 Emulator Performance
  836 
  837 Question 4.1
  838 
  839 SLiRP has become stable and the lock-up bug was finally fixed(?).
  840 I think it's time for new benchmark test on TIA and SLiRP. 
  841 
  842 (*** Well, seems like I will have to do another test in 2 weeks. 
  843 TIA 2.0 beta will be released in next month. I just got new TIA news.)
  844 
  845 Anyway,
  846 
  847 I performed a small benchmark test using ws_ftp. The method used is mostly
  848 the same as the previous test I did and posted here few month ago.
  849 
  850 I transferred file between UNIX host and local PC over serial line three
  851 times in each direction and averaged the speed (in Kbps).
  852 
  853 This time I could use the same Trumpet setting for both TIA and SLiRP,
  854 which means you can compare data of the two directly. Also, I used
  855 both compressed and non-compressed files in the tests.
  856 
  857 Let's show you the result first.
  858 
  859 
  860 WS_FTP.EXE (150944 byte, a binary executable)
  861 =============================================
  862 	TIA	SLiRP
  863 	SLIP	SLIP	CSLIP	PPP
  864 ---------------------------------------------
  865 Downld	18.06	17.31	18.53	18.45 (Kbps) 
  866 Upload	18.94	18.88	19.35	19.30
  867 =============================================
  868 
  869 WS_FTP.ZIP (117641 byte, ZIP compressed)
  870 =============================================
  871 	TIA	SLiRP
  872 	SLIP	SLIP	CSLIP	PPP
  873 ---------------------------------------------
  874 Downld	15.87	14.97	16.24	16.14 (Kbps)
  875 Upload	16.36	16.32	16.70	16.66
  876 =============================================
  877 
  878 What do you think? It's interesting, isn't it?
  879 
  880 * Actually, the result is not much different from the previous test.
  881 In the previous test, I used MTU of 552 for Slirp and I thought it
  882 made Slirp slower than TIA. However, Slirp is still slower than the
  883 TIA in SLIP. Slirp gave me *really* good result in CSLIP and PPP. 
  884 CSLIP is slightly faster than PPP but I think the difference has 
  885 become small. (Acutually, I lost the old result. ^^; Am I telling 
  886 you the truth?)
  887 
  888 * As a result of tcp_input.c fix, Slirp now works even if you don't
  889 use Passive mode in ws_ftp. However, you should always get faster
  890 transfer if you use Passive mode. This applies to TIA, too.  
  891 
  892  
  893 #####
  894 Here's hardware and software information:
  895 
  896 UNIX  -- SparcSun-4/280. SunOS-4.1.3
  897 PC    -- Toshiba T3400, i486SX-33MHz, 4MBram, Windows for Workgroups.
  898 Modem -- US Robotics WorldPort 14.4K PCMCIA Fax/Modem.
  899 
  900 WS-FTP version 95.06.11
  901 	Recv Bytes 4096
  902 	Send Bytes 1500
  903 	*Passive Mode* is used in all transferres.
  904 
  905 Trumpet Winsock version 2.1b 
  906 	MTU 1500, RWIN 4096, MSS 1460.
  907 	Baudrate 38400
  908 
  909 TIA version 1.04c (beta)
  910 
  911 Slirp version 0.9o (tcp_input.c fixed)
  912 			[.slirprc]
  913 	SLIP		CSLIP		PPP
  914 	************** 	**************	*****************
  915 	Baudrate 38400	Baudrate 38400	Baudrate 38400
  916 	mtu 1500	compress	ppp
  917 	mru 1500	mtu 1500	mtu 1500
  918 			mru 1500	mru 1500
  919 					asyncmap 00000000
  920 	**************	**************	*****************
  921 
  922 
  923 *** All Data ***
  924 
  925 ## TIA ##
  926 [SLIP]	ws-ftp.exe			ws-ftp.zip
  927 --------------------------------------	------------------------------
  928 	Down		Up		Down		Up
  929 	(Sec)	(Kbps)	(Sec)	(Kbps)	(Sec)	(Kbps)	(Sec)	(Kbps)  
  930 --------------------------------------	------------------------------
  931 1.	81.8	18.08	78.0	18.95	72.6	15.88	70.4	16.37
  932 2.	82.0	18.04	78.1	18.94	72.9	15.82	70.5	16.35
  933 3.	81.8	18.08	78.2	18.92	72.5	15.90	70.4	16.37
  934 --------------------------------------  ------------------------------
  935 Ave.	81.9	18.06	78.1	18.94	72.7	15.87	70.4	16.36
  936 --------------------------------------	------------------------------
  937 
  938 ## SLiRP ##
  939 [SLIP]	ws-ftp.exe			ws-ftp.zip
  940 --------------------------------------	------------------------------
  941 	Down		Up		Down		Up
  942 	(Sec)	(Kbps)	(Sec)	(Kbps)	(Sec)	(Kbps)	(Sec)	(Kbps)  
  943 --------------------------------------	------------------------------
  944 1.	85.6	17.28	78.4	18.88	77.3	14.92	70.7	16.31
  945 2.	85.5	17.31	78.5	18.84	77.0	14.98	70.6	16.32
  946 3.	85.4	17.33	78.2	18.91	76.8	15.02	70.6	16.32
  947 --------------------------------------  ------------------------------
  948 Ave.	85.5	17.31	78.4	18.88	77.0	14.97	70.6	16.32
  949 --------------------------------------	------------------------------
  950 
  951 
  952 ## SLiRP ##
  953 [CSLIP]	ws-ftp.exe			ws-ftp.zip
  954 --------------------------------------	------------------------------
  955 	Down		Up		Down		Up
  956 	(Sec)	(Kbps)	(Sec)	(Kbps)	(Sec)	(Kbps)	(Sec)	(Kbps)  
  957 --------------------------------------	------------------------------
  958 1.	79.8	18.53	76.4	19.36	71.0	16.24	69.0	16.70
  959 2.	79.8	18.53	76.5	19.33	71.0	16.24	69.0	16.70
  960 3.	79.8	18.53	76.4	19.36	71.0	16.24	69.0	16.70
  961 --------------------------------------  ------------------------------
  962 Ave.	79.8	18.53	76.4	19.35	71.0	16.24	69.0	16.70
  963 --------------------------------------	------------------------------
  964 
  965 
  966 ## SLiRP ##
  967 [PPP]	ws-ftp.exe			ws-ftp.zip
  968 --------------------------------------	------------------------------
  969 	Down		Up		Down		Up
  970 	(Sec)	(Kbps)	(Sec)	(Kbps)	(Sec)	(Kbps)	(Sec)	(Kbps)  
  971 --------------------------------------	------------------------------
  972 1.	80.1	18.46	76.6	19.30	71.5	16.12	69.2	16.66
  973 2.	80.3	18.42	76.6	19.30	71.4	16.15	69.2	16.66
  974 3.	80.1	18.46	76.7	19.29	71.3	16.16	69.2	16.66
  975 --------------------------------------  ------------------------------
  976 Ave.	80.2	18.45	76.6	19.30	71.4	16.14	69.2	16.66
  977 --------------------------------------	------------------------------
  978 
  979 That's all. (Hope I didn't make any stupid mistake.)
  980 
  981 Thanks.
  982 
  983 ---
  984 
  985 Masa. <msato@calstatela.edu>
  986 
  987 [Editors' note:  I think this one gets the best post of the week award!]
  988 ----------------------------------------------------------------------------
  989 
  990 5.0 Miscellaneous Problems/Solutions
  991 
  992 Question 5.1
  993 >                           LATEST INFORMATION
  994 >                  --------------------------------------
  995 >
  996 >  *  (21/6/94) I think I finally fixed the "locking-up" problem. Edit the
  997 >    file tcp_input.c and uncomment the lines:
  998 >    /* if (so->so_snd.sb_cc)
  999 >    * (void) tcp_output(tp);
 1000 >    */
 1001 >    This means you can use a low RWIN again, and still have it work (I
 1002 >    hope).
 1003 >  *  (5/6/94) Get version 0.9o, it should fix the nasty SunOS problem, as
 1004 >    well as others. This will be the last release for around a month or
 1005 >    two (provided I find no major bugs (again)), since a) I have tests
 1006 >    coming up, and b) I'm planning big changes/additions to slirp for the
 1007 >    next release (It'll probably be a BETA release, finally).
 1008 >
 1009 >  [Back To SLiRP Home Page] [Features] [danjo@blitzen.canberra.edu.au]
 1010 >
 1011 >                Copyright ©1995 Phase One WWW Publishing
 1012 
 1013 I tried out the code change and it seems to be working fine for me.
 1014 
 1015 I am now able to reduce my RWIN in trumpet back to 4 times my MTU and I have no lockups.
 1016 
 1017     o      _____         ||Jose Barandiaran | |joseb@twisto.compaq.com  |
 1018 ----------------------------------------------------------------------------
 1019 Question 5.2
 1020 
 1021 >sterns@rahul.net (Steven Stern) wrote:
 1022 >Hi,
 1023 >    I'm running Win95 (build 484) and just tried to run the 32 bit
 1024 >version of Netscape with no luck. I can't get DNS lookup to work.
 1025 >
 1026 >Is this combination possible or will it not work because Trumpet is
 1027 >not a 32 bit application ?
 1028 >
 1029 >BTW the 16 bit version works just fine !
 1030 >
 1031 >Steve
 1032 >                                                               ~~~
 1033 >                                                              (o o)
 1034 > ----------------------------------------------------------ooO--U--Ooo-----
 1035 > Steven Stern           email: sterns@rahul.net     
 1036 
 1037 
 1038 It seems that the 32-bit version of Netscape cannot communicate 
 1039 with a 16-bit TCP/IP stack.  However, you don't need to use 
 1040 Trumpet anymore.  Just use SLiRP with the -P or ppp option (for 
 1041 Point-to-Point Protocol).  On the Windows 95 end, you'll need 
 1042 to go into Dial-Up Networking in My Computer and define dialer 
 1043 "objects" for each of the numbers you wish to call on your 
 1044 server.  The default protocol is PPP and is set under Server 
 1045 Type.  You'll then need to set up a dummy IP address in either 
 1046 Network under Control Panel or on the object itself, if your 
 1047 build of Windows 95 supports that (which I think 484 does).  
 1048 There are a few other things, such as Name Servers and 
 1049 Gateways, but since you've already set up Trumpet, you'll know 
 1050 what to put in there.  You'll want to specify that Windows 95 
 1051 bring up the terminal window after dialing so that you can 
 1052 enter your login information.  This can be done in Server Type 
 1053 as well.  Don't worry about the login name and password in the 
 1054 dialer object; it can't be resolved anyway and you'll connect 
 1055 just fine when you enter it in your terminal window.  After 
 1056 entering your user ID and password and finally the SLiRP 
 1057 command line, you simply press F7 (Continue) and you're all 
 1058 set.  All of your winsock apps will work, 32-bit and 16-bit.
 1059 
 1060 If you have any trouble setting this up, let me know. Maybe I 
 1061 can help.  Just short on time at the moment.  
 1062 mailto:davidb@mordor.com
 1063 ----------------------------------------------------------------------------
 1064 Question 5.3
 1065 
 1066 whoa@netcom.com (arlene agcongay) wrote:
 1067 >
 1068 >hi, i just got SLiRP working for me the other day, but i have a
 1069 >question.  I'm using OS/2 Warp with SLIRP, and when i start it up,
 1070 >it tells me that my baud rate is 1200.  I would like to configure
 1071 >this part to a higher baud rate, but i don't know which file to
 1072 >edit.  What i've been doing is opening up another comm software like
 1073 >ZOC and have it initialize my modem to 38400.  but there has to be
 1074 >an easier way!  i'm a newbie to this, so please help me.. =)
 1075 >
 1076 >thanks in advance!!
 1077 >
 1078 >
 1079 >-arlene
 1080 >
 1081 >
 1082 
 1083 slirp -b 38400  will tell SLiRP to send and receive data from 
 1084 your provider's modem at 38,400 bits per second.  To receive 
 1085 the data at the fastest possible rate, you'll need to call a 
 1086 number that supports the highest transmission rate possible 
 1087 with your modem and be sure you are connecting at that speed.  
 1088 What concerns me is that SLiRP defaults to 9600 "baud" and 
 1089 should not be reporting 1200 unless you have explicitly 
 1090 requested it with the -b switch. Maybe you are misreading one 
 1091 of the other parameters, such as MTU?
 1092 
 1093 db
 1094 
 1095 ----------------------------------------------------------------------------
 1096 Qeustion 5.4
 1097 
 1098 [ Editors' note: I screwed up the request below...so added the one line
 1099   to get the context of the original question back.. Sorry 'bout that.]
 1100 >How does one get to a 
 1101 >unix shell using slirp.telnetd .. no one can answer this for me, it seems 
 1102 >and I haven't been able to find any documentation on the subject.. it's 
 1103 >rather frustrating. Thanks. E-Mail Please.
 1104 >
 1105 >--
 1106 > ______  
 1107 >( ____ \  rampage@ccnet.com	http://www.ccnet.com/~rampage	net-geek
 1108 
 1109 	Simple, in your .slirprc you have a line such as is mine for tcsh:
 1110 		shell /usr/local/bin/tcsh
 1111 Then (if 10.0.2.0 is your SPECIAL address as it is for me) you telnet from your
 1112 local machine to 10.0.2.1 to get a 'shell' on your remote machine.  In my case
 1113 I put a lines in /etc/hosts such as:
 1114 		10.0.2.0 slirp
 1115 		10.0.2.1 remote
 1116 so that I can 'telnet remote' to get a shell or 'telnet slirp' to talk to
 1117 SLiRP's command line.
 1118 
 1119 rdt
 1120                                                    mailto:rdt@realm.net    
 1121                                                or  mailto:rdt@kaiwan.com   
 1122 ----------------------------------------------------------------------------
 1123 Question 5.5
 1124 
 1125 On Sun, 25 Jun 1995 08:34:57 GMT Steven Stern (sterns@rahul.net) wrote in alt.dcom.slip-emulators:
 1126 : I'm running Win95 CSLIP with Slirp at the other end. After I start
 1127 : Slirp I get the following msg:
 1128 
 1129 : SLiRP Ready ... (autodetect SLIP/CSLIP, MTU 552, 9600 baud)
 1130 
 1131 : I'm using a 14.4 modem. Does the message above really says I'm only
 1132 : connected at 9600 ?
 1133 
 1134 : Before Win95 Cslip, I always got 14.4 connections with Trumpet !
 1135 
 1136 : Please help !
 1137 
 1138 You need to specify the baud rate on the command you use to start slirp,
 1139 like: 
 1140       slirp -b 14400 -c
 1141 
 1142 Ahmad
 1143 --
 1144 Ahmad Al-Nusif            | E-Mail: morpheus@kuwait.net                      |
 1145 -----------------------------------------------------------------------------
 1146 Question 5.6
 1147 
 1148 stew1117@netcom.com (stewart coulter) wrote:
 1149 >Hello, I am using Slirp version O, everything is running fine except the 
 1150 >news.  I have a netcom account and was told I need the file NNTPD, where 
 1151 >can I find this file and what type configuring do I have to do to the 
 1152 >slirp O program?  Please respond via email
 1153 
 1154 >From a directory in your path (probably either your home directory or ~/bin), 
 1155 do
 1156 
 1157   ln -s ~seligman/bin/nntpd
 1158 
 1159 Or, if you want your own copy (just in case), do
 1160 
 1161   cp -p ~seligman/bin/nntpd .
 1162 
 1163 This version, written by Scott Seligman, supports XOVER. The TIA version will 
 1164 also work with either TIA or Slirp. Find it at
 1165 
 1166   ~barryn/pub/nntpd
 1167 
 1168 These are on Netcom, of course, since they're only needed to emulate a normal 
 1169 NNTP server with Netcom's disk-based equivalent.
 1170 
 1171 To use this with Slirp, add the following line to your .slirprc file:
 1172 
 1173   add exec nntpd 10.0.2.1:119
 1174 
 1175 unless you use the TIA-style addresses, in which case you'd add
 1176 
 1177   add exec nntpd 192.0.2.3:119
 1178 
 1179 Lee Dobbs                     Milpitas CA            Voice: 408-946-7860
 1180 ldobbs@netcom.com                 USA                Fax:   408-262-9392
 1181 -----------------------------------------------------------------------------
 1182 Question 5.7
 1183 D. Henry (marbling@apk.net) wrote:
 1184 : In article <3sj8cs$j3e@metz.une.edu.au>, jzhou1@metz.une.edu.au (JUN ZHOU) says:
 1185 : >
 1186 : >Hello,
 1187 : >
 1188 : >I am trying to run Netscape and Eudora on a PC with a modem. I have installed
 1189 : >the Trumpet winsock and can loging manually from TCPMAN widows. However, when 
 1190 : >I try to run the wisock applications, the Tcpman is lunched and minimized but
 1191 : >the Netscape windows never pop up.
 1192 : >
 1193 : >Any help is highly appreciated
 1194 
 1195 
 1196 He-he. I used to make the same mistake when I just installed Trumpet 
 1197 Winsock. Here's the catch. If you select 'Manual Login' option from the 
 1198 Trumpet Winsock's Dialler menu, SLIP is automatically disabled. After you 
 1199 manually log in and start your SLIP emulation, don't forget to press the 
 1200 'ESC' key. It will enable SLIP, and Trumpet Winsock will start talking 
 1201 to your SLIP emulator. If you don't do so, Netscape window will never pop 
 1202 up...
 1203 I hope this helps.
 1204 
 1205 Regards,
 1206 Stan
 1207 
 1208 ----------------------------------------------------------------------------
 1209 Question 5.8
 1210 
 1211 In article <3t278g$46r@newsbf02.news.aol.com>,
 1212 rmpshaker2@aol.com (RmpShaker2) wrote:
 1213 >Hey guys, When I setup my network settings, my only server type is PPP. I
 1214 >don't have a PPP connection, I have a slip.  I tried configuring the damn
 1215 >thing, but I found NO option for slip anywheres. I went through all the
 1216 >help and found jack.  Does anyone know how to setup a SLIP?
 1217 >
 1218 >Thanks, Chris
 1219 
 1220 Unfortunately Win95 does not automatically set-up SLIP protocol, but it's 
 1221 quite easy.
 1222 
 1223 Go into control panel, then add/remove software, then Windows Setup, the Have 
 1224 disk, now browse for a file named RNAPLUS.INF, it's on the cd, in think in 
 1225 admin\apptools\slip, and that's it.  Now when you set up server you should 
 1226 have cslip and slip options
 1227 
 1228 ----------------------------------------------------------------------------
 1229 Question 5.9
 1230 browe@netcom.com (Bill Rowe) wrote:
 1231 >In article <stevewDB8u3p.FIv@netcom.com>, stevew@netcom.com (Steve Wilson)
 1232 >wrote:
 1233 >>When you start up a shell, you tie-up a certain amount of memory
 1234 >>with local defines...like the path you use to search for commands,
 1235 >>any special "environment variables," etc.  If you fork off another
 1236 >>shell via telnetd, it will inherit this same environment...what
 1237 >>Lee is saying is that you probably just get a link to this stuff
 1238 >>instead of taking up X amount of more memory...
 1239 >
 1240 >Are you saying with telnetd the path to my home directory is not
 1241 >available? If it is available, how could it not be taking memory? If it
 1242 >isn't available, this seems to me a good reason not to use telnetd to
 1243 >access my shell account. 
 1244 >
 1245 >Usually, if I telnet to my shell it is because I want to manipulate one or
 1246 >more files there. Lack of access variables which are defined at login such
 1247 >as $PATH would seem to make it significantly more difficult to do the
 1248 >usual things with a shell account.
 1249 
 1250 All the environment variables that were set by your login shell process 
 1251 *are* available to any subprocess. If the subprocess happens to be another 
 1252 shell, any reference to an unmodified environment variable just points back 
 1253 to the memory block attached to your login process. So, things like your 
 1254 path, term, prompt, shell, etc., don't have to be recopied -- they're 
 1255 already available.
 1256 
 1257 The situation is different, however, when you start up a shell from an 
 1258 intermediate process like telnetd. telnetd doesn't pass the environment 
 1259 variables to the shell, so it starts up with just the default subshell 
 1260 parameters. You have to tell it to do something extra. If your shell is one 
 1261 of the csh derivatives, you need to tell it to execute your .login file in 
 1262 addition to the usual .cshrc file. One way to do this is 
 1263 
 1264   exec csh -l
 1265 
 1266 which replaces the original telnet shell process with another one, but this 
 1267 time reading the .login file first. There are equivalents for the Bourne 
 1268 derivatives so that it executes your .profile first, but I don't remember 
 1269 what those are right now.
 1270 
 1271 By the way, the shell variables are only part of the environment memory 
 1272 usage. There is some environment memory dedicated by your host to keep track 
 1273 of your login process and all your subprocesses. This includes space for:
 1274 
 1275  All the open files
 1276  Access rights to files and processes
 1277  The working directory
 1278  The file creation mask
 1279  Values of resource limits
 1280  Signals to be ignored by the parent
 1281  Signals not to be ignored by the parent
 1282 
 1283 That's why it's still better for the host if you use a subshell through 
 1284 telnetd and then set your PATH, etc., than if you start a completely new 
 1285 login session.
 1286 
 1287 Does this help? Are we having fun yet? :)
 1288 
 1289 Lee Dobbs                     Milpitas CA            Voice: 408-946-7860
 1290 ldobbs@netcom.com                 USA                Fax:   408-262-9392
 1291 ----------------------------------------------------------------------------
 1292 Question 5.10
 1293 wmcbrine@clark.net (William McBrine):
 1294 > FTP-PM never connects when I use it under SLiRP. Pretty much everything 
 1295 > else works fine, including FTP and NcFTP, except of course ping. What's 
 1296 > the problem, and is there a fix?
 1297 
 1298 Well... You actually stated the problem yourself. Ping soesn't work,
 1299 and FTPPM uses PING. You can tell the IAK that PING is not available
 1300 by remarking the line starting with "icmp" in the file "protocol"
 1301 thats the fix).
 1302 
 1303 /Jonas
 1304 Jonas Eckerman                    FSDB
 1305 jpe@algonet.se    www.algonet.se/~jpe/
 1306 
 1307 ----------------------------------------------------------------------------
 1308 Question 5.11
 1309 
 1310 Editors' Note:  This question is slightly out of date.  Tia 2.0 is
 1311 available now...but the discussion is still relevant.
 1312 
 1313 In article <DBDL0D.Ltu@dorsai.org>, Mike Russo <stardate@dorsai.org> wrote:
 1314 >At least, that's how I got TIA to work. I hope either TIA 2.0 or the 
 1315 >next SLiRP will support this protocol, along with PPP (and maybe automatic 
 1316 >port redirection? in my dreams?) =)
 1317 
 1318 PPP is in TIA 2.0 (as is CSLIP).  It is working even as I type this,
 1319 but we've not released TIA 2.0 yet, so I can't say more at this time.
 1320 
 1321 The others are tough nuts to crack, so let me address them one at a
 1322 time.
 1323 
 1324 The ICMP protocol is simple and easily implemented.  However, there is
 1325 one minor problem (or major depending on who you are): root access.
 1326 ping must be run by root to work (or be setuid uid 0).  TIA or SLiRP
 1327 would need to be installed setuid, which violates one of the prime
 1328 assumptions that at least TIA has: No extra ordinary privs should be
 1329 required to use TIA.  So ICMP could be implemented for the link, but
 1330 not forwarded to other machines.  TIA 1.x doesn't choose to do this.
 1331 TIA 2.0 likely won't either.  Creative solutions to this problem may
 1332 be possible, but I've not had time to fully investigate my ideas, so
 1333 I'll not speculate on them just now.
 1334 
 1335 Automatic port redirection is also hard.  When the TIA client[*] has a
 1336 program that wants to listen on a port, nothing happens over the wire.
 1337 Sure, buffer space gets allocated, the TCP stack's internal data
 1338 structures are setup, but no packets are sent over the link.  Since no
 1339 data flows accross the link, TIA (and SLiRP) have no way of knowing
 1340 that you desire to have a server or do port redirection.  Also, if TIA
 1341 or SLiRP were to try to do this, how could it inform you of the ports
 1342 that it chose for the servers you wish to run?  How would you know you
 1343 needed to connect to port 8456 to connect to your FTP server?  That's
 1344 why you need to tell TIA (and SLiRP) how to redirect the ports.
 1345 
 1346 I wish I could have told you that TIA 2.0 solves all the hard problems
 1347 that exist in your dream product, but I can't because some of them are
 1348 very hard nuts to crack.
 1349 
 1350 [*] A TIA client is the machine at the end of the point to point link
 1351     that isn't running TIA.
 1352 
 1353 Warner Losh		"VMS Forever"		home: imp@village.org
 1354 Cyberspace Development, Inc			work: imp@marketplace.com
 1355 ----------------------------------------------------------------------------
 1356 Question 5.12
 1357 
 1358 In article <3tqam6$lsv$1@mhafm.production.compuserve.com>, Jeff
 1359 Morganstern <102174.225@CompuServe.COM> wrote:
 1360 
 1361 > Can someone explain to me why (from an annex type server) I can use 
 1362 > rlogin to my unix account and slirp works fine, but if I telnet 
 1363 > there, it does not?  I'm able to get into my (free but far away) 
 1364 > unix account through a local gopher server, but it can only telnet 
 1365 > there.  In order to use the rlogin protocol, I need to dial up 
 1366 > directly (expensive).  Is there any way around this?
 1367 > 
 1368 > Thanks.
 1369 > 
 1370 > Jeff
 1371 
 1372 The reason is that rlogin is a much simpler program than telnet,
 1373 and is therefore more "transparent" in terms of not mucking about with
 1374 the characters that go through.
 1375 
 1376 For SLiRP to work, you need a relatively "clean" 8-bit connection.
 1377 Telnet may do any or all of the following.
 1378 
 1379 1. Strip out the eighth bit, leaving a 7-bit link.
 1380 2. Intercept certain characters, and translate them into telnet
 1381    escape sequences.
 1382 3. Break the link if it receives certain characters.
 1383 
 1384 That is not to say that it is impossible to get telnet to work.
 1385 Depending on the version of telnet you may be able to get an eightbit
 1386 link by either specifying it as an option (telnet -8), or by careful
 1387 settings on the machine you are telnetting from, for example,
 1388 
 1389 stty -parenb                ; no parity, 8-bit characters
 1390 stty crtscts                ; hardware flow-control
 1391 stty -ixon                  ; no XON
 1392 stty -istrip                ; don't strip off eighth bit
 1393                             ; what else?? mdmbuf?
 1394 
 1395 You may also need to use PPP so that you can "escape" the characters
 1396 that would telnet would intercept.
 1397 
 1398 There may be other things that need to be done.  I've been able to get
 1399 a connection established with slirp through a telnet link, but have not
 1400 gotten it to work satisfactorily, whereas rlogin works fine.  Your results
 1401 may differ.
 1402 
 1403 ---------------------------------------------------------------------
 1404 Question 5.13
 1405 
 1406 In article <1995Jul13.110622@acad.drake.edu>, jms015@acad.drake.edu
 1407 (Pilfered Publishing TM) wrote:
 1408 
 1409 > I login with ZTerm and quit without hanging up and then start InterSLIP
 1410 > on my Mac.  I load up telnet 2.6 and try the default as stated in the Home
 1411 > page "10.0.2.0".
 1412 
 1413 
 1414 I was never able to get the special "telnet 10.0.2.0" to work form my mac
 1415 using interslip, but it works using macppp.  At any rate, all the other
 1416 internet functions worked fine with both setups, although I highly
 1417 recommend macppp, as it is much faster.
 1418 
 1419 -- 
 1420 Marshall Levin <levin@cobalt.middlebury.edu>
 1421 
 1422 
 1423 -------------------------------------------------------------------
 1424 Question 5.14
 1425 
 1426 Daniel Ptacnik - BBMD/F94 (dptacnik@acs.ryerson.ca) wrote:
 1427 :
 1428 : I just got slirp to work properly. But I don't know what my pop mail (smtp)
 1429 : server is, is there a unix command that can tell you this info. Or 
 1430 : another other way of determining this. Any help is gladly appreciated. 
 1431 : Everthing else works fine like netscape, ftp, and irc. BTW I am using 
 1432 : slirp v.9o. Thanx again 
 1433 :
 1434 
 1435 First, are you sure that your service provider supports POP at all? The 
 1436 POP server would have to run on the same machine as your mailbox in order 
 1437 to work (not quite true, it could run on a machine that NFS mounts your 
 1438 mailboxes too). Since your email address is: dptacnik@acs.ryerson.ca
 1439 you would find out where your mail is delivered by looking for the DNS MX 
 1440 record for that address: dig acs.ryerson.ca mx
 1441 
 1442 	;; ANSWERS:
 1443 	acs.ryerson.ca. 843     MX      10 hopper.acs.ryerson.ca.
 1444 
 1445 Next, find out if there is a POP server running on this host by telneting 
 1446 to port 110 (POP3) or port 109 (POP2) and see what you get:
 1447 
 1448 	telnet hopper.acs.ryerson.ca 110
 1449 	Trying 141.117.101.8...
 1450 	Connected to hopper.acs.ryerson.ca.
 1451 	Escape character is '^]'.
 1452 	+OK hopper.acs.ryerson.ca POP3 3.3(18) w/IMAP2 client (Comments to 
 1453 	MRC@CAC.Washington.EDU) at Thu, 13 Jul 1995 15:10:16 -0400 (EDT)
 1454 
 1455 You're in luck, your MX host has a POP3 server running (looks like the 
 1456 POP server that comes with Pine, since it mentions IMAP too). Close this 
 1457 connection by pressing control-backbracket and entering "close" at the 
 1458 telnet prompt, don't just break the connection, it isn't nice.
 1459 
 1460 Now you are ready to enter this information into your POP client:
 1461 
 1462 	POP host: hopper.acs.ryerson.ca
 1463 	SMTP host: hopper.acs.ryerson.ca
 1464 
 1465 Have fun.
 1466 
 1467 --
 1468 | John Lucas                          jlucas@uvi.edu                 |
 1469 
 1470