On 6/18/20 1:35 PM, Lamar Owen wrote:
So, I set up another development host, but this time using a team instead of a bond, and I'm going to try to get that working with bridged networking to a virtual guest, since it really is supposed to work, and I'm very curious why it didn't.
So, finally got back around to this. So, on this host I had set up a team0 with a bridge192 and with the bridge192 having an IP address, etc. That all worked fine. However, after creating a guest on this host, the guest had no connectivity through the same bridge. So, I thought I might see what setting the hairpin option might do, on the port of the bridge connected to the team. Well, lo and behold, after setting this up in the cockpit web interface, and after the networking restart initiated by cockpit, now I have connectivity to the guest. HOWEVER, the bridge port is NOT showing hairpin as configured. Could it have been the connection restart that connected the bridge port up correctly, since the guest was running which the connection restart occurred? Whatever; it is now passing traffic with no other configuration changes.
Now to see if I can duplicate this on a reboot later this week; that server is busy running some other things right now.
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx https://lists.centos.org/mailman/listinfo/centos
