Guest zin105 Posted October 5, 2017 Share Posted October 5, 2017 (edited) I first posted this to the 6.4 forum but I think it applies to current stable version awell. My log is filled with: Oct 2 14:14:03 HTPC kernel: bond0: found a client with no channel in the client's hash table I have a dual NIC that's bonded with mode 6 and a VLAN 20 on top of that for VMs. I also have a seperate NIC for some other VMs. Everything seems to work exactly as expected so the log spam is confusing me. Edited March 13, 2018 by zin105 Quote Link to comment
Guest zin105 Posted October 8, 2017 Share Posted October 8, 2017 No one have any idea what the problem could be? Quote Link to comment
Guest zin105 Posted October 9, 2017 Share Posted October 9, 2017 I removed the VLANs from the bonded interface and use a third NIC for VLANs for now since I got sick of the log spam. Quote Link to comment
bonienl Posted October 9, 2017 Share Posted October 9, 2017 When I have time I will test this. Keep you posted. Quote Link to comment
bonienl Posted October 9, 2017 Share Posted October 9, 2017 I have setup a bonded + bridged interface in load-balancing mode (6). The bonded interface has fixed IP assignments. In addition VLAN 10 is created with a dynamic IP assignment (address 10.0.10.10 is obtained from the DHCP server on this VLAN). Switch is configured with additional VLAN 10 on both interfaces which connect to the server. Made several tests and all is working fine. There are NO error messages and I can't make them appear either. Quote Link to comment
Guest zin105 Posted October 10, 2017 Share Posted October 10, 2017 I set my VLANs to not have an IP adress at all. Doesn't that make unRAID accessible from the VLAN? I create them for seperation, to only have internet access and nothing else. Quote Link to comment
bonienl Posted October 10, 2017 Share Posted October 10, 2017 1 hour ago, zin105 said: I set my VLANs to not have an IP adress at all. Doesn't that make unRAID accessible from the VLAN? I create them for seperation, to only have internet access and nothing else. When the server itself does not need to participate in the communication, no IP assignment is the recommended setting and only VMs or containers have assignments. Tested as well without IP assignment, no errors either. Quote Link to comment
Guest zin105 Posted October 10, 2017 Share Posted October 10, 2017 (edited) Ok this is very strange. I removed all VLANs from the bonded interface, but I'm still getting spammed with bond0: found a client with no channel in the client's hash table The ethernet ports connected to the switch are untagged with VLAN1. Nothing else. Edit: Rebooted and I think it has stopped. Will update otherwise. Edited October 10, 2017 by zin105 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.