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
Good morning I use ROOTer fw on my Lynksys WRT3200 . On 21.02.snap and 19.07.6 I see the following error when vpnbypass starts but:
Thu Feb 9 12:27:21 2023 daemon.err modprobe: xt_set is already loaded Thu Feb 9 12:27:21 2023 daemon.err modprobe: ip_set is already loaded Thu Feb 9 12:27:21 2023 daemon.err modprobe: ip_set_hash_ip is already loaded Thu Feb 9 12:27:21 2023 user.notice vpnbypass [11293]: ERROR: iptables -t mangle -D PREROUTING -m mark --mark 0x00/0xff0000 -g VPNBYPASS Thu Feb 9 12:27:21 2023 user.notice vpnbypass [11293]: service started with TID: 200; FW_MARK: 0x010000 Thu Feb 9 12:27:21 2023 user.notice vpnbypass [11293]: service monitoring interfaces: VPN VPNS TAP TAPS wan1
also vpnbypass doesnt start after router reboot.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Good morning
I use ROOTer fw on my Lynksys WRT3200 . On 21.02.snap and 19.07.6 I see the following error when vpnbypass starts but:
version of vpnbypass 1.3.2-1
Thu Feb 9 12:27:21 2023 daemon.err modprobe: xt_set is already loaded
Thu Feb 9 12:27:21 2023 daemon.err modprobe: ip_set is already loaded
Thu Feb 9 12:27:21 2023 daemon.err modprobe: ip_set_hash_ip is already loaded
Thu Feb 9 12:27:21 2023 user.notice vpnbypass [11293]: ERROR: iptables -t mangle -D PREROUTING -m mark --mark 0x00/0xff0000 -g VPNBYPASS
Thu Feb 9 12:27:21 2023 user.notice vpnbypass [11293]: service started with TID: 200; FW_MARK: 0x010000
Thu Feb 9 12:27:21 2023 user.notice vpnbypass [11293]: service monitoring interfaces: VPN VPNS TAP TAPS wan1
also vpnbypass doesnt start after router reboot.
The text was updated successfully, but these errors were encountered: