I am using the (slightly modified but not in this point) diald config file 'standard.filter' . It worked fine for me until I set up my own little dns. Usually a domain request is the first packet sent out which will bring up the link, as standard.filters comments it: ># Rules for UDP packets ># ># We time out domain requests right away, we just want them to bring ># the link up, not keep it around for very long. ># This is because the network will usually come up on a call ># from the resolver library (unless you have all your commonly ># used addresses in /etc/hosts, in which case you will discover ># other problems.) ># Note that you should not make the timeout shorter than the time you ># might expect your DNS server to take to respond. Otherwise ># when the initial link gets established there might be a delay ># greater than this between the initial series of packets before ># any packets that keep the link up longer pass over the link. a few lines later I find ># Don't bring up on domain name requests between two running nameds. >ignore udp udp.dest=udp.domain,udp.source=udp.domain ^^^^^^^^^^^^^^^^^^ ># Bring up the network whenever we make a domain request from someplace ># other than named. >accept udp 30 udp.dest=udp.domain >accept udp 30 udp.source=udp.domain But when I am using my own dns (with my provider's dns "above it", of course) there will always be a domain request from my named to that on e of my provider. So I need to comment out the line marked ^^^^^^ to get things working. Q: In which situations other than forwarding a domain request diald will see packets matching the rule marked above? Could there arise any problems from this? I intend to run my linux box unattended in the future. Mike or Eric, could you add a little comment on that line that there must be made a difference when one is running it's own dns? Olaf - To unsubscribe from this list: send the line "unsubscribe linux-diald" in the body of a message to [EMAIL PROTECTED]
