Date: Thu, 10 May 2018 18:08:26 +0300 From: Alexander Zagrebin <alex@zagrebin.ru> To: freebsd-net@freebsd.org Subject: Re: kernel: in6_delayed_cksum: delayed m_pullup Message-ID: <20180510180826.7bb1d861@vm2.home.zagrebin.ru> In-Reply-To: <007101d3e86f$196e4fb0$4c4aef10$@gmail.com> References: <5ae60f44.1c69fb81.ee4a5.1043@mx.google.com> <20180429190450.GA97911@tom-desk.erg.abdn.ac.uk> <5ae6cbc7.1c69fb81.ed649.655e@mx.google.com> <20180510134746.GD37534@tom-desk.erg.abdn.ac.uk> <007101d3e86f$196e4fb0$4c4aef10$@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
В Thu, 10 May 2018 16:56:38 +0200 "Dries Michiels" <driesm.michiels@gmail.com> пишет: > I had updated the day after to see if it was just a regression but > the error message was not gone: May 1 22:19:51 vados kernel: > in6_delayed_cksum: delayed m_pullup, m->len: 48 plen 68 off 56 > csum_flags=400<CSUM_IP6_TCP> May 1 22:27:57 vados last message > repeated 29 times May 1 22:36:53 vados last message repeated 17 > times May 1 22:49:41 vados last message repeated 6 times May 1 > 23:00:09 vados last message repeated 8 times May 1 23:01:06 vados > last message repeated 7 times May 1 23:18:05 vados last message > repeated 12 times For this reason I had disabled IPV6 for my LAN > clients (disabled rtadvd). My server was still ipv6 reachable and > error messages where gone. I've observed such messages when ipv6 packets was passed via ipv4 NAT. After changing ipfw rule from (for example) nat 1 ip from any to me in via re1 to nat 1 ipv4 from any to me in via re1 this messages has gone. -- Alexander Zagrebin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180510180826.7bb1d861>