Scottbg1
Posts: 4
Joined: Mon Jul 10, 2017 5:20 pm

Re: RPi Cam Web Interface

Tue Jul 09, 2019 2:57 am

Having read that RPi Cam Web Interface was now working on Buster, I opted to do a fresh install of Buster and re-install the web interface.
I did the usual apt-get update and dist-upgrade before attempting the install.
Once I run the Web Interface installer, I get these messages after collecting the install packages and the installer stops.

Code: Select all

After this operation, 513 MB of additional disk space will be used.
Err:1 http://raspbian.raspberrypi.org/raspbian buster/main armhf libpq5 armhf 11.3-1
  404  Not Found [IP: 93.93.128.193 80]
E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/p/postgresql-11/libpq5_11.3-1_armhf.deb  404  Not Found [IP: 93.93.128.193 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Are these repos just down temporarily, or is there an error in the install script?

Scottbg1
Posts: 4
Joined: Mon Jul 10, 2017 5:20 pm

Re: RPi Cam Web Interface

Tue Jul 09, 2019 1:12 pm

I discovered the problem was because since Buster's release it has been marked as stable, but apparently the source list needed to be tweaked.

I fixed it by running:

Code: Select all

sudo apt update --allow-releaseinfo-change
I hope this helps someone.

Manisch
Posts: 4
Joined: Sun May 12, 2019 1:34 pm

Re: RPi Cam Web Interface

Tue Jul 09, 2019 1:48 pm

ras07 wrote:
Mon Jul 08, 2019 3:05 pm
Manisch wrote:
Mon Jul 08, 2019 11:54 am
Manisch wrote:
Tue Jul 02, 2019 8:53 am
I'm still having the issue that the Camera is rebooting quite often. I would say...once every 10 minutes? Sometimes more, sometimes less...
Isn't there anyone who could help? :(

I don't want to sell this stuff again, because my project doesn't work...
Can you give some more information? What do you mean exactly by "the camera is rebooting" - the Pi itself reboots? What Pi version, OS version, etc.
Hmm, I'm not sure, wheater or not it's just the camera or the whole Pi that's rebooting. Is there some sort of log that's writing down such events?

I'm using:
Raspberry Pi Zero WH
Raspbian Stretch Lite. latest version
Joy-it IR-Pro 5MP IR CUT Camera

itsmedoofer
Posts: 356
Joined: Wed Sep 25, 2013 8:43 am

Re: RPi Cam Web Interface

Tue Jul 09, 2019 2:54 pm

wpballa1 wrote:
Sun Jul 07, 2019 12:37 am
Bob,
Now that Buster is out I'm having problems updating a Stretch installation. update.sh seems to work fine, but after I accept all the settings I get the following messages
E: Unable to locate package php7
E: Unable to locate package php7-cli
E: Unable to locate package libapache2-mod-php7
And the update to 6.5.1 process dies. I must reboot to get the camera going again, working through the interface it won't let me restart things. All of this is after a update/upgrade within Stretch. I can't tell whose problem this is.
Bill

Let me be a bit more clear. I have no intention of upgrading these Raspberry Pis to Buster as they are 3000 miles away and I can't easily get my hands on them. So, I guess I will leave the one at 6.4.50, but is there a way I could revert the 6.5.1 back to 6.4.50?
Have you tried entering 7.0 in the PHP field of the installer, when it asks for the port and so on, I think the issue could be you entered 7 ? Guessing here, but I think the script takes the exact value you enter and appends it to the package name, and the earlier packages are 7.0.

Worth a pop, save a bit of gas driving 6K miles :)

wpballa1
Posts: 59
Joined: Sat Jun 27, 2015 12:49 am

Re: RPi Cam Web Interface

Tue Jul 09, 2019 11:43 pm

Thanks, entering 7.0 in the php section did the trick, and thanks Bob for making a note of that in the installer.

ras07
Posts: 40
Joined: Tue May 22, 2018 4:04 am

Re: RPi Cam Web Interface

Wed Jul 10, 2019 1:30 am

Manisch wrote:
Tue Jul 09, 2019 1:48 pm
Hmm, I'm not sure, wheater or not it's just the camera or the whole Pi that's rebooting. Is there some sort of log that's writing down such events?
Well, there are lots of logs, but without knowing more about the symptoms, it's hard to know where to point you.

/var/log has most of the system logs. The syslog, kern.log, and messages files in the /var/log directory may have important info if the Pi is crashing. The Linux command dmesg may also give you useful info.

