On Thu, 25 May 2000, Philip Lehman wrote:
> >...with isdn in autodial mode I guess. Try setting up ipchains and log
> >all output over ippp0.
put kdebug to a high level, 9 or something, and grep for
"kernel: OPEN" in /var/log/messages, it will tell you the details of
the packet that triggered t
On Thu, 25 May 2000, Philip Lehman <[EMAIL PROTECTED]> wrote:
>On Thu, 25 May 2000, Ron Rademaker <[EMAIL PROTECTED]> wrote:
>
>>See subject.
>>
>>I'm using a ISDN connection.
>
>...with isdn in autodial mode I guess. Try setting up ipchains and log
>all output over ippp0.
>
>/sbin/ipchains -A inp
On Thu, 25 May 2000, Ron Rademaker <[EMAIL PROTECTED]> wrote:
>See subject.
>
>I'm using a ISDN connection.
...with isdn in autodial mode I guess. Try setting up ipchains and log
all output over ippp0.
/sbin/ipchains -A input -j ACCEPT -i ippp0 -l
Then watch your syslog and try to guess from IP
On Thu, 25 May 2000, Ron Rademaker wrote:
> See subject.
>
> I'm using a ISDN connection.
>
> Ron Rademaker
Are you running a nameserver? If you are, that could open a connection.
ipchains could do the same, if you have your packet filter starting whenever
you reboot the machine, but it will ope
look at the system logs.
*possibly* you could set up verbose ipchains rules, to see, which service
is tried to be accessed. but i have no idea, how dial on demand works, so
this idea may be useless.
--
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
If Windows is the answer
See subject.
I'm using a ISDN connection.
Ron Rademaker
6 matches
Mail list logo
