On Sat, 26 Jun 1999, Denis Voitenko wrote:
> Okay, people. I have spend all night trying to get 0.99.1 or 0.16.5 getting
> to work on RH5.2 (2.0.36). 
> ...
> Here is the dump
> of my "route" when it is not connected:
> >>
> and here comes /etc/diald.conf

What is wrong is how you have initialized 'sl0' and 'sl1'. Your 'remote' IP
declared in 'diald.conf' should be in your own network, otherwise you don't
have a route to it. The idea is that when a packet comes to this address 'diald'
establishes the link. This address is managed as a SLIP connection.

Try the following steps (at least is how it has been working at my net in the
last 2 years):

1) In the /etc/sysconfig/network file check that you have the following
parameters:

NETWORKING=yes
FORWARD_IPV4=yes
HOSTNAME=linux
DOMAINNAME=homerubbe.xx
GATEWAY=
GATEWAYDEV=sl0

2) Check that '/etc/sysconfig/network-scripts/ifcfg-eth0 shows something like:

DEVICE=eth0
IPADDR=192.168.10.1
NETMASK=255.255.255.0
NETWORK=192.168.10.0
BROADCAST=192.168.10.255
ONBOOT=yes
BOOTPROTO=none

3) Add a ficticious address for diald in your /etc/hosts as if it was another
machine in your net, for instance:

        # Your server
        192.168.10.1       linux.homerubbe.xx  linux

        # Your diald ficticious address 
        192.168.10.200  diald.o3m.com diald

3) Restart the network (without any 'diald') and control that your LAN is
working OK. The network is restarted with:

        /etc/rc.d/init.d/network stop
        /etc/rc.d/init.d/network start

'route -n' should give you something like:

        Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
        192.168.10.1    0.0.0.0         255.255.255.255 UH    0      0        0 eth0
        192.168.10.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0
        127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo

4) I assume your ISP gives you a dynamic IP, so you don't need real local and
remote addresses. Your /etc/diald.conf should look like:

debug 127
mode ppp
connect /etc/diald/connect
device /dev/ttyS0
speed 115200
modem
lock
crtscts
local 192.168.10.1
remote 192.168.10.200
dynamic
defaultroute
include /usr/lib/diald/standard.filter

I did the following changes to your file:

- Added a full debug request
- I use the actual device directly, just to be sure (/dev/ttyS0 or /dev/ttyS1)
- The speed is the speed of the modem-computer link, not the modem-modem link
(that normally is negociated between modems depending on line conditions and the
modems, so it's none of your business). So, if you have a reasonable computer
115200 is ok.
- I put the host IP as 'local' and the ficticious IP as 'remote'.
- I added the 'dynamic' keyword. If your ISP gives you a fixed IP, just delete
the 'dynamic' line and use the 'local' you had in your example. 

5) Start diald with:
        diald

while you look what is happening in the log with (in a separate window or
console):

        tail -f /var/log/messages

6) I assume you don't have a real DNS on your net, so your '/etc/resolv.conf'
should use your ISP DNSs

7) Do:
        ping www.yahoo.com

On the log you should see how the communication is requested, the modem
answers, and finally the connection and login in your ISP net, receiving the
dynamic IP addresses.

With 'route -n' you should see the correct route through ppp0 once the link is
up.

If you came this far you have 'diald' up and running!

Carlos Vidal
[EMAIL PROTECTED]

-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]

Reply via email to