This guide talks about how to setup Budabot in linux. Budabot is a organization bot for the game Anarchy Online. If you don’t play that game then you don’t need to setup a bot. If u prefer windows follow this guide.

This guide assumes you have a working version of Ubuntu or Debian setup on a server or VPS server. If you don’t then get that setup first before you try to follow my guide.

These steps also assume you have already created a new character and joined it to your org (if it’s an org bot)

Now that the requirements are out of the way, lets start.

Install packages required to make it run

It will ask u to set a password for mysql so make sure u do that.

apt-get -y install php php-mbstring php-curl php-xml php-mysql php-sqlite3 php-bcmath unzip mysql-server

Optional.. Install phpmyadmin by following Digital oceans guide

Download Budabot

You can find the downloads here. You may have to update the link I show below with the latest version.

cd /home/matt
mkdir budabot
cd budabot
wget https://github.com/Budabot/Budabot/releases/download/3.5_GA/Budabot3.5_GA.zip
unzip Budabot3.0_GA_build1303251942_linux.zip
cd Budabot3.0_GA_build1303251942_linux/

Setup Database

Now its time to login to mysql and setup the database. U can do that using the following commands.

Mysql -u root -p
CREATE DATABASE IF NOT EXISTS `myBudabot` ;
CREATE USER 'myBudabot'@'localhost' IDENTIFIED BY 'myBudabotpass1';
GRANT ALL PRIVILEGES ON `myBudabot`.* TO 'myBudabot'@'localhost' IDENTIFIED BY 'myBudabotpass1';

make chatbot executable

chmod +x ./chatbot.sh

Start the bot & setup database

Type in the command below & follow the prompts to setup the bot.

./chatbot.sh

Make sure you use mysql database and that you set it up manually, give it the information u used above when u created it.

You will also need an Anarchy Online account and character to run as the bot. I used a froob account that was a Squad Commander in a guild.

Once u are done setting it up you can “ctrl + C” to kill the bot so we can set it up to boot at startup.

Start bot at boot up

sudo nano /etc/systemd/system/Budabot.service

and enter something like this

[Unit]
Description=Budabot
After=network.target

[Service]
User=myname
Group=myname
WorkingDirectory=/home/myname/Budabot
ExecStart=/home/myname/Budabot/chatbot.sh

[Install]
WantedBy=multi-user.target

replace “myname” with whatever user/group you want running it. I kept it simple and ran it as my user account and from my home directory.

Test your new service

sudo service Budabot start

And you can set it to run at start with:

sudo systemctl enable Budabot

Systemd logs all output, so while you can’t actually see the terminal you can access that services current log to see what would of been in the terminal up to that point, which is pretty cool. The command for that is:

sudo journalctl -u Budabot.service

Raspberry Pi 3 Specs:

• SoC: Broadcom BCM2837
• CPU: 64-bit 1.2GHz quad-core ARM Cortex-A53 CPU
• GPU: Broadcom VideoCore IV
• RAM: 1GB LPDDR2 (900 MHz)
• Networking: 10/100 Ethernet, 2.4GHz 802.11n wireless
• Bluetooth: Bluetooth 4.1 Classic, Bluetooth Low Energy
• Storage: microSD
• GPIO: 40-pin header, populated
• Video: HDMI – VideoCore IV 3D
• Audio: 3.5mm analogue audio-video jack,
• USB: 4× USB 2.0
• Other Ports: Camera Serial Interface (CSI), Display Serial Interface (DSI)
• Power: 2.5 Amps
• Operating system support – Linux and Unix or Windows 10 IoT

Below I have shared some photos of my Raspberry Pi 3 B that I had planned to possibly install Nagios on to monitor my home network but before I find a main use for it I plan to try a bunch of different tasks with it and experiment a bit.

This guide contains network configuration steps in both GUI and command mode.

Setup Network on Centos 7

At the command prompt type

nmcli d

