Skip to content

Latest commit

 

History

History
37 lines (28 loc) · 1.82 KB

afn_yusadge_client.md

File metadata and controls

37 lines (28 loc) · 1.82 KB

AFN Yusadge Client Project

2016-03-08

So today I tried getting Win 10 64-bit up and running with Visual Studio installed. But I couldn't get the VirtualBox Guest additions to install. So I went and installed AFN's Win 7 64-bit ISO, then Visual Studio. After that I still couldn't figure out how to compile for 64-bit. So I went back to Google and found a bunch of options I had to set. That seems to work. So now I have a 64-bit build of Yusadge. The next step is to see if I can add the passive mode option.

2016-03-29

Let's run our version of Yusadge to see if it actually sends stuff. So I built YusadgeTimer. Ok so the prebuilt stuff is running. Let's try to get it to report faster than an hour for testing purposes.

According to John Neal's README, there should be a file tranferred right when you start Yusadge. However, I can't see any file uploaded from my hostname. I've got to get the current version to work before I can start making changes!

2016-4-12

John's trying to help me get the current client up and running. Ok, so I ended up having to put the test VM in bridge mode. At that point Yusadge uploaded the FTP file. Note that gvfs-ftp has an issue where the LIST -a command gets truncated to 1000 entries by the server so doing a ls -l doesn't return all the files and since WIN7-64BIT shows up later in the list it doesn't show up. So we use ncftp instead. I've verified that the current Yusadge client is not using passive mode since the FTP data port 20 shows up in wireshark. Now we need to see if our new client properly uses passive mode.

Ok so my new client uses passive mode properly. I think we're ready to test in a real lab.