Swann CONHD-A4MPCAM — need help accessing cameras independently after NVR failure

S

SwannNovice

n3wb
May 18, 2026
10
0
Calgary
My Swann NVR has died and I am trying to access my CONHD-A4MPCAM PoE cameras independently. Here is everything I have tried:
  • Camera pings immediately at correct IP
  • Not Hikvision based — SADP finds zero devices
  • Not ONVIF compliant — ONVIF Device Manager finds nothing
  • SwannView Link says "login failed" on all attempts with passwords: blank, admin, 12345, 888888, 666666 and custom NVR password
  • VLC RTSP fails after 8-9 seconds on all channels 1-8
  • Cannot locate physical reset button yet
  • Camera is 2016 era wired PoE

Does anyone know the underlying manufacturer, default credentials, or reset button location for this specific model?
 
Ok, Thank you. I am now to this type of posting (a forum newbie). I will delete the other post.
I will also click the link you suggested after deleting the other post
 
Can you please tell me if you link in your post is valid? When I click on it there is an error message "The requested thread could not be found" Can you provide an active link if it exists
 
That was the link to your other thread that you deleted - I added it in the event you couldn't delete it that people would see there were two threads and should only comment in one.
 
Keep in mind NVRs assign the cameras an IP address different than the IP address of the NVR.

Swann PoE NVRs typically assign internal cameras IP addresses in the 172.16.25.x or 172.16.1.x subnets, so you would have to put your network or a computer with the cameras connected to a POE switch on that subnet to access them.
 
Ok thank you. Does it make any difference that I was able to connect an "air gapped" router to a single camera (as a bench test) and then the router to a Win11 computer (all isolated on the same network).

Since I don't have a POE switch (at least not yet - until I can confirm the 8 identical Swann cameras are viable either through Blue Iris or a Linux software). So I found 3 switching power supplies and connected to my camera because it also has a power input plug cable separate from the CAT5 supplied power. When connected to the wall power - the IR lights turn on with a click in the dark. The air gapped router gave the camera the IP address of 192.168.1.3 with the laptop being 192.168.1.2 and router being 192.168.1.1 . I was able to ping the camera with immediate response (0 ms) and no failed out of (I think) 4 trials. It is then, I tried the VLC media player commands which failed (I think because they were based on Hikivision?)

