From: Ron Flory <ron.flory@adtran.com>
To: Kevin Fry <kevin@carts.com>
Cc: linuxppc emb3dd3d list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Strange bootpd behavior (server side)
Date: Tue, 07 Aug 2001 16:18:26 -0500 [thread overview]
Message-ID: <3B705B22.366AE18F@adtran.com> (raw)
In-Reply-To: 3B703ADA.9ADAFBAD@carts.com
Kevin Fry wrote:
>
> I'm having a small problem with our redhat 6.2 bootp server and maybe
> yous guys can shed some light on it for me. The problem is that
> whenever our DSL internet connection is down(which is too much.. I wish
> cable was available!), the bootpd stops responding to requests.. I can
> see the requests with tcpdump, but no replys. and when the internet is
> up sometimes is takes a little bit for the bootpd to respond to
> requests.
> I think it's doing DNS resolution and if it can't find a DNS server
> when the net's down, it just stops working. Does linux automatically do
> name resolution on every address it gets? If so can i turn this off?
> Our network is behind a DSL modem/router (Flowpoint 2200) acting as
> gateway(192.168.254.254), and we have 3 switches after that.
> A lot of the time the router is finicky with linux even when
> everything is working.. I know this is a bit off topic, but ANY
> suggestions are very welcome.
it sounds like 'fun with PAM' that causes similar problems with my
TFTP server. I need to write a simple inetd replacement (sans PAM)
just for TFTP, so we don't get killed by the delays caused by PAM
authorization checks.
ron
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-08-07 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-07 19:00 Strange bootpd behavior (server side) Kevin Fry
2001-08-07 21:18 ` Ron Flory [this message]
2001-08-08 9:48 ` Mark Powell
2001-08-08 12:54 ` Andrew Dixon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B705B22.366AE18F@adtran.com \
--to=ron.flory@adtran.com \
--cc=kevin@carts.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).