John,

The Protocol Number is not the Number you see in the
Services File.  The Services File contains the Port Numbers
associated with the various Services which execute using
the Protocols.  The Protocols are tcp, udp, etc.....   The
Protocol #6 you are seeing is TCP.

The Protocol Numbers are defined by the Standard
RFC 1060.  Here are a few of these:

# Format:
#
# <protocol name>  <assigned number>  [aliases...]   [#<comment>]

ip             0     IP                 # Internet protocol
icmp        1     ICMP          # Internet control message protocol
ggp          3     GGP           # Gateway-gateway protocol
tcp           6     TCP            # Transmission control protocol
egp          8     EGP           # Exterior gateway protocol
pup        12    PUP            # PARC universal packet protocol
udp        17    UDP            # User datagram protocol
hmp       20    HMP           # Host monitoring protocol
xns-idp  22    XNS-IDP    # Xerox NS IDP
rdp         27    RDP           # "reliable datagram" protocol
rvd         66    RVD            # MIT remote virtual disk


With respect to the Rule #6 in the Phone Filter, it is
the rule set for HTTP/WWW (Web Pages) via TCP.
Based on the Service 80 Request, this filter processing
would be correct.

With respect to the Rules #6 and #7, I would keep the Time
Values in the several minutes range.  Otherwise, your
DIALD link will bounce while you are on the Web.  I have
mine setup for 5 Minutes:

# make sure http transfers hold the link for 5 minutes, even after they end.
# NOTE: Your /etc/services may not define the tcp service www, in which
# case you should comment out the following two lines or get a more
# up to date /etc/services file. See the FAQ for information on obtaining
# a new /etc/services file.
accept tcp 300 tcp.dest=tcp.www
accept tcp 300 tcp.source=tcp.www

As to what is activating this DIALD Rule.....
Do you have an active Web Browser executing on a
Machine in you Network ?  As you stated, the IP Address
of the Destination is not a registered WEB Address -
Is your Linux Machine or another System performing this
Request ?  Do you have your Linux Machine setup as
a Web Server (i.e. Apache) ?


----- Original Message -----
From: John Logsdon <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, November 20, 1999 4:56 AM
Subject: Diald keeps bringing link back up ...


> Hi
>
> Can someone interpret the rule numbers and protocols in the diald debug
> facility please?
>
> I have chopped all my accept times down to 5 seconds in diald/phone.filter
> (with an impulse 30,0,0 to keep the link up for the first 30 secs) and
> this seems to work OK.  Except after the link is dropped, debug 31 leads
> to the following message in my /var/log/messages file which prompts
> reconnection.  Nothing happens and the link is dropped again and so on.
> Not a good idea.
>
> -------------------------------------------------------------------------
> Nov 20 09:10:53 mercury diald[16310]: filter accepted rule 6 proto 6 len
> 40 seq f4c760aa ack fd4deed3 flags FIN ACK packet 192.168.1.250,62889 =>
> 194.205.254.81,80
> -------------------------------------------------------------------------
>
> The 194.205.254.81 is obviously a web page from the port number but
> otherwise does not resolve to anything and I get no response from ping.
> The 192.168.1.250 is the local IP number that is replaced by the dynamic
> address.
>
> There is no protocol 6 in /etc/services and is the rule the 6th in the
> phone.filter file or what?  Similar messages are found when pulling my
> mail so I don't want to filter them out at all.
>
> Any ideas?
>
> John
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [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