The tap errors in your log can be ignored as long as you have slip compiled into the
kernel.
----------
From: Joerg Friedrich[SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, 15 March 2000 23:19
To: linux-diald
Subject: Diald doesen't dial any more after swithching to the ethertap-device
Hi!
I switched to diald 0.99.1 and now diald wants to use the ethertap-device.
This seems to be a problem. diald doesn't receive any packets when
offline. I cat force diald to dial by writing 'up' or 'force' to the fifo.
then the link will come up and work, but when the link is down no packet
will get diald to bring it up.
can anyone help?
My system:
Debian 2.1 (slink)
Kernel 2.2.14
Ethertap-Device-Support compiled in the kernel (not as module)
I created all tap-devices:
<root:/root># ls -la /dev/tap*
crw-rw---- 1 root dialout 36, 16 Mar 15 13:30 /dev/tap0
crw-rw---- 1 root dialout 36, 17 Mar 15 13:30 /dev/tap1
crw-rw---- 1 root dialout 36, 26 Mar 15 13:31 /dev/tap10
crw-rw---- 1 root dialout 36, 27 Mar 15 13:31 /dev/tap11
crw-rw---- 1 root dialout 36, 28 Mar 15 13:31 /dev/tap12
crw-rw---- 1 root dialout 36, 29 Mar 15 13:31 /dev/tap13
crw-rw---- 1 root dialout 36, 30 Mar 15 13:31 /dev/tap14
crw-rw---- 1 root dialout 36, 31 Mar 15 13:31 /dev/tap15
crw-rw---- 1 root dialout 36, 18 Mar 15 13:31 /dev/tap2
crw-rw---- 1 root dialout 36, 19 Mar 15 13:31 /dev/tap3
crw-rw---- 1 root dialout 36, 20 Mar 15 13:31 /dev/tap4
crw-rw---- 1 root dialout 36, 21 Mar 15 13:31 /dev/tap5
crw-rw---- 1 root dialout 36, 22 Mar 15 13:31 /dev/tap6
crw-rw---- 1 root dialout 36, 23 Mar 15 13:31 /dev/tap7
crw-rw---- 1 root dialout 36, 24 Mar 15 13:31 /dev/tap8
crw-rw---- 1 root dialout 36, 25 Mar 15 13:31 /dev/tap9
when offline:
<root:/root># ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:40903 errors:0 dropped:0 overruns:0 frame:0
TX packets:40903 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
tap0 Link encap:Ethernet HWaddr FE:FD:00:00:00:00
inet addr:192.168.0.1 Bcast:0.0.0.0 Mask:255.255.255.0
UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2193 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
<root:/root># route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 tap0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 tap0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 tap0
when online:
<root:/root># ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:40910 errors:0 dropped:0 overruns:0 frame:0
TX packets:40910 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
ppp0 Link encap:Point-to-Point Protocol
inet addr:195.226.102.103 P-t-P:195.226.96.232
Mask:255.255.255.0
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
<root:/root># route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
195.226.96.232 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
195.226.96.0 0.0.0.0 255.255.255.0 U 0 0 0 ppp0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0
<root:/root># cat /etc/diald/diald.options
# /etc/diald/diald.options
#
# $Id: diald.options,v 1.8 1996/12/08 20:33:01 gv Exp $
#
# Sample diald.options -- works for PPP links and fixed IP
#
# Edit to match your set up.
#
# This is the port the modem is connected to.
# *** MODIFY to match your set up ***
# See the file /usr/doc/diald/debian.device.gz for discussion about
# the use of /dev/ttyS? instead of /dev/cua?.
device /dev/ttyS1
# diald log file: do not change.
accounting-log /var/log/diald.log
# diald monitoring pipe: do not change.
fifo /var/run/diald/diald.fifo
# This turns on full debugging.
debug 31
# We have PPP
mode ppp
local 192.168.0.1
# IP number for the provider's machine. This is different each time we connect.
# This is not a problem, but it'll make the routine table look funny.
remote 192.168.0.2
netmask 255.255.255.0
dynamic
# If the connection gets broken from the ISP, redial only
# if there's outgoing traffic from our side.
two-way
# When the link's up, change routes to point to the real link
# instead of the proxy.
reroute
# diald should set a default route to the proxy SLIP link.
defaultroute
# These two scripts must be executable.
ip-up /etc/ppp/ip-up
ip-down /etc/ppp/ip-down
# Scripts used to bring up/shut down the serial line.
connect "/etc/diald/connect"
# disconnect "/usr/bin/poff" #"/etc/ppp/ppp-disconnect"
# Do UUCP locking.
lock
# We connect through a modem.
modem
crtscts
# Local tweaking
connect-timeout 60
redial-timeout 10
dial-fail-limit 10
died-retry-count 10
# Dutch PTT timetable: same charge for 2.5 (peak) 5 (night) minutes.
# restrict 09:00:00 21:00:00 0-6 * *
# down
restrict * * * * *
include /etc/diald/standard.filter
<root:/root># cat /etc/diald/connect
#!/bin/sh
# Copyright (c) 1996, Eric Schenk.
# Copyright (c) 1997, 1998 Philippe Troin <[EMAIL PROTECTED]> for Debian GNU/Linux.
#
# $Id:$
#
# This script is intended to give an example of a connection script that
# uses the "message" facility of diald to communicate progress through
# the dialing process to a diald monitoring program such as dctrl or diald-top.
# It also reports progress to the system logs. This can be useful if you
# are seeing failed attempts to connect and you want to know when and why
# they are failing.
#
# This script requires the use of chat-1.9 or greater for full
# functionality. It should work with older versions of chat,
# but it will not be able to report the reason for a connection failure.
# Configuration parameters
# When debugging a connection, set DEBUG to -v to increase chat's
# verbosity and to report on this script's progress.
# WARNING: THIS MIGHT CAUSE YOUR PASSWORD TO SHOW UP IN THE SYSTEM LOGS
# DEBUG=-v
# The initialization string for your modem
MODEM_INIT="ATZ"
# The phone number to dial
PHONE_NUMBER="xxxxxxx"
# If the remote system calls you back, set to 1; otherwise leave to 0.
CALLBACK=0
# If you authentify using PAP or CHAP (that is let pppd handle the
# authentification, set this to 0.
AUTHENTIFY=0
# The chat sequence to recognize that the remote system
# is asking for your user name.
USER_CHAT_SEQ="name:--name:--name:--name:--name:--name:--name:"
# The string to send in response to the request for your user name.
USER_NAME="USER"
# The chat sequence to recongnize that the remote system
# is asking for your password.
PASSWD_CHAT_SEQ="word:"
# The string to send in response to the request for your password.
PASSWORD="PASSWORD"
# The prompt the remote system will give once you are logged in
# If you do not define this then the script will assume that
# there is no command to be issued to start up the remote protocol.
PROMPT="annex:"
# The command to issue to start up the remote protocol
PROTOCOL_START="ppp"
# The string to wait for to see that the protocol on the remote
# end started OK. If this is empty then no check will be performed.
START_ACK="Switching to PPP."
# Pass a message on to diald and the system logs.
message () {
if [ "$DEBUG" != "" ]
then
[ "$FIFO" != "" ] && echo "message $*" >$FIFO
logger -p local2.info -t connect "$*"
fi
}
# Initialize the modem. Usually this just resets it.
message "Initializing Modem"
chat $DEBUG TIMEOUT 5 "" "$MODEM_INIT" TIMEOUT 45 OK ""
if [ $? != 0 ]; then
message "Failed to initialize modem"
exit 1
fi
# Dial the remote system.
message "Dialing system"
chat $DEBUG \
TIMEOUT 45 \
ABORT "NO CARRIER" \
ABORT BUSY \
ABORT "NO DIALTONE" \
ABORT ERROR \
"" "ATB40&K44DI$PHONE_NUMBER" \
CONNECT ""
case $? in
0) message Connected;;
1) message "Chat Error"; exit 1;;
2) message "Chat Script Error"; exit 1;;
3) message "Chat Timeout"; exit 1;;
4) message "No Carrier"; exit 1;;
5) message "Busy"; exit 1;;
6) message "No DialTone"; exit 1;;
7) message "Modem Error"; exit 1;;
*)
esac
# Return here if the script doesn't handle authentification (pppd should).
if [ "$AUTHENTIFY" == 0 ]; then
exit 0
fi
# We're connected try to log in.
message "Logging in"
chat $DEBUG \
TIMEOUT 5 \
"$USER_CHAT_SEQ" "\\q$USER_NAME" \
TIMEOUT 45 \
"$PASSWD_CHAT_SEQ" "$PASSWORD"
if [ $? != 0 ]; then
message "Failed to log in"
exit 1
fi
# Wait eventually for callback
if [ "$CALLBACK" != 0 ]; then
message "Waiting for callback"
chat $DEBUG \
TIMEOUT 20 \
RING ATA
if [ $? != 0]; then
message "Remote system did not call back"
exit 1
fi
fi
# We logged in, try to start up the protocol (provided that the
# user has specified how to do this)
if [ "$PROMPT" != "" ]; then
message "Starting Comm Protocol"
chat $DEBUG TIMEOUT 15 "$PROMPT" "$PROTOCOL_START"
if [ $? != 0 ]; then
message "Prompt not received"
exit 1
fi
fi
if [ "$START_ACK" != "" ]; then
chat $DEBUG TIMEOUT 15 "$START_ACK" ""
if [ $? != 0 ]; then
message "Failed to start Protocol"
exit 1
fi
fi
# Success!
message "Protocol started"
--
Heute ist nicht alle Tage, ich komme wieder, keine Frage!!!
Joerg
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
