[prev in list] [next in list] [prev in thread] [next in thread]
List: fedora-list
Subject: Re: Change in behavior of libvirt networking
From: Jeff Sadowski <jeff.sadowski () gmail ! com>
Date: 2023-01-29 17:27:46
Message-ID: CAM9ceLjC8Qudpkf1fK6G0bFWeQLthEM86gP2upStb+ZEhH2r8w () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I am using Fedora 37.
# uname -a
Linux methanemaker.mooo.com 6.1.7-200.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC
Wed Jan 18 17:11:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Installed Packages
libvirt.x86_64 8.6.0-5.fc37
@updates
libvirt-client.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-config-network.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-config-nwfilter.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-interface.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-libxl.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-lxc.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-network.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-nodedev.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-nwfilter.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-qemu.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-secret.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-storage.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-storage-core.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-storage-disk.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-storage-gluster.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-storage-iscsi.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-storage-iscsi-direct.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-storage-logical.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-storage-mpath.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-storage-rbd.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-storage-scsi.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-storage-sheepdog.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-storage-zfs.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-driver-vbox.x86_64 8.6.0-5.fc37
@updates
libvirt-daemon-kvm.x86_64 8.6.0-5.fc37
@updates
libvirt-dbus.x86_64 1.4.0-6.fc37
@fedora
libvirt-gconfig.x86_64 4.0.0-6.fc37
@fedora
libvirt-glib.x86_64 4.0.0-6.fc37
@fedora
libvirt-gobject.x86_64 4.0.0-6.fc37
@fedora
libvirt-libs.x86_64 8.6.0-5.fc37
@updates
python3-libvirt.x86_64 8.6.0-1.fc37
@fedora
On Sun, Jan 29, 2023 at 10:01 AM Jeff Sadowski <jeff.sadowski@gmail.com>
wrote:
> I have a freepbx vm. A month ago it was working perfectly.
> Then either a patch or me playing with docker broke something. ( I had
> updated my system before starting to play with Docker
> So the logs after the break show as follows
>
> 15018 [2023-01-25 18:53:59] NOTICE[32354] res_pjsip/pjsip_distributor.c:
> Request 'INVITE' from '"My Name " <sip:+(My Phone Number)@(freepbxvm ip)>'
> failed for '(host ip):26346' (callid: e87aca96e0e926db@(obi200 local sip
> provider ip)) - No matching endpoint found
> 15019 [2023-01-25 18:53:59] NOTICE[32354] res_pjsip/pjsip_distributor.c:
> Request 'INVITE' from '"My Name " <sip:+(My Phone Number)@(freepbxvm ip)>'
> failed for '(host ip):26346' (callid: e87aca96e0e926db@(obi200 local sip
> provider ip)) - No matching endpoint found
> 15020 [2023-01-25 18:53:59] NOTICE[32354] res_pjsip/pjsip_distributor.c:
> Request 'INVITE' from '"My Name " <sip:+(My Phone Number)@(freepbxvm ip)>'
> failed for '(host ip):26346' (callid: e87aca96e0e926db@(obi200 local sip
> provider ip)) - Failed to authenticate
> 15021 [2023-01-25 18:53:59] NOTICE[32354] res_pjsip/pjsip_distributor.c:
> Request 'INVITE' from '"My Name " <sip:+(My Phone Number)@(freepbxvm ip)>'
> failed for '(host ip):26346' (callid: e87aca96e0e926db@(obi200 local sip
> provider ip)) - No matching endpoint found
> 15022 [2023-01-25 18:53:59] NOTICE[32354] res_pjsip/pjsip_distributor.c:
> Request 'INVITE' from '"My Name " <sip:+(My Phone Number)@(freepbxvm ip)>'
> failed for '(host ip):26346' (callid: e87aca96e0e926db@(obi200 local sip
> provider ip)) - Failed to authenticate
>
> Since I had started playing with docker and created an ipvlan. I tried
> removing the ipvlan but the behavior is the same. I do not expect the (host
> ip) to be in the logs at all since it is not sending that traffic. I can
> ping the ip of the (obi200) with no issues. That is the device ip I expect
> instead of the (host ip).
>
> A long time ago when I started using libvirt
> I had turned off Network manager on my machine and am using systemd to set
> up my network.
> In /etc/systemd/network/
> I have 3 files 1-br0-bind.network, 2-br0-static.network and vr.netdev
>
> # cat /etc/systemd/network/1-br0-bind.network
> [Match]
> Name=enp34s0
> [Network]
> Bridge=br0
>
> # cat /etc/systemd/network/2-br0-static.network
> [Match]
> Name=br0
> [Network]
> Address=192.168.0.7/24
> Gateway=192.168.0.1
> [Resolve]
> DNS=192.168.0.7 8.8.8.8
> Domains=my.domain
>
> # cat vr.netdev
> [NetDev]
> Name=br0
> Kind=bridge
> MACAddress=aa:bb:cc:dd:ee:ff
>
> enp34s0 is my onboard ethernet
>
> All my vm's used bridge type and connected to br0
> Freepbx seems to be a little more picky.
> For now a solution that worked for me was to use a second ethernet card
> for my freepbx vm to use. Instead of bridge mode I selected direct attach.
> But I would like to solve what happened so I can move it back to my bridge
> interface I had set up for my vm's.
>
>
[Attachment #5 (text/html)]
<div dir="ltr">I am using Fedora 37.<div># uname -a<br>Linux <a \
href="http://methanemaker.mooo.com">methanemaker.mooo.com</a> 6.1.7-200.fc37.x86_64 \
#1 SMP PREEMPT_DYNAMIC Wed Jan 18 17:11:49 UTC 2023 x86_64 x86_64 x86_64 \
GNU/Linux<br></div><div>Installed Packages<br>libvirt.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-client.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-config-network.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-config-nwfilter.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-interface.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-libxl.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-lxc.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-network.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-nodedev.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-nwfilter.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-qemu.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-secret.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-storage.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-storage-core.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-storage-disk.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-storage-gluster.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-storage-iscsi.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-storage-iscsi-direct.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-storage-logical.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-storage-mpath.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-storage-rbd.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-storage-scsi.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-storage-sheepdog.x86_64 \
8.6.0-5.fc37 @updates<br></div><div>libvirt-daemon-driver-storage-zfs.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-driver-vbox.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-daemon-kvm.x86_64 \
8.6.0-5.fc37 @updates<br>libvirt-dbus.x86_64 \
1.4.0-6.fc37 @fedora <br>libvirt-gconfig.x86_64 \
4.0.0-6.fc37 @fedora <br>libvirt-glib.x86_64 \
4.0.0-6.fc37 @fedora <br>libvirt-gobject.x86_64 \
4.0.0-6.fc37 @fedora <br>libvirt-libs.x86_64 \
8.6.0-5.fc37 @updates<br>python3-libvirt.x86_64 \
8.6.0-1.fc37 @fedora <br></div></div><br><div class="gmail_quote"><div \
dir="ltr" class="gmail_attr">On Sun, Jan 29, 2023 at 10:01 AM Jeff Sadowski <<a \
href="mailto:jeff.sadowski@gmail.com">jeff.sadowski@gmail.com</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I have \
a freepbx vm. A month ago it was working perfectly.<div>Then either a patch or me \
playing with docker broke something. ( I had updated my system before starting to \
play with Docker</div><div>So the logs after the break show as \
follows</div><div><br></div><div>15018 [2023-01-25 18:53:59] NOTICE[32354] \
res_pjsip/pjsip_distributor.c: Request 'INVITE' from '"My Name \
" <sip:+(My Phone Number)@(freepbxvm ip)>' failed for '(host \
ip):26346' (callid: e87aca96e0e926db@(obi200 local sip provider ip)) - No \
matching endpoint found<br>15019 [2023-01-25 18:53:59] NOTICE[32354] \
res_pjsip/pjsip_distributor.c: Request 'INVITE' from '"My Name \
" <sip:+(My Phone Number)@(freepbxvm ip)>' failed for '(host \
ip):26346' (callid: e87aca96e0e926db@(obi200 local sip provider ip)) - No \
matching endpoint found<br>15020 [2023-01-25 18:53:59] NOTICE[32354] \
res_pjsip/pjsip_distributor.c: Request 'INVITE' from '"My Name \
" <sip:+(My Phone Number)@(freepbxvm ip)>' failed for '(host \
ip):26346' (callid: e87aca96e0e926db@(obi200 local sip provider ip)) - Failed to \
authenticate<br>15021 [2023-01-25 18:53:59] NOTICE[32354] \
res_pjsip/pjsip_distributor.c: Request 'INVITE' from '"My Name \
" <sip:+(My Phone Number)@(freepbxvm ip)>' failed for '(host \
ip):26346' (callid: e87aca96e0e926db@(obi200 local sip provider ip)) - No \
matching endpoint found<br>15022 [2023-01-25 18:53:59] NOTICE[32354] \
res_pjsip/pjsip_distributor.c: Request 'INVITE' from '"My Name \
" <sip:+(My Phone Number)@(freepbxvm ip)>' failed for '(host \
ip):26346' (callid: e87aca96e0e926db@(obi200 local sip provider ip)) - Failed to \
authenticate<br></div><div><br></div><div>Since I had started playing with docker and \
created an ipvlan. I tried removing the ipvlan but the behavior is the same. I do not \
expect the (host ip) to be in the logs at all since it is not sending that traffic. I \
can ping the ip of the (obi200) with no issues. That is the device ip I expect \
instead of the (host ip).<br></div><div><br></div><div>A long time ago when I \
started using libvirt</div><div>I had turned off Network manager on my machine and am \
using systemd to set up my network.</div><div>In /etc/systemd/network/</div><div>I \
have 3 files 1-br0-bind.network, 2-br0-static.network and \
vr.netdev</div><div><br></div><div># cat /etc/systemd/network/1-br0-bind.network \
<br>[Match]<br>Name=enp34s0<br>[Network]<br>Bridge=br0<br></div><div><br></div><div># \
cat /etc/systemd/network/2-br0-static.network \
<br>[Match]<br>Name=br0<br>[Network]<br>Address=<a href="http://192.168.0.7/24" \
target="_blank">192.168.0.7/24</a><br>Gateway=192.168.0.1<br>[Resolve]<br>DNS=192.168.0.7 \
8.8.8.8<br>Domains=my.domain<br></div><div><br></div><div># cat vr.netdev \
<br>[NetDev]<br>Name=br0<br>Kind=bridge<br>MACAddress=aa:bb:cc:dd:ee:ff<br></div><div><br></div><div>enp34s0 \
is my onboard ethernet<br></div><div><br></div><div>All my vm's used bridge type \
and connected to br0</div><div>Freepbx seems to be a little more \
picky.</div><div><div>For now a solution that worked for me was to use a second \
ethernet card for my freepbx vm to use. Instead of bridge mode I selected direct \
attach. But I would like to solve what happened so I can move it back to my bridge \
interface I had set up for my vm's.</div><div><br></div></div></div> \
</blockquote></div>
[Attachment #6 (text/plain)]
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic