From: Marc Joliet <marcec@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Strange network behaviour: NIC goes down, DHCP lease renewal fails
Date: Thu, 5 Mar 2015 22:46:12 +0100 [thread overview]
Message-ID: <20150305224612.760248d5@marcec.fritz.box> (raw)
In-Reply-To: <201503052119.47793.michaelkintzios@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2306 bytes --]
Am Thu, 5 Mar 2015 21:19:46 +0000
schrieb Mick <michaelkintzios@gmail.com>:
> On Thursday 05 Mar 2015 18:33:23 Todd Goodman wrote:
> > * Marc Joliet <marcec@gmx.de> [150305 04:47]:
> > [..SNIP..]
> >
> > > 1.) The NIC is brought up (some built-in Intel model).
> > >
> > > 2.) A DHCP client configures it.
> > >
> > > 3.) The network connection is lost at some point (the amount of time this
> > > takes
> > >
> > > varies, but it can be as little as 20 minutes).
> > >
> > > 4.) Eventually the lease runs out and the DHCP client tries to renew it,
> > > but
> > >
> > > gets no response. Sometimes, after many hours (at least 6), it will
> > > get a DHCPACK, but that's it. One of our sysadmins says that not
> > > only does the DHCP server never see the packets, but the managed
> > > switch that the PC is directly attached to *also* never does (again,
> > > except for when the occasional DHCPACK comes).
> > >
> > > 4.) Restart the network device. A reboot is not required, but it is
> > > necessary
> > >
> > > to terminate the DHCP client. After that everything works again.
> > >
> > > 5.) GOTO 3.
> >
> > [..SNIP..]
> >
> > Is this a WiFi NIC?
> >
> > Is it possible the device is powering down?
> >
> > I've had lots of problems with WiFi devices powering down (both driver
> > issues as well as just trying to disable the default setting of powering
> > down.)
> >
> > Todd
>
> If not a WiFi, have you also tried to mirror a port at the router where the
> DHCP server is running and sniff packets there? Does the router see the
> DHCPREQ coming through from the client PCs?
They apparently don't even reach the managed switch, which is what the PC is
directly connected to (but again: the third affected PC is on a different
switch). I find this very confusing :-/ (and so does our local sysadmin, or
so I'm told).
(I have to mention that the best I can do is relay ideas here to my boss and the
aforementioned sysadmin, as I don't have access to any of the network
hardware and software, save for the affected PCs. I am mostly trying to
collect ideas.)
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-05 21:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 9:46 [gentoo-user] Strange network behaviour: NIC goes down, DHCP lease renewal fails Marc Joliet
2015-03-05 18:33 ` Todd Goodman
2015-03-05 21:19 ` Mick
2015-03-05 21:46 ` Marc Joliet [this message]
2015-03-06 7:15 ` Mick
2015-03-05 21:38 ` Marc Joliet
2015-03-06 6:01 ` Alan McKinnon
2015-03-06 18:45 ` [gentoo-user] Strange network behaviour: NIC goes down, DHCP lease renewal fails (WORKED AROUND) Marc Joliet
2015-03-06 19:35 ` Alan McKinnon
2015-03-06 19:57 ` Marc Joliet
2015-03-06 20:57 ` Daniel Frey
2015-03-07 10:04 ` [gentoo-user] Strange network behaviour: NIC goes down, DHCP lease renewal fails thegeezer
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=20150305224612.760248d5@marcec.fritz.box \
--to=marcec@gmx.de \
--cc=gentoo-user@lists.gentoo.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