rdmitry0911

Here it is: ``` omr-bypass.all=interface omr-bypass.m6replay=proto omr-bypass.m6replay.url='m6web.fr' '6play.fr' '6cloud.fr' omr-bypass.mycanal=proto omr-bypass.mycanal.url='mycanal.fr' 'canal-plus.com' 'canalplus.com' 'canalplus-cdn.net' 'canalplus.pro' 'canal-plus.net' omr-bypass.minecraft=proto omr-bypass.minecraft.url='authserver.mojang.com' omr-bypass.lesnumeriques=proto omr-bypass.lesnumeriques.url='lesnumeriques.com' 'botscorner.com' 'app.botscorner.com' omr-bypass.disneyplus=proto omr-bypass.disneyplus.url='bamgrid.com' 'disney-plus.net' omr-bypass.amazonvideo=proto omr-bypass.amazonvideo.url='cloudfront.net' 'llnw.net' omr-bypass.free=proto omr-bypass.free.url='free.fr'...

in /etc/firewall.omr-bypass I need ``` nft insert rule inet fw4 ss_rules_pre_tcp ip daddr @omr_dst_bypass_eth0_4 meta mark set 0x45391001 accept nft insert rule inet fw4 ss_rules_local_out ip daddr @omr_dst_bypass_eth0_4 meta mark...

I've just checked /etc/init.d/omr-bypass and found inconsistency in naming with /etc/config/firewall. In /etc/config/firewall there are separate rules for ipv4 and ipv6 For example there is such a rule: ``` config...

Where can I get the fix?

Ok, I managed to build image from the developer branch with the latest commits and found out that you made substantial changes to omr-bypass logic. Now I see the correct...

Still not all the problems are resolved. When I added another interfaces eth4 and eth5 for bypassing it got the same metric for them as for the previous one. And...

It's here: ``` root@OpenMPTCProuter:~# uci show network network.loopback=interface network.loopback.proto='static' network.loopback.ipaddr='127.0.0.1' network.loopback.netmask='255.0.0.0' network.loopback.multipath='off' network.loopback.device='lo' network.loopback.metric='1000' network.globals=globals network.globals.ula_prefix='fdcf:f4c9:d08e::/48' network.globals.multipath='enable' network.globals.mptcp_path_manager='fullmesh' network.globals.mptcp_scheduler='blest' network.globals.congestion='bbr' network.globals.mptcp_checksum='0' network.globals.mptcp_debug='0' network.globals.mptcp_syn_retries='4' network.globals.mptcp_subflows='8' network.globals.mptcp_add_addr_accepted='1' network.globals.mptcp_add_addr_timeout='120' network.globals.mptcp_pm_type='0' network.globals.mptcp_disable_initial_config='0' network.globals.mptcp_force_multipath='1' network.globals.mptcpd_enable='0'...

Here they are: ``` root@OpenMPTCProuter:~# uci show openmptcprouter.wan1.metric openmptcprouter.wan1.metric='2' root@OpenMPTCProuter:~# uci show openmptcprouter.wan2.metric openmptcprouter.wan2.metric='3' root@OpenMPTCProuter:~# uci show openmptcprouter.wan3.metric openmptcprouter.wan3.metric='1' root@OpenMPTCProuter:~# uci show openmptcprouter.wan4.metric openmptcprouter.wan4.metric='1' root@OpenMPTCProuter:~# uci show openmptcprouter.wan5.metric openmptcprouter.wan5.metric='1' ```

I also noticed, that if I delete an interface, for example wan3 and then add a new one using settings wizard, the script will assign a next number to it....

> Ok, thank you