fareign

Results 40 comments of fareign
trafficstars

so it need to restart XRAY Jan 9 07:15:44 OpenMPTCProuter daemon.info procd: - init complete - Jan 9 07:15:44 OpenMPTCProuter daemon.info xray[28355]: Xray 1.8.6 (Xray, Penetrates Everything.) Custom (go1.21.4 linux/amd64)...

Jan 28 08:54:38 OpenMPTCProuter daemon.err omr-tracker[6233]: sh: 33.3333: bad number

root@OpenMPTCProuter:/tmp# cat ssrules.nft set ss_rules_src_bypass { type ipv4_addr; flags interval; auto-merge; } set ss_rules6_src_bypass { type ipv6_addr; flags interval; auto-merge; } set ss_rules_src_forward { type ipv4_addr; flags interval; auto-merge; }...

root@OpenMPTCProuter:/tmp# uci show shadowsocks-libev shadowsocks-libev.hi1=ss_redir shadowsocks-libev.hi1.server='sss0' shadowsocks-libev.hi1.local_address='::' shadowsocks-libev.hi1.local_port='1100' shadowsocks-libev.hi1.mode='tcp_and_udp' shadowsocks-libev.hi1.timeout='1000' shadowsocks-libev.hi1.fast_open='1' shadowsocks-libev.hi1.verbose='0' shadowsocks-libev.hi1.syslog='1' shadowsocks-libev.hi1.reuse_port='1' shadowsocks-libev.hi1.mptcp='1' shadowsocks-libev.hi1.ipv6_first='1' shadowsocks-libev.hi1.no_delay='1' shadowsocks-libev.hi1.ebpf='0' shadowsocks-libev.hi2=ss_redir shadowsocks-libev.hi2.server='sss0' shadowsocks-libev.hi2.local_address='::' shadowsocks-libev.hi2.local_port='1101' shadowsocks-libev.hi2.mode='tcp_and_udp' shadowsocks-libev.hi2.timeout='1000' shadowsocks-libev.hi2.fast_open='1' shadowsocks-libev.hi2.verbose='0' shadowsocks-libev.hi2.syslog='1' shadowsocks-libev.hi2.reuse_port='1' shadowsocks-libev.hi2.mptcp='1' shadowsocks-libev.hi2.ipv6_first='1'...

this problem cause on startup.not working.

> I'm not able to reproduce these errors, can you try again with latest snapshot ? Do you import a previous config ? Do you use snapshot image or custom...

I use an old snap firmware which download at 2023.12.21 is OK openmptcprouter-v0.60beta1-6.1-r0+24041-74e7f8ebbd-x86-64-generic-ext4-combined-efi (3).img

I found the problem. it must use more than one interface .

> Interface status is checked with OMR-Tracker, so if master interface is down then routes are removed and another interface is used. @Ysurac I know OMR-tracker do this JOB, but...