SSLUG-msg00203.html

[an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive]

[an error occurred while processing this directive] [an error occurred while processing this directive]

	Home		Subscribe		Mail Archive		Forum		Calendar		Search
	Date:				Thread:

Yet another diald problem

To: sslug@sslug
Subject: Yet another diald problem
From: Steen Palm <sslug@sslug>
Date: Wed, 05 Apr 2000 23:40:37 +0200
Newsgroups: sslug.teknik
Organization: SSLUG

Min entre i Linux-verdenen skete med installation af Redhat 6.1. Derfor
var rp3 baseret på wvdial mit første valg for at etablere en forbindelse
til min ISP (CyberCity). Da jeg senere læste ppp-info.html på SSLUG's
hjemmeside implementerede jeg de to scripts, ppp-on og ppp-off, udfra
anvisningerne. De virker fint.

Nu er jeg så blevet opmærksom på diald som automatisk åbner og lukker
forbindelsen udfra nettrafik. Jeg har brugt man-page for diald-examples
som udgangspunkt for mit setup. Men det er bestemt ikke nemt at få diald
til at makke ret. Jeg har læst korrespondancen mellem Frank Damgaard og
Anders M (diald spørgsmål) og forsøgt at rette ind, men uden at det er
lykkedes.

Diald forsøger fint at åbne forbindelsen når jeg fx ping'er min ISP's
name server, men forbindelsen bliver aldrig oprettet, muligvis fordi
diald ikke kan finde /etc/ppp/pap-secrets. I hvert fald finder jeg
fejlbeskeden:

   Apr  5 22:54:26 localhost pppd[704]: The remote system is required to
authenticate itself but I
   Apr  5 22:54:26 localhost pppd[704]: couldn't find any suitable
secret (password) for it to use to do so.
 
i /var/log/messages. Ping hænger, men skriver dog en enkelt linie:

   sslug@sslug ping 212.242.40.3
   PING 212.242.40.3 (212.242.40.3) from 192.168.0.56 : 56(84) bytes of
data.

Jeg håber der er nogen der kan hjælpe mig lidt på vej. Som modem
benytter jeg en ISDN TA, ZyXEL Elite 2864I, og jeg har hverken fetchmail 
eller andre spændende server programmer kørende (såvidt jeg ved).

Hilsen
Steen

-----------------------------------------------------------------------------------

/etc/diald.config
------------------
debug 24

# General options
mode ppp
accounting-log /var/log/diald.log
fifo /etc/diald/diald.ctl

# Device configuration
device /dev/ttyS1
speed 115200
modem
lock
crtscts
#connect "/usr/bin/wvdial --remotename ppp0 --chat CyberCity"
connect /etc/ppp/chatscript
pppd-options user NNNNNN

# Network configuration
local 192.168.0.56
remote 192.168.0.57
#mtu 576
#mru 576
#window 2048
dynamic
defaultroute

# Timeouts
redial-backoff-start 4
redial-backoff-limit 300
dial-fail-limit 15

# Get the standard filter policy
include /usr/lib/diald/standard.filter



/etc/ppp/options
----------------
asyncmap 0

debug

novj
noccp
nobsdcomp
noaccomp
nodeflate
nopcomp
novjccomp


/var/log/messages
-----------------

Apr  5 22:54:01 localhost diald[678]: Using fifo /etc/diald/diald.ctl
Apr  5 22:54:01 localhost modprobe: can't locate module tap0
Apr  5 22:54:02 localhost modprobe: can't locate module tap1
Apr  5 22:54:02 localhost modprobe: can't locate module tap2
Apr  5 22:54:03 localhost modprobe: can't locate module tap3
Apr  5 22:54:03 localhost modprobe: can't locate module tap4
Apr  5 22:54:04 localhost modprobe: can't locate module tap5
Apr  5 22:54:04 localhost modprobe: can't locate module tap6
Apr  5 22:54:05 localhost modprobe: can't locate module tap7
Apr  5 22:54:05 localhost modprobe: can't locate module tap8
Apr  5 22:54:06 localhost modprobe: can't locate module tap9
Apr  5 22:54:06 localhost modprobe: can't locate module tap10
Apr  5 22:54:06 localhost modprobe: can't locate module tap11
Apr  5 22:54:07 localhost modprobe: can't locate module tap12
Apr  5 22:54:07 localhost modprobe: can't locate module tap13
Apr  5 22:54:08 localhost modprobe: can't locate module tap14
Apr  5 22:54:08 localhost modprobe: can't locate module tap15
Apr  5 22:54:09 localhost kernel: CSLIP: code copyright 1989 Regents of
the University of California 
Apr  5 22:54:09 localhost kernel: SLIP: version
0.8.4-NET3.019-NEWTTY-MODULAR (dynamic channels, max=256) (6 bit
encapsulation enabled). 
Apr  5 22:54:09 localhost kernel: SLIP linefill/keepalive option. 
Apr  5 22:54:09 localhost diald[678]: Proxy device established on
interface sl0
Apr  5 22:54:09 localhost diald[678]: start sl0: SIOCSIFMETRIC:
Operation not supported 
Apr  5 22:54:09 localhost diald[678]: Diald initial setup completed.
Apr  5 22:54:22 localhost diald[678]: Trigger: icmp    
192.168.0.56/257       212.242.40.3/257  

