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
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.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
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@xxxxxxxxx> 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 DockerSo the logs after the break show as follows15018 [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 authenticateSince 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 libvirtI 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:ffenp34s0 is my onboard ethernetAll my vm's used bridge type and connected to br0Freepbx 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.
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue