Date: Sun, 30 Apr 2017 15:22:03 -0400 From: George Mitchell <george+freebsd@m5p.com> To: freebsd-hackers@FreeBSD.org Subject: TCP6 problem Message-ID: <82600781-7892-63ea-feac-35a140dbf95d@m5p.com>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--B08votonULj2vlPOBBV9bvomAuf8BMFXi
Content-Type: multipart/mixed; boundary="vhFB3q1MLd9gbWQ85chcSTWwJ3aRbxQim";
protected-headers="v1"
From: George Mitchell <george+freebsd@m5p.com>
To: freebsd-hackers@FreeBSD.org
Message-ID: <82600781-7892-63ea-feac-35a140dbf95d@m5p.com>
Subject: TCP6 problem
--vhFB3q1MLd9gbWQ85chcSTWwJ3aRbxQim
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
In certain cases, TCP6 stopped working between machines on my local
net and the outside world when I updated to 10.3-RELEASE-p18 on my
network. Here is my network setup:
+--------------+ +---------------+
| sullivan | +--------+ | haymarket |
| 6-core | | | | 8-core |
| amd64 alc0 +------+ | switch +-------+ re0 amd64 |
+--------------+ | | 2 | +---------------+
| +--+ +---+
+--------------+ | | | | | +---------------+
| scollay | | | +--------+ | | pi Raspberry |
| 1-core | | | | | Pi (orig.) |
| amd64 nfe0 +----+ | | +---+ ue0 arm |
+--------------+ | | | +--------+ +---------------+
| | | | |
+--------------+ | | +--+ switch | +---------------+
| parkstreet | | +----+ 1 | | mattapan |
| 1-core | +------+ | | 1-core amd64 |
| and64 nfe0 +-----------+ +-------+ alc0 gif0 +---IPv6
+--------------+ +------- + +---------------+ world
Throughout this process, pi has been running 10.3-RELEASE and has not
had any problems.
All the other machines were running 10.3-RELEASE-p13 up until April 17,
when I upgraded them to 10.3-RELEASE-p18. At this point, TCP6 still
worked normally, except on sullivan and scollay. Even sullivan and
scollay can perform TCP6 to other local machines, but it fails in the
following manner when attempted to the outside world, as observed using
tcpdump on the alc0 interface of mattapan and either the alc0 interface
of sullivan or the nfe0 interface of scollay:
sullivan (or scollay) sends SYN.
outside machine replies with SYN/ACK, and sullivan (or scollay)
receives the SYN/ACK.
sullivan (or scollay) replies with ACK (as seen on sullivan or
scollay), but the ACK is not seen at mattapan alc0. sullivan
(or scollay) fruitlessly retransmits the ACK, but it is never
seen at mattapan.
mattapan is using pf filtering on gif0 (which physically is on the
re0 interface), but no other machines are filtering packets.
My best guess at the moment is that somehow tcpdump is lying to me
about the captured packets, because I rebooted mattapan and sullivan
with my /boot/kernel.old and it did not fix the problem. Any clues?
-- George
--vhFB3q1MLd9gbWQ85chcSTWwJ3aRbxQim--
--B08votonULj2vlPOBBV9bvomAuf8BMFXi
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlkGOWEACgkQwRES3m+p
4fl8Xg/+Lya6VmXDhzlkXeDeaPEK5saQmAvLeVACrbyuYB4vAoKPjyxW1/i9Hraa
N8XMF853j4GYz5Iwb++t6YYnwfcDL/ePFqam8z8xZusInD2MsuSb4gdg2NLxFljt
rOHp1Q8xLEYFTll6g6ArZnyPK/53njwvrKcaSTDI1dsu/x6rUvuEH2vUDy+2BDZZ
KORSGfPrgzrgpPXXNS2IFCKmwhaYBCKBFgoitsaqKd/O/1/jn655UqELPNXPRn/m
59/QbFYQB8lJxEnnlzX6JtJfe+oMl2PEr2dq6wmyy6NFfaBJovjH8aWbLAE6y8B7
nXQFKDbI/bR1Fe+z9bc1q9sSO7sosugy0fv2zIr+UyoqMK3blmTmJSUo53zH72YU
DBHLCDf5Yogo+5FDIIKjPN+me9PVLqPVRE0AMutptbTwW3uA1eo+AkaELT6TWKVJ
xCLoWxsXeU19M1LoOZWQEq8mLMTAaldg2QRj9kk3WJt1O4DghAPGG5cQnzwifaZE
dNRY8HBxTssFSVowY/G3qCUPZduhwWNX9nynBhjiNQlqy34p+eBq047E/hHrTdxM
+Sk+JKvB2nCV1R8R/0TZKpKERuhJcyEWTPFCJwiNdQG3+pzjbZD99t7cKSOyxC6E
08H0NTid0S+jdTICE4QSTJVBg79/vBtKuiBqmsZa6awKeSCJPyM=
=A1fS
-----END PGP SIGNATURE-----
--B08votonULj2vlPOBBV9bvomAuf8BMFXi--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?82600781-7892-63ea-feac-35a140dbf95d>