Turns out if I use -w 0 I have to specify any OTHER port than 3000 for
-W. Another problem seems to be in using an interface with multiple IPs
for the -i param.
I have
eth1 = 10.1.0.1
eth0 = 10.2.0.1
eth0:0 = 10.3.0.1
...
(netmask/16)
and if i use -i eth1, everything works fine: ssl binds to
I'm testing v.2.0.99rc1 on Windows 2000.
I can't figure out how to use the startup options.
Obviously, the first option has to be one of /i, /r, /c
and (as I understand it) the usal parameters can follow
after /c or /i.
I'm able to run ntop by using 'ntop /c' but none of
the remaining options
Please ignore.
Luca
--
Luca Deri NETikos S.p.A.
Via Matteucci 34/B56124 Pisa, Italy.
Ph. +39/050/968.639 Fax. +39/050/968.626
Personal: [EMAIL PROTECTED] Business: [EMAIL PROTECTED]
WWW: http://www.lucaderi.org/ ICQ: 68183632
Hacker: someone who
Luca - this one is too weird for me, help! (I'm not talking about the ssl
issue, but rather the hang in termIPServices...)
-Burton
That's very interesting ... and I see much the same - I'm researching if it
has to
