Hi,

I've been hacking away at getting diald 0.99-3 to work on my RH 6.0 system.

I started with a working manually invoked ppp connection to my ISP.
I have a note and two questions about diald which is now _almost_ working.

First the note:

I copied the following line from /etc/ppp/options:

        connect "/usr/sbin/chat -f /etc/sysconfig/network-scripts/chat-ppp0"

To my /etc/diald.conf file as my connect script.

However, I discovered that I had to comment it out of the /etc/ppp/options file
to prevent diald from trying to log in twice.

I this because normally ppp was intended to be invoked the the -connect 
argument on the command line?  If so, I guess I understand this, it just 
took me a while to figure it out.

Well I now have diald so that it will create a connection when it 
is supposed to... but I get tons of errors on the ppp connection that 
I do not get when I connect  with with pppd.


 Feb  6 21:52:00 hostname pppd[2793]: Protocol-Reject for unsupported protocol 0x5072
 Feb  6 21:52:00 hostname pppd[2793]: Protocol-Reject for unsupported protocol 0x7263
 Feb  6 21:52:00 hostname pppd[2793]: Protocol-Reject for unsupported protocol 0x7263
 Feb  6 21:52:00 hostname pppd[2793]: Protocol-Reject for unsupported protocol 0x5072
 Feb  6 21:52:00 hostname pppd[2793]: Protocol-Reject for unsupported protocol 0x7263
 Feb  6 21:52:00 hostname last message repeated 3 times
 Feb  6 21:52:00 hostname pppd[2793]: Protocol-Reject for unsupported protocol 0x5072
 Feb  6 21:52:00 hostname pppd[2793]: Protocol-Reject for unsupported protocol 0x7263
 Feb  6 21:52:01 hostname pppd[2793]: Protocol-Reject for unsupported protocol 0x7263
 Feb  6 21:52:01 hostname pppd[2793]: Protocol-Reject for unsupported protocol 0x5072
 Feb  6 21:52:01 hostname pppd[2793]: Protocol-Reject for unsupported protocol 0x7263
 Feb  6 21:52:01 hostname pppd[2793]: Protocol-Reject for unsupported protocol 0x7263
 Feb  6 21:52:01 hostname pppd[2793]: Protocol-Reject for unsupported protocol 0x5072

etc... thousands of these.  Does anyone know what protocols: 0x5072 and 0x7263 are?
and how to prevent these? I figure I get this text because I had pppd running in
debug mode, but I wanted to know what it was rejecting.

I also get the following error on diald startup which I do not understand, but which
seems to be harmless.

Feb  6 22:44:54 lbaxter diald[2952]: start sl0: SIOCSIFMETRIC: Operation not supported 

Any help would be appreciated.

Thanks

My diald.conf looks like this:

        mode ppp
        accounting-log /var/log/diald.log
        debug 0x0009
        fifo /etc/diald/diald.ctl
#this is identical to the line commented out in /etc/ppp/options
        connect "/usr/sbin/chat -f /etc/sysconfig/network-scripts/chat-ppp0"
        device /dev/ttyS1
        speed 115200
        modem
        lock
        crtscts
        local 192.168.0.1
        remote 192.168.0.2
        dynamic
        defaultroute
        mtu 576
        mru 576
        window 2048
        #pppd-options noauth

        #from an earlier post to the diald mail list:
        ignore udp udp.source=udp.netbios-ns,udp.dest=udp.netbios-ns
        ignore udp udp.dest=udp.netbios-ns
        ignore udp udp.source=udp.netbios-ns
        ignore udp udp.dest=udp.netbios-ssn
        ignore udp udp.source=udp.netbios-ssn
        ignore udp udp.dest=udp.netbios-dgm
        ignore udp udp.source=udp.netbios-dgm
        ignore tcp tcp.dest=tcp.netbios-ns
        ignore tcp tcp.source=tcp.netbios-ns
        ignore tcp tcp.dest=tcp.netbios-ssn
        ignore tcp tcp.source=tcp.netbios-ssn
        ignore tcp tcp.dest=tcp.netbios-dgm
        ignore tcp tcp.source=tcp.netbios-dgm

        include /usr/lib/diald/standard.filter

