Linux Ftp Client Download File
Hue Charters
Sounds like y'all are pretty understaffed and I'm sure it's not your decision directly, but I will say: leaving a clearly half-finished client as the only option for (paying) customers while a new client is in the works -- and scrolling up, this thread has been open for over a year now -- well, I think y'all will start to burn through good will pretty quickly.
My honest suggestion would be: take a pause from the new client development for a month. Squash some bugs. Plug some memory leaks. Make the current client stable and unbroken. (Not talking new features even, just... not broken.) Put it in a decent spot, then leave it to focus on the new client. (And even then, if bugs come up in the old client, I think you have a responsibility to fix them.)
Also, seeing something happen on the current client will make your (paying!) customers feel less abandoned. (Take me for example: as I said, I love the Proton mission, but even I feel like this is a bit of a bait-and-switch.)
And as an addendum: if you're not going to implement actual fixes, please put an asterisk on the Proton VPN marketing copy, be clear about your (lack of) Linux support. Call it a "beta" client, explicitly say which features are not supported. Something, anything.
The CLI client is a big improvement over the GUI client. It (mostly) works! You can (e.g.) connect to a P2P- or Tor-enabled server easily, or the fastest server in a given country. Also, it does not hemorrhage memory.
However, its initial connection takes minutes. I can't imagine why. I didn't have this issue with the GUI client. (It's slow, but not that slow.) Note that if you have the kill switch enabled (which you should!), you have no network at all during this time. (By the way: after that initial connection, e.g. if you disconnect and reconnect, it's not nearly as bad.)
Also note that after you're finally connected, many apps that will have started during that time will silently have lost their network connection. (Possibly a kill switch bug?) Dropbox and Steam were two obvious and consistent examples of this for me. This also happens when resuming from suspend, or any time the VPN connection status changes for any reason, manual or otherwise. This is also consistent for me -- happens every time. I do not experience this with any other Linux VPN client.
There's no bulk-download option, no way to dynamically connect to servers in different regions based on capabilities or load. This is a downgrade from just about any other VPN client out there. The only upsides are: you avoid having to use Proton's own client and you get support for wireguard (and port-forwarding!).
I'm not writing this (just) to complain -- more for visibility. Both for the Proton team as well as potential users. If I had read something like this before paying for the service, I simply would have continued using my existing VPN and kept my eye out for the arrival of the "new" Proton Linux client at some point in the future.
Hi, I've just bought a RLC-411WS on Ebay to be used as a webcam displaying current weather at my location. Buying the camera was based on what looked like very good specs and the fact that it seemed to be based on embedded version of Linux. I was therefore somewhat surprised when I discovered that there was no way I could access the system from my Ubuntu Linux client. All my browsers (Firefox, Chromium) just presented me with an option to download a Windows client.
I did a portscan just in case you had enabled ssh protocol. That would have made it possible for me to log on to the system and accessing snapshots or videos on the built-in microSD-card. I discovered that you had enabled port 554 (RTSP), 1935 (RTMP), 6001 (X11 ?) and 8000 (another HTTP server ?) in addition to 80 and 443 (HTTP/HTTPS) but nothing that looked like ssh (normally on port 22). No FTP either as far as I could discover.
I managed to get vlc to display the RTSP stream but not the RTMP stream. The fact that I can't administer the camera from Linux (upgrading, accessing files, etc) makes it somewhat useless and I may have to consider returning it.
My question is if you are planning to make a Linux client for the camera ? Or if you have any other ways of giving a Linux enthusiast ways of controlling the camera without the need for Windows or Mac client ?
Regards,
Per
Hi and thanks for your reply. The issue now is that I have to upgrade my camera with the latest firmware in order to get Flash support and I can't upgrade unless I have a Windows system.
The camera is installed at a remote location (my cabin used during summer) and my plan was to either have the camera send short, 30 secs of video to a server I have or to access the camera remotely in a secure way. Enabling either ssh server in the camera or having the camera use ssh client (or scp) would provide a secure channel for communication.
Would enabling ssh be something you would consider for a later firmware release ?
Hi,
I've been trying to run the Reolink client under Wine 3.0, on Ubuntu 18.04. I presume that the NVRs firmware is the latest version, as I purchased it a couple of weeks ago.
I have downloaded an executable DvrWebClient.exe from http://ip-address-of-dvr/. When I execute this with wine DvrWebClient.exe I get a dialog popup with Path Not Found. The only b**ton is OK, which when pressed exits the application.
When I set the WINEDEBUG=+relay environment variable and re-run the application then, I get a lot of information, however it seems to be having trouble running cmd /c uninstall.bat i, indicating that uninstall.bat can not be found.
As a wine newbie am I doing anything wrong? Has anyone got this working under Wine and if so it would be helpful to know exactly how?
Kind Regards,
B
There are two kinds of client that can be used to add our device: one is Windows Client, the other is Mac Client. Sorry for any inconvenience caused to you. For the clip issue, could you please send an email to sup...@reolink.com? Our support team will check it for you soon. Thanks.
@carl: Ok i will do that.
@Crimp on: The goal is to run the reolink client to access/view/config multiple cameras or nvr's, maybe do shots or records, too. It's also possible to run the reolink client as a kind of survellaince server. It would be nice to get this working on linux, too.
Alternatively we could connect the cameras to motion/motioneye/motioneyeos. It's an nice open source-thing running on linux, but i miss some features like clip/zoom.
A few days ago i released a blogpost for that:
-ip-kamera-an-motioneye-anbinden
It's in german. Mostly you need the right url's. I tested with an rlc-420-5mp, but i have to reduce the resoltion to get this working with motion...
Ah, I see now. My focus was on the question by "per". My guess is a native Linux client is beyond the capabilities at Reolink (and, only a tiny fraction of market share so not likely to be a high priority). Maybe instead of a unified solution (one program), there might be more success in separating the "configure" function from the "monitoring" functions. i.e. use the web interface to set up cameras, and use something else for viewing/recording, etc. On Windows, people report using Blue Iris with Reolink cameras.
I know it is frustrating. I simply LOVE the Reolink 5MP cameras. The price/performance ratio is superior to any other commonly available cameras.
... it is really, very sad, that there is no client for Linux. Especially in the age of pretty powerful and video-trimmed minicomputers like a Raspberry 3 or 4, it would be desirable not only for energy reasons, here to use an energy-saving combination of microcomputer and economical display ...
... but that's just my irrelevant opinion ...
Greetings from Germany...
Micha
Thank you for supporting Reolink. Sorry that Reolink Client can only work with the Windows and Mac system at present. Thank you for your eager concern about the Linux client support. We will collect and forward those suggestions to our R&D staff, we will notify you if we have the plan to publish the new Linux software.
Sorry for the inconvenience. You may subscribe our emails to get the newest update: -Us. Have a wonderful day!
Maybe (for the first step) it's easier for the developers to make the Windows-client wine-compatible. As me and others wrote, you can run the Windows-client with it, but for me i can't get no video running.
Other native Windows-software running this way, too, and it's supported by there makers, f.e. PuTTY or TeamViewer.
For the WorkSpaces Linux client version 2023.x to be able to access the WorkSpaces service, you must add the WorkSpaces Web Access domain ( ) to the allowlist on the network from which the client is trying to access the service.
By default, Linux client access is disabled. To use this client with your WorkSpace, your Amazon WorkSpaces administrator must enable Linux client access for your WorkSpaces directory. For more information, see Control Device Access in the Amazon WorkSpaces Administration Guide.
Download and install the WorkSpaces Linux client application from Amazon WorkSpaces Client Downloads. Detailed installation instructions are included on the Linux client page on the Client Downloads site.
When running a new client application, you will be prompted for your registration code, which is can be found in your welcome email. For existing customers, you can find the registration code under /home/UserName/.local/share/Amazon Web Services/Amazon WorkSpaces/RegisterationList.json.
The first time that you run the client application, you are prompted for your registration code, which is contained in your welcome email. The WorkSpaces client application uses the registration code and user name to identify which WorkSpace to connect to. When you launch the client application later, the same registration code is used. To enter a different registration code, launch the client application, and then choose Change Registration Code at the bottom of the login page.
35fe9a5643