From owner-freebsd-bugs@freebsd.org Fri Nov 24 13:21:00 2017 Return-Path: Delivered-To: freebsd-bugs@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 DEFD1DE53EE for ; Fri, 24 Nov 2017 13:21:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CD555740EB for ; Fri, 24 Nov 2017 13:21:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vAODL05x020868 for ; Fri, 24 Nov 2017 13:21:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 223835] BGP session not established with md5 password via FRRouting Date: Fri, 24 Nov 2017 13:21:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: pautina@kharkiv.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2017 13:21:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223835 --- Comment #8 from Alexey --- (In reply to Andrey V. Elsukov from comment #6) >This means that socket is configured to receive and send TCP MD5 signature= s, but TCP segments has wrong signatures. You need to make sure that used p= assword is correct. I copied the password from the emails and use this password for tcpdump wti= s -M I run tcpdump: 'tcpdump -M some_password -i vlan62 -vvv -n host 185.1.62.69= and port bgp' go to vtysh and run: clear ip bgp 185.1.62.69 after this have res= ults in attachment --=20 You are receiving this mail because: You are the assignee for the bug.=