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
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
On 2/14/22 10:18 AM, Tom Ammon wrote:
Laine,
Though I can't remember the particulars, I have a vague memory of the
sysctl settings in that article indeed solving the problem of traffic
not being forwarded on the bridge when I had configured no filtering on
the guest - hence my attempt to s
Hi Michal,
I am able to build qemu with the options you have suggested. It indeed is a
qemu issue. Thank you for pointing that out.
On Mon, Feb 14, 2022 at 3:51 PM Michal Prívozník
wrote:
> On 2/14/22 10:09, Sai Kiran Kumar Reddy wrote:
> > Hi Peter,
> >
> > Thanks for your inputs. I have looke