AOC USB Displaylink Raspberry Pi

AOC_e1659FwuThere’s good news and bad news:

Bad News:

You expected to struggle with this. You expected that this will be as tricky as it used to be. Rotten luck, chum.

Good news:

Create a file called called:



Autorun apps Raspberry Pi on Raspbian GUI / Terminal

Raspberry Pi 3Sometimes you want stuff to run at startup, be it an application or a forced setting. This is fairly easy to achieve in Rasbpian, here’s how:

You can use the Raspbian preferences via the GUI to cause the pi user to be auto logged in at boot up and the GUI to automatically run. However, if you need to run with root privileges due to needing IO pin control (PLEASE NOTE: It is not advised to run as root) then set the Raspbian preferences to boot to the command line. Now open this file by editing it(you can use your favourite editor, for this example we use nano):

sudo nano /etc/rc.local

Before the “exit 0” line in it add the following line:

#Auto run the GUI as root
sudo startx

Save it by pressing Ctrl+X, ” Y“, ENTER

Reboot your RPi and it should automatically run the GUI as the root user.

Setting An Application To Automatically Run In The GUI (more…)

Need Help? Troubleshooting made easy!

Here are some tips that makes troubleshooting easy:

1) Check the event log
2) Google it
3) Reboot
4) Run IISreset
5) Empty the Recycle Bin
6) Hit [CTRL]+[BREAK]
7) Kill the ASPNET worker process
8) Clear Temporary Internet Files
9) Touch the config file
10) Degauss the monitor (Not that applicable any more, I suppose)
11) Simmer ground rhino horn on a bed of whale pancreas
12) "get latest" and rebuild
13) Login as admin
14) Run ipconfig /renew (Windows)
15) Check if CAPSLOCK is on.

HowTo: Static HOSTNAME For Your Pi On The Internet(dyndns)

Once again, if your ISP already gives you a static IP address, you don’t need to worry about this section.

We’ve already set up a static internal IP address for the Raspberry Pi, which means computers inside your local network will always know where to find your Pi. But what about projects that require Raspberry Pi to be connected to the Internet? If you want to build a Web server with your Raspberry Pi, people outside your network need to know where your Pi lives, which means setting a public IP that always looks the same.

I say “looks the same” because we’re really setting up a pseudo-static IP. Your ISP will continue to change the address as usual. So every time somebody connects to your Pi, the script we’re about to write will say, “Looks like the Pi has moved! Let me redirect you to the new address.”

We do this with a Dynamic DNS (DDNS), which maintains a name server that gets updated in real-time, and DDClient, a program that will correspond with DDNS directly from your Pi.

First sign up for a free dynamic host service like DNS Dynamic. Follow the instructions and create a new nameserver like

Now go to the command line on your Raspberry Pi and install DDClient with the following line:

sudo apt-get install ddclient

We need to edit the DDClient configuration with our DDNS’s new name server:

sudo nano /etc/ddclient/ddclient.conf

Every service will have slightly different configuration, but the DDNS website should tell you what you need to do to configure this file. A standard configuration for DNS Dynamic, for example, goes like this. Copy and paste it in.


Building A Raspberry Pi VPN HowTo: Creating An Encrypted Client Side

By now, it’s pretty apparent that turning your Raspberry Pi into a Virtual Private Network is an all-evening activity. But as security flaws further compromise our Internet lives, it feels increasingly worth it to have a secure server on your side. That way, you’re free to write emails and transfer data without worrying about what or whom might be intercepting it as it travels from your computer to the Web.

If you’ve followed the steps from other Raspberry Pi VPN HowTo, you’ve got a fully functional VPN server on your Raspberry Pi. You can use this to connect securely to your home network wherever there’s an unencrypted wireless connection. You can also access shared files and media you keep stored on your home network.

Only, you can’t access those files just yet. We’ve created keys for clients (computers and devices) to use, but we haven’t told the clients where to find the server, how to connect, or which key to use.

If you remember, we created several different client keys for each of the devices we want to grant VPN access. We called them Client1, Client2 and Client3.

It’d be a lot of trouble to generate a new configuration file for each client from scratch, which is why we’ll use an ingenious script written by Eric Jodoin of the SANS institute. Instead of generating a file for each client on our own, this script will do it for us.

Following The Script

The script will access our default settings to generate files for each client. The first thing we need to do, then, is create a blank text file in which those default settings can be read.

nano /etc/openvpn/easy-rsa/keys/Default.txt

Fill in the blank text file with the following:

dev tun
proto udp
resolv-retry infinite
ns-cert-type server
key-direction 1
cipher AES-128-CBC
verb 1
mute 20

It should look like the screenshot below, except it should show your public IP address. You’ll see that I deleted my own public IP address because that’s private information you shouldn’t be sharing around. On the other hand, local static IP addresses are very similar for everyone. They usually start with “192.168.”
Now, if you don’t have a static public IP address, you need to use a dynamic domain name system (DDNS) service to give yourself a domain name to put in place of the IP address. I recommend using the free service DNS Dynamic, which lets you pick a name of your choice. Then on your Pi, you need to run DDclient to update your DDNS registry automatically. I wrote a full tutorial for how to do this here.