XS Community Edition/0.3/Configuring: Difference between revisions
Line 41: | Line 41: | ||
===Proxy server and web cache (squid)=== |
===Proxy server and web cache (squid)=== |
||
To disable squid: |
To disable squid: (EG. on an XO-1 whose memory/storage only handle minimal services) |
||
<pre> |
<pre> |
||
systemctl stop squid.service |
systemctl stop squid.service |
Revision as of 04:25, 12 May 2013
Initial Setup
- Use "ifconfig" to determine the ip address of the XS.
Take note of its eth0-ip-address = WAN-ip.
If you've inserted the USB Ethernet Adapter above (serving the LAN/Intranet) also take note of the school server's eth1-ip-address = LAN-ip = 172.18.96.1 - If you inserted the USB Ethernet Adapter above, configure its own Wifi Access Point (AP) to properly serve other LAN/Intranet client XOs. (If the Wifi AP is a router, DO NOT plug into its "WAN" port -- instead use any of its LAN/normal ports. And be sure to enable the AP's "bridge mode" or similar, or specifically disable the AP's own DHCP)
Dynamic Host Configuration Protocol (dhcpd)
Internet Domain Name Server (named)
Network Address Translation/NAT (iptables)
XMPP server (ejabberd)
IDMGR
Web server (apache)=
If you want to have simple password authentication to a web directory, it's fairly simple. Here's an example.
Say you'd like http://schoolserver/secret to be password protected. Create /etc/httpd/conf.d/secret.conf:
<Directory /var/www/html/secret> Options Indexes FollowSymLinks MultiViews AllowOverride AuthConfig AuthName "This is a secret dir, but the user/password is secret/phoebe" AuthType Basic AuthUserFile /home/admin/.htpasswd Require user secret </Directory>
Generate the password hash (these aren't the usual instructions because of a bug in Apache 2.4.4):
htpasswd -nb secret phoebe > /home/admin/.htpasswd
Where secret is the user name (no, it's not a user on the XSCE) and phoebe is the password.
Restart the server:
systemctl restart httpd.service
Now when users go to http://schoolserver/secret, they'll have to enter the username and password in a login box.
Proxy server and web cache (squid)
To disable squid: (EG. on an XO-1 whose memory/storage only handle minimal services)
systemctl stop squid.service systemctl disable squid.service rm /etc/sysconfig/xs_httpcache_on xs-setup-network
OLPC-update (rsync)
Activity update (activity updater)
Virtual Private Network (open vpn)
Content Filtering with OpenDNS
There are two components to settting up content filtering with OpenDNS. First, the XSCE needs to look at OpenDNS's DNS IP addresses for DNS. Then there must be an OpenDNS account associated with the XSCE's public IP address. Simply specifying the OpenDNS servers as the XSCE's DNS servers doesn't filter any content. You need to set up an account and configure the content filter level so that OpenDNS knows what to block for your specific IP address.
You may wish to use the OpenDNS DNS servers instead of your ISPs DNS servers if your ISP's DNS servers are unreliable. If you don't need content filtering, no account is required.
To point the XSCE to the OpenDNS DNS servers, edit /etc/named-xs.conf.in
for the forwarders line:
options { /* make named use port 53 for the source of all queries, to allow * firewalls to block all ports except 53: */ forwarders {208.67.222.222; 208.67.220.220;};
Run this command to write the change to named-xs.conf.in to named-xs.conf:
xs-domain-config
Restart the named service:
systemctl restart named.service
Now the XSCE is pointing to OpenDNS's DNS servers. However, internet content will not be filtered until you set up an account with OpenDNS and configure your filter level.
From the IP you wish to enable content filtering for, go to http://www.opendns.com and create an account. When setting a label (friendly name) for your network, it's best to avoid special characters and spaces.
Once your OpenDNS account is created and your network is listed in the settings tab, click on the network's IP to manage settings. Under "Web Content Filtering," select your desired content filter level and click Apply.
If you have a static IP, setup is complete. If your IP is dynamic, the ddclient service is necessary to update OpenDNS when your IP changes.
The ddclient service requires three pieces of information about your OpenDNS account: username, password, and network label. The network label can be found under the OpenDNS Dashboard, in the settings tab, listed in the "LABEL" column under "Your networks."
To install ddclient:
yum -y install ddclient
At the bottom of /etc/ddclient.conf, append the following lines:
## ## OpenDNS.com account-configuration ## use=web, web=myip.dnsomatic.com ssl=yes server=updates.opendns.com protocol=dyndns2 login=yourlogin password=yourpassword your-network-name
Remember how you needed three pieces of information about your OpenDNS account? Edit these three lines with your OpenDNS login credentials and your OpenDNS network label:
login=yourlogin password=yourpassword your-network-name
Enable the ddclient service, for all future boots:
systemctl enable ddclient.service
Start the ddclient service, during the current boot:
systemctl start ddclient.service
If ddclient fails to start with the above command, reboot the XSCE and verify that ddclient came up at boot:
systemctl status ddclient.service
The default ddclient update interval is 300 seconds, which you can change in /etc/ddclient.conf.