Network errors and timeouts

[smartypantsuk]

Hi,

Regularly I'm getting these errors in the logs and it coincides with either the gui timing out during operations such as app deployments or just general poor/intermittent network performance. I'm not sure what it all means, I've only got one active Ethernet 1GB connection (the other is bios disabled) and I've not touched anything network related from the clean install.

Code:

Feb 17 04:07:18 truenas kernel: bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
Feb 17 04:07:18 truenas kernel: Bridge firewalling registered
Feb 17 04:07:53 truenas kernel: IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP)
Feb 17 04:07:53 truenas kernel: IPVS: Connection hash table configured (size=4096, memory=32Kbytes)
Feb 17 04:07:53 truenas kernel: IPVS: ipvs loaded.
Feb 17 04:07:54 truenas kernel: IPVS: [rr] scheduler registered.
Feb 17 04:07:54 truenas kernel: Initializing XFRM netlink socket
Feb 17 04:07:55 truenas kernel: kube-bridge: port 1(vethe16d190e) entered blocking state
Feb 17 04:07:55 truenas kernel: kube-bridge: port 1(vethe16d190e) entered disabled state
Feb 17 04:07:55 truenas kernel: device vethe16d190e entered promiscuous mode
Feb 17 04:07:55 truenas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe16d190e: link becomes ready
Feb 17 04:07:55 truenas kernel: kube-bridge: port 1(vethe16d190e) entered blocking state
Feb 17 04:07:55 truenas kernel: kube-bridge: port 1(vethe16d190e) entered forwarding state
Feb 17 04:07:55 truenas kernel: kube-bridge: port 2(vetha46b6fa4) entered blocking state
Feb 17 04:07:55 truenas kernel: kube-bridge: port 2(vetha46b6fa4) entered disabled state
Feb 17 04:07:55 truenas kernel: device vetha46b6fa4 entered promiscuous mode
Feb 17 04:07:55 truenas kernel: kube-bridge: port 2(vetha46b6fa4) entered blocking state
Feb 17 04:07:55 truenas kernel: kube-bridge: port 2(vetha46b6fa4) entered forwarding state
Feb 17 04:15:15 truenas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5eb4987d: link becomes ready
Feb 17 04:15:15 truenas kernel: kube-bridge: port 3(veth5eb4987d) entered blocking state
Feb 17 04:15:15 truenas kernel: kube-bridge: port 3(veth5eb4987d) entered disabled state
Feb 17 04:15:15 truenas kernel: device veth5eb4987d entered promiscuous mode
Feb 17 04:15:15 truenas kernel: kube-bridge: port 3(veth5eb4987d) entered blocking state
Feb 17 04:15:15 truenas kernel: kube-bridge: port 3(veth5eb4987d) entered forwarding state
Feb 17 04:15:29 truenas kernel: kube-bridge: port 3(veth5eb4987d) entered disabled state
Feb 17 04:15:29 truenas kernel: device veth5eb4987d left promiscuous mode
Feb 17 04:15:29 truenas kernel: kube-bridge: port 3(veth5eb4987d) entered disabled state
Feb 17 04:15:32 truenas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2c5a2516: link becomes ready
Feb 17 04:15:32 truenas kernel: kube-bridge: port 3(veth2c5a2516) entered blocking state
Feb 17 04:15:32 truenas kernel: kube-bridge: port 3(veth2c5a2516) entered disabled state
Feb 17 04:15:32 truenas kernel: device veth2c5a2516 entered promiscuous mode
Feb 17 04:15:32 truenas kernel: kube-bridge: port 3(veth2c5a2516) entered blocking state
Feb 17 04:15:32 truenas kernel: kube-bridge: port 3(veth2c5a2516) entered forwarding state

Anyone?

Thanks