Archive | Uncategorized RSS for this section

SoftEther Server

The SoftEther VPN server installation is fairly well documented at  The download file for x64 is

What isn’t document is how to start the service under CentOS, which uses the new systemd files for services instead of the init.d scripts that SoftEther is expecting.

  1. Create a file in /etc/systemd/system named vpnserver.service.  This should be owned by root, have attributes 644 and contain:

    #  This file is part of systemd.

    ExecStart=/usr/local/vpnserver/vpnserver start
    ExecStop=/usr/local/vpnserver/vpnserver stop

  2. sudo systemctl enable vpnserver
  3. systemctl start vpnserver
    systemctl status vpnserver # optional, just to verify

Creating a Windows 8 WiFi hotspot

Windows 8 supports ad hoc networks and WiFi sharing, but not through a GUI interface.  To setup the WiFi adapter on a Windows 8 system to act as a hotspot:

  1. Open an administrative command prompt (Administrator: cmd) via the Win + X shortcut.  You can also type cmd on the Start Screen, right-click and select Run as administrator.
  2. Confirm the WiFi NIC supports virtualization.  Run: netsh wlan show drivers.  The “Hosted network supported : Yes” should be listed.
  3. If it says No then try updating the adapter driver.
  4. Configure an ad hoc connection: netsh wlan set hostednetwork mode=allow ssid=<ad hoc network name> key=<password>.  This sets up a WPA2 PSK network.
  5. Start the network: netsh wlan start hostednetwork
  6. If step 5 fails with a hosted network couldn’t be started and a message about not being in the correct state, go into the Device Manager, and find the Microsoft  virtual NIC under Network adapters.  Disable it, then re-enable it.
  7. Open up the Network Connections and right click on the connection with Internet connectivity.  That’s probably “Local Area Connection”.  Select the Sharing tab, and enable Allow other network users to connect through this computer’s Internet connection.  For the Home networking connection, select the virtual NIC setup by the ad hoc network.  That’s probably something like Local Area Connection*32.  Don’t select the Allow other network users to control or disable the shared Internet connection.
  8. If using something like WireShark for capturing network traffic, select the virtual NIC for the capture interface.  There’s no need to run in Promiscuous mode, and that isn’t well tolerated under Windows 8 anyway.
  9. The ad hoc network will have an adapter IP of  It’s best to make the devices using the hotspot have fixed IPs and then specify192.168.137.1 as the gateway address.  Not specifying IPs results in DHCP, but I’ve never seen the ad hoc gateway successfully act as a DHCP server.  In that case, APIPA kicks in and the hotspot clients have to specify the gateway’s APIPA IP.  Messing with the ICS service under Windows 8 didn’t seem to help the situation.

Changing the boot order in a dual-boot configuration

The default entry for booting in a dual-boot Ubuntu 14.04 and Windows configuration is the first entry in the list.  The dual-boot configuration uses Grub2 for the boot manager.  The settings are under /etc/default and not Grub’s /boot/grub location.  While there are GUI ways to update the order (Grub-Customizer from the Software Center), people have had mixed results with it.  It is easy to go the text file route to change the order.

  1. sudo vi /etc/default/grub
  2. find the GRUB_DEFAULT=0 line and change 0 to 5.  The 5 corresponds to the zero based entry on the boot menu
  3. save the file
  4. run sudo update-grub

If you put an entry in for the index that’s invalid, then the boot loader will use 0 instead.

Installing Flyspray

The list of prerequisites for Flyspray is long.  The easy way is to install XAMPP as a starting point.

Then download and install Flyspray.

That should be easy, but it isn’t.  You get a .zip with .html instructions in it that you don’t know how to display.  The answer is:

  1. install XAMPP by:
    1. chmod 755
    2. ./
    3. press <enter> to get the default settings for the install
    4. start the XAMPP server via /opt/lamp/lamp start
    5. check that <http://ip of box> displays a XAMPP page
  2. delete or move off the files in /opt/lampp/htdocs.
  3. unzip the Flyspray files into the /opt/lampp/htdocs directory.  You should have files like robots.txt and index.php in it.
  4. chmod 777 /opt/lampp/htdocs/cache and /opt/lampp/htdocs/attachments
  5. delete the flyspray.conf.php file from /opt/lampp/htdocs if it exists.  It probably doesn’t.
  6. chmod 777 /opt/lampp/htdocs – this changes the write permission so you don’t get the ../flyspray.conf.php unwriteable warning about a file that doesn’t even exist (yet.)
  7. tighten security on XAMPP by running /opt/lampp/lampp security
  8. display the root of the web site for install instructions and checklists.
  9. delete the /opt/lamp/htdocs/setup directory

Installing an RPM under CentOS from a local repository

The problem with the standard -Uvh install of an RPM is that it doesn’t resolve any dependencies.  For example, the iperf package from: iperf-2.0.5-5.3.i686.rpm

needs a boatload of other packages.  You could add the dependencies one at a time, but you’d be doing that all afternoon.  Using yum and a local repository will do the heavy lifting.

  • Create a directory for you local repository, e.g. /root/repo.
  • Put a copy of the RPM into that directory.
  • Fix the ownership and files permissions if root doesn’t own the repository directory:
    # chown -R root.root /root/repo
  • Install the createrepo package if not installed yet, and then run:
    # createrepo /root/repo
    # chmod -R o-w+r /root/repo
  • Make a repository configuration file in /etc/yum.repos.d/, e.g. /etc/yum.repos.d/my.local.repo containing:
    name=My local repository
  • Install the package (iperf in this case) using:
    # yum install iperf
  • Once the local repository is setup, you can add other RPMs to the repository directory without need to rerun the repository creation or configuration steps.

Startup script in Fedora 19

In /etc/systemd/system/<x>.service:

Description=What the script will do

ExecStart=/bin/sh -c ‘/full/path/to/’


Then systemctl enable <x>.service

Building MPTCP iproute

You built a new Multi-Path TCP kernel from  Guess what?  You didn’t get matching tools like a revised “ip” to go with it.  Here’s how to build them and get them to a target Fedora 19+ system:

  1. git clone –depth=1 git://
  2. yum install libdb-devel  this is needed for Berkley DB support
  3. cd iproute-mptcp
  4. make
  5. scp ./etc/iproute2/* <dest>:/etc/iproute2
  6. cd ip
  7. scp ifcfg ip routef routel rtacct rtmon rtpr <dest>:/sbin
  8. cd ../tc
  9. scp tc <dest>:/sbin