Mailinglist Archive: opensuse (2522 mails)
|< Previous||Next >|
RE: [SLE] Please Help - wvdial.dod ruines me!
- From: joakim@xxxxxxxxxxxx (Joakim Schramm)
- Date: Sun, 2 Jul 2000 13:30:50 +0200
- Message-id: <NDBBLNKOALDHOLHPNNJEKEIKCJAA.joakim@xxxxxxxxxxxx>
Thanks for your input Juergen,
I understand it can be a tricky path to track what's trigger the dial out,
so I decided to let it rest for now and just fall back to the modem on my
workstation, and skip the dial out server for now. After all, it's summer
now so better enjoy some more trivial things like visiting the beach :)
Thank you all for the help given with this anyway.
> -----Original Message-----
> From: juergen.braukmann@xxxxxxxxxxxx
> Sent: Saturday, July 01, 2000 10:40 PM
> To: Joakim Schramm
> Subject: Re: [SLE] Please Help - wvdial.dod ruines me!
> Joakim Schramm wrote:
> > Ok thanks, not that I know what ntop is but I guess I have to
> find out the
> > usual way...
> > Sorry about the language quirk, english is not my main language
> and didn't
> > mean to be or sound rude. I merly ment that no one did notice to reply.
> > Sorry if it turned out wrong.
> > /Joakim
> Hi Joakim,
> you realy seem to have a difficult problem. I use ISDN with DoD and
> therefor can't be of great help, sice I set up wvdial in just one or two
> cases and there more experimental.
> >From my ISDN experiance -since you seem to use DoD as well- I can tell
> that most dialups are due DNS requests. These can be caused by any
> machine on the net. Part of the solution is to set up a caching
> nameserver (bind8, Support DB) to find out *what* is requested. All
> local known interfaces / IP's should appear somehow in /etc/hosts. There
> is /etc/networks to list the known networks (like the local network)
> oddly, some programs trigger DNS requests on their own to resolve local
> IP's to names. (i.e. sendmail, calling of "route", calling of "ipchains
> If this happens in regular time intervalls, it can be some service
> running on the machine, probably doing just the above.
> Any automated routing daemon (routed or gated) might be a cause as well.
> Sadly, if you're in a network, any networked machine can be the
> culprit. Windows machines in a Samba network do a lot of nasty things
> ... Ports 135-137. There is an option
> like "interfaces=192.168.42.243/24" in smb.conf for IP and netmask or
> number of netmask bits to bind samba to one network interface only, and
> stop that problem.
> As a crude hack, I set my machine to runlevel 1, logged onto the second
> terminal and did a "tail -f /var/log/messages" there, went back and
> started every start script for level 2 (/sbin/init.d/rc2.d/S*) by hand
> -or rather a small script- after starting, I changed to the log window
> to see what happened.
> Theorie: when a service is the culprit, it might be that it dials out if
> I start the service. In my case, after booting, my machine always dialed
> out. That way, I discovered that sendmail resoves IP's to names...
> ...ages ago...
> It could be a help to visit the german SDB on ISDN and unwanted dialouts
> for further clues. (Just if my theory is right...)
> =========================================== __ _
> Juergen Braukmann juergen.braukmann@xxxxxx| -o)/ / (_)__ __ ____ __
> Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ /
> ===========================================_\_v __/_/_//_/\_,_/ /_/\_\
To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the FAQ at http://www.suse.com/support/faq
|< Previous||Next >|