From owner-freebsd-questions@freebsd.org Tue Feb 14 04:07:27 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2CB3FCDE782 for ; Tue, 14 Feb 2017 04:07:27 +0000 (UTC) (envelope-from thenewcq@optimum.net) Received: from mta4.srv.hcvlny.cv.net (mta4.srv.hcvlny.cv.net [167.206.4.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.optonline.net", Issuer "DigiCert SHA2 Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E59731FA4 for ; Tue, 14 Feb 2017 04:07:26 +0000 (UTC) (envelope-from thenewcq@optimum.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=optimum.net; s=dkim-001; t=1487044037; bh=bVQEkWTc19YhBQ20o6K7Bb9O/yCkyzh9PpbNivEAssU=; h=Date:From:To:Subject:Message-ID; b=MGLUMyPIYuULR8K9PKi0IgUkfdGvC0pHqpSCJUAINkyUN68o3HpjF8Kjxc1fC0Dsu mGMYfCVPRTiZKfYtgmPjTWWuJuQScg0BJ/Hu8z1W/sD85x0M14wPRE6mjJ9pqsKEGs eJjf4WVxcwqYNjOitScPrpgu8+dY/7/OeuZw9ejn3lFkbT2N+2XZbv+edYBrqmNQur ACBGQJsX+6W5huAQauuy3+eXR2l9GRDxJ2tBRCzkS6cmACD4ZmYsym0ig4AhIdpXDw lgiaifPTEDhzIpn6RYgY46L83woIwVENafM99eH5QL2oVN2s2HNg1fkLtzmK5jms7W X0V0B+69rorEA== X-Content-Analysis: v=2.1 cv=dOJb47tb c=1 sm=1 tr=0 a=6ZHx/kdBrWiwm0FuVBO0fg==:117 a=6ZHx/kdBrWiwm0FuVBO0fg==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=kj9zAlcOel0A:10 a=bAAmCkz9I0oA:10 a=5VuI2xrpEGUaiI7bqU4A:9 a=CjuIK1q_8ugA:10 Received: from [69.125.2.106] ([69.125.2.106:13468] helo=newer.home) by mta4.srv.hcvlny.cv.net (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id AB/11-27613-5CD72A85; Mon, 13 Feb 2017 22:47:17 -0500 Date: Mon, 13 Feb 2017 22:47:37 -0500 From: sixto areizaga To: freebsd-questions@freebsd.org Cc: Polytropon , Jon Radel Subject: Re: wireshark issue Message-ID: <20170213224737.087dcdb3@newer.home> In-Reply-To: <20170213043346.863220d1.freebsd@edvax.de> References: <20170209174405.5d551b88@newer.home> <20170212121809.5bf28626@newer.home> <20170213043346.863220d1.freebsd@edvax.de> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; i386-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Feb 2017 04:07:27 -0000 I apologize this is a little wordy, I just tried to answer everything all at once...I am thinking its not wireshark. Let me know if you find anything interesting... IP = 119.249.54.71 $ whois 119.249.54.71 inetnum: 119.248.0.0 - 119.251.255.255 netname: UNICOM-HE descr: China Unicom Heibei Province Network I concluded windows because, Putty is a windows program. Nmap scan report for 119.249.54.71 Host is up (0.36s latency). Not shown: 993 closed ports PORT STATE SERVICE VERSION 25/tcp filtered smtp 135/tcp filtered msrpc 139/tcp filtered netbios-ssn 445/tcp filtered microsoft-ds 593/tcp filtered http-rpc-epmap 4444/tcp filtered krb524 6006/tcp open tcpwrapped I googled krb524 it was super-interesting, check it out from wireshark.... No. time source destination protcol length info 71 41.065180 119.249.54.71 192.168.#.# SSHv2 81 Client: Protocol (SSH-2.0-PUTTY) 72 41.088654 192.168.#.# 119.249.54.71 SSHv2 104 Server: Protocol (SSH-2.0-OpenSSH_7.2 FreeBSD-20160310) > /var/log/security > and /var/log/auth.log should be interesting. show nothing for this IP. a few days before there is a different IP, I am looking into that now. Well, I dont think the vulnorability was in wireshark... I think I am having a "pest" problem...