The Linux command uptime will tell you when the system was last rebooted, which may help you figure out what exactly is crashing.

If it's directly related to the camera, scheduleLog.txt in the /var/www/html (or wherever you have installed RPiCWI) may contain useful info.

One important thing to note - the Pi doesn't have a real-time clock, which means that immediately after booting, the time will be off until the system can synchronize the time from the internet. This can lead you astray when using log files for debugging purposes - if you see a big time jump, you might assume that's when the Pi rebooted. In reality that's when the time was synchronized. If your Pi crashes at 10:00 and you reboot it at 11:00, the Pi is still going to think it's 10:00 for most of the boot process. So if you're looking for the cause of a crash, it may not be whatever happened right before the time jump.

Can you SSH into the Pi (or access the terminal with a screen, keyboard and mouse) after it has "crashed"?

ras

CharlyDelta
Posts: 120
Joined: Thu Jul 18, 2013 4:04 am
Location: Montreal

Re: RPi Cam Web Interface ANNOTATE 3 SOLVED

Thu Jul 11, 2019 6:03 pm

After countless tests, I was finally able to print the temperature from an 18B20 on the monitor screen, with ANNOTATE function. But, the device id, 28-xxxxxxxxxxxxx also appears. How could it be possible to get only the temperature displayed?

Here is the code I'm trying now:

Code: Select all

#!/usr/bin/env python

import glob
import time

# DS18B20.py
# 2016-04-25
# Public Domain

# Typical reading
# 73 01 4b 46 7f ff 0d 10 41 : crc=41 YES
# 73 01 4b 46 7f ff 0d 10 41 t=23187

while True:

   for sensor in glob.glob("/sys/bus/w1/devices/28-00*/w1_slave"):
      id = sensor.split("/")[5]

      try:
         f = open(sensor, "r")
         data = f.read()
         f.close()
         if "YES" in data:
            (discard, sep, reading) = data.partition(' t=')
            t = float(reading) / 1000.0
            print("{} {:.1f}".format(id, t))
            annotate = open("/dev/shm/mjpeg/user_annotate.txt", 'w')
            annotate.write('{} {:.1f}' .format(id, t))
            annotate.close()
         else:
            print("999.9")

      except:
         pass

   time.sleep(3.0)
Thanks for your help

I finaly found the solution:

annotate.write('"{:.1f}"'.format ( t))

huresaich
Posts: 1
Joined: Fri Jul 12, 2019 10:33 am

Re: RPi Cam Web Interface

Fri Jul 12, 2019 10:45 am

I have a working installation and want to setup user access. During the install script I entered a username + password. However when I open the cam URL I can instantly access it. I assumed there would be some kind of login prompt, but the page behaves exactly the same as a previous install where I didn't specify a user. Now I am confused about how this is supposed to work. Can anybody tell me what I have to do to enable full access for one "admin" user and another user with restricted access in more detail?

User avatar
Mettauk
Posts: 235
Joined: Mon Dec 10, 2012 12:40 pm
Location: Zarg

Re: RPi Cam Web Interface

Tue Jul 16, 2019 12:52 pm

I've managed to get userbuttons working to switch GPIO to high/Low which is great news for all sorts of projects and can now switch the IR cut filter using the buttons, but...

I want to automate the IR cut filter on my camera for dawn and dusk and am bewildered by the Schedule Settings, totally bewildered.

I changed lattitude for RPi camera location but thats as far as I've got. Can someone please walk me through all or part of how?

To get userbuttons working I wrote a small python script and an sh script, I'm now guessing but maybe the On.sh and Off.sh scrips need to be integrated into the Schedule Settings, but how?

One of scripts

Code: Select all

#!/usr/bin/python
#IR cut filter switch OFF
import RPi.GPIO as GPIO
import time
GPIO.setmode(GPIO.BCM)
GPIO.setwarnings(False)
GPIO.setup(23,GPIO.OUT)
#print "IR cut on"
#GPIO.output(23,GPIO.HIGH)
time.sleep(0.3)
#print "IR cut off"
GPIO.output(23,GPIO.LOW)
The Macro

Code: Select all

#!/usr/bin/env bash
#echo "This is the bash script" &&
/usr/bin/python /home/pi/ir_cut_OFF.py
#echo "OFF"
As humans we have been the same for a very very long time, technology changes how we do... not who we are as people.

