Set up a network-based solution for transferring files between two virtual machines.
Set up a network-based solution for transferring files between two virtual machines.
Hello, I'm just starting out with networking and needed to build a file transfer service between virtual machines. I searched online but didn't find useful solutions. That's why I'm here asking for advice. The VMs will run on a laptop, and each one should use no more than 700 MB of memory or RAM. Since the laptop has only 4 GB total and Windows 8.1 uses around 2 GB just to run, it's a challenge. Why would you choose a laptop? It's simple—I want to demonstrate this project to my professor and create documentation. I'm leaning toward using Linux with a GUI, even though it might be tough with limited RAM, and I'd like to add some encryption to the transfer if needed. Any suggestions would be appreciated. Cheers!
You can leverage established solutions like FTP or SMB. Existing protocols often suffice for many tasks.
It seems focused on internal operations or a specific protocol, with the professor demonstrating a virtual machine and web-accessible interfaces—similar to how Linus handled setup for multiple players on one system.
Additionally, I think we can leverage servers, AD, and hypervisors. Right now I have a VM running Windows 2012 R2 on a laptop with Windows 8.1. If I switch to a Linux environment (either on the VMs or elsewhere), it might be possible to set up file transfers using Linux. I’m not sure which Linux distro would work best yet. For the hypervisor, I’m using VirtualBox.
Most modern web interfaces rely on common backend protocols such as FTP, SFTP or SMB for data transfer.
I plan to configure the system around a local FTP server (just installed) alongside another user, possibly using an encrypted VPN for connectivity. I’m aiming for a simple, low-issue home storage solution. Right now, I’m running a VM on Ubuntu 17.10.
This task is straightforward—just use netcat for sending data. It’s a fundamental tool, so you’re likely being asked to build something simple but still understand protocol design. You can either recreate the HTTP functionality from scratch or focus on learning rsync. For your Linux setup, doing it locally should be simpler since many utilities are already available. Pick a distribution that appeals to you, whether it’s sleek or colorful, and go with one that matches your style.
Sure, I can rephrase that for you. If creating protocols is tough, then I won’t bother. I don’t need to put in extra effort just because I’m short on time. My idea is to set up an FTP home server on Linux (Ubuntu) that I’ve already configured to be accessible through a VPN. Now the challenge is setting up OpenVPN, but I don’t have a VPS. Do you have any suggestions? Is a VPS really necessary? Most people seem to use Windows and Putty for VPS connections, but I’d prefer something different.
Well.. so here are my thoughts and opinions on things. Just do whatever is required for the project, don't be cute pass school and get a job (or get a job and leave school prob better.. nobody care in enterprise what you did academically so getting real experience is better.) FTP is a pretty crappy protocol. better things exist (rsync ssh unison etc). Partial writes can happen and corrupt files. Linux is good for programming in C, FreeBSD is better (in FreeBSD all the header files have man pages) You don't need a VPS but if you think you do a good VPS provider that is cheep is Digital Ocean. MobaXterm is a good shell for windows if you need one.
I found guides on OpenVPN, but often they needed a VPS. The issue is that a professor can likely explain why it's not sufficient.