My ppp/options file looks like this:


        /dev/modem 
        lock modem crtscts  
        asyncmap 00000000 
        defaultroute name pbaxter 
        #debug
        remotename ppp0 
        ipparam ppp0
        mru 576
        mtu 576

        #need this if we are invoking pppd manually... 
        #NOT needed if started by diald...
        #connect "/usr/sbin/chat -v -f /etc/sysconfig/network-scripts/chat-ppp0" 

        #115200 #doesn't work ... must be on command line or speed will be 9600

Lincoln
# create by lab 2/5/00 from the sample in
# man diald-examples for dynamic IP address assignment

        mode ppp
        accounting-log /var/log/diald.log
# debug bits for the debug mask
#                   0x0001         FILTER_MATCH
#                   0x0004         PROXYARP
#                   0x0008         VERBOSE
#                   0x0010         STATE_CONTROL
#                   0x0020         TICK
#                   0x0040         CONNECTION_QUEUE
        debug 0x0009
        fifo /etc/diald/diald.ctl
#this is identical to the line commented out in /etc/ppp/options
        connect "/usr/sbin/chat -f /etc/sysconfig/network-scripts/chat-ppp0"
#       connect /usr/lib/diald/connect
        device /dev/ttyS1
        speed 115200
        modem
        lock
        crtscts
        local 192.168.0.1
        remote 192.168.0.2
        dynamic
        defaultroute
        mtu 576
        mru 576
        window 2048
        #pppd-options noauth
#ip-up /etc/diald/shipmail

#linux-diald: The Windows Machines are causing the Link to be brought up due
#linux-diald: to that they are trying to use DNS for NETBIOS Name Resolution.
#linux-diald: This is a little quirk with Windows Networking.  With WinNT
#linux-diald: Systems you can easily disable this by TCP/IP Protocol Network
#linux-diald: Control Panel Dialog Setting related to WINS Addressing.  With
#linux-diald: Win9x Systems it is a little trickier in that you must modify a Registry
#linux-diald: Setting.  Attached is a Registry Edit Macro File which will change
#linux-diald: the DNS Enable.  Note, once this Macro is run, it will appear
#linux-diald: that all DNS functionality is disabled when you look at the Networking
#linux-diald: Control Panel DNS Dialogue -- this is not the case, only DNS related
#linux-diald: to NETBIOS Name Resolution is disabled.  If you need to perform
#linux-diald: further DNS Edits (such as add DNS Servers), then enable DNS
#linux-diald: from the DNS Dialogue, perform changes, save, and then reapply
#linux-diald: the Registry Macro.
#linux-diald: 
#linux-diald: In addition to the above, you may want to filter all NETBIOS traffic
#linux-diald: from causing DIALD from activating the Link.  Below are the filter
#linux-diald: rules you will need to add to your filter file:
#linux-diald: 

ignore udp udp.source=udp.netbios-ns,udp.dest=udp.netbios-ns
ignore udp udp.dest=udp.netbios-ns
ignore udp udp.source=udp.netbios-ns
ignore udp udp.dest=udp.netbios-ssn
ignore udp udp.source=udp.netbios-ssn
ignore udp udp.dest=udp.netbios-dgm
ignore udp udp.source=udp.netbios-dgm
ignore tcp tcp.dest=tcp.netbios-ns
ignore tcp tcp.source=tcp.netbios-ns
ignore tcp tcp.dest=tcp.netbios-ssn
ignore tcp tcp.source=tcp.netbios-ssn
ignore tcp tcp.dest=tcp.netbios-dgm
ignore tcp tcp.source=tcp.netbios-dgm


        include /usr/lib/diald/standard.filter

Reply via email to