On 2/16/22 4:40 AM, Peter Crowther wrote:
... 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.
It's not the IP address of the bridge, it's the IP address of the
"default / built-in" port of the bridge. The standard way
>
> ... 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.
>
>
??? Depends on how you use it.
... 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 wrote:
> On 15 Feb 2022, at 20:04, Peter Crowther
> wrote:
>
>
> And eno1 and eno2 are *both* connected to the same
On 15 Feb 2022, at 20:04, Peter Crowther mailto: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.
And eno1 and eno2 are *both* connected to the same external switch, yes?
Cheers,
Peter
On Tue, 15 Feb 2022 at 17:17, Wolf 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
>
> 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 b
