Networking issue from 2 network interface unable to access network from second interface

I have 2 network interface connecting each on a specific network.
the default gw is 192.168.50.1 on enp6s0.
The second interface is connecting to network 192.168.100.0/24 with address 192.168.100.26 as enp7s0. I am unable to access an address on 192.168.100.0/24 network. I tried everything I know, to no sucess. I have install a jailmaker docker on interface enp7s0, from the docker container I have no issue access any address on network 196.168.100.0/26. itried also to add a route for 192.168.100.0/24 with Gateway address 192.168.100.1., with a response that route already exist. I missing something, just don’t what.Anyone can help figure out what is missing ?
Here some command I tried with the result:

root@new-mikey[~]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         GT-BE98_Pro-135 0.0.0.0         UG    0      0        0 enp6s0
172.16.0.0      0.0.0.0         255.255.0.0     U     0      0        0 kube-bridge
192.168.50.0    0.0.0.0         255.255.255.0   U     0      0        0 enp6s0
192.168.100.0   0.0.0.0         255.255.255.0   U     0      0        0 enp7s0
root@new-mikey[~]# ping 192.168.100.52
PING 192.168.100.52 (192.168.100.52) 56(84) bytes of data.
From 192.168.100.26 icmp_seq=1 Destination Host Unreachable
From 192.168.100.26 icmp_seq=2 Destination Host Unreachable
From 192.168.100.26 icmp_seq=3 Destination Host Unreachable
From 192.168.100.26 icmp_seq=4 Destination Host Unreachable
^C
--- 192.168.100.52 ping statistics ---
5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4047ms
pipe 4
root@new-mikey[~]# ping 192.168.50.7
PING 192.168.50.7 (192.168.50.7) 56(84) bytes of data.
64 bytes from 192.168.50.7: icmp_seq=1 ttl=128 time=0.195 ms
64 bytes from 192.168.50.7: icmp_seq=2 ttl=128 time=0.270 ms
64 bytes from 192.168.50.7: icmp_seq=3 ttl=128 time=0.309 ms
^C
--- 192.168.50.7 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2041ms
rtt min/avg/max/mdev = 0.195/0.258/0.309/0.047 ms
root@new-mikey[~]# ip route add 192.168.100.0/24 via 192.168.100.1
RTNETLINK answers: File exists
root@new-mikey[~]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         GT-BE98_Pro-135 0.0.0.0         UG    0      0        0 enp6s0
172.16.0.0      0.0.0.0         255.255.0.0     U     0      0        0 kube-bridge
192.168.50.0    0.0.0.0         255.255.255.0   U     0      0        0 enp6s0
192.168.100.0   0.0.0.0         255.255.255.0   U     0      0        0 enp7s0

From the Jail container:

root@new-mikey[~]# jlmkr shell docker 
Connected to machine docker. Press ^] three times within 1s to exit session.
root@docker:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.100.1   0.0.0.0         UG    0      0        0 mv-enp7s0
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
172.18.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-965aee7b3882
172.19.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-3d4b4b730839
192.168.100.0   0.0.0.0         255.255.255.0   U     0      0        0 mv-enp7s0
root@docker:~# ping 192.168.100.52
PING 192.168.100.52 (192.168.100.52) 56(84) bytes of data.
64 bytes from 192.168.100.52: icmp_seq=1 ttl=64 time=0.019 ms
64 bytes from 192.168.100.52: icmp_seq=2 ttl=64 time=0.024 ms
^C
--- 192.168.100.52 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1031ms
rtt min/avg/max/mdev = 0.019/0.021/0.024/0.002 ms

I have a router GT-BE98_Pro, with a the vlan 50 (192.168.100.0/24) and default lan as 192.168.50.0/24. At this level everything is work fine.
From a windows machine connecting to network 192.168.50.0/24:

ping 192.168.100.52

Envoi d’une requête 'Ping'  192.168.100.52 avec 32 octets de données :
Réponse de 192.168.100.52 : octets=32 temps=16 ms TTL=63
Réponse de 192.168.100.52 : octets=32 temps<1ms TTL=63
Réponse de 192.168.100.52 : octets=32 temps=1 ms TTL=63