You ran some other command not the one I asked for.
Sorry about that here is the correct response:
PS C:\Users\Tom> curl.exe -v http://192.168.0.185:8089
- Rebuilt URL to: http://192.168.0.185:8089/
- Trying 192.168.0.185...
- TCP_NODELAY set
- Connected to 192.168.0.185 (192.168.0.185) port 8089 (#0)
GET / HTTP/1.1
Host: 192.168.0.185:8089
User-Agent: curl/7.55.1
Accept: /
< HTTP/1.1 200 OK
< Content-Type: text/html
< Date: Fri, 26 Mar 2021 21:37:48 GMT
< Content-Length: 1233
<
that doesnt look correct recopying
PS C:\Users\Tom> curl.exe -v http://192.168.0.185:8089
* Rebuilt URL to: http://192.168.0.185:8089/
* Trying 192.168.0.185...
* TCP_NODELAY set
* Connected to 192.168.0.185 (192.168.0.185) port 8089 (#0)
> GET / HTTP/1.1
> Host: 192.168.0.185:8089
> User-Agent: curl/7.55.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: text/html
< Date: Fri, 26 Mar 2021 21:37:48 GMT
< Content-Length: 1233
<
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">
<link rel="icon" type="image/png" href="/favicon-32x32.png" sizes="32x32">
<link rel="icon" type="image/png" href="/favicon-16x16.png" sizes="16x16">
<link rel="manifest" href="/manifest.json">
<meta name="apple-mobile-web-app-capable" content="yes">
<title>Channels DVR</title>
</head>
<body>
<div id="content"></div>
<div id="modal-wrapper"></div>
<div id="modal"></div>
<script async type="text/javascript" src="https://www.gstatic.com/cv/js/sender/v1/cast_sender.js?loadCastFramework=1"></script>
<script type="text/javascript" src="/bundle.js"></script>
<script>
if ('serviceWorker' in navigator) {
navigator.serviceWorker.register('/service-worker.js').then(function(registration) {
console.log('Service worker registration succeeded:', registration)
}, function(error) {
console.log('Service worker registration failed:', error)
})
}
</script>
</body>
</html>
* Connection #0 to host 192.168.0.185 left intact
PS C:\Users\Tom>Your server is working as expected.
Something is up with the browser if its not loading http://192.168.0.185:8089/
You should try that link from another PC or phone or tablet
You can also try to open the browser's javascript console and see if there are errors there when its failing to load
when I tried from the browser on the android box I got the same response. will try my laptop and if all else fail the wife's iMac
If and when I get this configured. How do I add a firewall to the system to block the HDHomerun Prime I have on the SageTV Media Center from the Channels DVR?
Not necessary. Just don't assign guide info to the Prime in Channels, and it won't use the tuner. (Unless something has changed?)
Results--It seems Channels-DVR on a Raspberry Pi4 has a different IP Packet than Channels-DVR on a Win10 platform. My EdgeMax Router-Firewall allowed the Win10 Config to get through, and blocked the Raspberry Pi packets. Configuration packets only. TV Everywhere on my Android box and FireTv sticks no problem.
I disabled the HDHomerun in Config from the Android box TV Everywhere, unfortunately have tuner problem in SageTV since Channels DVR hook up. May have to configure a separate network for the SageTV and the HDHomerun, if it continues.
THANK YOU to tmm1 for your great assistance
Because of the lack of real flexibility with the RPi4 image, I've taken a different tack. I am using an UEFI image/bootloader on an external USB3 drive with a mainline aarch64 Fedora server install. Then I'm running Channels in a container on through podman with a separate macvlan configuration. Haven't had any issue since I started running this several months ago.
I have Ubiquiti ER-4 router, and Unifi switches, and have not had any issues with its EdgeOS firewall.
I have 2x Pi4's as Channels DVR servers.
I also have 2 other Pi4's running a DNS sever and PiVPN.
No issues.
Such routers are not for a novice. it requires moderate to advanced networking skills and previous experience with setting up enterprise routers like Cisco etc.
if it is blocking things, or is the cause of your issues with the pi, then you have it config to do so, or improper config. Do you use advanced routing or VLANS?
If you wish to further trouble shoot your issues, I suggest going to the Ubiquiti forms and post your config there and experts can advise you on what to change or if the router is your issue blocking a network device.
Looks like I get to experiment with a desktop install. Add the UFW firewall block the HDHomerun IP. Install Channels-DVR. Disable my switch firewall and install/config Channels DVR. Re-enable my switch firewall. Because of the channel limitations my cable company put on TV Everywhere it is a backup DVR. But I'm an old retired tech, I believe in fail overs / backups. I like the internet Play On possibilities of Channels DVR, but right now I like the ISP Cable better.
Thank You for sharing your knowledge with me as I worked through the Chanel-DVR Image for Pi4.
I have some networking skills and it is a firewall rule I disabled to get things to work. But I'm a home network, so do not use advanced routing or VLANS. Being retired eliminated the need for such tech. I took on this endeavor with the purpose of learning Linux and backing up my SageTV Media Server. My cable company got a serious case of stupid. They claim they don't support M-cards anymore, but every device they issue to customers use them. I had to give up a 6 tuner cable tuner for a 3 tuner HDHomerun.
The odd thing is config worked from a Win10 Channels setup but not from a Pi4 Channels setup. I do not have the desire to get into the network layers difference between Windows and Linux IP protocols. I have overseen Advanced Cisco switch setups. I do not want or need that complexity at home.
Plenty of people setup advanced routing, or use VLAN in home.
Many folks like certain items, such as IoT to be on one vlan, while other things use another etc. Some ISPs require vlan taging to get connectivity.
Anyways, I guess I just don't really understand what you are trying to do, or why, and to what end. There normally is no reason to use firewall rules to block things in your LAN from communicating with each other.
Clearly you have a non-standard router config, that adds complexity to your network setup, and is the cause of your issue with using the Pi image as intended.
As, a Ubiquiti user, and a Linux, Win10, MacOS user, I have not had any issues whatsoever with the Pi4 using "normal" basic configuration on my networking hardware.