Greetings Laine,
I've found the issue, I was able install tcpdump within libreelec, I saw that
the dhcp sends and receives pkts well.
so I've thought it might be related to the, I've replaced type from virtio to
e1000 and it worked.
libreelec uses kernel 5.1.16 so I assume there is a bug there
> > It's just some name tcpdump used to replace the IP address of one of the
> > machines, and since it's the source IP of a DHCP reply packet, it most
> > likely is the IP of the DHCP server.
> ok, sounds reasonable
>
> >
> > > here is the requested dump: https://dpaste.com/849DMX9ND
> >
> > What
Greetings Laine,
> It's just some name tcpdump used to replace the IP address of one of the
> machines, and since it's the source IP of a DHCP reply packet, it most
> likely is the IP of the DHCP server.
ok, sounds reasonable
>
> > here is the requested dump: https://dpaste.com/849DMX9ND
>
>
On 9/6/20 12:02 PM, daggs wrote:
Greetings LAine,
When you say "the vm", you mean the one running libreelec, that is
trying to get and IP address, correct?
yes, you are correct.
I guess Broadcom.home is the IP of the VM that's running the dhcp
server? (I should have suggested using
Greetings LAine,
> When you say "the vm", you mean the one running libreelec, that is
> trying to get and IP address, correct?
yes, you are correct.
> I guess Broadcom.home is the IP of the VM that's running the dhcp
> server? (I should have suggested using "tcpdump -n -e -v" :-/)
>
frankly, I
On 9/4/20 6:47 PM, daggs wrote:
Greetings Laine,
I would start troubleshooting by making sure that the dhcp server is
running, and that you can communicate between the machine with DHCP
server and the guest once a manual IP is assigned. Then use tcpdump or
wireshark at different places on the
Greetings Laine,
> >
> > I would start troubleshooting by making sure that the dhcp server is
> > running, and that you can communicate between the machine with DHCP
> > server and the guest once a manual IP is assigned. Then use tcpdump or
> > wireshark at different places on the path between
Greetings Laine,
> You haven't said which distro, nor what is the libvirt exact libvirt
> version (probably won't matter in this case, but in general "libvirt
> x.y.z" is more useful than "latest stable libvirt").
you are correct, the previous os was debian 10 with libvirt 3, the new os is
On 9/4/20 12:38 AM, daggs wrote:
Greetings,
up until a year ago, I was running a server with Debian 10 (stable) on it with
the latest versions of libvirt, qemu and kernel 4.19.x Debian 10 had to offer
(both libvirt and qemu versions were really old).
the network config was simple, one of the
Greetings,
up until a year ago, I was running a server with Debian 10 (stable) on it with
the latest versions of libvirt, qemu and kernel 4.19.x Debian 10 had to offer
(both libvirt and qemu versions were really old).
the network config was simple, one of the vm acted as a router and provided
10 matches
Mail list logo
