From srv01 (192.168.1.205) to gwith02 (host to VM vlan25, 192.168.25.75) I can join simply advantageous. Nevertheless, since this site visitors forwards by the br25 bridge, the site visitors supply is from 192.168.25.250. That is advantageous for srv01 -> gwith02. Nevertheless, site visitors initiated from gwith02 -> srv01 will not get there (by identify). I’ve to do that numerically, by the br25 bridge.
I do not suppose it is a routing concern. Is there one thing I can do to the bridge to vary this?
A easy illustration:
srv01> curl gwith02 # 192.168.25.75 howdy my identify is gwith02 gwith02> curl srv01 # 192.168.1.205 ... no response gwith02> curl 192.168.25.250 # aka br25 howdy my identify is srv01
srv01> ip route default through 192.168.1.1 dev br0 proto static 192.168.1.0/24 dev br0 proto kernel scope hyperlink src 192.168.1.205 192.168.25.0/24 dev br25 proto kernel scope hyperlink src 192.168.25.250
srv01> ip addr * notice: 1: simply loopback, 6:, 7:, and so on. are simply virt nics for hosts 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel grasp br0 state UP group default qlen 1000 hyperlink/ether 90:b1:1c:a0:b6:a5 brd ff:ff:ff:ff:ff:ff altname enp0s25 3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 hyperlink/ether a6:79:99:d5:b0:de brd ff:ff:ff:ff:ff:ff inet 192.168.1.205/24 brd 192.168.1.255 scope world br0 valid_lft perpetually preferred_lft perpetually inet6 fe80::a479:99ff:fed5:b0de/64 scope hyperlink valid_lft perpetually preferred_lft perpetually 4: br25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 hyperlink/ether be:4b:ed:b2:0d:69 brd ff:ff:ff:ff:ff:ff inet 192.168.25.250/24 brd 192.168.25.255 scope world br25 valid_lft perpetually preferred_lft perpetually inet6 fe80::bc4b:edff:feb2:d69/64 scope hyperlink valid_lft perpetually preferred_lft perpetually 5: vlan25@eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue grasp br25 state UP group default qlen 1000 hyperlink/ether 90:b1:1c:a0:b6:a5 brd ff:ff:ff:ff:ff:ff 6: vnet0: ... 7: vnet1: ...
gwith02> ip addr 2: ens6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 hyperlink/ether 52:54:00:87:24:cd brd ff:ff:ff:ff:ff:ff altname enp0s6 inet 192.168.25.75/24 brd 192.168.25.255 scope world ens6 valid_lft perpetually preferred_lft perpetually inet6 fe80::5054:ff:fe87:24cd/64 scope hyperlink valid_lft perpetually preferred_lft perpetually
gwith02> ip route default through 192.168.25.1 dev ens6 proto static 192.168.25.0/24 dev ens6 proto kernel scope hyperlink src 192.168.25.75
gwith02> ping -c 1 srv01 PING srv01.vv.web (192.168.1.205) 56(84) bytes of knowledge. 64 bytes from srv01.sfio.win (192.168.1.205): icmp_seq=1 ttl=64 time=0.274 ms
gwith02> traceroute srv01 traceroute to srv01 (192.168.1.205), 30 hops max, 60 byte packets 1 192.168.25.1 (192.168.25.1) 0.334 ms 0.306 ms 0.399 ms 2 srv01.vv.web (192.168.1.205) 0.329 ms 0.391 ms *
