Klaus Drews said: > I commented it out (as shown), but dialing goes on. In the manpages it says, > that I won't > have to restart cron after shanging jobs. So it should have worked. > > The logfile stats > Jan 4 14:56:43 coma diald[169]: Trigger: udp 192.168.0.1/138 > 192.168.0.255/138 > before modem is dialing, but not always. > This port I found in services: > netbios-dgm 138/tcp # NETBIOS Datagram Service > netbios-dgm 138/udp
Are you running samba or acting as a gateway for any Windows or samba machines? They'd most likely be the ones sending out these packets, which your dial-on-demand sofware is diligently coming up and trying to send out. I missed the start of this thread, so I don't know what dial-on-demand software you're using, but I know that diald can be configured to ignore data on certain ports, so you can tell it to never bring (or keep) the link up for traffic on port 138. -- Geek Code 3.1: GCS d- s+: a- C++ UL++$ P+>+++ L++>++++ E- W--(++) N+ o+ !K w---$ O M- !V PS+ PE Y+ PGP t 5++ X+ R++ tv- b++ DI++++ D G e* h+ r++ y+
