John F Feist wrote:
>
> First off, thank you too Jan for the great information. The system
> here is a dual Pentium Pro 200 running SMP, RedHat 5.1, kernel 2.0.34,
> Local slip IP 172.16.0.1, Remote slip IP 172.16.0.2, server IP 44.8.0.112
> and ISP IP XXX.XXX.XXX.XXX on a ascend server.
It may not matter, but I used slip addresses from 192.168.X.X, one of
the
official 'private, non routing' nets.
>
> I installed both diald-0.16.5a-1.i386.rpm and
> diald-config-0.16.5a-1.i386.rpm packages.
>
> I had to relocate my internal slip link (slattatch) and its routes to
> sl1. Seems that diald does not like to be run as sl1 but defaults to sl0.
> No problem with the relocation.
>
> Ran my ppp-on and ppp-off scripts making sure that everything still works
The official scripts are /sbin/ifup ppp0 (and ifdown)
to test the manual ppp0 setup, according to the docs I have seen.
These are what netcfg implements, and what is compatible with diald.
Your way may work fine, but it differs from what Jeff and I did, so
I don't know how to help you debug it. Knowing one working method
is enough for me.
> with the manual connection. I did get my dynamic local address and the
> default route was added to the ISP connection. Looks good! I had removed
> all the commands (with the exception of 'name xxxxxx' and 'login') from
> the /etc/ppp/options file. All the options commands for ppp reside in the
> /usr/sbin/ppp-on script.
>
> Configured diald.conf per doc's. I do have the triple nameserver lines in
> the resolve.conf to my local dns here. (actually its the same machine
> running named), added the echo 7 > /proc/sys/net/ipv4/ip_dynaddr to the
> init.d/networking file. Added both slip IP address's to the /etchosts
> file. edited the /etc/diald/connect script for the ISP phone number.
> edited the diald-on and diald-off scripts in the /usr/sbin dir to reflect
> the proper init line (diald vice diald.init). and tried the connection.
>
> I started diald and it installed a default route to:
> 0.0.0.0 0.0.0.0 0.0.0.0 sl0
> Ifconfig sl0 showed the proper IP information for the P-T-P link
> 172.16.0.1
> The remote sl0 address was included in the netstat -rn statement.
>
> I then tried a telnet app to the local ISP. I am required to run PAP for
> authentication. The modem dials up the connection and makes the PAP
> link. The system reports via a tail:
>
> CONNECT: ppp0 <--> /dev/ttyS1
> Remote message:
> Local IP address: 44.8.0.112
> Remote IP address: xxx.xxx.xxx.xxx (it was the correct ISP address on a
> ascend server)
> Linux diald New address : local 44.8.0.112, remote xxx.xxx.xxx.xxx
> Linux kernel: ip_rewrite_addr () shifting Saddr from 172.16.0.1 to
> 44.8.0.112 (state 2)
>
> Doing a netstat -rn show that I now have two default routes, one to sl0
> (initial diald slip link) and one for ppp0 to the correct ISP address.
That's normal.
> The link then times out due to inactive link and tries to redial in 10
> seconds.
There are lots of ways to configure the inactive timeouts in the
files diald uses. The default ones may be too short.
>
> What I don't see is the changing of the local IP address too the dynamic
> one provided by the ISP (as it does during the ppp manual link).
> Remember, everything is stripped from the /etc/ppp/options file with the
> exception of 'name' and 'login'.
I think /etc/ppp/options should have only one line: 'lock'.
Any other options you had there should move elsewhere.
The PAP login name and password secret belong in /etc/ppp/pap-secrets.
>
> When diald connects and makes the PAP exchange, does not the sl0 default
> path drop allowing the pppd default patch to be the single outgoing
> route?
When diald is running but not connected, it should have a default
route to sl0. When it IS connected, that route remains, and another
default route to ppp0 is added. The one to sl0 seems to be ignored,
and everything works.
>
> So close, I have tried various configurations and could use the third
> eye.
>
> Thank You in advance, Seasons Greetings to *ALL*, and best 73,
>
> John, AA6QN [44.8.0.32]
>
> [EMAIL PROTECTED]
If you have more difficulty, try using the GUIs per the directions.
The PPP configs that netcfg creates are compatible with diald.
Use netcfg to set up the ppp0 config from scratch.
Then you will have PPP configs that do not interfere
with DIALD configs and everything will work.
Once you do that, look at the configs that netcfg creates, and you
will see the conflict.
>
> ___________________________________________________________________
> You don't need to buy Internet access to use free Internet e-mail.
> Get completely free e-mail from Juno at http://www.juno.com/getjuno.html
> or call Juno at (800) 654-JUNO [654-5866]
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]
--
Jan Carlson
[EMAIL PROTECTED] Scarborough, Ontario, Canada
Mailed with Netscape 4.5 on Red Hat Linux 5.2
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