RaspiChase
Posts: 1
Joined: Fri Jul 19, 2019 12:12 pm

Re: RPi Cam Web Interface

Fri Jul 19, 2019 12:17 pm

Removed, solved issue with fresh install of Raspian.
Last edited by RaspiChase on Fri Jul 26, 2019 9:38 pm, edited 1 time in total.

User avatar
Mettauk
Posts: 235
Joined: Mon Dec 10, 2012 12:40 pm
Location: Zarg

Re: RPi Cam Web Interface

Mon Jul 22, 2019 10:00 pm

Trying to install gstreamer on Buster Lite...

Code: Select all

sudo apt-get install gstreamer1.0
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'gstreamer1.0-python-dbg-plugin-loader' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-plugins-ugly-amr' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-videosink' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-alsa' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-plugins-ugly-dbg' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-plugins-ugly-doc' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-plugins-base-apps' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-rtsp-dbg' for regex 'gstreamer1.0'
Note, selecting 'libgstreamer1.0-dev' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-tools' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-python3-dbg-plugin-loader' for regex 'gstreamer1.0           '
Note, selecting 'gstreamer1.0-plugins-good' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-qapt' for regex 'gstreamer1.0'
Note, selecting 'libgstreamer1.0-0-dbg' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-espeak' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-omx' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-nice' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-omx-rpi-dbgsym' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-omx-rpi' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-opencv' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-omx-rpi-config' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-videosource' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-crystalhd' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-fluendo-mp3' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-rtsp' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-plugins-bad' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-plugins-base' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-audiosource' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-gnonlin-dbg' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-gnonlin-doc' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-pipewire' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-plugins-bad-videoparsers' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-plugins-really-bad' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-clutter' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-pulseaudio' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-pocketsphinx' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-plugins-bad-dbg' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-plugins-bad-doc' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-gtk3' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-visualization' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-plugins-bad-faad' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-omx-generic' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-lame' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-x' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-python-plugin-loader' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-plugins-rtp' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-omx-generic-dbgsym' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-gnonlin' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-vaapi-doc' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-omx-generic-config' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-libav' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-plugins-base-dbg' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-plugins-good-dbg' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-plugins-base-doc' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-plugins-good-doc' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-dvswitch' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-clutter-3.0' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-vaapi' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-libav-dbg' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-packagekit' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-python3-plugin-loader' for regex 'gstreamer1.0'
Note, selecting 'libgstreamer1.0-0' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-omx-dbg' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-omx-bellagio-config' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-gl' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-plugins-ugly' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-doc' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-audiosink' for regex 'gstreamer1.0'
Note, selecting 'gstreamer1.0-plugins-bad' instead of 'gstreamer1.0-plugins-bad-           faad'
Note, selecting 'gstreamer1.0-plugins-bad' instead of 'gstreamer1.0-plugins-bad-           videoparsers'
Note, selecting 'gstreamer1.0-plugins-ugly' instead of 'gstreamer1.0-plugins-ugl           y-amr'
gstreamer1.0-tools is already the newest version (1.14.4-1).
libgstreamer1.0-0 is already the newest version (1.14.4-1).
libgstreamer1.0-0 set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gstreamer1.0-omx-dbg : Depends: gstreamer1.0-omx (= 1.0.0.1-0+rpi12+jessiepmg)            but 1.14.4-1+rpt1 is to be installed
 gstreamer1.0-python3-dbg-plugin-loader : Conflicts: gstreamer1.0-python3-plugin           -loader but 1.14.4-1 is to be installed
 gstreamer1.0-python3-plugin-loader : Conflicts: gstreamer1.0-python3-dbg-plugin           -loader but 1.14.4-1 is to be installed
E: Unable to correct problems, you have held broken packages.
Any suggestions? I cant get zip to zip up time lapses, I just get an empty zip file and I cant seem to get conversions to work?
As humans we have been the same for a very very long time, technology changes how we do... not who we are as people.

placidchat
Posts: 17
Joined: Wed Jul 17, 2019 9:21 am

Re: RPi Cam Web Interface

Fri Jul 26, 2019 6:21 pm

A question about the raspimjpeg:

I've tried echo -n 'ca 1' to the FIFO, and the subsequent 'ca 0' , but raspimjpeg doesn't write out any media files. How can i go about getting this to work?

placidchat
Posts: 17
Joined: Wed Jul 17, 2019 9:21 am

Re: RPi Cam Web Interface

Fri Jul 26, 2019 9:26 pm

