tlug: mouse fixed; now what about email

[Kei Furuuchi <kfur@example.com>]

Stephen J. Turnbull writes:

 > If you're talking about a phone connection via ppp, this should be set
 > up by installing the relevant package from `dselect'.  (Although I
 > believe that's already installed in the base system.)  If that doesn't
 > set up automatically, then you need to edit /etc/ppp.chatscript and
 > maybe /etc/ppp.options.
 > 
 > I will admit that TurboLinux set up diald very nicely; it's a damn
 > shame that the last thing I need is diald coming up automatically at
 > boot, stealing the phone line, and stomping on the ethernet gateway I
 > want configured ;-) But that's my fault for not being a typical luser,
 > right, Scott?

If you are going to use diald, you have to reconfig kernel to set slip 
too. After that, diald uses a script called /etc/diald/diald.options,
which reads like this:
    fifo /var/run/diald/diald.fifo
    mode ppp
    connect "sh /etc/diald/connect"
    device /dev/ttyS1
    speed 115200
    modem
    two-way
    impulse 600,20
    mru 552
    mtu 552
    lock
    crtscts
    local 192.168.1.1
    remote 192.168.1.2
    dynamic
    defaultroute
    pppd-options asyncmap 0
    redial-timeout 0
    include /etc/diald/standard.filter

Then, it is /etc/diald/connect script that makes dial out and log in.
In the script, chat is used. So I recommend placing "-v" argument
after chat to monitor what chat is doing at /var/log/messages. This
gives you enough idea to change connect script accordingly. Also you
can set "debug" and "kdebug" options in /etc/ppp/options to monitor
what pppd is doing at /var/log/messages too. If there is no log in
sequence in connect script, there have to be pap or chap authorization 
sequence in pppd. So you have to set "name" option in /etc/ppp/options 
and set your password in pap-secrets or chap-secrets file.
those files read like this:
in /etc/ppp/options:
        name myusername

in /etc/ppp/pap-secrets:
        myusername * mypassword

Then set nameserver in /etc/resolv.conf.
/etc/resolv.conf reads like this:

     nameserver 206.165.5.10
     nameserver 206.165.50.10
     
temporarily you  use ISP's nameservers. 
Then start diald. ping nameserver to see if diald starts calling.
To monitor, "tail -f /var/log/messages" read like this:
      
     May 30 09:27:57 conner connect: Initializing Modem
     May 30 09:27:58 conner connect: Dialing system
     May 30 09:28:20 conner connect: Connected
     May 30 09:28:20 conner connect: Loggin in
     May 30 09:28:22 conner connect: Protocol started
     May 30 09:28:22 conner diald[108]: Running pppd (pid = 350).
     May 30 09:28:22 conner pppd[350]: pppd 2.2.0 started by root, uid 0
     May 30 09:28:22 conner pppd[350]: Using interface ppp0
     May 30 09:28:22 conner pppd[350]: Connect: ppp0 <--> /dev/ttyS1
     May 30 09:28:26 conner pppd[350]: local  IP address 207.218.63.157
     May 30 09:28:26 conner pppd[350]: remote IP address 207.218.32.42
     May 30 09:28:26 conner diald[108]: New addresses: local 207.218.63.157, remote 207.218.32.42.

This changes how you set debug options.
Then ifconfig read like this:
     lo        Link encap:Local Loopback  
               inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
               UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
               RX packets:83 errors:0 dropped:0 overruns:0
               TX packets:83 errors:0 dropped:0 overruns:0
     
     eth0      Link encap:10Mbps Ethernet  HWaddr 00:40:33:23:F3:38
               inet addr:192.168.0.7  Bcast:192.168.0.255  Mask:255.255.255.0
               UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
               RX packets:0 errors:0 dropped:0 overruns:0
               TX packets:0 errors:0 dropped:0 overruns:0
               Interrupt:10 Base address:0x300 
     
     sl0       Link encap:Serial Line IP  
               inet addr:192.168.1.1  P-t-P:192.168.1.2  Mask:255.255.255.0
               UP POINTOPOINT RUNNING  MTU:552  Metric:1
               RX packets:0 errors:0 dropped:0 overruns:0
               TX packets:15 errors:0 dropped:0 overruns:0
     
     ppp0      Link encap:Point-Point Protocol  
               inet addr:207.218.63.157  P-t-P:207.218.32.42  Mask:255.255.255.0
               UP POINTOPOINT RUNNING  MTU:552  Metric:1
               RX packets:74 errors:0 dropped:0 overruns:0
               TX packets:76 errors:0 dropped:0 overruns:0

Then you can use netscape at least to read and write mails.

In conclusion, I found this is easy. All I have to know is how to read 
scripts and how to monitor what programs do. It is easy to the point I 
can post the question nobody seems to know the answer about.
This is one of things I like about Linux.

Regards,
Kei.



--------------------------------------------------------------
Next TLUG Meeting: 13 June Sat, Tokyo Station Yaesu gate 12:30
Featuring Stone and Turnbull on .rpm and .deb packages
Next Nomikai: (?) July, 19:30 Tengu TokyoEkiMae 03-3275-3691
--------------------------------------------------------------
Sponsor: PHT, makers of TurboLinux http://www.pht.co.jp