Richard Vaughan wrote:
>
> Rodney,
>
> Comments below...
>
> ----- Original Message -----
> From: Rodney Holm <[EMAIL PROTECTED]>
> To: Richard Vaughan <[EMAIL PROTECTED]>
> Sent: Monday, March 15, 1999 4:03 PM
> Subject: Re: DialD Config Problems
>
> >Do you have a diald.options file setup with rules about when to bring the
> link
> >up? Another way to see if any traffic is recieved is to turn on debug mode
> >of 1. This will print messages in the log for all of the rules that diald
> >ignores or accepts. (no accepting yet in your case)
> >
>
> No, I don't have a diald.options file. Is that mandatory? If so, what do I
> need to have in it?
>
Actually diald.options is wrong. In the diald source code:
config.h:#define DIALD_CONFIG_FILE "/etc/diald.conf"
This file contains lines of the following type:
# ignore those pesky netbios-ns requests
ignore tcp tcp.source=tcp.netbios-ns
ignore tcp tcp.dest=tcp.netbios-ns
ignore tcp tcp.dest=tcp.netbios-dgm
ignore tcp tcp.source=tcp.netbios-dgm
ignore tcp tcp.dest=tcp.netbios-ssn
ignore tcp tcp.source=tcp.netbios-ssn
accept tcp 600 tcp.source=tcp.www
accept tcp 600 tcp.dest=tcp.www
accept tcp 600 tcp.source=tcp.https
accept tcp 600 tcp.dest=tcp.https
There should be some examples of this file somewhere, /usr/doc/diald ???
I am not sure which Linux distribution you are using so I do not know where on
your system it is kept. These rules tell diald when to bring up the link and
how long to keep it up.
> >
> >> The other problem is that even if I do force the link up, I can't see
> past
> >> my ISPs domain. I can't seem to see the rest of the net, just "local"
> >> addresses.
> >>
> >Do you have DNS servers setup in your resolv.conf? Are you able to use
> >names or just ip addresses? Do you have a default route setup? These are
> all
> >things that need to be done in order to have a fully working internet
> >connection.
>
> I can use both IP addresses, and canonical names on my local ISP. If I try
> to ping an address "further away" than that (ie. www.freshmeat.net), then it
> will resolve the name to an IP address, but I can't see any return packets
> if I use ping. Telnet does the same thing.
>
> My ISP gives me a dynamic IP address so I have put the keywords "dynamic"
> and "defaultroute" into my diald.conf to account for that. Is this correct?
>
Yes that is correct. dynamic means your isp gives you an address and
defaultroute will cause diald to add a default route that uses your ppp
interface. From the route.dat file you sent it is working correctly.
> I have my ISPs DNS servers address in my /etc/resolv.conf file.
>
You are resolving names if the ping behaves as you mention above so that
seems correct.
> I have attached the output from the route command, when I brought the link
> up manually.
I am somewhat concerned about the second default route
default * 0.0.0.0 U 0 0 1 ppp0
default 172.16.1.7 0.0.0.0 UG 0 0 2 eth0
default * 0.0.0.0 U 1 0 0 sl0
The one using eth0. You are telling your machine that 172.16.1.7 is the
address that all packets should be routed to. This is in direct conflict
with the rule above that says all should go to ppp0. Your rule above those:
172.16.1.0 * 255.255.255.0 U 0 0 7 eth0
should take care of any packets destined for 172.16.1.0 network
remove the default route on eth0:
# route del default eth0
>
> My box is a RH 5.2 machine.
>
> Thanks,
>
> Richard
>
> --------------------------------------------------------------------------------
> Name: route.dat
> route.dat Type: unspecified type (application/octet-stream)
> Encoding: quoted-printable
--
-------------------------------------------------------------------------------
Rodney D. Holm [EMAIL PROTECTED]
Apexx Technology, Inc. http://www.apexxtech.com
-------------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
