Re: IPV6 TCP6 Slow Connect

On Fri, Feb 12, 2016 at 07:56:08AM -0600, Larry Rosenman wrote:

> On 2016-02-12 07:45, Slawa Olhovchenkov wrote:
> > On Thu, Feb 11, 2016 at 08:50:59PM -0600, Larry Rosenman wrote:
> > 
> >> On 2016-02-11 14:40, Larry Rosenman wrote:
> >> 
> >> > On 2016-02-11 14:25, Kristof Provost wrote:
> >> >
> >> > On 11 Feb 2016, at 21:23, Larry Rosenman <ler_at_lerctr.org> wrote:
> >> > From which system(s) perspective do you want the packet captures?
> >> > (Firewall, FreeBSD, Windows)? I wouldn't expect it to make much of a difference in this case.
> >> > Let's start with whatever is easiest.
> >> >
> >> > Regards,
> >> > Kristof
> >> 
> >> I'll try and get these tonight when I am home, after a meetup.
> >> 
> >> (will be late US/CST).
> >> 
> >> --
> >> Larry Rosenman                     http://www.lerctr.org/~ler
> >> Phone: +1 214-642-9640                 E-Mail: ler_at_lerctr.org
> >> US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961
> >> 
> >> at http://www.lerctr.org/~ler/FreeBSD/win10.pcap
> >> 
> >> http://www.lerctr.org/~ler/.FreeBSD/fbsd11.pcap
> >> 
> >> Please let me know what else you need.
> >> 
> >> I **CAN** supply accesss to a _at_FreeBSD.org developer to:
> >> 
> >> 1) the FreeBSD 11 host
> >> 
> >> 2) the FreeBSD(pfSense) Firewall
> >> 
> >> 3) the IPv6 host (FreeBSD 10) that I ssh'd to.
> >> 
> >> 4) the FireWall in front of the FreeBSD 10 box (also pfSense)
> > 
> > First try: MTU issuse (1480, not 1500)?
> how do I change the MTU on a LAGG interface?
> 
> borg.lerctr.org /usr/src # ifconfig lagg0 mtu 1300
> ifconfig: ioctl SIOCSIFMTU (set mtu): Invalid argument
> borg.lerctr.org /usr/src #
> 
> how can I change it on a lagg interface?

Change MTU on members.

ix0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8407bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO>
        ether 90:e2:ba:27:ff:b8
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: Ethernet autoselect (10Gbase-SR <full-duplex,rxpause,txpause>)
        status: active
ix1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8407bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO>
        ether 90:e2:ba:27:ff:b8
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: Ethernet autoselect (10Gbase-SR <full-duplex,rxpause,txpause>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128 
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 
        inet 127.0.0.1 netmask 0xff000000 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8407bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO>
        ether 90:e2:ba:27:ff:b8
        inet 37.220.36.11 netmask 0xffffff00 broadcast 37.220.36.255 
        nd6 options=9<PERFORMNUD,IFDISABLED>
        media: Ethernet autoselect
        status: active
        laggproto lacp lagghash l2,l3,l4
        laggport: ix0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
        laggport: ix1 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>

> And, I still find it weird that Windows on the same lan segment, with a 
> 1500 MTU,
> can connect.

I am don't see in win10.pcap large packets.
All packets under 1KB.