which will give you a quick identification of Ethernet cards installed on your machine

Here we have 2 interfaces named “enp0s17” and “enp0s18“. It might be different in your case however.

Setup GUI Mode

Recommended for beginners

Step 1

Type in this command

nmtui

to open network manager and press enter after choosing “edit  a connection” (use tab for choosing options)

Step 2

Now you can see all network interfaces, choose one and click “Edit”

DHCP Configuration

Step 3

for dhcp,

1. Choose “Automatic” in IPv4 CONFIGURATION.
2. Choose Automatic connect check box.
3. Press Ok and quit Network manager.

Now restart network services by typing this command

systemctl restart network

Now your server will get an IP from DHCP

Step 4

For manual IP address,
1. Choose “Manual” in IPv4 CONFIGURATION.
2. Add IP Address with Subnet , Gateway and DNS server ( Refer below image ).
3. Choose Automatic Connect check box.
4. Press OK and quit Network manager.

Now restart network services by typing this command

systemctl restart network

Now your server will have a static IP.

Command Mode

Step 1

Network interface config files are located in /etc/sysconfig/network-scripts/ directory. Open ifcfg-enp0s17 file ( For interface enp0s17 ) and you can see the content like below.

[root@krizna ~]# vi /etc/sysconfig/network-scripts/ifcfg-enp0s17
TYPE=Ethernet
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=enp0s17
UUID=7f1aff2d-b154-4436-9497-e3a4dedddcef
ONBOOT=no
HWADDR=00:0C:29:A1:B5:D6
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes

DHCP Configuration

Step 2

For DHCP
Find the below lines in config File.

BOOTPROTO=none
ONBOOT=no

and replace with

BOOTPROTO=dhcp
ONBOOT=yes

Now Restart network service by typing below command.

systemctl restart network

Now your server will get IP Address from DHCP

» Static configuration

Step 3 » For Static IP.
Find the below lines in config File.

BOOTPROTO=none
ONBOOT=no

and replace with

BOOTPROTO=static
ONBOOT=yes

And add the below lines at the end of the file.

IPADDR=172.27.0.32
NETMASK=255.255.255.0
GATEWAY=172.27.0.1
DNS1=172.27.0.5

File will look like below after changes.

TYPE=Ethernet
BOOTPROTO=static
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=enp0s17
UUID=f0c5b37d-299a-43cb-b74b-618bb252d129
ONBOOT=yes
HWADDR=00:0C:29:A1:B5:CC
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPADDR=192.168.1.10
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
DNS1=192.168.1.5

Now Restart network service by typing below command.

systemctl restart network

Now Interface will have static IP.
Additionally you can use /etc/sysconfig/network file for hostname and DNS .

HOSTNAME=server.krizna.com
DNS1=192.168.1.5
DNS2=8.8.8.8
SEARCH=krizna.com

I hope this helps anybody reading. Have a great day!

Below are the complete specs

Raspberry Pi 3 Specs:

• SoC: Broadcom BCM2837
• CPU: 64-bit 1.2GHz quad-core ARM Cortex-A53 CPU
• GPU: Broadcom VideoCore IV
• RAM: 1GB LPDDR2 (900 MHz)
• Networking: 10/100 Ethernet, 2.4GHz 802.11n wireless
• Bluetooth: Bluetooth 4.1 Classic, Bluetooth Low Energy
• Storage: microSD
• GPIO: 40-pin header, populated
• Video: HDMI – VideoCore IV 3D
• Audio: 3.5mm analogue audio-video jack,
• USB: 4× USB 2.0
• Other Ports: Camera Serial Interface (CSI), Display Serial Interface (DSI)
• Power: 2.5 Amps
• Operating system support – Linux and Unix or Windows 10 IoT

