Hi -- Sorry for my delay in replying. My comments are found below:
At 8:58 PM +0200 7/31/98, Thomas Michalka wrote:
>We should compare these as quickly as possible, because I'm really sad about
>that I cannot reach the Internet via diald (version 0.14) anymore; it
>
The current version of diald is 0.16 and if you are using the newest gnu
compilers you need to look on the diald web page for the the 0.16.5 update.
>
>It would also be useful if we exchanged our relevant network config files, but
>not on the list and for now I want to mail this quickly!
>
My config files are attached at the end of the message.
>I don't know much about IP masquerading but if having system addresses which
>differ from that of the ppp-device when connected to the ISP (dynamic
>assignment) then I can say that mine works fine together with running the
>ppp-demon.
>
IP masquerading uses IP firewall protection to allow a single externally
assigned ip address to be shared by systems inside the firewall. Under
Linux it is necessary to set a flag in the ip_dynaddr file (see the lines
from my rc.local below).
>
>Have you watched, after typing 'route', the output a bit longer?
>At my system it takes nearly a minute to get one line, then a minute again and
>so on. But you're right, it obviously hangs (the same with 'netstat -r').
>Typing 'netstat -rn' results in a fast output, so I had the suspicion of
>having
>to do with name resolving, but I do not longer believe in.
>The same on my system with 'ifconfig' as on yours.
My route resolution problem was casued mainly by a redundant 'defaultroute'
option. This should not appear in /etc/ppp/options but in /etc/diald.conf
(when diald is to be used).
>
>> So it appears that my diald configuration successfully makes the "connect"
>> and sets up the "bogus" slip interface. But it screws up the routing. IP
>> forwarding is on.
>
>Yes, this observation coincides with mine too.
>
>May be a problem within diald itself or a bad interference with kernel code.
>But whatever it is, I think it must be something basic as we independently
>watched this on different systems.
>Have other people watched a similar strange behavior?
>
>Where do you make the difference to your observation (above) by typing
>'route'?
>I do nearly get no routing table, at least very slow output without a ppp0
>device to see.
My route resolution problem was casued mainly by a redundant 'defaultroute'
option. This should not appear in /etc/ppp/options but in /etc/diald.conf
(when diald is to be used).
>
>
>> (To keep bandwidth down, please feel free to mail me directly rather than
>> respond to the list.)
>I think this phenomenons around diald may become so important that we should
>keep the dialog on the list.
>
Files:
>From my rc.local file:
# Set up ip masquerade
echo "setting up ip masquerde"
/sbin/depmod -a
#order ppp modules
/sbin/modprobe /lib/modules/2.0.34/net/slhc.o
/sib/modprobe /lib/modules/2.0.34/net/ppp.o
/sbin/modprobe /lib/modules/2.0.34/net/bsd_comp.o
#load IP masq modules
/sbin/modprobe ip_masq_ftp.o
/sbin/modprobe ip_masq_raudio.o
/sbin/modprobe ip_masq_irc.o
echo "setting up permissions for 192.168.1.0 domain"
/sbin/ipfwadm -I -f #flush old rule
/sbin/ipfwadm -O -f #flush old rule
/sbin/ipfwadm -F -f #flush old IP forward entries
#accept any i/o unless otherwise denied
/sbin/ipfwadm -I -p accept
/sbin/ipfwadm -O -p accept
/sbin/ipfwadm -F -p deny #default deny to keep out crackers
#Following for no diald operation
#allow packets from anywhere to dest on local net
#/sbin/ipfwadm -F -i accept -S 0.0.0.0/0 -D 192.168.1.0/24 -W eth0
#set up IP masq for packets from local net to dest anywhere
#/sbin/ipfwadm -F -a m -S 192.168.1.0/24 -D 0.0.0.0/0 -W ppp0
#Following for use with diald
/sbin/ipfwadm -F -a m -S 192.168.1.0/24 -D 0.0.0.0/0
echo "1" > /proc/sys/net/ipv4/ip_forwarding #start IP forwarding
echo "1" > /proc/sys/net/ipv4/ip_dynaddr #dynamic address flag (1 for
#normal, 5 to clear socket)
#start diald
echo "starting diald"
my /etc/diald.conf file
mode ppp
connect "/usr/sbin/chat -f /etc/sysconfig/network-scripts/chat-ppp0"
device /dev/cua0
speed 115200
modem
lock
crtscts
local 192.168.1.20
remote 192.168.1.21
dynamic
defaultroute
include /usr/lib/diald/standard.filter
#following are for local timing issues
impulse 600,30 #keep link up for 10 min and probe 30 sec before drop
redial-timeout 5
start-pppd-timeout 15
retry-count 1
redial-backoff-start
#following is for dctl
#fifo /etc/diald/diald/ctl
my /etc/sysconfig/network-scripts/ifcfg-ppp0:
PERSIST="no"
DEFROUTE="no"
ONBOOT="no"
INITSTRING="AT&F&D2&C1X4V1Q0S6=3S7=70&M4&B1&H1&R2M0"
MODEMPORT="/dev/cua0"
LINESPEED="115200"
ESCAPECHARS="no"
DEFABORT="yes"
HARDFLOWCTL="yes"
DEVICE="ppp0"
PPPOPTIONS=""
DEBUG="yes"
PAPNAME="rlpcon"
REMIP=""
IPADDR=""
BOOTPROTO="none"
MTU=""
MRU=""
DISCONNECTTIMEOUT="5"
RETRYTIMEOUT="0"
USERCTL="yes"
NETMASK="255.255.255.0"
Note that the use of a correct modem string is important.
--dick peskin
=================================
R. L. Peskin, Rutgers Univ. ; <[EMAIL PROTECTED]>;
<http://www.caip.rutgers.edu/~peskin>
VT Phone (802) 824-4558 NJ Phone (732) 445-4208
"The corporate culture is concerned less with Occam's razor than his
aftershave lotion."
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
