Mike,
I just upgraded to diald-0.99.1 as you know.
I'm now getting occasional weird garbled messages coming out to the xconsole AND
all the xterms (well, KDE's "kvt" really) where I'm running a shell under my own
user name, but NOT to those where I'm running a root shell.
Here's a sample:
Message from syslogd@jove at Wed Jun 30 12:52:28 1999 ...
jove 151>^
u^.^`^s0^`12^z52^z18^`d^)ald[158^v2]^z^`^3lot^`def^z^`0^`8^v^s^y^y^`^wf^`^wfffffff^`fff
What the hell is that? I see a fragment of the diald process name and PID in
there, and diald is the only thing I changed just before it started appearing.
There's no clue I can see in the system log at anywhere around that time, here's
a small sample:
Jun 30 12:52:28 jove diald[15862]: term: shift 24 op 1 off 13d msk 1 tst 0
Jun 30 12:52:28 jove diald[15862]: slot check: 46347 3 30 5
Jun 30 12:52:28 jove diald[15862]: slot def: 0 86399 7f 7fffffff fff
Jun 30 12:52:28 jove diald[15862]: testing ip ed8372d1:d17283ed data
10223814:14382210 mask 1 shift 18 test 0 v 0
Jun 30 12:52:28 jove diald[15862]: filter: prl 0 log 0 type 2 cnt 1 tm 60
Jun 30 12:52:28 jove diald[15862]: term: shift 25 op 1 off 13d msk 1 tst 0
Jun 30 12:52:28 jove diald[15862]: slot check: 46347 3 30 5
Jun 30 12:52:28 jove diald[15862]: slot def: 0 86399 7f 7fffffff fff
Jun 30 12:52:28 jove diald[15862]: testing ip ed8372d1:d17283ed data
10223814:14382210 mask 1 shift 19 test 0 v 0
Jun 30 12:52:28 jove diald[15862]: filter: prl 0 log 0 type 3 cnt 1 tm 0
Jun 30 12:52:28 jove diald[15862]: term: shift 16 op 0 off 2d msk ffff tst
35
Jun 30 12:52:28 jove diald[15862]: slot check: 46347 3 30 5
Oh yes, and what *are* those "filter", "testing ip" and "slot" messages
cluttering up the log? There are millions of them. I've always used debug 31
which almost gave me the level of reporting I wanted up till now, showing which
packets were ignored and accepted. How do I turn these off these new messages
but retain the old ones?
I'm running diald-0.99.1 on SuSE Linux 6.1 with kernel 2.2.9; I compiled diald
with the "demasq" stuff re-enabled and dctrl is connecting via a socket.
Here's my diald command line:
/usr/sbin/diald -file /etc/suseppp/diald/generic.diald \
connect /etc/suseppp/scripts/generic.connect \
pidfile diald_0.pid \
-- \
file /etc/suseppp/generic.options
And here's the options file generic.diald (on SuSE, /etc/diald.conf only
contains filtering rules):
device /dev/modem
-m ppp
speed 115200
two-way
local 193.237.131.114
remote 158.152.1.222
defaultroute
disconnect-timeout 30
redial-timeout 0
dial-fail-limit 5
demasq
#fifo /var/adm/diald/diald.ctl
authsimple /etc/diald.auth
tcpport 7002
debug 31
Apart from the garbled syslogd broadcast and the new voluminous diagnostics in
in the log file, everything seems to be working OK. The "demasq" option seems to
be working too, if that just means allowing dctrl to display the demasqueraded
IP address for the client. I wouldn't know if the port number it's reporting is
being demasqueraded correctly. It shows port 1028 for a http connection to
remote site's http server, and ports 1030-1032 to my ISP's web proxy when
downloading its first web page since it was booted.
--
[EMAIL PROTECTED] Ralph Clark, Virgo Solutions Ltd (UK)
__ _
/ / (_)__ __ ____ __ * Powerful * Flexible * Compatible * Reliable *
/ /__/ / _ \/ // /\ \/ / *Well Supported * Thousands of New Users Every Day*
/____/_/_//_/\_,_/ /_/\_\ The Cost Effective Choice - Linux Means Business!
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
