03-21-2023, 08:24 PM
(03-21-2023, 07:07 PM)TheOldPresbyope Wrote: Could be...but it seems a better audience would be the gurus who hang out on the Raspberry Pi Forum (I'd go there first) or the counterpart github repo (I'd go there only if I had a pretty clear idea of the source of the incompatibilities, but that's just me).
If you had a USB-Ethernet adapter (or USB-WiF adapter for that matter) lying around, you could bypass the Ethernet aspect of the LAN9514 as a test of your hypothesis.
The difficulty with such problems is to find out where exactly the error lies.
Only then it is possible to say to which place it is best to turn to get help.
In any case, I am extremely grateful for your helpful tips and the time you take!
I had an Ugreen USB-to-Ethernet adapter (AX88179A chip) here that I had just tested to be able to exclude the LAN9514 chip as the cause of the error.
But also with this adapter I get the same error.
After I had dismantled everything again, I have undertaken another test.
I have activated the DLNA server in addition to the UPnP renderer.
The network technology used is basically the same. Multicast packets are sent here as well.
Curiously, the DLNA server from Moode can be displayed at the UPnP control points and at the BubbleUPnP server. However, the UPnP renderer from Moode on the same device does not.
What can be deduced from this?
(03-21-2023, 08:13 PM)Tim Curtis Wrote: I just tested with my Pi-1B both Ethernet and WIFi and no issues whatsoever. I set Server type to "OpenHome" in UPnP Config and "Moode UPNP" renderer showed up in Linn Kazoo after a bit.
This indicates no hardware incompatibility between Pi-1B and UPnP stack.
This makes the whole thing seem even stranger.
What makes your setup different from mine?
Is there a particular setting I made that doesn't exist in your setup that could cause complications here?
I already posted my system information in the first post.
