u/capilot

Thinking of uninstalling and reinstalling, but don't want to lose all my saved games.

Posting here in the hopes that someone finds it useful. If I've gotten anything wrong, please let me know and I'll correct it. I will add to this post as I learn more.

Overview

• IP cameras use static IP addresses. These are assigned at the factory and should be written on the box. The IP address can be changed in the camera's configuration interface. For example, the cameras that came with my Swann system have IP addresses starting with 172.16.1.151.
• There is no "probe" function. That is, your NVR can't just go out, look for cameras, and then determine exactly what those cameras are. You need the exact camera model and IP address and give that information to the NVR. You might be able to scan the network for IP addresses, but only if the cameras are on the subnet you're scanning and you still won't have the make and model.
• Cameras have a command-and-control interface on port 80 (yes, each camera has its own tiny built-in web server).
  • The starting page url varies according to the camera model. Typically /, /index.asp, /doc/page/login.asp (Common for Hikvision OEM cameras), or /login.htm
  • There is no way to know what the starting url is unless you know the camera model.
• Actual video data is accessed via the RTSP protocol. The typical URI for the video stream is e.g. RTSP://[camera IP]:554/ch01/1.
  • Again, there is no way to know the exact URI without knowing the exact camera model. Blue Iris can infer most of the URI for you as long as you get the model correct.
• The VLC media player understands RTSP protocol. If you can connect a computer to the same network as your camera, and you know the correct URI for the camera's video stream, you can access the camera directly from VLC without needing Blue Iris or any other NVR. This is an excellent way to confirm the camera is functional and you have the right URI.

Connecting cameras

• To configure a camera before connecting it to your NVR, you'll need to find a way to connect to the camera's configuration interface via http on port 80. A "null modem" ethernet cable or a dedicated switch would do the trick. You'll need to set your computer's ethernet interface to the same network as the camera. Once connected, you can change the camera's IP address as needed.
• One approach is to set the camera's IP address to an unused address on your house network. Then your NVR will be able to access the camera over the house network. This has the advantage that any computer in the house can look at any camera using VLC. It has the disadvantage that everything on the house network may be competing with the cameras for bandwidth. You will also need to program your house router to reserve those addresses for the cameras and not to assign them to any other device on the network. This is also a security risk as it brings attackers one step closer to being able to look through your cameras.
• A better approach is to give the cameras a private network by using a dedicated switch or a router for the cameras. If these are PoE (power over ethernet) cameras, they'll already have a dedicated switch anyway.
  • If all of the cameras' static IP addresses are all on the same subnet, you won't even need to modify them. Just use that subnet for your dedicated camera network. For example, my Swann cameras are all on the 172.16.x.x subnet.
  • Connect your cameras to your PoE switch, and then connect that switch to the ethernet port on your computer.
  • Go to Control Panel and manually configure the ethernet port. Give it an IP address on the same subnet as the cameras, but at an address that none of the cameras use. For example, my Swann cameras have addresses 172.16.1.151 - 172.16.1.158, so I choose 172.16.1.10 for my computer's ethernet port.
  • The configuration interface on your computer will probably automatically assign the correct subnet mask. Leave gateway and nameserver fields blank, as your private camera network has neither.

---

Hubs and switches and routers, oh my

A very quick suplemental primer of how ethernet works and what's the difference between hubs, switches, and routers.

The basic concept behind ethernet is that all the computers transmit their data "into the ether" to be received by any other computer interested in receiving it. In the old days, ethernet was literally a coaxial cable snaking through the ceiling, going from room to room. Any computer on the network literally tapped into the cable. Any time a computer wanted to send data to another computer, it transmitted a packet of data onto that wire. The packet contains the IP address of both the sending computer and the intended recipient. All computers received the packet, but all but the recipient simply dropped the packet. Only one computer at a time can transmit, and if two accidentally transmit at the same time, they both stop, wait a random amount of time, and try again.

Nowadays, the data is transmitted and received over four wires in a CAT 5,6, or 7 cable to a dedicated transceiver box which then relays the data back out to other computers over their own cables.

There are basically three types of tranceiver boxes:

• Hub. This is conceptually the same as simply connecting all those cables together. A signal sent by one computer is received by all and then discarded by most. This is much like OG ethernet in that every computer receives every transmission and only one computer at a time can transmit.
• Switch. This is most likely what you'll be using to connect your cameras. A switch keeps track of which IP address belongs to which cable. An incoming message is examined to see what computer it's intended for, and then sent out to only that computer. Multiple sender/receiver pairs can be active at once as long as there's no collision. This allows much greater bandwidth on the network.
  • Most relevant for switches: if your cameras and your computer are all connected to a switch, it doesn't matter if they're all on the house network as the data from the cameras will be sent directly to the computer and the other devices on the house network will not need to compete for bandwidth most of the time.
• Router: A router is a switch that also knows how to route packets back and forth between two networks. You most likely already have a router at home, as this is what provides connectivity between your ISP's "wide area network" (WAN) and your house's "local area network" (LAN).
  • Unlike switches and hubs, routers do require some configuration. If your ISP provided your router, they likely took care of this for you. But either way, you may want to modify the configuration slightly. In particular, you might want to assign your NVR system a fixed IP address and then set up the router to make that IP address accessible from the outside world so you can access your NVR when you're away. If your cameras are on the house network, you'll also want to configure the router's DHCP service so that it never assigns those addresses to another system.

Wanting to retire my NVR8-8580 and replace with BI. I don't want to replace the cameras for obvious reasons. Searching indicates that the cameras are either NHD-887MSFB or NHD-885MSFB.

I ask Google if these cameras work with BI, and the Google AI responds

> Yes, Blue Iris can work with Swann NHD-887MSFB and NHD-885MSFB cameras, but they must be connected directly to your local network via a PoE switch rather than isolated behind a proprietary Swann NVR.

but AI is notoriously unreliable about things like this.

For the life of me, I can't get them to work. What I've done so far:

• Before shutting down the Swann NVR, I looked at the list of cameras and noted their IP addresses. These were all 172.16.1.15x.
• Plugged the cameras into a PoE switch which was then plugged into the ethernet jack on my PC
• On the PC, configured that port to have static IP address 172.16.1.10
• Went through the "Add a camera" dialog on BI. Sometimes I left the http: field blank, sometimes I manually entered the IP address of one of the cameras. When I left that field blank, it found the first two cameras but that's all.
• I tried setting the Vendor/Model to Swann/something similar to NHD-887.

All cameras report RTSP: 400 Bad Request.

Any ideas how I should proceed?

Say I have a bowl that was hand-built in a previously-bisque-fired form. It's too fragile to remove from the form for firing. Can I just fire them together?

(Maybe a bowl isn't the best example since shrinkage as it dries makes this all moot, but you get the idea.)

I was looking at this Beelink mini PC which caught my attention because it has two ethernet ports. Would it be practical to use one port to connect to the network and dedicate the other to the cameras? I assume I'd have to configure the system to provide DHCP to that one port. Would there be any real advantage?

And now that I think about it, even a single-port system could dedicate one port to the cameras and use WiFi to connect to the network at large.

Now when I select "Log in" I get taken to bambulabs instead, and my login that worked at makerworld no longer works.

It wasn't until the second reading that I realized who the drifter was. It wasn't until the third reading that I caught the glowing paste he used on his paddle. Or the significance of his stealing something from the cavern.

I have to say, the writing this season is absolutely epic.