Apr  5 22:54:22 localhost diald[678]: Calling site 192.168.0.57 
Apr  5 22:54:23 localhost chat[703]: report (CONNECT)
Apr  5 22:54:23 localhost chat[703]: report (OK)
Apr  5 22:54:23 localhost chat[703]: report (BUSY)
Apr  5 22:54:23 localhost chat[703]: report (ERROR)
Apr  5 22:54:23 localhost chat[703]: report (NO CARRIER)
Apr  5 22:54:23 localhost chat[703]: report (NO DIALTONE)
Apr  5 22:54:23 localhost chat[703]: timeout set to 8 seconds
Apr  5 22:54:23 localhost chat[703]: send (ATZ1^M)
Apr  5 22:54:23 localhost chat[703]: expect (OK)
Apr  5 22:54:23 localhost chat[703]: ATZ1^M^M
Apr  5 22:54:23 localhost chat[703]: OK
Apr  5 22:54:23 localhost chat[703]:  -- got it 
Apr  5 22:54:23 localhost chat[703]: send (ATDI103333361333^M)
Apr  5 22:54:23 localhost chat[703]: abort on (NO CARRIER)
Apr  5 22:54:23 localhost chat[703]: abort on (BUSY)
Apr  5 22:54:23 localhost chat[703]: abort on (NO DIALTONE)
Apr  5 22:54:23 localhost chat[703]: abort on (WAITING)
Apr  5 22:54:23 localhost chat[703]: timeout set to 50 seconds
Apr  5 22:54:23 localhost chat[703]: expect (CONNECT)
Apr  5 22:54:23 localhost chat[703]: ^M
Apr  5 22:54:25 localhost chat[703]: ATDI103333361333^M^M
Apr  5 22:54:25 localhost chat[703]: CONNECT
Apr  5 22:54:25 localhost chat[703]:  -- got it 
Apr  5 22:54:25 localhost diald[678]: Connected to site 192.168.0.57 
Apr  5 22:54:25 localhost diald[678]: Running pppd (pid = 704).
Apr  5 22:54:26 localhost modprobe: can't locate module char-major-108
Apr  5 22:54:26 localhost kernel: PPP: version 2.3.7 (demand dialling) 
Apr  5 22:54:26 localhost kernel: PPP line discipline registered. 
Apr  5 22:54:26 localhost kernel: registered device ppp0 
Apr  5 22:54:26 localhost pppd[704]: The remote system is required to
authenticate itself but I
Apr  5 22:54:26 localhost pppd[704]: couldn't find any suitable secret
(password) for it to use to do so.
Apr  5 22:54:26 localhost diald[678]: start sl0: SIOCSIFMETRIC:
Operation not supported 
Apr  5 22:54:26 localhost diald[678]: start sl0: SIOCADDRT: File exists 
Apr  5 22:54:26 localhost diald[678]: start sl0: SIOCADDRT: File exists 
Apr  5 22:54:26 localhost diald[678]: start sl0: SIOCSIFMETRIC:
Operation not supported 
Apr  5 22:54:26 localhost diald[678]: start sl0: SIOCADDRT: File exists 
Apr  5 22:54:27 localhost diald[678]: start sl0: SIOCADDRT: File exists 
Apr  5 22:54:27 localhost diald[678]: Disconnected. Call duration 2
seconds. 
Apr  5 22:54:27 localhost diald[678]: IP transmitted 336 bytes and
received 0 bytes. 
Apr  5 22:54:27 localhost diald[678]: Closing /dev/ttyS1
Apr  5 22:54:28 localhost diald[678]: Delaying 30 seconds before clear
to dial.
Apr  5 22:54:57 localhost diald[678]: Calling site 192.168.0.57 
Apr  5 22:54:58 localhost chat[714]: report (CONNECT)
Apr  5 22:54:58 localhost chat[714]: report (OK)
...



/var/log/diald.log
------------------
Wed Apr  5 22:54:22 2000 CEST: Calling site 192.168.0.57.
Wed Apr  5 22:54:25 2000 CEST: Connected to site 192.168.0.57.
Wed Apr  5 22:54:27 2000 CEST: Disconnected. Call duration 2 seconds.
      IP transmitted 336 bytes and received 0 bytes.
Wed Apr  5 22:54:57 2000 CEST: Calling site 192.168.0.57.
...

Follow-Ups:
- Re: [TEKNIK] Yet another diald problem
  - From: Erling Jacobsen

Prev by Date: Re: [TEKNIK] Lydkort
Next by Date: Re: [TEKNIK] Samba og stabilitet, Morten Christensen
Previous by Thread: Re: [TEKNIK] LYDKORT UNDER LINUX
Next by Thread: Re: [TEKNIK] Yet another diald problem
Index(es)
- Date Index
- Thread Index

Home

Subscribe

Mail Archive

Index

Calendar

Search

Questions about the web-pages to <www_admin>.

Last modified 2005-08-10, 21:38 CEST [an error occurred while processing this directive]
This page is maintained by [an error occurred while processing this directive]MHonArc [an error occurred while processing this directive] # [an error occurred while processing this directive] *