Date: Thu, 11 Feb 2016 14:23:18 -0600 From: Larry Rosenman <ler@lerctr.org> To: Kristof Provost <kp@freebsd.org> Cc: Freebsd current <freebsd-current@freebsd.org> Subject: Re: IPV6 TCP6 Slow Connect Message-ID: <b152cabdaafbbfea7b17c7ebb4a0fb35@thebighonker.lerctr.org> In-Reply-To: <20160211101449.GI19084@vega.codepro.be> References: <8ca0068954b5cb25891c3324b2e8c863@thebighonker.lerctr.org> <20160211101449.GI19084@vega.codepro.be>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-02-11 04:14, Kristof Provost wrote: > On 2016-02-10 20:38:02 (-0600), Larry Rosenman <ler@lerctr.org> wrote: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206904 >> >> I've also posted lots of info to freebsd-net, and not gotten any >> response. >> >> Summary: >> >> Cable Modem-> EM0 on a pfSense Firewall (FreeBSD 10.1, pfSense 2.2.6) >> set to dhcp6, and ask for a /56 prefix >> >> EM1->LAN, set to track interface, prefix id 0, radvd running >> advertising >> the 00 /64 >> LAN-> borg.lerctr.org using lagg0, SLAAC (rtsold). Gets an address, >> icmp6 works, tcp6 times out. >> -> win10 SLAAC, tcp6 works fine, as does icmp6. >> > For this I'd start by taking packet captures of both the FreeBSD tcp6 > connection and the win10 tcp6 connection. Finding the difference > between > the two will likely go a long way in finding the cause. > > Regards, > Kristof From which system(s) perspective do you want the packet captures? (Firewall, FreeBSD, Windows)? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b152cabdaafbbfea7b17c7ebb4a0fb35>