The NVR has literally smoked (with actual a burned smell and no power (so it is now unplugged) and completely inaccessible. I do have a program called Swannview link on my desktop computer and tried to connect to the camera via that software as well but it reported "Login: Failed" when I tried 9000 and the routers given IP address of the specific camera.

I will try the other options in my previous post as well as your suggestion of trying 172.16.25.x or 172.16.1.x subnets, I think I can set the router to whatever DHCP I prefer - do you have a suggestion? I assume it will have to be 172.16.25.1 (??) with the camera assigned a static or dynamic IP address (?). I have no real background in networking and could use any suggestions you would have.
 

I have 8 Swann security cameras manufactured by Shenzhen Baichuan Digital Technology that I'm trying to integrate with Blue Iris video management software. Standard approaches (VLC, direct RTSP, ONVIF) don't work because these cameras use a proprietary Baichuan protocol on port 9000, not standard RTSP on port 554.​


The solution is Neolink, which acts as a protocol translator (Baichuan → RTSP). I was initially attempting this on Windows 11 but hit a dead end with GStreamer DLL issues. I've now pivoted to Linux Mint 22.3 Xena, which should be more straightforward.

Current situation: Linux environment is ready, network connectivity is proven, but Neolink won't run due to a TOML parsing error.



Hardware & Network Details​


Camera Specifications:
  • Manufacturer: Shenzhen Baichuan Digital Technology
  • MAC Address: EC:71:DB:51:2E:B2
  • Default Credentials: admin / 123456 (assumed)
  • Network IP: 172.16.25.57 (on isolated 172.16.25.x laboratory subnet)
  • Only Open Port: 9000/tcp (Baichuan protocol)
  • Closed Port: 554 (RTSP is blocked)
  • Network Response: 0.3–0.7ms ping (sub-millisecond, extremely healthy)

Linux Machine:
  • OS: Linux Mint 22.3 Xena (freshly upgraded)
  • IP: 172.16.25.3
  • Connection: Wired Ethernet
  • GStreamer: Installed via apt (complete with RTSP components)
  • Neolink: Version 0.6.2 (linux_x86_64_ubuntu build)

Network Connectivity Verified:

$ ping 172.16.25.57<br>64 bytes from 172.16.25.57: icmp_seq=1 ttl=64 time=0.456 ms<br>[all packets successful, 0% loss]<br><br>$ nc -zv 172.16.25.57 9000<br>Connection to 172.16.25.57 9000 port [tcp/*] succeeded!<br>

✅ Camera is reachable and port 9000 is confirmed open




The TOML Configuration Error​


Config file content (config.toml):

[bind]<br>bind = "0.0.0.0"<br><br>[[cameras]]<br>name = "swann1"<br>username = "admin"<br>password = "123456"<br>address = "172.16.25.57:9000"<br><br>[cameras.stream.Main]<br>name = "Main"<br><br>[cameras.stream.Sub]<br>name = "Sub"<br>

Error when running ./neolink rtsp --config config.toml:

2026-05-24T07:36:41Z INFO neolink | Neolink e47a0d5734b0a06b53bd8d78be9ca2f6b8396a<br>Error: Failed to parse the "config.toml" config file<br>Caused by:<br> TOML parse error at line 1, column 1<br> 1 | [bind]<br> | ^^^^^^<br> invalid type: map, expected a string<br>

Key point: The error says the TOML parser expected a string but got a map at line 1. This suggests either:
  1. TOML parser itself has a bug
  2. Some invisible character is corrupting the file before parsing
  3. Config structure needs to be different for Linux version



Troubleshooting Already Attempted​


File Creation Methods Tried:​

  1. nano editor — manually typed, saved correctly, still failed
  2. cat > file << 'EOF' — pasted content, still failed
  3. printf command — used escaped newlines (\n), still failed

File Validation:​

$ file config.toml<br>config.toml: ASCII text<br><br>$ hexdump -C config.toml | head -5<br>00000000 5b 62 69 6e 64 5d 0a 62 69 6e 64 20 3d 20 22 30 |[bind].bind = "0|<br>00000010 2e 30 2e 30 2e 30 22 0a 0a 5b 5b 63 61 6d 65 72 |.0.0.0"..[[camer|<br>...<br>

✅ File is pure ASCII, first line is correct (5b 62 69 6e 64 5d = [bind])


Different Neolink Versions:​

  • Tried 0.5.0 (not available for Linux)
  • Tried 0.6.2 (same error)

Environment:​

  • GStreamer installed correctly: gstreamer1.0-rtsp via apt
  • All dependencies present
  • Environment variables set properly



What This Is NOT​

  • Not a network issue: Port 9000 confirmed open, camera responding at sub-millisecond latency
  • Not a credential issue: Haven't reached authentication yet; failing at config parse stage
  • Not a copy-paste corruption: File manually typed from scratch, verified with hexdump
  • Not a missing dependency: GStreamer complete, all RTSP components present



Questions for the Community​

  1. Has anyone successfully run Neolink 0.6.2 on Linux with a valid config? Any known workarounds for this TOML parser error?
  2. Is there a known issue with Neolink's TOML parsing on Linux vs Windows? The same config structure would theoretically work on both.
  3. Should the config structure be different for Linux? Any Linux-specific syntax requirements I'm missing?
  4. Verbose logging options? Is there a way to get Neolink to output more details about what's failing in the TOML parse?
  5. Alternative protocol translators? If Neolink is unreliable, are there other tools that can translate Baichuan protocol to RTSP on Linux?



What Happens When This Works​


Once the TOML parse error is resolved:
  • Neolink will expose the camera stream as RTSP at rtsp:/127.0.0.1:8554/swann1
  • Blue Iris can connect to that RTSP URL and display the video feed
  • I can then add the remaining 7 cameras using the same method
  • Eventually migrate to a dedicated Linux/Frigate setup for recording and AI features



Additional Context​

  • I'm the IT department for my office; I have full control over the network
  • The 172.16.25.x subnet is isolated from the main office network (192.168.x.x)
  • All 8 cameras are Baichuan-based (same manufacturer, same protocol)
  • This is for a laboratory security setup, not a commercial deployment



Config File Location & Reproduction Steps​


To reproduce the error:
  1. Download Neolink 0.6.2 (linux_x86_64_ubuntu): Releases · QuantumEntangledAndy/neolink
  2. Create the config.toml file (content above)
  3. Run: ./neolink rtsp --config config.toml
  4. Observe the TOML parse error at line 1, column 1



Attachments / References​


Any help would be greatly appreciated. Thank you.
 
# MAJOR BREAKTHROUGH: Swann Baichuan Camera Authentication Solved via Neolink on Linux

## Previous Status (May 23-24)
We were completely blocked on Windows trying to integrate 8 Swann security cameras (manufactured by Shenzhen Baichuan Digital Technology) with Blue Iris. The cameras use a proprietary Baichuan protocol on port 9000, not standard RTSP. After a week of Windows troubleshooting (GStreamer DLL missing, Neolink 0.6.2 TOML parse errors), we pivoted to Linux.

## TODAY'S BREAKTHROUGH (May 25, Evening)

### ✅ Problem SOLVED: Camera Authentication
The default password is 12345 — not 123456

This was the critical missing piece. We had been trying:
  • admin / 123456 (WRONG — has 6 digits)
  • admin / blank (WRONG)
  • admin / EC71DB512EB2 (MAC address — WRONG)

But the actual default is: admin / 12345 (exactly 5 digits)

### ✅ Neolink on Linux is WORKING
Once we used the correct password, Neolink 0.6.2 immediately:
  • Connected to camera at 172.16.25.57:9000
  • Successfully authenticated
  • Established TCP connection
  • Retrieved camera details:
- Model: IPC-388M
- Firmware: Version 541.15120202
- Streams available at multiple paths

### ✅ RTSP Server is Running
Neolink is successfully serving RTSP streams at port 8554 with these available paths:
  • /swann1/main and /swann1/Main
  • /swann1/mainStream and /swann1/MainStream
  • /swann1/sub and /swann1/Sub
  • /swann1/subStream and /swann1/SubStream

### ✅ Network Connectivity Verified
  • Windows laptop → Linux machine: ping successful (0.3-0.7ms latency)
  • Port 8554 firewall verified open: sudo ufw allow 8554
  • Network path is solid and confirmed working

### ⏳ Current Blocker: Blue Iris RTSP 404 Error

When Blue Iris attempts to connect to the RTSP stream at 172.16.25.3:8554/swann1/main, it returns:

Code: 
Cam1: No signal
RTSP 404 not found

This is puzzling because:
  • Neolink IS running and serving streams
  • Port 8554 IS open and reachable
  • Network connectivity IS confirmed
  • Camera authentication IS successful

Blue Iris can reach the RTSP server (it gets a response) but is getting a 404 error, suggesting the stream paths or stream format might not match Blue Iris's expectations.

## Technical Details

System Configuration:
  • Linux Mint 22.3 Xena (dual-boot, recently upgraded)
  • Neolink 0.6.2 (linux_x86_64_ubuntu)
  • GStreamer 1.0 installed via apt (complete with RTSP components)
  • Blue Iris 5 on Windows 11 HP laptop

Camera Details:
  • IP: 172.16.25.57
  • Port: 9000 (Baichuan proprietary protocol)
  • Username: admin
  • Password: 12345 ← KEY FINDING
  • Manufacturer: Shenzhen Baichuan Digital Technology
  • MAC: EC:71:DB:51:2E:B2
  • Model: IPC-388M
  • Firmware: 541.15120202

Network Topology:
Code: 
Windows 11 (Blue Iris) ← → Linux (Neolink) ← → Camera
192.168.x.x              172.16.25.3         172.16.25.57
                         Port 8554 (RTSP)    Port 9000

## What Works Now

1. Linux environment is stable — Xena upgrade was seamless, package management works well
2. Neolink successfully translates Baichuan → RTSP — authentication and connection working perfectly
3. Camera is accessible and responsive — all 8 cameras in the box likely have same default credentials (12345)
4. Network infrastructure is solid — no latency issues, firewall manageable

## Remaining Questions for Community

1. RTSP 404 Error: Why is Blue Iris getting 404 when Neolink says streams are available? Is this a stream format issue, authentication in the URL, or something else?

2. Stream Path Format: Should the URL be:
- 172.16.25.3:8554/swann1 (base path)?
- 172.16.25.3:8554/swann1/main (with main stream)?
- Something else entirely?

3. Blue Iris Compatibility: Does anyone have experience connecting Blue Iris to Neolink-proxied camera streams? Any known issues or workarounds?

## Next Steps We're Exploring

1. Contact Blue Iris support — since the error is originating from their RTSP client, they may have insight into the 404 issue
2. Try Frigate as alternative — native Linux video management software, might handle these camera streams differently than Blue Iris proxy approach
3. Test other Baichuan cameras — all 8 came in same box, should respond to same credentials (12345)

## Key Takeaway for Others

If you have Swann cameras from Shenzhen Baichuan Digital Technology:
  • Default credentials are: admin / 12345 (not 123456)
  • Use Neolink on Linux (not Windows) to avoid GStreamer DLL issues
  • Camera is at port 9000, not standard RTSP port 554
  • Linux infrastructure (Docker, apt packages) handles this setup much more smoothly than Windows

We're very close to full integration. The authentication breakthrough suggests the other 7 cameras in the box are equally accessible once we resolve the Blue Iris RTSP connection issue.

Any insights from the community would be greatly appreciated.

---

Update Status: May 25, 2026, ~11:45 PM
Project Progress: 85% (authentication solved, RTSP serving confirmed, only client connection issue remains)
 

MAJOR BREAKTHROUGH: Swann Baichuan Camera Authentication Solved via Neolink on Linux​


Previous Status (May 23-24)​


We were completely blocked on Windows trying to integrate 8 Swann security cameras (manufactured by Shenzhen Baichuan Digital Technology) with Blue Iris. The cameras use a proprietary Baichuan protocol on port 9000, not standard RTSP. After a week of Windows troubleshooting (GStreamer DLL missing, Neolink 0.6.2 TOML parse errors), we pivoted to Linux.


TODAY'S BREAKTHROUGH (May 25, Evening)​


✅ Problem SOLVED: Camera Authentication​


The default password is 12345 — not 123456


This was the critical missing piece. We had been trying:


  • admin / 123456 (WRONG — has 6 digits)
  • admin / blank (WRONG)
  • admin / EC71DB512EB2 (MAC address — WRONG)

But the actual default is: admin / 12345 (exactly 5 digits)


✅ Neolink on Linux is WORKING​


Once we used the correct password, Neolink 0.6.2 immediately:


  • Connected to camera at 172.16.25.57:9000
  • Successfully authenticated
  • Established TCP connection
  • Retrieved camera details:
    • Model: IPC-388M
    • Firmware: Version 541.15120202
    • Streams available at multiple paths

✅ RTSP Server is Running​


Neolink is successfully serving RTSP streams at port 8554 with these available paths:


  • /swann1/main and /swann1/Main
  • /swann1/mainStream and /swann1/MainStream
  • /swann1/sub and /swann1/Sub
  • /swann1/subStream and /swann1/SubStream

✅ Network Connectivity Verified​


  • Windows laptop → Linux machine: ping successful (0.3-0.7ms latency)
  • Port 8554 firewall verified open: sudo ufw allow 8554
  • Network path is solid and confirmed working

⏳ Current Blocker: Blue Iris RTSP 404 Error​


When Blue Iris attempts to connect to the RTSP stream at 172.16.25.3:8554/swann1/main, it returns:


Cam1: No signal<br>RTSP 404 not found<br>

This is puzzling because:


  • Neolink IS running and serving streams
  • Port 8554 IS open and reachable
  • Network connectivity IS confirmed
  • Camera authentication IS successful

Blue Iris can reach the RTSP server (it gets a response) but is getting a 404 error, suggesting the stream paths or stream format might not match Blue Iris's expectations.


Technical Details​


System Configuration:


  • Linux Mint 22.3 Xena (dual-boot, recently upgraded)
  • Neolink 0.6.2 (linux_x86_64_ubuntu)
  • GStreamer 1.0 installed via apt (complete with RTSP components)
  • Blue Iris 5 on Windows 11 HP laptop

Camera Details:


  • IP: 172.16.25.57
  • Port: 9000 (Baichuan proprietary protocol)
  • Username: admin
  • Password: 12345 ← KEY FINDING
  • Manufacturer: Shenzhen Baichuan Digital Technology
  • MAC: EC:71:DB:51:2E:B2
  • Model: IPC-388M
  • Firmware: 541.15120202

Network Topology:


Windows 11 (Blue Iris) ← → Linux (Neolink) ← → Camera<br>192.168.x.x 172.16.25.3 172.16.25.57<br> Port 8554 (RTSP) Port 9000<br>

What Works Now​


  1. Linux environment is stable — Xena upgrade was seamless, package management works well
  2. Neolink successfully translates Baichuan → RTSP — authentication and connection working perfectly
  3. Camera is accessible and responsive — all 8 cameras in the box likely have same default credentials (12345)
  4. Network infrastructure is solid — no latency issues, firewall manageable

Remaining Questions for Community​


  1. RTSP 404 Error: Why is Blue Iris getting 404 when Neolink says streams are available? Is this a stream format issue, authentication in the URL, or something else?
  2. Stream Path Format: Should the URL be:
    • 172.16.25.3:8554/swann1 (base path)?
    • 172.16.25.3:8554/swann1/main (with main stream)?
    • Something else entirely?
  3. Blue Iris Compatibility: Does anyone have experience connecting Blue Iris to Neolink-proxied camera streams? Any known issues or workarounds?

Next Steps We're Exploring​


  1. Contact Blue Iris support — since the error is originating from their RTSP client, they may have insight into the 404 issue
  2. Try Frigate as alternative — native Linux video management software, might handle these camera streams differently than Blue Iris proxy approach
  3. Test other Baichuan cameras — all 8 came in same box, should respond to same credentials (12345)

Key Takeaway for Others​


If you have Swann cameras from Shenzhen Baichuan Digital Technology:


  • Default credentials are: admin / 12345 (not 123456)
  • Use Neolink on Linux (not Windows) to avoid GStreamer DLL issues
  • Camera is at port 9000, not standard RTSP port 554
  • Linux infrastructure (Docker, apt packages) handles this setup much more smoothly than Windows

We're very close to full integration. The authentication breakthrough suggests the other 7 cameras in the box are equally accessible once we resolve the Blue Iris RTSP connection issue.


Any insights from the community would be greatly appreciated.




Update Status: May 25, 2026, ~11:45 PM
Project Progress: 85% (authentication solved, RTSP serving confirmed, only client connection issue remains)
 
You must log in or register to reply here.
Top Bottom