Comment 3 for bug 2025532

Thanks for the patch.

I'm uncomfortable applying as is because (AIUI) /proc/net/if_inet6 won't exist on kernels where ipv6 is compiled as a module but isn't loaded yet. ufw starts very in boot before network interfaces are up and I suspect if this patch were applied there might be times when ufw is started, would detect /proc/net/if_inet6 isn't there, would fail to put the rules in place, only to have the ipv6 module loaded after when interfaces come up. On a system like yours where you've removed ipv6 support and you know it, this is fine but it wouldn't be good for ufw in general.

I can say that ufw operates fine when the kernel is booted with ipv6.disable=1. It seems like you perhaps left out too much of your custom kernel? Or, left too much in since 'ip6tables -L INPUT -n' is showing that the input chain is available?

I've made this change to ufw to give a better diagnostic for this situation: https://git.launchpad.net/ufw/commit/?id=a024e6824c777518ad463abde4cdfc00ee3a4e20

I'm going to close this for now since ufw is designed to be run on general purpose systems with more or less standard kernel config and so as it stands, this falls outside of the project's scope. I suggest that you continue to patch ufw for your needs or explore your kernel config.

Thanks again for your report.