public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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 (WORKED AROUND)
Date: Fri, 6 Mar 2015 20:57:53 +0100	[thread overview]
Message-ID: <20150306205753.1f3cfdd1@marcec.fritz.box> (raw)
In-Reply-To: <54FA0191.6090900@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2493 bytes --]

Am Fri, 06 Mar 2015 21:35:45 +0200
schrieb Alan McKinnon <alan.mckinnon@gmail.com>:

> On 06/03/2015 20:45, Marc Joliet wrote:
> > First of all, thanks to everybody who responded so far.
> > 
> > I wanted preface my reply to Alan by mentioning that the local sysadmin made
> > changes to the DHCP server that appear to have worked around whatever the issue
> > is.
> > 
> > I don't fully understand the error analysis (something to do with the DHCP
> > client reaching a particular state and sending DHCP packets that something
> > in-between it and the DHCP server doesn't like and that might result in vendor
> > dependent behaviour), but what the DHCP server now does is tell the client to
> > use the broadcast address as the DHCP server address (which is weird, because
> > the DHCP clients always switch to the broadcast address after a timeout, but of
> > course I'm no DHCP expert).  The affected PCs have been working normally all
> > day today.
> 
> In light of what you say below:
> 
> 
> I'd be interested to hear what your sysadmin has to say; dhcp is one of
> those things that JustWork(tm) - it uses regular tcp and nothing funny
> about it at all. The only thing normally between your NIC and the dhcp
> server is a switch, so that's what I'd be looking at.

That's also why I was confused about the whole thing and why I originally
thought that it was either a power management issue or some sort of network
problem.

I'll see if I can ask when I'm there again next week.

[...]
> I wasn't aware you had e1000e hardware - those are about as reliable as
> they come. I've used many of them and never had the slightest trouble at
> all. By all means study up on firmware and driver options - if you don;t
> know much about that area it's very illuminating to find out more. But
> based on experience I'd say the chances of finding an oddity with e1000e
> are slim, and I'd be looking at a misconfigured switch.

That's pretty much what the sysadmin said, too, when I asked what he thought
of the "power management issue" idea.

> There are some strange switches out there that let you make crazy
> configuration, like eg blanket drop all broadcast traffic on one or more
> ports. That's where I'd be looking first.

Yeah, that agrees with my instinct that it's most something to do with the
switch.

-- 
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 --]

  reply	other threads:[~2015-03-06 19:58 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
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 [this message]
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=20150306205753.1f3cfdd1@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