Dear readers, if I possibly refer to a known bug of diald-0.16, please excuse the repetition, but I couldn't find a hint in the manual pages nor elsewhere. Sometimes, when diald has brought up a link for a few times, it impossible to make it doing its duty for further transfer requests of any client. /var/log/messages has the output Aug 7 10:35:47 terra diald[10333]: filter ignored rule 0 proto 17 len 85 packet 192.168.1.1,1697 => 129.187.10.25,53 Aug 7 10:35:57 terra diald[10333]: filter ignored rule 0 proto 17 len 85 packet 192.168.1.1,1698 => 129.187.16.1,53 [... and so on] Let me comment this rather strange message: yes, diald is ignoring a rule, but look at the number, it is the rule 0, a non-existing one! Why doesn't rule 0 really exist on my opinion? Say actually there is an amount of 32 rules in /etc/diald.conf (or /usr/lib/diald/standard.filter included in the first file, if you want). If one begins counting them with 0 the last one would be the number 31. But some accepting (observed in /var/log/messages, not listed here) refers to rule 32, so the first rule *must* have the number 1, *not* 0. My questions: What ist then the mysterious rule 0? Is it used when a packet matches with no rule in /etc/diald.conf? I thought the rule "accept any 60 any" catches any packet which hasn't been catched above of this last rule in /etc/diald.conf. So, how can I make diald make to bring up a link, not ignoring a rule 0? BTW: The normal filter accepting which initiates a link you can see below: Aug 6 16:31:23 terra diald[9952]: filter accepted rule 24 proto 17 len 57 packet 192.168.1.1,1607 => 129.187.10.25,53 [rule 24 is "accept udp 30 udp.source=udp.domain" a DNS request - at first, of course.] Thank to all who can help! Best regards, Thomas - To unsubscribe from this list: send the line "unsubscribe linux-diald" in the body of a message to [EMAIL PROTECTED]
