Date: Mon, 25 Jul 2016 18:13:20 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-questions@freebsd.org Subject: Re: Losing network connectivity - Is there a virus on my system ? Message-ID: <156494d2-ae9a-0a3f-a42d-536773187d8a@infracaninophile.co.uk> In-Reply-To: <VI1PR02MB097438151662BE0EA1696382D10D0@VI1PR02MB0974.eurprd02.prod.outlook.com> References: <VI1PR02MB097438151662BE0EA1696382D10D0@VI1PR02MB0974.eurprd02.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --1xcC1g0Rcna0jGOl1UBnCCm1xw3C9qpJW Content-Type: multipart/mixed; boundary="lNDIvrNXDCFdr50DftsM3L5Jv6AWM182H" From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-questions@freebsd.org Message-ID: <156494d2-ae9a-0a3f-a42d-536773187d8a@infracaninophile.co.uk> Subject: Re: Losing network connectivity - Is there a virus on my system ? References: <VI1PR02MB097438151662BE0EA1696382D10D0@VI1PR02MB0974.eurprd02.prod.outlook.com> In-Reply-To: <VI1PR02MB097438151662BE0EA1696382D10D0@VI1PR02MB0974.eurprd02.prod.outlook.com> --lNDIvrNXDCFdr50DftsM3L5Jv6AWM182H Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2016/07/25 17:54, Manish Jain wrote: > I am using FreeBSD 10.2 amd64, with Win XP as a backup OS. Since=20 > yesterday, I am experiencing a strange situation. Internet connectivity= is=20 > lost every 10-15 minutes. 'ping www.freebsd.org' starts reporting 100% = > packet loss. If I run 'service netif restart', ping reports "No route t= o=20 > host". Try mtr instead of ping (in ports) -- it shows you /where/ the packets are being lost. 'netstat -i' is also a good thing to check. If there are any packet errors, particularly if they are going up over time, then there's a physical problem somewhere on your local network. Frequently this is due to bad ethernet cables, but it could be some more expensive bit of hardware going wonky. Also, you need to do: service netif restart && service routing restart to completely refresh your network interfaces. Not restarting the routing explains at least part of what you're seeing. This sort of problem is almost never down to malfeasance -- the black hats would typically rather have control over your fully working hardware and will frequently try and avoid doing anything that would lead to being discovered. Most likely it's a software configuration problem, or failing that, hardware failure. Cheers, Matthew --lNDIvrNXDCFdr50DftsM3L5Jv6AWM182H-- --1xcC1g0Rcna0jGOl1UBnCCm1xw3C9qpJW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJXlki2XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTn4qcQALeGXgysdcbEmhR8emf87sQJ EjRz+1fZr7Htqm1H9FTcBR6xsx12fZUpYMmzN8Q/vFdb0LM6M+78A6aSWNGAwW7k z7ORk5V03lqnA2v+f7uWUzSQLQtxEQgoeds3IyH5gAG/zdHzBiC2hcXnvX969Fy8 dLyTHC/62Y/cxJIKkmv2udJo5r+48fZ8Q7jpYgjooPLkUcmZodI+LYEsMiwrHaEY hP5FY3wuPg3EhnaGjG8F+CS/ljHS4wH9qkLbO3ZDrl1MKZ84y6up78C4C+Mi7Z6M 1U6QbVoTGIQFvJftj1G4DObD+uE03DWeSOAsikvLCGCArSceUEj+PD7IeDk1kVMk yoLTxDHQesqD3kMARpfqZvZp2j8X4UgUpYoGUbJTffpxol4oKhy04N7XRTDS7cEg BWlHjPKvSD1zaX1u14B2bVpgGnosQ6iQwF8T6FJ/2c+r4XE+UNRmahrTBX59n4EM HEbHTGU1haHCuWP79qHsCA2kLBHgsW9ZlpoDWpHB4CiiJ2tH2es1bvS6E1ya8KPs S3XvHvL1ks58njYV3f8ag4VJpJSSs6tUplQsl3bm7qNArLPBBs0dDhzXCcSFCrzD crmzOtX5xOy8kpR3MO+sWU259eILFbmE8CrjYYjpunT1oKM2WFwz6kRF5rPVGNNT GdO0PgR7NfZbKrDl+Gts =v75O -----END PGP SIGNATURE----- --1xcC1g0Rcna0jGOl1UBnCCm1xw3C9qpJW--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?156494d2-ae9a-0a3f-a42d-536773187d8a>