I've got a problem with diald being triggered to dial out and I can't seem
to figure out the reason why. This is on a box with a 192.168.1.x network
of internal Linux and Windows machines, and is operating over a dynamic ppp
link. I've added diald's netbios filters for everything under the sun:
ignore udp udp.source=udp.netbios-ns
ignore udp udp.dest=udp.netbios-ns
ignore udp udp.source=udp.netbios-dgm
ignore udp udp.dest=udp.netbios-dgm
ignore udp udp.source=udp.netbios-ssn
ignore udp udp.dest=udp.netbios-ssn
ignore tcp tcp.source=tcp.netbios-ns
ignore tcp tcp.dest=tcp.netbios-ns
ignore tcp tcp.source=tcp.netbios-dgm
ignore tcp tcp.dest=tcp.netbios-dgm
ignore tcp tcp.source=tcp.netbios-ssn
ignore tcp tcp.dest=tcp.netbios-ssn
but that doesn't seem to stop things. Now what I'm seeing is this in my
log:
Jun 14 19:47:53 spartacus diald[913]: Trigger: tcp 192.168.1.1/1063
204.97.120.35/21
[...]
Jun 14 19:49:05 spartacus diald[913]: Trigger: tcp 192.168.1.1/1062
204.97.120.35/21
[...]
Jun 14 19:49:35 spartacus diald[913]: Trigger: tcp 192.168.1.1/1064
204.97.120.35/21
These trigger lines seem to have various numbers in place of 106x but
nothing I've seen in the docs give me a clue as to what's going on.
Can anyone smack me with a clue-bat and fill me in on what's going on?
Or, barring that, anyone have a good /etc/diald/standard.filter file that
kills all the misc. netbios stuff?
--
"If the current stylistic distinctions between open-source and commercial
software persist, an open-software revolution could lead to yet another
divide between haves and have-nots: those with the skills and connections
to make use of free software, and those who must pay high prices for
increasingly dated commercial offerings." -- Scientific American
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
