Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 2 Oct 2017 07:23:56 +0100
From:      Matthew Seaman <matthew@FreeBSD.org>
To:        freebsd-questions@freebsd.org
Subject:   Re: Weird turnoff
Message-ID:  <841d595b-7f26-a891-5c96-8ebb155f7707@FreeBSD.org>
In-Reply-To: <20171002025542.GA13466@doctor.nl2k.ab.ca>
References:  <20171001232531.GA18260@doctor.nl2k.ab.ca> <20171002021140.931f17de.freebsd@edvax.de> <20171002002506.GA42212@doctor.nl2k.ab.ca> <20171002041047.31f81a0d.freebsd@edvax.de> <20171002023157.GA1163@doctor.nl2k.ab.ca> <20171002025542.GA13466@doctor.nl2k.ab.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--uDfwQdaahSKncMAOKfe7pLQWhIFGtbu68
Content-Type: multipart/mixed; boundary="0GJTGmd0vHmNWtKbpd59Ix9MdwOrVP0OL";
 protected-headers="v1"
From: Matthew Seaman <matthew@FreeBSD.org>
To: freebsd-questions@freebsd.org
Message-ID: <841d595b-7f26-a891-5c96-8ebb155f7707@FreeBSD.org>
Subject: Re: Weird turnoff
References: <20171001232531.GA18260@doctor.nl2k.ab.ca>
 <20171002021140.931f17de.freebsd@edvax.de>
 <20171002002506.GA42212@doctor.nl2k.ab.ca>
 <20171002041047.31f81a0d.freebsd@edvax.de>
 <20171002023157.GA1163@doctor.nl2k.ab.ca>
 <20171002025542.GA13466@doctor.nl2k.ab.ca>
In-Reply-To: <20171002025542.GA13466@doctor.nl2k.ab.ca>

--0GJTGmd0vHmNWtKbpd59Ix9MdwOrVP0OL
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: quoted-printable

On 02/10/2017 03:55, The Doctor wrote:
> Or hinder.
> Just did a manual test and now the server in
> question cannot see outside the LAN.

Errr... yes.  Running 'service netif restart' will clear your routing
table.  You need to run 'service routing restart' or 'service
defaultroute restart' as well.

What does your routing table look like before and after you run your
network restart?  Compare the results from in either case:

   # netstat -rn

If your interface has started spontaneously going down for no apparent
reason, I'd suspect some sort of hardware problem.  See if the i/f is
recording any errors:

  # netstat -i

If you have a decent switch, you should be able to get equivalent output
from that end too.

If there are any non-zero entries in the ierr or oerr columns, and
particularly if those counters are increasing over time, then start by
checking your cabling.  Try a new ethernet cable.  Make sure that cables
are not kinked or even tied down too tightly.  Make sure plugs are
firmly seated in sockets.  Failing that, try moving the machine to a
different switch port temporarily.

	Cheers,

	Matthew


--0GJTGmd0vHmNWtKbpd59Ix9MdwOrVP0OL--

--uDfwQdaahSKncMAOKfe7pLQWhIFGtbu68
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJ8BAEBCgBmBQJZ0dt8XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC
QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkAT98kQAKfXWgmWF0Quolj001AR0Hp+
nIuxOxNa875h2yJuUueSXOdJ8CRj9b4J+5fZfphC5dtSia6h8h70GXITcZSOOWtv
8yEHZQcj+qHpxkmhqHLUcuiAG0b7R5C7vBLRyR5WJXvPs6ZoOHGvUBsZ003kf5Gz
HZY8yOhRBhiE3wTRtT/Zd1bdTKMPnNAIqdLKlK02oEcs0108vgZhEzPf/slKIjCt
n+zIPwGPcdNnIcNE3nLvbUjkce9kvMow62LyFrmf9E1eRbH7CUkT4esDZ3gvOlkj
Q7PhFlFEMpX77wHoi5H2oM8mHT7+rD8dgxl/SlUUCzMh700i/wEQ7JeEUdLmxpmk
iExvnTp6M6fw6q6nS2xn3iV2qtn4xb/0ga2OzKVrC84GXcotNiq6iwO1b9fj5wCU
FnuuQ4dPzCR1xZOWvtg/zv/g7PubOLgUurgVymcnP9VlpgVtDX8x0v0dUYIDiMaF
V4kTnFBAMwxDGDesMGp0T/0sWJYeaBgRXwwQNOI+dtdh9cSCDAMt2NiBY35xcV8b
4MGTafCKZhNUjSLG/PfBD84krIoslYfGHGemrRr4VAvzw0PRyk9plPvTmEEuToGJ
cCd2jOwtv6aSbzFgXEGXut+zKNaEc9GYV133N63CIcO26dQkPN0KdboTvXc4/Qi2
fxWbHV333lN+J8ohYuEj
=QE0e
-----END PGP SIGNATURE-----

--uDfwQdaahSKncMAOKfe7pLQWhIFGtbu68--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?841d595b-7f26-a891-5c96-8ebb155f7707>