So once more I upgraded my system. It gets smother and smother. This time, the only problem I had was that I could not the machine to route any traffic through. It turned out that I should not remove the IPDIVERT option from the kernel config. I dont really understand why since what I read on hte man-pages it should only be used if you divert traffic to a specific socket. I dont think I do that… but I must since I need it.<\/p>\n
EDIT: Should have read the firewall configuration more carefully!
\n # Network Address Translation. This rule is placed here deliberately
\n # so that it does not interfere with the surrounding address-checking
\n # rules. If for example one of your internal LAN machines had its IP
\n # address set to 192.0.2.1 then an incoming packet for it after being
\n # translated by natd(8) would match the `deny’ rule above. Similarly
\n # an outgoing packet originated from it before being translated would
\n # match the `deny’ rule below.
\n case ${natd_enable} in
\n [Yy][Ee][Ss])
\n if [ -n ”${natd_interface}” ]; then
\n ${fwcmd} add divert natd all from any to any via ${natd_interface}
\n fi
\n ;;
\n esac<\/p>\n
There is the rule that use DIVERT!<\/p>\n","protected":false},"excerpt":{"rendered":"
So once more I upgraded my system. It gets smother and smother. This time, the only problem I had was that I could not the machine to route any traffic through. It turned out that I should not remove the … Continue reading