[2070] in linux-net channel archive
Re: Diald doesn't work with 1.3.72
daemon@ATHENA.MIT.EDU (Eric Schenk)
Thu Mar 14 03:27:41 1996
To: kev@primenet.com
cc: linux-net@vger.rutgers.edu, linux-diald@vger.rutgers.edu
In-reply-to: Your message of "Wed, 13 Mar 1996 00:51:55 EST."
<199603130551.WAA01164@redrock.lan>
Date: Wed, 13 Mar 1996 01:10:31 -0500
From: "Eric Schenk" <schenk@cs.toronto.edu>
Kevin Buettner <kev@primenet.com> writes:
>> These bugs together hose anyone who is using dynamic PPP or SLIP,
>> and anyone who sets things like "remote 127.0.0.3" in their diald options.
>> If you must have things working before I can figure out the necessary
>> fixes for the last bug, make sure that you use the "reroute" option,
>> and set your "remote" address correctly!
>
>I can't set my "remote" address correctly because it is dynamic. OTOH,
>my local address is static. Should I still specify the dynamic option
>or not?
You don't need it, but the remote address won't show up in your
routing tables if you don't use it. For dynamic remote addresses
this is mostly an esthetic choice.
For the moment you must use the "reroute" option (which was broken
in diald-0.12) with kernel versions 1.3.7[2-3]. This is fixed
in 0.13, which I will try to release tomorrow.
The need for the reroute option may go away if I can figure out
why the 1.3.7[2-3] kernels don't allow SOCK_PACKET packets to
be forwarded on ppp devices. I suspect this will be a kernel
side patch though, so we'll probably have to wait for the
patch to appear in the kernel sources (once one of us figures
out what the patch should be!)
-- eric
---------------------------------------------------------------------------
Eric Schenk www: http://www.cs.toronto.edu/~schenk
Department of Computer Science email: schenk@cs.toronto.edu
University of Toronto
