... hang on. Why does the *bridge* have an IP address? Think of a bridge as being like a switch; it has no address of its own.
Cheers, Peter On Tue, 15 Feb 2022 at 20:21, Wolf <ort_libv...@bergersen.no> wrote: > On 15 Feb 2022, at 20:04, Peter Crowther <peter.crowt...@melandra.com> > wrote: > > > And eno1 and eno2 are *both* connected to the same external switch, yes? > > > Correct, where each NIC has its ip access-list. > XX1.XX1.XX1.150 and XX2.XX2.XX2.100 are on separate NICs. > > When I ping the VM, XX2.XX2.XX2.100, from the host, XX1.XX1.XX1.150, the > host pings itself. > > Thanks! > > Wolf > > > > > On Tue, 15 Feb 2022 at 17:17, Wolf <ort_libv...@bergersen.no> wrote: > >> Hi! >> >> 1) I have two network ports on my server. >> - eno1 has the IP: XX1.XX1.XX1.150 >> >> - bridge0 has the IP: XX2.XX2.XX2.100 >> and has the interface member: port eno2. >> eno2 is not set up with an IP address. >> >> 2) The host runs on IP: XX1.XX1.XX1.150 >> >> 3) A VM uses the bridge: bridge0, and has the IP: XX2.XX2.XX2.100 >> >> I have a problem with this setup: >> I can ssh the VM on XX2.XX2.XX2.100 from outside, but from the host, >> XX1.XX1.XX1.150, I can't ssh the VM on XX2.XX2.XX2.100. >> >> Have I set up this wrong or is it something I can do to solve this? >> >> Thanks! >> >> Wolf >> >> >> >