I've compiled a version of the userland git to get a raspimjpeg, but on starting, it complains about various wrong settings in the config file.

ras07
Posts: 40
Joined: Tue May 22, 2018 4:04 am

Re: RPi Cam Web Interface

Sat Jul 27, 2019 4:00 am

placidchat wrote:
Fri Jul 26, 2019 6:21 pm
I've tried echo -n 'ca 1' to the FIFO, and the subsequent 'ca 0' , but raspimjpeg doesn't write out any media files. How can i go about getting this to work?
First, double-check that all the media directories listed in raspimjpeg and/or uconfig exist and have write permission for www-data. Also make sure that you get media files written out when you hit the record video start and record video stop buttons.

Assuming that all checks out - I've had trouble writing to the FIFO queue with echo - seems to be a timing thing. (Also seems to be worse on low-end boards like the Pi Zero W's I'm running.) What has worked for me is to set enforce_lf 1 in uconfig, and then use the echo command without the -n parameter. enforce_lf 1 changes the behavior of the FIFO queue - instead of relying on a complete command coming through the queue in a set amount of time, it just waits for a newline before executing a command.

See https://github.com/silvanmelchior/RPi_C ... issues/477 for more details. (FWIW I couldn't get the fifo_interval to work for me, although I didn't try very hard, since enforce_lf 1 seems to solve my problem.)

placidchat
Posts: 17
Joined: Wed Jul 17, 2019 9:21 am

Re: RPi Cam Web Interface

Sat Jul 27, 2019 9:27 am

I've recompiled a version of raspimjpeg from the userland git repo, and used the buildme to build a version. When i strace raspimjpeg, the /etc/raspimjpeg gets opened and read, but raspimjpeg is saying various commands in /etc/raspimjpeg is unknown. Why would it do that? There are no tags in the repo, so i assume whatever gets git cloned is the lastest version. So the configuration commands shouldn't have been deprecated.

Should i have used a different repo to build raspimjpeg?

placidchat
Posts: 17
Joined: Wed Jul 17, 2019 9:21 am

Re: RPi Cam Web Interface

Sat Jul 27, 2019 10:05 am

It appears the raspiberrypi/userland doesn't have the RaspiMJPEG.c at all. The silvanmelchior/userland has RaspiMJPEG.c but the version of that is 4.2.3. The version compiled for RPi_Cam_Web_Interface is 5.8.17. Where is the repository for this?

henrique_mg
Posts: 2
Joined: Sun Jul 28, 2019 5:34 pm

Re: RPi Cam Web Interface 3D stereo

Sun Jul 28, 2019 5:43 pm

can enable 2 camera to have stereo 3D image?

User avatar
mahjongg
Forum Moderator
Forum Moderator
Posts: 12117
Joined: Sun Mar 11, 2012 12:19 am
Location: South Holland, The Netherlands

Re: RPi Cam Web Interface 3D stereo

Sun Jul 28, 2019 5:51 pm

