We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seems like a kernel-side shit
12-26 17:48:34.388 835 1155 I chatty : uid=1000(system) SoundPoolThread expire 12 lines 12-26 17:48:34.391 266 290 W IptablesRestoreController: iptables-restore process 272 terminated status=256 12-26 17:48:34.394 266 290 W IptablesRestoreController: iptables-restore process 273 terminated status=256 12-26 17:48:34.394 266 290 E IptablesRestoreController: iptables error: 12-26 17:48:34.394 266 290 E IptablesRestoreController: ------- COMMAND ------- 12-26 17:48:34.394 266 290 E IptablesRestoreController: *filter 12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_penalty_log -j CONNMARK --or-mark 0x1000000 12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_penalty_log -j NFLOG --nflog-group 0 12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_penalty_reject -j CONNMARK --or-mark 0x2000000 12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_penalty_reject -j NFLOG --nflog-group 0 12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_penalty_reject -j REJECT 12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_clear_detect -m connmark --mark 0x2000000/0x2000000 -j REJECT 12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_clear_detect -m connmark --mark 0x1000000/0x1000000 -j RETURN 12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_clear_detect -p tcp -m u32 --u32 "52>>26&0x3C@ 40&0xFFFF0000=0x16030000 &&52>>26&0x3C@ 44&0x00FF0000=0x00010000" -j CONNMARK --or-mark 0x1000000 12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_clear_detect -p udp -m u32 --u32 "48&0xFFFF0000=0x16FE0000 &&60&0x00FF0000=0x00010000" -j CONNMARK --or-mark 0x1000000 12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_clear_detect -m connmark --mark 0x1000000/0x1000000 -j RETURN 12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_clear_detect -p tcp -m state --state ESTABLISHED -m u32 --u32 "52>>26&0x3C@ 40&0x0=0x0" -j st_clear_caught 12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_clear_detect -p udp -j st_clear_caught 12-26 17:48:34.394 266 290 E IptablesRestoreController: COMMIT 12-26 17:48:34.394 266 290 E IptablesRestoreController: 12-26 17:48:34.394 266 290 E IptablesRestoreController: ------- ERROR ------- 12-26 17:48:34.394 266 290 E IptablesRestoreController: ip6tables-restore: line 227 failed
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Seems like a kernel-side shit
12-26 17:48:34.388 835 1155 I chatty : uid=1000(system) SoundPoolThread expire 12 lines
12-26 17:48:34.391 266 290 W IptablesRestoreController: iptables-restore process 272 terminated status=256
12-26 17:48:34.394 266 290 W IptablesRestoreController: iptables-restore process 273 terminated status=256
12-26 17:48:34.394 266 290 E IptablesRestoreController: iptables error:
12-26 17:48:34.394 266 290 E IptablesRestoreController: ------- COMMAND -------
12-26 17:48:34.394 266 290 E IptablesRestoreController: *filter
12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_penalty_log -j CONNMARK --or-mark 0x1000000
12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_penalty_log -j NFLOG --nflog-group 0
12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_penalty_reject -j CONNMARK --or-mark 0x2000000
12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_penalty_reject -j NFLOG --nflog-group 0
12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_penalty_reject -j REJECT
12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_clear_detect -m connmark --mark 0x2000000/0x2000000 -j REJECT
12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_clear_detect -m connmark --mark 0x1000000/0x1000000 -j RETURN
12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_clear_detect -p tcp -m u32 --u32 "52>>26&0x3C@ 40&0xFFFF0000=0x16030000 &&52>>26&0x3C@ 44&0x00FF0000=0x00010000" -j CONNMARK --or-mark 0x1000000
12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_clear_detect -p udp -m u32 --u32 "48&0xFFFF0000=0x16FE0000 &&60&0x00FF0000=0x00010000" -j CONNMARK --or-mark 0x1000000
12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_clear_detect -m connmark --mark 0x1000000/0x1000000 -j RETURN
12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_clear_detect -p tcp -m state --state ESTABLISHED -m u32 --u32 "52>>26&0x3C@ 40&0x0=0x0" -j st_clear_caught
12-26 17:48:34.394 266 290 E IptablesRestoreController: -A st_clear_detect -p udp -j st_clear_caught
12-26 17:48:34.394 266 290 E IptablesRestoreController: COMMIT
12-26 17:48:34.394 266 290 E IptablesRestoreController:
12-26 17:48:34.394 266 290 E IptablesRestoreController: ------- ERROR -------
12-26 17:48:34.394 266 290 E IptablesRestoreController: ip6tables-restore: line 227 failed
The text was updated successfully, but these errors were encountered: