I officially unplugged my 2 Tivos this past weekend. Huge milestone! An end of a VERY long era. I got to re-appropriate one of the cable cards for a second Prime giving me 2 Primes and a Connect. 8 Tuners! It’s exciting.
I’m almost there too. I only used my TiVo once since I started the Alpha for a missed episode on the bad update, and wife and kids are using this too. That’s the most important part.
How’s the iSCSI performance as opposed to NFS or SMB ?
I use it for my vSphere environment - It’s currently serving a couple of VM’s in my lab. Works well, I don’t see many network disconnects and the performance is pretty solid. It helps that I’m using a mirrored pair of 1TB SSDs for the datastore. I only keep my horizon VDI VMs on it - The rest (of my lab) stay on a NFS share that’s on the other HDD volume.
I would just like to say “Thank you” to tmm1 and all Channels Developers for resolving the issue as quickly as you did.
I am a first time user (as of today), and I have a similar setup as blanier, except I have a QNAP TS-453 Pro NAS. The curl command ran successfully, and a quick untick and re-tick of the bonjour service corrected the unavailable DVR function.
I am just waiting for the guide data to download now, and then I think I should be able to start testing the service.
Sounds like I should give the bond devices priority so a bunch more people don’t have to go through this too.
I think as the community grows, you’re going to find a bunch of different use cases for users network setups. Probably the best method is to expose the individual interfaces and then allow the user to check the interfaces that Channels would use. I’m sure i’m trivializing the complexity, but at least it’s an option that allows for maximum flexibility
Is there a way to set the bond devices priority on a windows system running the DVR service? I am having a similar issue when I have a VPN client running. The Apple TV apps doesn’t always see the DVR server and I would like to set just one IP for the Bonjour advertising.
Thank you
Can you send me the output of “ipconfig /all” from your windows machine?
Here you go:
Windows IP Configuration
Host Name . . . . . . . . . . . . : home-dk-01
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hidden.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : hidden.com
Description . . . . . . . . . . . : Sophos SSL VPN Adapter
Physical Address. . . . . . . . . : 00-FF-CF-17-3A-79
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::48c3:2103:1982:97c7%5(Preferred)
IPv4 Address. . . . . . . . . . . : 10.242.2.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Saturday, April 1, 2017 3:50:10 PM
Lease Expires . . . . . . . . . . : Sunday, April 1, 2018 3:50:09 PM
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 10.242.2.254
DHCPv6 IAID . . . . . . . . . . . : 151060431
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-0E-DD-A1-C4-34-6B-73-EA-9E
DNS Servers . . . . . . . . . . . : 192.168.114.10
192.168.114.15
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Connection I217-LM
Physical Address. . . . . . . . . : C4-34-6B-73-EA-9E
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::855c:2f5f:5fa6:6dfc%3(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.99.91(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.99.1
DHCPv6 IAID . . . . . . . . . . . : 63190123
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-0E-DD-A1-C4-34-6B-73-EA-9E
DNS Servers . . . . . . . . . . . : 192.168.99.1
8.8.8.8
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VMware Network Adapter VMnet1:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
Physical Address. . . . . . . . . : 00-50-56-C0-00-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c075:acb7:2fef:37e2%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.79.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 67129430
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-0E-DD-A1-C4-34-6B-73-EA-9E
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VMware Network Adapter VMnet8:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
Physical Address. . . . . . . . . : 00-50-56-C0-00-08
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::90a0:92d4:e920:3b55%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.30.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 151015510
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-0E-DD-A1-C4-34-6B-73-EA-9E
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
@BPH I added that VPN adapter to our internal blacklist, so the latest version shouldn’t have any more issues.
I’m also planning to add some advanced bonjour settings to the UI, so users can pick which adapter they want to use easily on both linux and windows.
Thanks for all the great instructions, y’all. I’m having an issue, though, with my QNAP TS453mini and the bind order. When I follow these instructions I get an Apache 405 error (shown below) for the target IP address. I’ve tried both the bond1 and br1 options that I’ve seen others post but to no avail. If I spin up the DVR on a mac, everything is recognized by the Apple TV app - just the QNAP one won’t appear.
Any thoughts? Help is much appreciated.
curl -XPUT http://192.168.0.14/bonjour/interface/br1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>405 Method Not Allowed</title>
</head><body>
<h1>Method Not Allowed</h1>
<p>The requested method PUT is not allowed for the URL /bonjour/interface/br1.</p>
<hr>
<address>Apache Server at 192.168.0.14 Port 80</address>
</body></html>
Missing :8089
ZOMG, I cannot believe i missed the port.
Thank you and extra thanks for not beating me up on it…
Hi folks, I’ve just finished a big update to our bonjour server which now makes it multi-interface and multi-IP aware. It’s available in the latest DVR pre-release which you can update to manually via the web UI. See NEW: DVR pre-release with Bonjour update (v2018.03.27.0215)
Would you mind testing this out for me and let me know if it works as expected? With the new build, you no longer need the “preferred interface” hack that you’ve been using. So basically update to the pre-release (hold down SHIFT key and click Check for Updates), then remove the preference you had previously set with a command like:
curl -XDELETE http://x.x.x.x:8089/bonjour/interface
or
iwr -Method Delete http://127.0.0.1:8089/bonjour/interface
My server is running on my Mac Studio M1. Details below. My Mac is connected via Ethernet and Wi-Fi. The service-order is set with Ethernet first and Wi-Fi second. Yet the server Bonjour configuration reports the networks in the order of Wi-Fi (192.168.0.72) and then Ethernet (192.168.0.69).
I need to ensure that my clients connect via Ethernet for optimal performance. How can this be accomplished?
OS Apple Mac13,1
Darwin 14.1.2 (kernel: 23.1.0)
CPU 10 cores / Apple M1 Max
load averages: 6.20 6.52 6.01
RAM 64.00 GB 62.9% free
Thank you.
Version 2023.11.13.2159
My suggestion would be to go into your Network Settings and set the WiFi settings for IPV4 to "Off". That way, the network interface is active so AirDrop can work, but nothing else will use that interface.
Thank you. That worked well. The Channels Server Bonjour service only advertises my Ethernet IP address and AirDrop still functions.