henrique_mg wrote:
Sun Jul 28, 2019 5:43 pm
can enable 2 camera to have stereo 3D image?
The compute modules (https://www.raspberrypi.org/forums/viewforum.php?f=98) support two camera interfaces, and already supports 3D camera's with software drivers to (among other things) support split screen video output (for 3D glasses).

Other RPI's only have one camera interface, so are not suitable for 3D recording, on their own, you will need two RPI, and you cannot simply mix their video signals into a split screen video signal.

henrique_mg
Posts: 2
Joined: Sun Jul 28, 2019 5:34 pm

Re: RPi Cam Web Interface 3D stereo

Sun Jul 28, 2019 5:58 pm

i'm using the stereoPi rasp that already has two cameras but i can't see both in RPi-Cam-Web-Interface

placidchat
Posts: 17
Joined: Wed Jul 17, 2019 9:21 am

Re: RPi Cam Web Interface

Mon Jul 29, 2019 4:42 am

It looks like the raspimjpeg.c resides in the roberttidey github userland repo. Unfortunately, i just found out linux builds have always been non reproducible, so compiling a version of raspimjpeg cannot confirm that the raspimjpeg that is in the silvanmelchior github bin directory is the same as the now compiled version. Isn't it possible to do one of those git submodule instances where the source for raspimjpeg is included in rpi cam web, and compiled at the same time?

placidchat
Posts: 17
Joined: Wed Jul 17, 2019 9:21 am

Re: RPi Cam Web Interface

Mon Jul 29, 2019 9:06 am

I've compiled a version of raspimjpeg from roberttidey's userland github. Whenever i do a

Code: Select all

 echo 'ca 1' > FIFO 
scheduleLog.txt logs the following
Error: could not enable connection camera -> video converter
Running raspimjpeg from the commandline, making sure that no motion or other raspimjpeg processes are running, the output on stdout when doing the same thing is
mmal: mmal_vc_port_enable: failed to enable port vc.ril.encode:in:0(OPQV): EINVAL
mmal: mmal_port_enable: failed to enable connected port (vc.ril.video_encode:in:0(OPQV))0x1432a80(EINVAL)
Also, for some reason my recently installed RPIs running buster seem to regularly suffer from dropped eth connections, like they were trying to powercycle the usb chip ( syslog containing entries of checking usb busses and reinitialising devices ).

raspivid compiled as part of the userland apps, works fine.

Archer322
Posts: 8
Joined: Wed Jan 11, 2017 4:54 pm

Re: RPi Cam Web Interface

Mon Aug 05, 2019 3:43 pm

Figured I'd post this as it wasn't immediately apparent to me and I had to search a bit before I found the solution:

I had several PiCams set up to automount a cifs network share and in Stretch it worked just fine. But when I upgraded one to Buster it wouldn't mount the share anymore. The key was to put [vers=1.0] in fstab, apparently they removed automatically switching to version 1 in Buster. Not sure how to get version 2 (or 3) working or what that would change exactly, my PiCams and shares are only accessible from inside my network anyway. Here's my fstab if it helps anyone else:

//192.168.1.1/PiCams/ /var/www/media cifs username=USERNAME,password=PASSWORD,x-systemd.automount,vers=1.0,noauto 0 1

ras07
Posts: 40
Joined: Tue May 22, 2018 4:04 am

Re: RPi Cam Web Interface

Mon Aug 05, 2019 8:37 pm

Archer322 wrote:
Mon Aug 05, 2019 3:43 pm
I had several PiCams set up to automount a cifs network share and in Stretch it worked just fine. But when I upgraded one to Buster it wouldn't mount the share anymore. The key was to put [vers=1.0] in fstab, apparently they removed automatically switching to version 1 in Buster.
Glad this worked for you, and it's cool as long as you really understand the implications. For others reading, however, I'll point out that there are serious security problems with SMBv1 (it's the vector for several widespread ransomeware attacks like WannaCry, for example). Even behind a firewall, using SMBv1 removes a layer of protection, and makes you vulnerable if, for instance, a friend connects to your wifi with a compromised device.

Everything's a tradeoff, and in some cases it may make sense to enable SMBv1 (hopefully only for the short term), if you really understand all the security issues. But for the most part it's a lot better idea to figure out why your share can't use SMBv2 or v3 and fix it. There's a good reason Buster defaults to disabling v1. (To be clear: the real vulnerability isn't in an RPI Cam utilizing v1, it's that the server hosting the share allows v1 connections at all.)

Archer322
Posts: 8
Joined: Wed Jan 11, 2017 4:54 pm

Re: RPi Cam Web Interface

Wed Aug 07, 2019 5:25 pm

Well for someone who used the instructions, which are still the same, to mount a network share that was broken by upgrading to Buster this is the workaround.

ras07
Posts: 40
Joined: Tue May 22, 2018 4:04 am

Re: RPi Cam Web Interface

Wed Aug 07, 2019 7:57 pm

Archer322 wrote:
Wed Aug 07, 2019 5:25 pm
Well for someone who used the instructions, which are still the same, to mount a network share that was broken by upgrading to Buster this is the workaround.
Fair enough, but understand that the problem is really on your CIFS server's end; it's not Buster that's "broken". Jessie would downgrade to SMBv1 if that was the only thing the server supported; by default, Buster doesn't (for good reasons).

Ideally, you should update whatever is hosting the share to support a more current version of SMB ... but sometimes that's easier said than done. Based on the IP address of 168.192.1.1 that your share is using, I'm going to guess that your router itself is hosting the share. It's worth looking for a current firmware upgrade for your router (always a good practice anyway), but since router manufacturers are notoriously bad about keeping their software up to date, you might be out of luck unless your router is a relatively new model.

Unfortunately, if the router software is so out of date that it only supports SMBv1, you've got to wonder what other vulnerabilities it has. Sadly consumer-grade routers tend to be a very weak link in network security.

Return to “Camera board”