As you can see the Pi 3 still doesn’t have SATA, USB3 and gigabit ethernet but the pricing still remains at $35 and does come with wifi, ethernet and a 64 bit quad core cpu. This little unit is fully supported by linux and mostly by FreeBSD and other Unix-like systems too. While this unit may not replace your desktop computer it defiantly is a great little performer for other uses. I hear the RPi3 has an awesome community to gain support from as well.

The biggest update is the 64 bit Quad Core Broadcom BCM2837 CPU and the addition of a BCM43143 wifi chip built in means no more wifi adapters. You can use Linux, Unix-life system such as FreeBSD, Centos, Ubuntu and even Windows 10 on the Raspberry Pi 3.

The price of the Pi 3 is listed at:

• $35 USD
• £30.00 (UK)
• INR 3000 (India)

So what are you waiting for? Go buy yours today!

In this tutorial, I will show you how to set up a Minecraft 1.9 Server on Linux (Ubuntu 14.04). Personally I installed Minecraft on a EC2 server on Amazon with only 1GB of ram and it runs just fine.

Here are some requirements before we get started:

• A machine running Ubuntu Server 14.04
• A machine with 1GB of RAM, but I would recommend 2GB or more

* Note – the rest of the tutorial assumes you have already installed Ubuntu Server 14.04, and you are able to login with a user that has root privileges.

Installing the Minecraft Server Requirements

First run this command to get a list of updates

sudo apt-get update

Then run this command to actually update the server

sudo apt-get upgrade

Once updates are complete, check to see if Java is installed on our server:

java -version

If no Java version gets displayed, you will need to install it before preceding:

sudo apt-get install default-jdk

Next, we will install an application called Screen. Screen allows us to use multiple terminal sessions in a single window. For example, you may have multiple tasks running on your server simultaneously. Screen allows you to switch between sessions, without having to close one, all within the same window.

sudo apt-get install screen

Install the Minecraft Server

Next, we will install the Minecraft Server onto our Ubuntu Server.

First, create a directory anywhere on your server that you want to store the Minecraft files. Be sure to switch into that directory after it is created.

mkdir minecraft 
cd minecraft

Now, within our newly created minecraft directory, download the Minecraft Server:

wget -O minecraft_server.jar https://s3-us-west-2.amazonaws.com/g3kxyz/minecraft_server.1.9.jar

Using Screen, create a new session for our Minecraft server:

screen -S "Minecraft"

Next we will create a short script that will launch our Minecraft server. To create in Nano, do the following:

sudo nano minecraft.sh

Once the editor is open, put this line into the script. Once done, save the file, and close Nano.

sudo java -Xmx1024M -Xms1024M -jar minecraft_server.jar nogui

Launching Minecraft Server

Finally, to run the server you simply execute the script you previously made

sudo ./minecraft.sh

With any luck the server will launch successfully. If it is running you should see the words “Done” at the bottom of your terminal output

If you do a dir of the minecraft directory then you will notice that a ‘server.properties’ file got generated too. Feel free to open it up with nano and adjust settings as needed. You may also want to open up port 25565 through port forwarding on your firewall to the outside world if you want others to connect to your server.

Additional tips

To leave your “minecraft” screen do the following:

ctrl-a d

You can reattach the screen with the following:

screen -R

To get a list of current screen sessions type:

screen -ls

Change your server settings

Make sure you are in the folder “minecraft” by typing:

cd minecraft

and then type

sudo nano server.properties

The below section is quoted from the article at zdnet.

“The security hole can be triggered by exploiting glibc’s gethostbyname functions. This function is used on almost all networked Linux computers when the computer is called on to access another networked computer either by using the /etc/hosts files or, more commonly, by resolving an Internet domain name with Domain Name System (DNS).

To exploit this vulnerability, all an attacker needs to do is trigger a buffer overflow by using an invalid hostname argument to an application that performs a DNS resolution. This vulnerability then enables a remote attacker to execute arbitrary code with the permissions of the user running DNS. In short, once an attacker has exploited GHOST they may be capable of taking over the system.”

For more details please read the full article at zdnet.