Witam,

mam taką sytuację że na serwerze z Debian (IP: 192.168.0.2 i brama: 192.168.0.1) zainstalowałem Docker.
W samym dokerze jest skonfigurowane połączenie sieciowe macvlan o nazwie "BRAMA2" gdzie brama ma IP: 192.168.0.5 (to jest 2gi router z innym netem). Ustawiłem tam w kontenerze IP 192.168.0.99 ...

Teraz kłopot polega na tym ze kontener widzi wszystkie IP w sieci, a klienci widzą 192.168.0.99 i wyświetlają NextCloud, tylko że kontyner nie widzi 192.168.0.2, a serwer (192.168.0.2) nie widzi 192.168.0.99

Jak zrobić by doker macvlan widział lokalny serwer i na odwrót?

root@SERWER:/etc# ifconfig
docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        inet6 fe80::42:bfff:fe8e:983a  prefixlen 64  scopeid 0x20<link>
        ether 02:42:bf:8e:98:3a  txqueuelen 0  (Ethernet)
        RX packets 69944564  bytes 10205298778 (9.5 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 78000014  bytes 12082607454 (11.2 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.2  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::e611:5bff:fe33:c9ad  prefixlen 64  scopeid 0x20<link>
        ether e4:11:5b:33:c9:ad  txqueuelen 1000  (Ethernet)
        RX packets 929271003  bytes 811597569369 (755.8 GiB)
        RX errors 15  dropped 35208685  overruns 0  frame 9
        TX packets 881867400  bytes 721647652760 (672.0 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xd0400000-d0420000

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 63838  bytes 3855284 (3.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 63838  bytes 3855284 (3.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth70b8ec5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::347c:c9ff:fe62:9be9  prefixlen 64  scopeid 0x20<link>
        ether 36:7c:c9:62:9b:e9  txqueuelen 0  (Ethernet)
        RX packets 110  bytes 47045 (45.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 125  bytes 21855 (21.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vethaee0cd3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::b8a6:e4ff:fee9:6405  prefixlen 64  scopeid 0x20<link>
        ether ba:a6:e4:e9:64:05  txqueuelen 0  (Ethernet)
        RX packets 14145  bytes 23751259 (22.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 20006  bytes 2066670 (1.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vethbce57c5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::e4d7:1eff:fe6b:eb81  prefixlen 64  scopeid 0x20<link>
        ether e6:d7:1e:6b:eb:81  txqueuelen 0  (Ethernet)
        RX packets 2638  bytes 2744599 (2.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2931  bytes 906525 (885.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vethcf49baf: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::10e9:76ff:fef0:f41a  prefixlen 64  scopeid 0x20<link>
        ether 12:e9:76:f0:f4:1a  txqueuelen 0  (Ethernet)
        RX packets 3  bytes 171 (171.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 36  bytes 3853 (3.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0