Question

modprobe: ERROR: could not insert 'ip6_tables': Unknown symbol in module, or unknown parameter

Posted October 6, 2016 4.3k views
DebianIPv6

kernel : linux-image-3.16.0-4-amd64

dmesg output :

[29203904.204752] ip6_tables: disagrees about version of symbol xt_compat_match_from_user
[29203904.204761] ip6_tables: Unknown symbol xt_compat_match_from_user (err -22)
[29203904.206552] ip6_tables: Unknown symbol xt_compat_check_entry_offsets (err 0)
[29203904.206617] ip6_tables: Unknown symbol xt_check_entry_offsets (err 0)
[29203904.206637] ip6_tables: Unknown symbol xt_copy_counters_from_user (err 0)
[29203910.877127] ip6_tables: disagrees about version of symbol xt_compat_match_from_user
[29203910.877133] ip6_tables: Unknown symbol xt_compat_match_from_user (err -22)
[29203910.877209] ip6_tables: Unknown symbol xt_compat_check_entry_offsets (err 0)
[29203910.877248] ip6_tables: Unknown symbol xt_check_entry_offsets (err 0)
[29203910.877267] ip6_tables: Unknown symbol xt_copy_counters_from_user (err 0)
[29203914.281423] ip6_tables: disagrees about version of symbol xt_compat_match_from_user
[29203914.281430] ip6_tables: Unknown symbol xt_compat_match_from_user (err -22)
[29203914.281508] ip6_tables: Unknown symbol xt_compat_check_entry_offsets (err 0)
[29203914.281548] ip6_tables: Unknown symbol xt_check_entry_offsets (err 0)
[29203914.281567] ip6_tables: Unknown symbol xt_copy_counters_from_user (err 0)

It appears this module is missing. ‘iptables’ works fine, the only issue is with 'ip6tables’

edited by asb
1 comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer
ip6_tables: disagrees about version of symbol xt_compat_match_from_user

This error occurs due to unmatching versions of the kernel and its modules. Usually this means that you have upgraded your kernel but have not rebooted your Droplet after doing so. Try rebooting your Droplet and seeing if you still receive the same error.

Submit an Answer