I am pretty sure the hdhomerun usually needs a dhcp server to get an ip address. there may be some default ip address. I don't see that my hdhomeruns have a way to set an ip address.
If there is a default ip address then both the adapter and the hdhome run need to be in the same subnet, and network manager appears to be doing an generally useless autoconfig ip address and if the hdhome run does not use an ip address in the same subnet (or use autoconfig ip address) and/or requires dhcp then it won't have an ip address in the right subnet and/or you won't know what its ip address is. If you are expecting autoconfig to be used then you need to figure out what ip address on the other end is.
nmap -sn 169.254.20.0/24 will scan the subnet.
tcpdump -i eno1 will show you what traffic is seen. This is a direct cable to the hdhomerun?
On Sat, Mar 19, 2022 at 6:37 PM Geoffrey Leach <geoffleach.gl@xxxxxxxxx> wrote:
_______________________________________________There is only one computer involvedHDHomerun is a box that converts OTA TV channels (i.e., a tuner) to a feed that is accessed by the local system.What is working? the code that accesses the ethernet feed, as far as I can tell
What isn't working? The connection between the local computer and the box that is supposed to receive and convert the OTA signal.% nmcli connection showCommunity support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx>On 3/19/22 16:18, Geoffrey Leach wrote:
NAME UUID TYPE DEVICE
NETGEAR78 a0ff17c5-90a4-4d27-99eb-21c0f59dd954 wifi wlp0s26u1u5
HDHomeRun d1e4d6c6-b6e1-32e9-ad5c-b005b7546f4c ethernet eno1
% nmcli connection reload
% nmcli connection up eno1
% ifconfig eno1
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.20.5 netmask 255.255.255.0 broadcast 169.254.20.255
inet6 fe80::ae29:5a0c:d1c4:5032 prefixlen 64 scopeid 0x20<link>
ether e8:40:f2:05:de:1c txqueuelen 1000 (Ethernet)
RX packets 63 bytes 21234 (20.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 30 bytes 3666 (3.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xf7d00000-f7d20000
> F35, fresh install. I have an ethernet-connected device (HDHomerun,
> fwiw) newly re-compiled on the newly-installed F35 xfce4 workstation. As
> far as I can tell from trying every network analysis I can find, the
> connection is good (exception, no response to ping) The interface was
> configured with the NetworkManager app, that assigned the device eno1.
>
> I'm sure that somewhere in all of the data that I collected, the problem
> sticks out like the proverbial sore thumb, but not to me, alas.
You need to provide more details. I don't understand what you're trying
to do and what isn't working. As far as I can tell, "HDHomerun" is some
sort of software.
How many computers are involved?
What is working?
What isn't working?
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 on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure
