Funtoo Resources on LAN

Revision as of 04:11, March 13, 2014 by 666threesixes666 (Talk) (warning of fail2ban being insufficient security.)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


This page will show you how to setup Funtoo resources on your LAN, so you can have a faster access to them via your local area network, for installing packages, updating your local trees, and keep everything in sync.

One use case for this is, if you have more than one machine and you want to keep all machines up to date in such a way that all the machines update to the tree of one machine, and that one primary machines pulls from the outside world (funtoo @ github).


Machine A = Primary Server on LAN (Pulls from github, contains distfiles, contains binaries - built by FEATURES="buildpkg")

Machine B = Another machine on your LAN. Could be a laptop. (Pulls from Machine A. Thus any distfiles that it can get will be pulled from the primary server - thus reducing network load and basically making your primary server a fast cache for future funtoo installs and upgrades. Also this means that you can compile packages on your primary server, and just pull them from Machine B. You can be confident that since Machine B can only be as up-to-date as Machine A, that it won't try to pull some unknown package that hasn't been compiled yet).

Setting up Machine A

Machine A is your primary server and it's basically already complete. Just make sure that SSH is enabled and started (Which it is by default on Funtoo) and make sure that your distfiles and packages are being served out over http. For this setup, root over SSH will be enabled and this is the user that we will be using to sync. You can change this to whatever you want if you really want to. You will need to modify the settings on your own though.

Setting up the binary server

Follow the instructions on this page: Setting up the Host Machine

Some security tips for SSH

In your /etc/ssh/sshd_config, you can add the following:

Change SSH default port

You should definitely do this because if you don't and you open port 22 to the world, you will get attacked. I noticed that I was getting attacked multiple times every single day and the only way I was able to reduce it was to install fail2ban. However, changing the port to another port dropped the number of attacks from [Every Day * Multiple] to 0.

# Change Port 22 to some other port
Port 8902

Limit users

Attackers will try to brute force user names. You can set the "AllowUsers" value so that it only lets those users login.

# Let's say that we only want root and roger to login
AllowUsers root roger

# PermitRootLogin should also be set to 'yes' if it isn't
PermitRootLogin yes

Setting up secondary machine

This section will teach you how to pull from a remote tree, and set up your machine to use the distfiles and packages that your remote tree has (Could be a tree from a local network).

We will assume that you are pulling the tree from your local network and that you are accessing the tree via ssh.

We will assume that this is a fresh install and that you don't have any previous portage trees or setting tweaks.


What we will first due is edit our make.conf so that it pulls resources from the correct locations.

We will assume that Machine A's IP is, SSH port is 8902, that we are logging in as the root user, and that the portage tree is in it's default location of /usr/portage on that machine.

Open up the make.conf file for Machine B and add the following:

# This is where it will try to pull the tree the first time it syncs. After this it will just use w/e the git tree origin is set to

# This sets where it will try to find source files (distfiles). We will try to pull from Machine A first, but if Machine A doesn't have the files we need, it will go to Gentoo to get them

# This sets where it will try to find binary packages (We are using an http server to make it more convenient for us because we don't need "security" to just download precompiled packages)

If you already have a tree

If you already have a tree and would like to delete it and start fresh, you can just delete the .git folder inside the /usr/portage directory and the next time you run emerge --sync, portage will tell you that it isn't a git repository, and it will wipe the contents and sync the new tree.


That is basically it.