Good evening,
after using FreeFileSync on my windows machine for some time (great product!) I wanted to use it on my Linux machine as well - no success though.
Executing install.run did not work (no error message!)but executing via terminal did (FreefileSync executable is generated, menu items in the "start menu" as well).
Starting the executable only generates the following error:
"Installation files are corrupt. Please reinstall FreeFileSync. Cannot get process information. No physical network card found (check on terminal via "ip a")"
Screenshot_Error_Message.png (26.45 KiB) Viewed 1744 times
ip a in terminal showes 2 entries. the second one eth0 is the one that is working --> internet connection is possible via browser etc.
FreeFileSync tends to run third-party programs by running in basically the same manner that you call them from the command line. The fact that this error message says to check "ip a" means that it is probably trying to run "ip a" (short for "ip address") which depends on the tool /usr/sbin/ip or similar.
Debian-based distros store /bin/ip in package iproute2 (sudo apt-get install iproute2) and Fedora-based distros store /usr/sbin/ip in iproute (sudo yum install iproute)
Many Linux distros have replaced the venerable ifconfig with this "ip" multitool, for better or worse.
I misread your first post; I thought you had not provided any output of "ip a." I'm guessing Zenju will fix his tool to handle the previously unexpected input of "eth0@if83" which is a style of network card name I've never seen before, and I'm guessing he hasn't either.
For our edification, does your host have a network card named "if83"?
I'm guessing Zenju will fix his tool to handle the previously unexpected input of "eth0@if83" which is a style of network card name I've never seen before, and I'm guessing he hasn't either.
bgstack15, 01 Mar 2021, 12:43
That's right, it should be fixed with the next version, release planned for latter today.
The mac address of eth0 is locally administered, thous was discarded by FFS in favor of not locally administered addresses (which don't exist in this case). So it's probably better to not discard them in first place.
I'm guessing Zenju will fix his tool to handle the previously unexpected input of "eth0@if83" which is a style of network card name I've never seen before, and I'm guessing he hasn't either.
bgstack15, 01 Mar 2021, 12:43
That's right, it should be fixed with the next version, release planned for latter today.
The mac address of eth0 is locally administered, thous was discarded by FFS in favor of not locally administered addresses (which don't exist in this case). So it's probably better to not discard them in first place.
Zenju, 01 Mar 2021, 13:37
Thank you very much! That sounds promising (great support! happy that i have donated --> and will do again in the future :))
So i guess the ethernet adapter check has something to do with the counting of the number of donated installations right?
So i guess the ethernet adapter check has something to do with the counting of the number of donated installations right?
tschedrick, 03 Mar 2021, 10:43
I misread your first post; I thought you had not provided any output of "ip a." I'm guessing Zenju will fix his tool to handle the previously unexpected input of "eth0@if83" which is a style of network card name I've never seen before, and I'm guessing he hasn't either.
For our edification, does your host have a network card named "if83"?
bgstack15, 01 Mar 2021, 12:43
...well i do not think the host does - i played around with the shell on the Proxmox host system but could not identify anything like that (I am not a linux expert , though).
I guess it has something to do with the container setup. I installed a ubuntu template (LXC) and installed LXCE on top (less overhead in comparison to a VM). I am building a sync "machine" to sync my OMV to cloud storage - i access it through x2go --> really prefer the UI of FreeFileSync in comparison to Rsync (so i need a linux desktop). Thanks for your support :) I really like this community
