http://bering-uclibc.zetam.org/api.php?action=feedcontributions&user=Etitl&feedformat=atombering-uClibc - User contributions [en]2024-03-28T10:15:14ZUser contributionsMediaWiki 1.26.0http://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Wireguard&diff=4647Bering-uClibc 7.x - User Guide - Advanced Topics - Wireguard2021-01-10T14:38:01Z<p>Etitl: /* Firewall settings */</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Configuring Wireguard|Advanced Topics - Configuring Wireguard]]<br />
|-<br />
| width="20%" align="left" | [[User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
==Configuring Wireguard==<br />
<br />
===Objectives===<br />
This is a short introduction on how to configure the wireguard VPN on your LEAF system.<br />
<br />
===Prerequisites===<br />
The software used build a VPN tunnel using '''''[https://www.wireguard.com/ wireguard]''''' is packaged in the '''''wireguard.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wireguard.lrp''''' depends on the following packages:<br />
* bash.lrp<br />
<br />
===Configuration===<br />
<br />
The wireguard VPN software is configured using a text file '''''/etc/wireguard/wg<tunnel ID>.conf''''', typically '''''/etc/wireguard/wg0.conf'''''. It is also controlled by the file '''''/etc/default/wireguard''''' where a few start parameters are defined. The '''''wireguard.lrp''''' package includes a copy of these two files for your reference.<br />
<br />
====/etc/wireguard/wg0.conf====<br />
<br />
The '''''/etc/wireguard/wg0.conf''''' file is used to tell hold the wireguard keys and information about the wireguard peer. The '''''wireguard''''' VPN is a peer network, however slight differences in the configurations exist, especially the initiator side uses the parameter Endpoint to address its peer. The example below shows the client or initiator side of the '''''wireguard''''' VPN.<br />
<br />
# This is a dummy configuration file for the wireguard VPN server.<br />
# It should reside in /etc/wireguard and is designed to be used<br />
# by the wg-quick script viz:<br />
# 'wg-quick up wg0' to start the VPN server and<br />
# 'wg-quick down wg0' to stop it.<br />
#<br />
# Generate the private & public keys required thus:<br />
# umask 077<br />
# wg genkey | tee private_key | wg pubkey > public_key<br />
#<br />
# Dummy config:<br />
#<br />
[Interface]<br />
Address = 192.168.17.2/24<br />
ListenPort = 11194<br />
PrivateKey = EKufmuT959jTCnFlK+jjhJvzPQWdEaEzNWsHIYnzTV8=<br />
#<br />
#<br />
# Peer1<br />
[Peer]<br />
PublicKey = DJDe260WVX8Cm2gjf/0nmklHkO8N8XgSTpvB34zJzz0=<br />
AllowedIPs = 192.168.17.1<br />
Endpoint = the_other_side.example.net:11194<br />
#<br />
# Peer2<br />
#[Peer]<br />
#PublicKey = <Peer 2 public key base64 string><br />
#AllowedIPs = <comma-separated address/cidr ranges allowed access from Peer 2><br />
#<br />
<br />
To configure wireguard you need to edit the wg0.conf file and generate a private and public key pair for each of the tunnel endpoints.<br />
<br />
For detailed information on how to set the up wireguard please refer to '''''[https://www.wireguard.com/ wireguard]'''''.<br />
<br />
====/etc/default/wireguard====<br />
<br />
This file controls the wireguard daemon. It just defines if the daemon is started at all and the name of the wireguard interface used.<br />
<br />
# Configuration for Wireguard init script<br />
#<br />
# Set to "yes" to start the VPN server at boot time<br />
START="yes"<br />
#<br />
# Interface name. It must have a matching ${INTERFACE}.conf file in /etc/wireguard<br />
INTERFACE="wg0"<br />
<br />
==Firewall settings==<br />
<br />
If you have to pass a firewall then you need to provide a way, possibly on both sides, for the tunnel and the tunneled packages to reach their respective destination. [https://shorewall.org/ Shorewall] provides a [https://shorewall.org/4.6/GenericTunnels.html configuration file] '''''/etc/shorewall/tunnels''''' which can be used to provide this access.</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Wireguard&diff=4646Bering-uClibc 7.x - User Guide - Advanced Topics - Wireguard2021-01-10T14:37:32Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Configuring Wireguard|Advanced Topics - Configuring Wireguard]]<br />
|-<br />
| width="20%" align="left" | [[User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
==Configuring Wireguard==<br />
<br />
===Objectives===<br />
This is a short introduction on how to configure the wireguard VPN on your LEAF system.<br />
<br />
===Prerequisites===<br />
The software used build a VPN tunnel using '''''[https://www.wireguard.com/ wireguard]''''' is packaged in the '''''wireguard.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wireguard.lrp''''' depends on the following packages:<br />
* bash.lrp<br />
<br />
===Configuration===<br />
<br />
The wireguard VPN software is configured using a text file '''''/etc/wireguard/wg<tunnel ID>.conf''''', typically '''''/etc/wireguard/wg0.conf'''''. It is also controlled by the file '''''/etc/default/wireguard''''' where a few start parameters are defined. The '''''wireguard.lrp''''' package includes a copy of these two files for your reference.<br />
<br />
====/etc/wireguard/wg0.conf====<br />
<br />
The '''''/etc/wireguard/wg0.conf''''' file is used to tell hold the wireguard keys and information about the wireguard peer. The '''''wireguard''''' VPN is a peer network, however slight differences in the configurations exist, especially the initiator side uses the parameter Endpoint to address its peer. The example below shows the client or initiator side of the '''''wireguard''''' VPN.<br />
<br />
# This is a dummy configuration file for the wireguard VPN server.<br />
# It should reside in /etc/wireguard and is designed to be used<br />
# by the wg-quick script viz:<br />
# 'wg-quick up wg0' to start the VPN server and<br />
# 'wg-quick down wg0' to stop it.<br />
#<br />
# Generate the private & public keys required thus:<br />
# umask 077<br />
# wg genkey | tee private_key | wg pubkey > public_key<br />
#<br />
# Dummy config:<br />
#<br />
[Interface]<br />
Address = 192.168.17.2/24<br />
ListenPort = 11194<br />
PrivateKey = EKufmuT959jTCnFlK+jjhJvzPQWdEaEzNWsHIYnzTV8=<br />
#<br />
#<br />
# Peer1<br />
[Peer]<br />
PublicKey = DJDe260WVX8Cm2gjf/0nmklHkO8N8XgSTpvB34zJzz0=<br />
AllowedIPs = 192.168.17.1<br />
Endpoint = the_other_side.example.net:11194<br />
#<br />
# Peer2<br />
#[Peer]<br />
#PublicKey = <Peer 2 public key base64 string><br />
#AllowedIPs = <comma-separated address/cidr ranges allowed access from Peer 2><br />
#<br />
<br />
To configure wireguard you need to edit the wg0.conf file and generate a private and public key pair for each of the tunnel endpoints.<br />
<br />
For detailed information on how to set the up wireguard please refer to '''''[https://www.wireguard.com/ wireguard]'''''.<br />
<br />
====/etc/default/wireguard====<br />
<br />
This file controls the wireguard daemon. It just defines if the daemon is started at all and the name of the wireguard interface used.<br />
<br />
# Configuration for Wireguard init script<br />
#<br />
# Set to "yes" to start the VPN server at boot time<br />
START="yes"<br />
#<br />
# Interface name. It must have a matching ${INTERFACE}.conf file in /etc/wireguard<br />
INTERFACE="wg0"<br />
<br />
==Firewall settings==<br />
<br />
If you have to pass a firewall then you need to provide a way, possibly on both sides, for the tunnel and the tunneled packages to reach their respective destination. [https://shorewall.org/ Schorewall] provides a [https://shorewall.org/4.6/GenericTunnels.html configuration file] '''''/etc/shorewall/tunnels''''' which can be used to provide this access.</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Wireguard&diff=4645Bering-uClibc 7.x - User Guide - Advanced Topics - Wireguard2021-01-10T14:36:20Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Configuring Wireguard|Advanced Topics - Configuring Wireguard]]<br />
|-<br />
| width="20%" align="left" | [[User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
==Configuring Wireguard==<br />
<br />
===Objectives===<br />
This is a short introduction on how to configure the wireguard VPN on your LEAF system.<br />
<br />
===Prerequisites===<br />
The software used build a VPN tunnel using '''''[https://www.wireguard.com/ wireguard]''''' is packaged in the '''''wireguard.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wireguard.lrp''''' depends on the following packages:<br />
* bash.lrp<br />
<br />
===Configuration===<br />
<br />
The wireguard VPN software is configured using a text file '''''/etc/wireguard/wg<tunnel ID>.conf''''', typically '''''/etc/wireguard/wg0.conf'''''. It is also controlled by the file '''''/etc/default/wireguard''''' where a few start parameters are defined. The '''''wireguard.lrp''''' package includes a copy of these two files for your reference.<br />
<br />
====/etc/wireguard/wg0.conf====<br />
<br />
The '''''/etc/wireguard/wg0.conf''''' file is used to tell hold the wireguard keys and information about the wireguard peer. The '''''wireguard''''' VPN is a peer network, however slight differences in the configurations exist, especially the initiator side uses the parameter Endpoint to address its peer. The example below shows the client or initiator side of the '''''wireguard''''' VPN.<br />
<br />
# This is a dummy configuration file for the wireguard VPN server.<br />
# It should reside in /etc/wireguard and is designed to be used<br />
# by the wg-quick script viz:<br />
# 'wg-quick up wg0' to start the VPN server and<br />
# 'wg-quick down wg0' to stop it.<br />
#<br />
# Generate the private & public keys required thus:<br />
# umask 077<br />
# wg genkey | tee private_key | wg pubkey > public_key<br />
#<br />
# Dummy config:<br />
#<br />
[Interface]<br />
Address = 192.168.17.2/24<br />
ListenPort = 11194<br />
PrivateKey = EKufmuT959jTCnFlK+jjhJvzPQWdEaEzNWsHIYnzTV8=<br />
#<br />
#<br />
# Peer1<br />
[Peer]<br />
PublicKey = DJDe260WVX8Cm2gjf/0nmklHkO8N8XgSTpvB34zJzz0=<br />
AllowedIPs = 192.168.17.1<br />
Endpoint = the_other_side.example.net:11194<br />
#<br />
# Peer2<br />
#[Peer]<br />
#PublicKey = <Peer 2 public key base64 string><br />
#AllowedIPs = <comma-separated address/cidr ranges allowed access from Peer 2><br />
#<br />
<br />
To configure wireguard you need to edit the wg0.conf file and generate a private and public key pair for each of the tunnel endpoints.<br />
<br />
For detailed information on how to set the up wireguard please refer to '''''[https://www.wireguard.com/ wireguard]'''''.<br />
<br />
====/etc/default/wireguard====<br />
<br />
This file controls the wireguard daemon. It just defines if the daemon is started at all and the name of the wireguard interface used.<br />
<br />
# Configuration for Wireguard init script<br />
#<br />
# Set to "yes" to start the VPN server at boot time<br />
START="yes"<br />
#<br />
# Interface name. It must have a matching ${INTERFACE}.conf file in /etc/wireguard<br />
INTERFACE="wg0"<br />
<br />
==Firewall settings==<br />
<br />
If you have to pass a firewall then you need to provide a way, possibly on both sides' for the tunnel and the tunneled packages to reach their respective destination. [https://shorewall.org/ Schorewall] provides a [https://shorewall.org/4.6/GenericTunnels.html configuration file] '''''/etc/shorewall/tunnels''''' which can be used to provide this access.</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Wireguard&diff=4644Bering-uClibc 7.x - User Guide - Advanced Topics - Wireguard2021-01-10T14:27:54Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Configuring Wireguard|Advanced Topics - Configuring Wireguard]]<br />
|-<br />
| width="20%" align="left" | [[User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
==Configuring Wireguard==<br />
<br />
===Objectives===<br />
This is a short introduction on how to configure the wireguard VPN on your LEAF system.<br />
<br />
===Prerequisites===<br />
The software used build a VPN tunnel using '''''[https://www.wireguard.com/ wireguard]''''' is packaged in the '''''wireguard.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wireguard.lrp''''' depends on the following packages:<br />
* bash.lrp<br />
<br />
===Configuration===<br />
<br />
The wireguard VPN software is configured using a text file '''''/etc/wireguard/wg<tunnel ID>.conf''''', typically '''''/etc/wireguard/wg0.conf'''''. It is also controlled by the file '''''/etc/default/wireguard''''' where a few start parameters are defined. The '''''wireguard.lrp''''' package includes a copy of these two files for your reference.<br />
<br />
====/etc/wireguard/wg0.conf====<br />
<br />
The '''''/etc/wireguard/wg0.conf''''' file is used to tell hold the wireguard keys and information about the wireguard peer. The '''''wireguard''''' VPN is a peer network, however slight differences in the configurations exist, especially the initiator side uses the parameter Endpoint to address its peer. The example below shows the client or initiator side of the '''''wireguard''''' VPN.<br />
<br />
# This is a dummy configuration file for the wireguard VPN server.<br />
# It should reside in /etc/wireguard and is designed to be used<br />
# by the wg-quick script viz:<br />
# 'wg-quick up wg0' to start the VPN server and<br />
# 'wg-quick down wg0' to stop it.<br />
#<br />
# Generate the private & public keys required thus:<br />
# umask 077<br />
# wg genkey | tee private_key | wg pubkey > public_key<br />
#<br />
# Dummy config:<br />
#<br />
[Interface]<br />
Address = 192.168.17.2/24<br />
ListenPort = 11194<br />
PrivateKey = EKufmuT959jTCnFlK+jjhJvzPQWdEaEzNWsHIYnzTV8=<br />
#<br />
#<br />
# Peer1<br />
[Peer]<br />
PublicKey = DJDe260WVX8Cm2gjf/0nmklHkO8N8XgSTpvB34zJzz0=<br />
AllowedIPs = 192.168.17.1<br />
Endpoint = the_other_side.example.net:11194<br />
#<br />
# Peer2<br />
#[Peer]<br />
#PublicKey = <Peer 2 public key base64 string><br />
#AllowedIPs = <comma-separated address/cidr ranges allowed access from Peer 2><br />
#<br />
<br />
To configure wireguard you need to edit the wg0.conf file and generate a private and public key pair for each of the tunnel endpoints.<br />
<br />
For detailed information on how to set the up wireguard please refer to '''''[https://www.wireguard.com/ wireguard]'''''.<br />
<br />
====/etc/default/wireguard====<br />
<br />
This file controls the wireguard daemon. It just defines if the daemon is started at all and the name of the wireguard interface used.<br />
<br />
# Configuration for Wireguard init script<br />
#<br />
# Set to "yes" to start the VPN server at boot time<br />
START="yes"<br />
#<br />
# Interface name. It must have a matching ${INTERFACE}.conf file in /etc/wireguard<br />
INTERFACE="wg0"<br />
<br />
==Firewall settings==</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Wireguard&diff=4643Bering-uClibc 7.x - User Guide - Advanced Topics - Wireguard2021-01-08T13:41:32Z<p>Etitl: /* /etc/default/wireguard */</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Configuring Wireguard|Advanced Topics - Configuring Wireguard]]<br />
|-<br />
| width="20%" align="left" | [[User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
==Configuring Wireguard==<br />
<br />
===Objectives===<br />
This is a short introduction on how to configure the wireguard VPN on your LEAF system.<br />
<br />
===Prerequisites===<br />
The software used build a VPN tunnel using '''''[https://www.wireguard.com/ wireguard]''''' is packaged in the '''''wireguard.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wireguard.lrp''''' depends on the following packages:<br />
* bash.lrp<br />
<br />
===Configuration===<br />
<br />
The wireguard VPN software is configured using a text file '''''/etc/wireguard/wg<tunnel ID>.conf''''', typically '''''/etc/wireguard/wg0.conf'''''. It is also controlled by the file '''''/etc/default/wireguard''''' where a few start parameters are defined. The '''''wireguard.lrp''''' package includes a copy of these two files for your reference.<br />
<br />
====/etc/wireguard/wg0.conf====<br />
<br />
The '''''/etc/wireguard/wg0.conf''''' file is used to tell hold the wireguard keys and information about the wireguard peer. The '''''wireguard''''' VPN is a peer network, however slight differences in the configurations exist, especially the initiator side uses the parameter Endpoint to address its peer. The example below shows the client or initiator side of the '''''wireguard''''' VPN.<br />
<br />
# This is a dummy configuration file for the wireguard VPN server.<br />
# It should reside in /etc/wireguard and is designed to be used<br />
# by the wg-quick script viz:<br />
# 'wg-quick up wg0' to start the VPN server and<br />
# 'wg-quick down wg0' to stop it.<br />
#<br />
# Generate the private & public keys required thus:<br />
# umask 077<br />
# wg genkey | tee private_key | wg pubkey > public_key<br />
#<br />
# Dummy config:<br />
#<br />
[Interface]<br />
Address = 192.168.17.2/24<br />
ListenPort = 11194<br />
PrivateKey = EKufmuT959jTCnFlK+jjhJvzPQWdEaEzNWsHIYnzTV8=<br />
#<br />
#<br />
# Peer1<br />
[Peer]<br />
PublicKey = DJDe260WVX8Cm2gjf/0nmklHkO8N8XgSTpvB34zJzz0=<br />
AllowedIPs = 192.168.17.1<br />
Endpoint = the_other_side.example.net:11194<br />
#<br />
# Peer2<br />
#[Peer]<br />
#PublicKey = <Peer 2 public key base64 string><br />
#AllowedIPs = <comma-separated address/cidr ranges allowed access from Peer 2><br />
#<br />
<br />
To configure wireguard you need to edit the wg0.conf file and generate a private and public key pair for each of the tunnel endpoints.<br />
<br />
For detailed information on how to set the up wireguard please refer to '''''[https://www.wireguard.com/ wireguard]'''''.<br />
<br />
====/etc/default/wireguard====<br />
<br />
This file controls the wireguard daemon. It just defines if the daemon is started at all and the name of the wireguard interface used.<br />
<br />
# Configuration for Wireguard init script<br />
#<br />
# Set to "yes" to start the VPN server at boot time<br />
START="yes"<br />
#<br />
# Interface name. It must have a matching ${INTERFACE}.conf file in /etc/wireguard<br />
INTERFACE="wg0"</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Wireguard&diff=4642Bering-uClibc 7.x - User Guide - Advanced Topics - Wireguard2021-01-08T13:40:49Z<p>Etitl: /* wg0.conf */</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Configuring Wireguard|Advanced Topics - Configuring Wireguard]]<br />
|-<br />
| width="20%" align="left" | [[User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
==Configuring Wireguard==<br />
<br />
===Objectives===<br />
This is a short introduction on how to configure the wireguard VPN on your LEAF system.<br />
<br />
===Prerequisites===<br />
The software used build a VPN tunnel using '''''[https://www.wireguard.com/ wireguard]''''' is packaged in the '''''wireguard.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wireguard.lrp''''' depends on the following packages:<br />
* bash.lrp<br />
<br />
===Configuration===<br />
<br />
The wireguard VPN software is configured using a text file '''''/etc/wireguard/wg<tunnel ID>.conf''''', typically '''''/etc/wireguard/wg0.conf'''''. It is also controlled by the file '''''/etc/default/wireguard''''' where a few start parameters are defined. The '''''wireguard.lrp''''' package includes a copy of these two files for your reference.<br />
<br />
====/etc/wireguard/wg0.conf====<br />
<br />
The '''''/etc/wireguard/wg0.conf''''' file is used to tell hold the wireguard keys and information about the wireguard peer. The '''''wireguard''''' VPN is a peer network, however slight differences in the configurations exist, especially the initiator side uses the parameter Endpoint to address its peer. The example below shows the client or initiator side of the '''''wireguard''''' VPN.<br />
<br />
# This is a dummy configuration file for the wireguard VPN server.<br />
# It should reside in /etc/wireguard and is designed to be used<br />
# by the wg-quick script viz:<br />
# 'wg-quick up wg0' to start the VPN server and<br />
# 'wg-quick down wg0' to stop it.<br />
#<br />
# Generate the private & public keys required thus:<br />
# umask 077<br />
# wg genkey | tee private_key | wg pubkey > public_key<br />
#<br />
# Dummy config:<br />
#<br />
[Interface]<br />
Address = 192.168.17.2/24<br />
ListenPort = 11194<br />
PrivateKey = EKufmuT959jTCnFlK+jjhJvzPQWdEaEzNWsHIYnzTV8=<br />
#<br />
#<br />
# Peer1<br />
[Peer]<br />
PublicKey = DJDe260WVX8Cm2gjf/0nmklHkO8N8XgSTpvB34zJzz0=<br />
AllowedIPs = 192.168.17.1<br />
Endpoint = the_other_side.example.net:11194<br />
#<br />
# Peer2<br />
#[Peer]<br />
#PublicKey = <Peer 2 public key base64 string><br />
#AllowedIPs = <comma-separated address/cidr ranges allowed access from Peer 2><br />
#<br />
<br />
To configure wireguard you need to edit the wg0.conf file and generate a private and public key pair for each of the tunnel endpoints.<br />
<br />
For detailed information on how to set the up wireguard please refer to '''''[https://www.wireguard.com/ wireguard]'''''.<br />
<br />
====/etc/default/wireguard====<br />
<br />
This file controls the wireguard daemon. It just defines if the daemon is started at all and the name if the wireguard interface used.<br />
<br />
# Configuration for Wireguard init script<br />
#<br />
# Set to "yes" to start the VPN server at boot time<br />
START="yes"<br />
#<br />
# Interface name. It must have a matching ${INTERFACE}.conf file in /etc/wireguard<br />
INTERFACE="wg0"</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Wireguard&diff=4641Bering-uClibc 7.x - User Guide - Advanced Topics - Wireguard2021-01-08T13:40:14Z<p>Etitl: /* /etc/default/wireguard */</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Configuring Wireguard|Advanced Topics - Configuring Wireguard]]<br />
|-<br />
| width="20%" align="left" | [[User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
==Configuring Wireguard==<br />
<br />
===Objectives===<br />
This is a short introduction on how to configure the wireguard VPN on your LEAF system.<br />
<br />
===Prerequisites===<br />
The software used build a VPN tunnel using '''''[https://www.wireguard.com/ wireguard]''''' is packaged in the '''''wireguard.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wireguard.lrp''''' depends on the following packages:<br />
* bash.lrp<br />
<br />
===Configuration===<br />
<br />
The wireguard VPN software is configured using a text file '''''/etc/wireguard/wg<tunnel ID>.conf''''', typically '''''/etc/wireguard/wg0.conf'''''. It is also controlled by the file '''''/etc/default/wireguard''''' where a few start parameters are defined. The '''''wireguard.lrp''''' package includes a copy of these two files for your reference.<br />
<br />
====wg0.conf====<br />
<br />
The '''''/etc/wireguard/wg0.conf''''' file is used to tell hold the wireguard keys and information about the wireguard peer. The '''''wireguard''''' VPN is a peer network, however slight differences in the configurations exist, especially the initiator side uses the parameter Endpoint to address its peer. The example below shows the client or initiator side of the '''''wireguard''''' VPN.<br />
<br />
# This is a dummy configuration file for the wireguard VPN server.<br />
# It should reside in /etc/wireguard and is designed to be used<br />
# by the wg-quick script viz:<br />
# 'wg-quick up wg0' to start the VPN server and<br />
# 'wg-quick down wg0' to stop it.<br />
#<br />
# Generate the private & public keys required thus:<br />
# umask 077<br />
# wg genkey | tee private_key | wg pubkey > public_key<br />
#<br />
# Dummy config:<br />
#<br />
[Interface]<br />
Address = 192.168.17.2/24<br />
ListenPort = 11194<br />
PrivateKey = EKufmuT959jTCnFlK+jjhJvzPQWdEaEzNWsHIYnzTV8=<br />
#<br />
#<br />
# Peer1<br />
[Peer]<br />
PublicKey = DJDe260WVX8Cm2gjf/0nmklHkO8N8XgSTpvB34zJzz0=<br />
AllowedIPs = 192.168.17.1<br />
Endpoint = the_other_side.example.net:11194<br />
#<br />
# Peer2<br />
#[Peer]<br />
#PublicKey = <Peer 2 public key base64 string><br />
#AllowedIPs = <comma-separated address/cidr ranges allowed access from Peer 2><br />
#<br />
<br />
To configure wireguard you need to edit the wg0.conf file and generate a private and public key pair for each of the tunnel endpoints.<br />
<br />
For detailed information on how to set the up wireguard please refer to '''''[https://www.wireguard.com/ wireguard]'''''. <br />
<br />
====/etc/default/wireguard====<br />
<br />
This file controls the wireguard daemon. It just defines if the daemon is started at all and the name if the wireguard interface used.<br />
<br />
# Configuration for Wireguard init script<br />
#<br />
# Set to "yes" to start the VPN server at boot time<br />
START="yes"<br />
#<br />
# Interface name. It must have a matching ${INTERFACE}.conf file in /etc/wireguard<br />
INTERFACE="wg0"</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Wireguard&diff=4640Bering-uClibc 7.x - User Guide - Advanced Topics - Wireguard2021-01-08T13:39:26Z<p>Etitl: Initial version for wireguard</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Configuring Wireguard|Advanced Topics - Configuring Wireguard]]<br />
|-<br />
| width="20%" align="left" | [[User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
==Configuring Wireguard==<br />
<br />
===Objectives===<br />
This is a short introduction on how to configure the wireguard VPN on your LEAF system.<br />
<br />
===Prerequisites===<br />
The software used build a VPN tunnel using '''''[https://www.wireguard.com/ wireguard]''''' is packaged in the '''''wireguard.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wireguard.lrp''''' depends on the following packages:<br />
* bash.lrp<br />
<br />
===Configuration===<br />
<br />
The wireguard VPN software is configured using a text file '''''/etc/wireguard/wg<tunnel ID>.conf''''', typically '''''/etc/wireguard/wg0.conf'''''. It is also controlled by the file '''''/etc/default/wireguard''''' where a few start parameters are defined. The '''''wireguard.lrp''''' package includes a copy of these two files for your reference.<br />
<br />
====wg0.conf====<br />
<br />
The '''''/etc/wireguard/wg0.conf''''' file is used to tell hold the wireguard keys and information about the wireguard peer. The '''''wireguard''''' VPN is a peer network, however slight differences in the configurations exist, especially the initiator side uses the parameter Endpoint to address its peer. The example below shows the client or initiator side of the '''''wireguard''''' VPN.<br />
<br />
# This is a dummy configuration file for the wireguard VPN server.<br />
# It should reside in /etc/wireguard and is designed to be used<br />
# by the wg-quick script viz:<br />
# 'wg-quick up wg0' to start the VPN server and<br />
# 'wg-quick down wg0' to stop it.<br />
#<br />
# Generate the private & public keys required thus:<br />
# umask 077<br />
# wg genkey | tee private_key | wg pubkey > public_key<br />
#<br />
# Dummy config:<br />
#<br />
[Interface]<br />
Address = 192.168.17.2/24<br />
ListenPort = 11194<br />
PrivateKey = EKufmuT959jTCnFlK+jjhJvzPQWdEaEzNWsHIYnzTV8=<br />
#<br />
#<br />
# Peer1<br />
[Peer]<br />
PublicKey = DJDe260WVX8Cm2gjf/0nmklHkO8N8XgSTpvB34zJzz0=<br />
AllowedIPs = 192.168.17.1<br />
Endpoint = the_other_side.example.net:11194<br />
#<br />
# Peer2<br />
#[Peer]<br />
#PublicKey = <Peer 2 public key base64 string><br />
#AllowedIPs = <comma-separated address/cidr ranges allowed access from Peer 2><br />
#<br />
<br />
To configure wireguard you need to edit the wg0.conf file and generate a private and public key pair for each of the tunnel endpoints.<br />
<br />
For detailed information on how to set the up wireguard please refer to '''''[https://www.wireguard.com/ wireguard]'''''. <br />
<br />
====/etc/default/wiregurard====<br />
<br />
This file controls the wireguard daemon. It just defines if the daemon is started at all and the name if the wireguard interface used.<br />
<br />
# Configuration for Wireguard init script<br />
#<br />
# Set to "yes" to start the VPN server at boot time<br />
START="yes"<br />
#<br />
# Interface name. It must have a matching ${INTERFACE}.conf file in /etc/wireguard<br />
INTERFACE="wg0"</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Wireguard&diff=4639Bering-uClibc 7.x - User Guide - Advanced Topics - Wireguard2021-01-08T13:23:35Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Configuring Wireguard|Advanced Topics - Configuring Wireguard]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
==Configuring Wireguard==<br />
<br />
===Objectives===<br />
This is a short introduction on how to configure the wireguard VPN on your LEAF system.<br />
<br />
===Prerequisites===<br />
The software used build a VPN tunnel using '''''[https://www.wireguard.com/ wireguard]''''' is packaged in the '''''wireguard.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wireguard.lrp''''' depends on the following packages:<br />
* bash.lrp<br />
<br />
===Configuration===<br />
<br />
The wireguard VPN software is configured using a text file '''''/etc/wireguard/wg<tunnel ID>.conf''''', typically '''''/etc/wireguard/wg0.conf'''''. It is also controlled by the file '''''/etc/default/wireguard''''' where a few start parameters are defined. The '''''wireguard.lrp''''' package includes a copy of these two files for your reference.<br />
<br />
====wpa_supplicant.conf====<br />
<br />
The '''''/etc/wireguard/wg0.conf''''' file is used to tell hold the wireguard keys and information about the wireguard peer. The '''''wireguard''''' VPN is a peer network, however slight differences in the configurations exist, especially the initiator side uses the parameter Endoint to address its peer. The example below shows the client or initiator side of the '''''wireguard''''' VPN.<br />
<br />
# This is a dummy configuration file for the wireguard VPN server.<br />
# It should reside in /etc/wireguard and is designed to be used<br />
# by the wg-quick script viz:<br />
# 'wg-quick up wg0' to start the VPN server and<br />
# 'wg-quick down wg0' to stop it.<br />
#<br />
# Generate the private & public keys required thus:<br />
# umask 077<br />
# wg genkey | tee private_key | wg pubkey > public_key<br />
#<br />
# Dummy config:<br />
#<br />
[Interface]<br />
Address = 192.168.17.2/24<br />
ListenPort = 11194<br />
PrivateKey = EKufmuT959jTCnFlK+jjhJvzPQWdEaEzNWsHIYnzTV8=<br />
#<br />
#<br />
# Peer1<br />
[Peer]<br />
PublicKey = DJDe260WVX8Cm2gjf/0nmklHkO8N8XgSTpvB34zJzz0=<br />
AllowedIPs = 192.168.17.1<br />
Endpoint = the_other_side.example.net:11194<br />
#<br />
# Peer2<br />
#[Peer]<br />
#PublicKey = <Peer 2 public key base64 string><br />
#AllowedIPs = <comma-separated address/cidr ranges allowed access from Peer 2><br />
#</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Wireguard&diff=4638Bering-uClibc 7.x - User Guide - Advanced Topics - Wireguard2021-01-08T12:59:42Z<p>Etitl: Created page with "{| summary="Navigation header" width="100%" ! colspan="3" align="center" | Bering-uClibc 7.x - User Guide - Advanced Topics - Configuring Wireguard|Advanced Topics - Configu..."</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Configuring Wireguard|Advanced Topics - Configuring Wireguard]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide&diff=4637Bering-uClibc 7.x - User Guide2021-01-08T07:14:30Z<p>Etitl: </p>
<hr />
<div>=WARNING: Work in progress, this doc. is not complete yet =<br />
<br />
This is the "Table of Contents" page for the [[Bering-uClibc 7.x - User Guide]].<br />
<br />
This guide provides information for Installers, Administrators and general Users of [[Bering-uClibc 7.x]]. <br />
<br />
Click on one of the links below to access the relevant Chapter or Sub-Chapter. Then, use the ''Next'' and ''Prev'' links to move from Chapter to Chapter, or click a ''Bering-uClibc 7.x - User Guide'' link (at the top of each Chapter or Sub-Chapter page) to return here.<br />
<br />
<br />
==Chapters==<br />
# [[Bering-uClibc 7.x - User Guide - Introduction|Introduction]]<br />
<!-- # [[Bering-uClibc 7.x - User Guide - Hardware Requirements|Hardware Requirements]]<br />
--><br />
# [[Bering-uClibc 7.x - User Guide - Installing the Disk Image|Installing the Disk Image]]<br />
# [[Bering-uClibc 7.x - User Guide - Basic Configuration|Basic Configuration]]<br />
#* [[Bering-uClibc 7.x - User Guide - Basic Configuration - Booting for the First Time|Booting for the First Time]]<br />
#* [[Bering-uClibc 7.x - User Guide - Basic Configuration - Basic System Configuration|Basic System Configuration]]<br />
#* [[Bering-uClibc 7.x - User Guide - Basic Configuration - LEAF Packages|LEAF Packages]]<br />
#* [[Bering-uClibc 7.x - User Guide - Basic Configuration - Log Files|Log Files]]<br />
#* [[Bering-uClibc 7.x - User Guide - Basic Configuration - Email Alerts|Email Alerts]]<br />
#* [[Bering-uClibc 7.x - User Guide - Basic Configuration - Setup a small timeserver|Setup a small timeserver]]<br />
#* [[Bering-uClibc 7.x - User Guide - Basic Configuration - Using dropbear - a small SSH replacement|Using dropbear - a small SSH replacement]]<br />
# [[Bering-uClibc 7.x - User Guide - IPv4 Networking|IPv4 Networking]]<br />
#* [[Bering-uClibc 7.x - User Guide - IPv4 Networking - External Network Connections|External Network Connections]]<br />
#* [[Bering-uClibc 7.x - User Guide - IPv4 Networking - Internal Network Connections|Internal Network Connections]]<br />
#* [[Bering-uClibc 7.x - User Guide - IPv4 Networking - Configure Shorewall|Configure Shorewall]]<br />
#* [[Bering-uClibc 7.x - User Guide - IPv4 Networking - Configure Traffic Management|Configure Traffic Management]]<br />
#* [[Bering-uClibc 7.x - User Guide - IPv4 Networking - Configure Dnsmasq|Configure Dnsmasq]]<br />
#* [[Bering-uClibc 7.x - User Guide - IPv4 Networking - Configure 802.1Q VLANs|Configure 802.1Q VLANs]]<br />
# [[Bering-uClibc 7.x - User Guide - IPv6 Networking|IPv6 Networking]]<br />
#* [[Bering-uClibc 7.x - User Guide - IPv6 Networking - External Network Connections|External Network Connections]]<br />
<!-- #* [[Bering-uClibc 7.x - User Guide - IPv6 Networking - Internal Network Connections|Internal Network Connections]]<br />
--><br />
#* [[Bering-uClibc 7.x - User Guide - IPv6 Networking - Configure Shorewall6|Configure Shorewall6]]<br />
#* [[Bering-uClibc 7.x - User Guide - IPv6 Networking - Configure Router Advertisements|Configure Router Advertisements]]<br />
#* [[Bering-uClibc 7.x - User Guide - IPv6 Networking - Configure DHCPv6|Configure DHCPv6]]<br />
# [[Bering-uClibc 7.x - User Guide - Advanced Topics|Advanced Topics]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Dynamic DNS Client with ezipupd |Setting Up a Client for Dynamic DNS with ezipupd]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Dynamic DNS Client with ddclient |Setting Up a Client for Dynamic DNS with ddclient]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Setting Up a Wireless Access Point]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Setting Up a Wireless Internet Connection]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network|Setting Up a Virtual Private Network (VPN)]]<br />
#** [[Bering-uClibc 7.x - User Guide - Advanced Topics - Wireguard|wireguard]]<br />
#** [[Bering-uClibc 7.x - User Guide - Advanced Topics - OpenVPN|OpenVPN]]<br />
#** [[Bering-uClibc 7.x - User Guide - Advanced Topics - IPsec|IPsec]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Routing Daemon|Setting Up a Routing Daemon]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Print Server|Setting Up a Print Server]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a VOIP Server|Setting Up a VOIP Server]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a File Server|Setting Up a File Server]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a RADIUS Server|Setting Up a RADIUS Server]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Bridge|Setting Up a Bridge]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Network Emulator|Setting Up a Network Emulator]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up Zeroconf Networking|Setting Up Zeroconf Networking]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up Universal Plug and Play|Setting Up Universal Plug and Play (UPnP)]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up Tor|Setting Up Tor]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up Remote Monitoring|Setting Up Remote Monitoring]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up Backup to Remote Server|Setting Up Backup to Remote Server]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a HTTP Anti Virus Proxy|Setting Up a HTTP Anti Virus Proxy]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Home Automation controller with heyu |Setting Up a Home Automation controller with heyu]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a DHCP server with a configuration stored in openLDAP | Setting Up a DHCP server with a configuration stored in openLDAP]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up Ad blocking with dnsmasq |Setting Up Ad blocking with dnsmasq]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up SSH password-less login and Port Knocking |Setting Up SSH password-less login and Port Knocking]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Raspberry PI as a net to serial gateway |Setting Up a Raspberry PI as a net to serial gateway]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Raspberry PI Zero W direct WIFI logon |Raspberry PI Zero W direct WIFI logon]]<br />
#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Unpacking a gpg signed lrp package|Unpacking a gpg signed lrp package]]<br />
<!--#* [[Bering-uClibc 7.x - User Guide - Advanced Topics - Modifying initrd.lrp|Modifying initrd.lrp and initmod.lrp]]--><br />
# [[Bering-uClibc 7.x - User Guide - Upgrade LEAF Bering-uClibc |Upgrade LEAF Bering-uClibc]]<br />
<br />
==Appendices==<br />
# [[Bering-uClibc 7.x - User Guide - Appendices - Upgrading from Bering-uClibc 6.x|Upgrading from Bering-uClibc 6.x]]<br />
# [[Bering-uClibc 7.x - User Guide - Appendices - Overview of the Startup Sequence|Overview of the Startup Sequence]]<br />
# [[Bering-uClibc 7.x - User Guide - Appendices - Hardware-Specific Guides|Hardware-Specific Guides]]<br />
# [[Bering-uClibc 7.x - User Guide - Appendices - Working with Disk Image Files|Working with Disk Image Files]]<br />
# [[Bering-uClibc 7.x - User Guide - Appendices - Troubleshooting/FAQ|Troubleshooting/FAQ]]<br />
<!--# [[Bering-uClibc 7.x - User Guide - Appendices - Hints and Tips for Network Booting|Hints and Tips for Network Booting]]--><br />
<br />
<br />
[[Category:Bering-uClibc_7.x]]<br />
[[Category:User_Guide]]</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4636Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-06T15:56:41Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi, e.g. [https://en.wikipedia.org/wiki/IEEE_802.11 IEEE-802.11] .<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called '''''[https://w1.fi/wpa_supplicant/ wpasupplicant]''''' and is packaged in the '''''wpasupp.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wpasupp.lrp''''' depends on the following packages:<br />
* libssl.lrp <br />
* libcrpto.lrp<br />
<br />
===Configuration===<br />
<br />
The wpasupplicant software is configured using a text file '''''/etc/wpa_supplicant.conf'''''. It is also controlled by the file '''''/etc/default/wpasupp''''' where a few start parameters are defined. The '''''wpasupp.lrp''''' package includes a copy of these two files for your reference.<br />
<br />
====wpa_supplicant.conf====<br />
<br />
The '''''/etc/wpa_supplicant.conf''''' file is used to tell wpasupplicant credentials to use with a certain '''''SSID'''''.<br />
<br />
# Minimal /etc/wpa_supplicant.conf to associate with open<br />
# access points. <br />
<br />
# path to UNIX socket control interface<br />
ctrl_interface=/var/run/wpa_supplicant<br />
<br />
eapol_version=1<br />
ap_scan=1<br />
fast_reauth=1<br />
<br />
### Example of basic WPA-PSK secured AP, uncomment the next 4 lines, add in your own ssid and psk...<br />
#network={<br />
# ssid="yournet"<br />
# psk="yourpassword"<br />
#}<br />
<br />
### Associate with any open access point<br />
### Scans/ESSID changes can be done with wpa_cli<br />
network={<br />
key_mgmt=NONE<br />
}<br />
<br />
Please refer to '''''[https://w1.fi/wpa_supplicant/ wpasupplicant]''''' for the complete description of the configuration parameters.<br />
<br />
====/etc/default/wpasupp====<br />
<br />
This file is used to activate wpasuppplicant and tell it about the interface and the driver used<br />
<br />
# To activate the wpasupplicant daemon, set ENABLED to 1<br />
<br />
ENABLED=1<br />
<br />
# Specify the network interface that the daemon will attach to.<br />
#<br />
# Examples: INTERFACE="eth1"<br />
# INTERFACE="ath0"<br />
#<br />
# Failure to set INTERFACE to a valid network interface name will<br />
# cause the daemon to fail or exit immediately.<br />
<br />
INTERFACE="wlan0"<br />
<br />
# DRIVER specifies the driver type of the interface defined above.<br />
#<br />
# If DRIVER is not set, the daemon will default to the "wext" driver<br />
#<br />
# Currently, the following drivers are supported:<br />
# hostap = Host AP driver (Intersil Prism2/2.5/3)<br />
# madwifi = MADWIFI 802.11 support (Atheros, etc.)<br />
# atmel = ATMEL AT76C5XXx (USB, PCMCIA)<br />
# wext = Linux wireless extensions (generic, ipw2100/2200/3495, linux >= 2.6.14)<br />
# ndiswrapper = Linux ndiswrapper<br />
# ipw = Intel ipw2100/2200 driver (linux kernels 2.6.13 or older only)<br />
# wired = wpa_supplicant wired Ethernet driver<br />
<br />
DRIVER=""<br />
<br />
# uncomment to make wpasupplicant wait for the control client<br />
#WPA_CLIENT_WAIT=-W<br />
<br />
===Firewall settings===<br />
<br />
If you use your wireless connection as your external interface you will have to configure your firewall software accordingly. Your external interface will most probably become '''wlan0'''. Please refer to the [[Bering-uClibc_7.x_-_User_Guide_-_IPv4_Networking_-_Configure_Shorewall|Shorewall configuration page]] for details.</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4635Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T17:41:59Z<p>Etitl: /* Configuration */</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi, e.g. [https://en.wikipedia.org/wiki/IEEE_802.11 IEEE-802.11] .<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called '''''[https://w1.fi/wpa_supplicant/ wpasupplicant]''''' and is packaged in the '''''wpasupp.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wpasupp.lrp''''' depends on the following packages:<br />
* libssl.lrp <br />
* libcrpto.lrp<br />
<br />
===Configuration===<br />
<br />
The wpasupplicant software is configured using a text file '''''/etc/wpa_supplicant.conf'''''. It is also controlled by the file '''''/etc/default/wpasupp''''' where a few start parameters are defined. The '''''wpasupp.lrp''''' package includes a copy of these two files for your reference.<br />
<br />
====wpa_supplicant.conf====<br />
<br />
Please refer to '''''[https://w1.fi/wpa_supplicant/ wpasupplicant]''''' for the complete description of the configuration parameters.<br />
<br />
====/etc/default/wpasupp====<br />
<br />
===Firewall settings===<br />
<br />
If you use your wireless connection as your external interface you will have to configure your firewall software accordingly. Your external interface will most probably become '''wlan0'''. Please refer to the [[Bering-uClibc_7.x_-_User_Guide_-_IPv4_Networking_-_Configure_Shorewall|Shorewall configuration page]] for details.</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4634Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T17:21:14Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi, e.g. [https://en.wikipedia.org/wiki/IEEE_802.11 IEEE-802.11] .<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called '''''[https://w1.fi/wpa_supplicant/ wpasupplicant]''''' and is packaged in the '''''wpasupp.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wpasupp.lrp''''' depends on the following packages:<br />
* libssl.lrp <br />
* libcrpto.lrp<br />
<br />
===Configuration===<br />
<br />
The wpasupplicant software is configured using a text file '''''/etc/wpa_supplicant.conf'''''. It is also controlled by the file '''''/etc/default/wpasupp''''' where a few start parameters are defined. The '''''wpasupp.lrp''''' package includes a copy of these two files for your reference.<br />
<br />
Please refer to '''''[https://w1.fi/wpa_supplicant/ wpasupplicant]''''' for the complete description of the configuration parameters.<br />
<br />
===Firewall settings===<br />
<br />
If you use your wireless connection as your external interface you will have to configure your firewall software accordingly. Your external interface will most probably become '''wlan0'''. Please refer to the [[Bering-uClibc_7.x_-_User_Guide_-_IPv4_Networking_-_Configure_Shorewall|Shorewall configuration page]] for details.</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4633Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T17:20:04Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi, e.g. [https://en.wikipedia.org/wiki/IEEE_802.11 IEEE-802.11] .<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called '''''[https://w1.fi/wpa_supplicant/ wpasupplicant]''''' and is packaged in the '''''wpasupp.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wpasupp.lrp''''' depends on the following packages:<br />
* libssl.lrp <br />
* libcrpto.lrp<br />
<br />
===Configuration===<br />
<br />
The wpasupplicant software is configured using a text file '''''/etc/wpa_supplicant.conf'''''. It is also controlled by the file '''''/etc/default/wpasupp''''' where a few start parameters are defined. The '''''wpasupp.lrp''''' package includes a copy of these two files for your reference.<br />
<br />
Please refer to '''''[https://w1.fi/wpa_supplicant/ wpasupplicant]''''' for the complete description of the configuration parameters.<br />
<br />
===Firewall settings===<br />
<br />
If you use your wireless connection as your external interface you will have to configure your firewalling software accordingly. Your external interface will most probably become '''wlan0'''. Please refer to the [[Bering-uClibc_7.x_-_User_Guide_-_IPv4_Networking_-_Configure_Shorewall|Shorewall configuration page]] for details.</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4632Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T17:19:20Z<p>Etitl: Added link to the shorewall configuration page</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi, e.g. [https://en.wikipedia.org/wiki/IEEE_802.11 IEEE-802.11] .<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called '''''[https://w1.fi/wpa_supplicant/ wpasupplicant]''''' and is packaged in the '''''wpasupp.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wpasupp.lrp''''' depends on the following packages:<br />
* libssl.lrp <br />
* libcrpto.lrp<br />
<br />
===Configuration===<br />
<br />
The wpasupplicant software is configured using a text file '''''/etc/wpa_supplicant.conf'''''. It is also controlled by the file '''''/etc/default/wpasupp''''' where a few start parameters are defined.<br />
<br />
The '''''wpasupp.lrp''''' package includes a copy of these two files for your reference.<br />
<br />
Please refer to '''''[https://w1.fi/wpa_supplicant/ wpasupplicant]''''' for the complete description of the configuration parameters.<br />
<br />
===Firewall settings===<br />
<br />
If you use your wireless connection as your external interface you will have to configure your firewalling software accordingly. Your external interface will most probably become '''wlan0'''. Please refer to the [[Bering-uClibc_7.x_-_User_Guide_-_IPv4_Networking_-_Configure_Shorewall|Shorewall configuration page]] for details.</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4631Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T17:11:43Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi, e.g. [https://en.wikipedia.org/wiki/IEEE_802.11 IEEE-802.11] .<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called '''''[https://w1.fi/wpa_supplicant/ wpasupplicant]''''' and is packaged in the '''''wpasupp.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wpasupp.lrp''''' depends on the following packages:<br />
* libssl.lrp <br />
* libcrpto.lrp<br />
<br />
===Configuration===<br />
<br />
The wpasupplicant software is configured using a text file '''''/etc/wpa_supplicant.conf'''''. It is also controlled by the file '''''/etc/default/wpasupp''''' where a few start parameters are defined.<br />
<br />
The '''''wpasupp.lrp''''' package includes a copy of these two files for your reference.<br />
<br />
Please refer to '''''[https://w1.fi/wpa_supplicant/ wpasupplicant]''''' for the complete description of the configuration parameters.</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4630Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T17:06:55Z<p>Etitl: /* Configuration */</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi, e.g. [https://en.wikipedia.org/wiki/IEEE_802.11 IEEE-802.11] .<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called '''''[https://w1.fi/wpa_supplicant/ wpasupplicant]''''' and is packaged in the '''''wpasupp.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wpasupp.lrp''''' depends on the following packages:<br />
* libssl.lrp <br />
* libcrpto.lrp<br />
<br />
===Configuration===<br />
<br />
The wpasupplicant software is configured using a text file '''''/etc/wpa_supplicant.conf'''''. It is also controlled by the file '''''/etc/default/wpasupp''''' where a few start parameters are defined.</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4629Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T17:02:44Z<p>Etitl: /* Configuration */</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi, e.g. [https://en.wikipedia.org/wiki/IEEE_802.11 IEEE-802.11] .<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called '''''[https://w1.fi/wpa_supplicant/ wpasupplicant]''''' and is packaged in the '''''wpasupp.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wpasupp.lrp''''' depends on the following packages:<br />
* libssl.lrp <br />
* libcrpto.lrp<br />
<br />
===Configuration===<br />
<br />
The wpasupplicant software is configured using a text file '''''wpa_supplicant.conf''''' which is located in '''''/etc'''''.</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4628Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T16:58:02Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi, e.g. [https://en.wikipedia.org/wiki/IEEE_802.11 IEEE-802.11] .<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called '''''[https://w1.fi/wpa_supplicant/ wpasupplicant]''''' and is packaged in the '''''wpasupp.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wpasupp.lrp''''' depends on the following packages:<br />
* libssl.lrp <br />
* libcrpto.lrp<br />
<br />
===Configuration===</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4627Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T16:57:14Z<p>Etitl: Adding dependencies</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi, e.g. [https://en.wikipedia.org/wiki/IEEE_802.11 IEEE-802.11] .<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called '''''[https://w1.fi/wpa_supplicant/ wpasupplicant]''''' and is packaged in the '''''wpasupp.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
====Dependencies====<br />
As of '''LEAF 7.x''' '''''wpasupp.lrp''''' depends on the following packages:<br />
* libssl.lrp <br />
* libcrpto.lrp</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4626Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T16:13:54Z<p>Etitl: Entering a few external links</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi, e.g. [https://en.wikipedia.org/wiki/IEEE_802.11 IEEE-802.11] .<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called '''''[https://w1.fi/wpa_supplicant/ wpasupplicant]''''' and is packaged in the '''''wpasupp.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
As of '''LEAF 7.x''' '''''wpasupp.lrp''''' depends on the following packages:<br />
* libssl.lrp <br />
* libcrpto.lrp</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4625Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T16:12:06Z<p>Etitl: /* Objectives */</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi, e.g. [https://en.wikipedia.org/wiki/IEEE_802.11 IEEE-802.11] .<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called '''''wpasupplicant''''' and is packaged in the '''''wpasupp.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
As of '''LEAF 7.x''' '''''wpasupp.lrp''''' depends on the following packages:<br />
* libssl.lrp <br />
* libcrpto.lrp</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4624Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T16:02:51Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi.<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called '''''wpasupplicant''''' and is packaged in the '''''wpasupp.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You should also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
As of '''LEAF 7.x''' '''''wpasupp.lrp''''' depends on the following packages:<br />
* libssl.lrp <br />
* libcrpto.lrp</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4623Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T16:02:23Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi.<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called '''''wpasupplicant''''' and is packaged in the '''''wpasupp.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. You shuld also be familiar on how to set up LEAF to automatically install packages.<br />
<br />
As of '''LEAF 7.x''' '''''wpasupp.lrp''''' depends on the following packages:<br />
* libssl.lrp <br />
* libcrpto.lrp</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4622Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T15:39:48Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi.<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called '''''wpasupplicant''''' and is packaged in the '''''wpasupp.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection.<br />
<br />
As of '''LEAF 7.x''' '''''wpasupp.lrp''''' depends on the following packages:<br />
* libssl.lrp <br />
* libcrpto.lrp</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4621Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T15:39:06Z<p>Etitl: Added Next link</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Virtual Private Network (VPN)|Next]]<br />
|}<br />
----<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi.<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called '''''wpasupplicant''''' and is packaged in the '''''wpasupp.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection.<br />
<br />
As of '''LEAF 7.x''' '''''wpasupp.lrp''''' depends on the following packages:<br />
* libssl.lrp <br />
* libcrpto.lrp</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4620Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T15:33:26Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Next]]<br />
|}<br />
----<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi.<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called '''''wpasupplicant''''' and is packaged in the '''''wpasupp.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection.<br />
<br />
As of '''LEAF 7.x''' '''''wpasupp.lrp''''' depends on the following packages:<br />
* libssl.lrp <br />
* libcrpto.lrp</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4619Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T15:30:08Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi.<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called '''''wpasupplicant''''' and is packaged in the '''''wpasupp.lrp''''' LEAF package. You should be familiar on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection.<br />
<br />
As of '''LEAF 7.x''' '''''wpasupp.lrp''''' depends on the following packages:<br />
aaaa<br />
<br />
<br />
The dependencies <code class="filename">libssl.lrp</code>, <code class="filename">libcrpto.lrp</code> and <code class="filename">libnl.lrp</code> will be loaded automatically.</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4618Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T15:21:10Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi.<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called wpasupplicant and is packaged in the wpasupp.lrp LEAF package. You should be familiar <br />
on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. <br />
<br />
To build a wireless access point one needs to add the Package <code class="filename">hostapd.lrp</code> to <code class="filename">leaf.cfg</code>.<br />
The dependencies <code class="filename">libssl.lrp</code>, <code class="filename">libcrpto.lrp</code> and <code class="filename">libnl.lrp</code> will be loaded automatically.</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4617Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T15:16:53Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Dynamic DNS Client with ddclient|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Setting Up a Wireless Internet Connection==<br />
<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point using Wifi.<br />
<br />
===Prerequisites===<br />
The software used to hook up to an uplink access point is called wpasupplicant and is packaged in the wpasupp.lrp package. You should be familiar <br />
on how to obtain LEAF packages from either a tarball in the LEAF file area or to download it using your internet connection. <br />
<br />
All LEAF packages can be configured using the CLI interface and you may have seen instructions floating around<br />
the net on how <br />
<br />
===Declare the packages===<br />
To build a wireless access point one needs to add the Package <code class="filename">hostapd.lrp</code> to <code class="filename">leaf.cfg</code>.<br />
The dependencies <code class="filename">libssl.lrp</code>, <code class="filename">libcrpto.lrp</code> and <code class="filename">libnl.lrp</code> will be loaded automatically.</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4616Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T15:08:54Z<p>Etitl: /* Setting Up a Wireless Internet Connection */</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|User Guide - Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Dynamic DNS Client with ddclient|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Next]]<br />
|}<br />
----<br />
{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Access Point|Advanced Topics - Setting Up a Wireless Access Point]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Dynamic DNS Client with ddclient|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Next]]<br />
|}<br />
----<br />
==Setting Up a Wireless Internet Connection==<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point<br />
<br />
All LEAF packages can be configured using the CLI interface and you may have seen instructions floating <br />
<br />
===Declare the packages===<br />
To build a wireless access point one needs to add the Package <code class="filename">hostapd.lrp</code> to <code class="filename">leaf.cfg</code>.<br />
The dependencies <code class="filename">libssl.lrp</code>, <code class="filename">libcrpto.lrp</code> and <code class="filename">libnl.lrp</code> will be loaded automatically.</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4615Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T15:05:36Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|User Guide - Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Dynamic DNS Client with ddclient|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Next]]<br />
|}<br />
----<br />
==Setting Up a Wireless Internet Connection==<br />
===Objectives===<br />
Here we will show you how to hook up your LEAF Box to an uplink access point<br />
<br />
All LEAF packages can be configured using the CLI interface and you may have seen instructions floating <br />
<br />
===Declare the packages===<br />
To build a wireless access point one needs to add the Package <code class="filename">hostapd.lrp</code> to <code class="filename">leaf.cfg</code>.<br />
The dependencies <code class="filename">libssl.lrp</code>, <code class="filename">libcrpto.lrp</code> and <code class="filename">libnl.lrp</code> will be loaded automatically.</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4614Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T15:02:08Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|User Guide - Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Dynamic DNS Client with ddclient|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Next]]<br />
|}<br />
----<br />
==Setting Up a Wireless Internet Connection==<br />
===Objectives===<br />
We assume here that you want to create a wireless access point secured by WPA/WPA2. Instructions for using WEP will not be given.<br />
<br />
For now, this only includes instructions for pci-cards supported by the hostap and kernel drivers (I use an Atheros WLAN NIC, supported by the ath5k driver).<br />
Feedback is welcome about what it takes to make other cards (other chipsets as well as PC-Card and USB models) to work.<br />
<br />
===Declare the packages===<br />
To build a wireless access point one needs to add the Package <code class="filename">hostapd.lrp</code> to <code class="filename">leaf.cfg</code>.<br />
The dependencies <code class="filename">libssl.lrp</code>, <code class="filename">libcrpto.lrp</code> and <code class="filename">libnl.lrp</code> will be loaded automatically.</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_User_Guide_-_Advanced_Topics_-_Setting_Up_a_Wireless_Internet_Connection&diff=4613Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection2021-01-04T14:59:26Z<p>Etitl: Created page with "{| summary="Navigation header" width="100%" ! colspan="3" align="center" | Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|User..."</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|User Guide - Advanced Topics - Setting Up a Wireless Internet Connection]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Dynamic DNS Client with ddclient|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - User Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - User Guide - Advanced Topics - Setting Up a Wireless Internet Connection|Next]]<br />
|}<br />
----</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.0.x_-_Changelog&diff=4596Bering-uClibc 7.0.x - Changelog2020-12-30T21:35:08Z<p>Etitl: Some more ingo to post-7.0.1</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.0.x - Changelog|Changelog]]<br />
|-<br />
| width="20%" align="left" |<br />
! width="60%" align="center" | [[Bering-uClibc 7.x|Bering-uClibc 7.x - Overview]]<br />
| width="20%" align="right" |<br />
|}<br />
----<br />
<br />
==Changes between 7.0.2-rc1 and 7.0.1==<br />
(unreleased)<br />
<br />
;webconf: Moved the content from the various .lwp files to the corresponding packages making the .lwp file building and loading making .lwp files redundant. Also improved webconf and login password handling to allow a user to log into webconf with known credentials (admin:admin). Some minor additions to the webconf pages.<br />
;leafinstall: Added code to support the single partition setup for ARM architecture.<br />
;wpasupplicant: Added code to allow the use of a wpasupplicant.conf file from the PKGPATH at first boot to mimic behaviour of Raspbian.<br />
;upgrade: Adapted the code to handle ARM architecture.<br />
; x86-63 and ARM architecture: Provided a few experimental images for easier system set up.<br />
<br />
==Changes between 7.0.1 and 7.0.1-rc1==<br />
(released 29 Dec 2020)<br />
<br />
;kernel: updated to upstream version 5.4.84<br />
;dnsmasq: move /etc/trust-anchors.conf to a more appropriate location in /etc/dnsmasq.d and change dnsmasq.conf accordingly<br />
<br />
==Changes between 7.0.1-rc1 and 7.0.0==<br />
(released 11 Dec 2020)<br />
<br />
;kernel: updated to upstream version 5.4.81<br />
:fix kernel config for rpi 3 and rpi 4 to boot from mmc<br />
:disable Intel NIC modules that are present with more recent/enhanced sources<br />
;accel-ppp: updated to latest trunk<br />
;e1000e: updated to upstream version 3.8.7<br />
;eoip: fix init script and permissions<br />
;igb: updated to upstream version 5.4.6<br />
;ixgbe: updated to upstream version 5.9.4<br />
;strongswan: updated to upstream version 5.9.1<br />
;tor: updated to upstream version 0.4.4.6<br />
;wireguard-linux-compat: updated to upstream version 1.0.20201112<br />
;wpa_supplicant: add libnl3 as dependency<br />
;xtables-addons: updated to upstream version 3.13<br />
<br />
==Changes between 7.0.0 and 7.0.0-rc2==<br />
(released 09 Nov 2020)<br />
<br />
;kernel: updated to upstream version 5.4.72<br />
:add APU LED driver in x86_64<br />
;general: add fetch_pkg to load/install packages from the package repository<br />
:improve installation LEAF Bering-uClibc from an USB stick<br />
;dropbear: updated to upstream version 2020.81<br />
;expat: updated to upstream version 2.2.10<br />
;freetype: updated to upstream version 2.10.4<br />
;nsd: updated to upstream version 4.3.3<br />
;webconf: Added build of hdsupp.lwp to the lwp buildtool target<br />
: add loading/installing packages through webconf from the web interface<br />
;strace: updated to upstream version 5.9<br />
<br />
==Changes between 7.0.0-rc2 and 7.0.0-rc1==<br />
(released 4 Oct 2020)<br />
<br />
;general: install.sh - changed block device selection algorithm to also show mmcblk devices<br />
:uclibc-ng: updated to upstream version 1.0.35<br />
;kernel: updated to upstream version 5.4.68<br />
;bash: updated to patchlevel 5.0p18<br />
;bind: add libatomic as requirement/depends on for named.lrp<br />
:fix error in /etc/init.d/named <br />
:fix permissions for /var/named <br />
:add localhost.ip6.zone <br />
;clamav: updated to upstream version 0.103.0<br />
;curl: updated to upstream version 7.72.0<br />
;dbus: updated to upstream version 1.12.20<br />
;ddclient: updated to upstream version 3.9.1<br />
;ethtool: updated to upstream version 5.8<br />
;dnsmasq: updated to upstream version 2.82<br />
;freetype: updated to upstream version 2.10.2<br />
;hdsupp: add libreadline (librl.lrp) as requirement <br />
;iperf3: updated to upstream version 3.9<br />
;keepalived: updated to upstream version 2.1.5<br />
:fix dependencies<br />
:fix location of pidfile<br />
;iptables: updated to upstream version 1.8.5<br />
;libcares: updated to upstream version 1.16.1<br />
;libconfuse: updated to upstream version 3.3<br />
;libell: updated to upstream version 0.32 <br />
;libevent: updated to upstream version 2.1.12<br />
;libffi: updated to upstream version 3.3<br />
;libgcrypt: updated to upstream version 1.8.6<br />
;libnetfilter_queue: updated to upstream version 1.0.5<br />
;libnftnl: updated to upstream version 1.1.7<br />
;libyaml: updated to upstream version 0.2.5<br />
;mini_httpd[s]: fix logrotation script for mini_hhtpd<br />
;nsd: updated to upstream version 4.3.2<br />
;openldap: updated to upstream version 2.4.53<br />
;openssh: updated to upstream version 8.4p1<br />
;oprofile: updated to upstream version 1.4.0 <br />
;pmacctd: updated to upstream version 1.7.5<br />
;python: updated to upstream version 3.8.5<br />
;rpi-firmware: update to latest upstream version (incl. support for kernel 5.4.65)<br />
;rsync: updated to upstream version 3.2.2<br />
;rsyslog: updated to upstream version 8.2008.0<br />
;sqlite: updated to upstream version 3.33.0<br />
;squid: updated to upstream version 4.13<br />
;strace: updated to upstream version 5.8<br />
;strongswan: updated to upstream version 5.9.0<br />
;sysstat: updated to upstream version 12.2.3<br />
;tor: updated to upstream version 0.4.4.5<br />
;unbound: updated to upstream release version 1.11.0<br />
;util-linux: updated to upstream version 2.36<br />
;wireguard: updated to upstream version wireguard-linux-compat-1.0.20200908 <br />
;wireguard-tools: updated to upstream version 1.0.20200827<br />
;xtables-addons: updated to upstream version 3.9<br />
<br />
;New Packages:<br />
;keyutils: Tools used to control the key management system built into the Linux kernel<br />
;libdata-validate-ip-perl: collecting ip validation routines to make input validation, and untainting easier and more readable<br />
;libnet-netmask-perl: Net::Netmask parses and understands IPv4 and IPv6 CIDR blocks<br />
<br />
==Changes between 7.0.0-rc1 and 7.0.0-beta2==<br />
(released 27 Jun 2020)<br />
<br />
;kernel: updated to upstream version 5.4.47<br />
:wireless-regdb updated to upstream version 2020.04.29<br />
;axel: updated to upstream version 2.17.9<br />
;busybox: updated to upstream version 1.32.0 <br />
;curl: updated to upstream version 7.70.0<br />
;dbus: updated to upstream version 1.12.18<br />
;igb: updated to upstream version 5.3.5.61<br />
;keepalived: updated to upstream version 2.1.2<br />
;libarchive: updated to upstream version 3.4.3<br />
;nano: updated to upstream version 4.9.3 <br />
;ncurses: updated to upstream version 6.2<br />
;nettle: updated to upstream version 3.6 <br />
;openssh: updated to upstream version 8.3p1<br />
;openvpn: updated to upstream version 2.4.9<br />
;pciutils: updated to upstream version 3.7.0<br />
; perl: updated to upstream version 5.32.0<br />
;rng-tools: updated to upstream version 6.10<br />
:add depedencies for installation<br />
;tor: updated to upstream version 0.4.3.5<br />
;sqlite: updated to upstream version 3.32.1<br />
;squid: updated to upstream version 4.12<br />
;sysfsutils: package libsysfs and sysfsutil<br />
<br />
==Changes between 7.0.0-beta2 and 7.0.0-beta1==<br />
(released 26 May 2020)<br />
<br />
;general: uclibc-ng: updated to upstream version 1.0.34<br />
:binutils updated to upstream version 2.34<br />
;kernel: updated to upstream version 5.4.42<br />
;avahi: updated to upstream version 0.8<br />
;axel: updated to upstream version 2.17.8<br />
;bash: updated to patchlevel 5.0p17<br />
;clamav: updated to upstream version 0.102.3<br />
;conntrack-tools: updated to upstream version 1.4.6<br />
;etc: fix /etc/logrotate.d/syslog to work with rsyslogd<br />
:add logrotate for ppp.log<br />
;e2fsprogs: updated to upstream version 1.45.6<br />
;e3: updated to upstream version 2.82<br />
;ethtool: update to upstream verson 5.6<br />
;igmpproxy: add latest fixes from github<br />
;ipset: updated to upstream version 7.6<br />
:fix rules restore<br />
;iptables: updated to upstream version 1.8.4<br />
;krb5: updated to upstream version 1.18.1<br />
;libnetfilter_conntrack: updated to upstream version 1.0.8<br />
;libnftnl: updated to upstream version 1.1.6<br />
;libtirpc: updated to upstream version 1.2.6<br />
;libusb-compat: updated to upstream version 0.1.7<br />
;monit: fix syslog monitoring<br />
;nano: updated to upstream version 4.9.2<br />
;nsd: updated to upstream version 4.3.1<br />
;ntp: fix logrotation script for rsyslogd<br />
;openldap: updated to upstream version 2.4.50<br />
;oprofile: updated to upstream verson 1.3.0<br />
;perl: updated to upstream version 5.30.2<br />
;pmacctd: updated to upstream version 1.7.4p1<br />
;ppp: fix logrotation script for rsyslogd<br />
;python: updated to upstream version 3.8.2<br />
;tor: updated to upstream version 0.4.2.7<br />
;rsyslog: updated to upstream version 8.2002.0<br />
:log all ppp daemons (ppp/pptp/l2tp/etc) to ppp.log<br />
;ser2net: updated to upstream version 4.1.8<br />
;strongswan: updated to upstream version 5.8.4<br />
;squid: updated to upstream version 4.11<br />
;unbound: updated to upstream version 1.10.1<br />
;util-linux: updated to upstream version 2.35.2<br />
;webconf: change syslog-ng to rsyslog<br />
;wireguard: updated to upstream version wireguard-linux- compat 1.0.20200506<br />
:updated wireguard-tools to upstream version 1.0.20200513<br />
<br />
;New Package:<br />
;libmspack: A portable library for some loosely related Microsoft compression formats<br />
<br />
==Changes between 7.0.0-beta1 and 7.0.0-alpha1==<br />
(released 18 Mar 2020)<br />
<br />
;general: gcc: updated to 8.4.0<br />
;kernel: updated to upstream version 4.19.109<br />
;arptables: updated to upstream version 0.0.5<br />
;axel: updated to upstream version 2.17.7<br />
;bash: updated to patchlevel 5.0p16<br />
;bind: updated to upstream version 9.14.10 <br />
;dhcpcd: updated to upstream version 8.1.5<br />
;e2fsprogs: updated to upstream version 1.45.5<br />
;ethtool: updated to upstream version 5.4<br />
;fail2ban: updated to upstream version 0.11.1<br />
;freeradius: updated to upstream version 3.0.20<br />
;ipset: updated to upstream version 7.5<br />
;libell: updated to upstream version 0.27<br />
;libgmp: updated to upstream version 6.2.0<br />
;libgpgerror: updated to upstream version 1.37<br />
;libmicrohttpd: updated to upstream version 0.9.70<br />
;openssh: updated to upstream version 8.2p1<br />
;pciutils: updated to upstream version 3.6.3 <br />
;pmacctd: updated to upstream version 1.7.4<br />
;ppp: updated to upstream version 2.4.8<br />
;rng-tools: updated to upstream version 6.9<br />
;rsyslog: updated to upstream version 8.1910.0<br />
;ser2net: updated to upstream version 4.1.6<br />
;sqlite: updated to upstream version 3.31.0<br />
;strongswan: load modules when starting ipsec<br />
;tor: updated to upstream version 0.4.2.6<br />
;unbound: updated to upstream version 1.10.0<br />
;util-linux: updated to upstream version 2.35.1<br />
;vim: updated to upstream version 8.2<br />
;xtables-addons: updated to upstream version 3.7<br />
;zabbix: updated to upstream version 4.0.16<br />
<br />
;New Packages: <br />
;gensio: General Stream I/O<br />
;libpcre2: PCRE2 package contains a new generation of the Perl Compatible Regular Expression libraries<br />
;libnet-cidr-lite-perl: Perl extension for merging IPv4 or IPv6 CIDR addresses<br />
;libtext-csv-xs-perl: Perl extension with comma-separated values manipulation routines<br />
<br />
==Changes between 7.0.0-alpha1 and 6.2.x==<br />
(released 4 Jan 2020)<br />
<br />
;general: uClibc-ng: updated to upstream version 1.0.32<br />
:gcc: updated to 8.3.0<br />
:binutils: updated to upstream version 2.32<br />
:replace syslog-ng with rsyslog<br />
;kernel: updated to LTS version 4.19.88<br />
:add support for Raspberry Pi 4<br />
:remove support for Raspberry Pi 1 (python packages fails to compile with gcc 8.3.0)<br />
;bird: updated to upstream version 2.0.7<br />
;dhcpcd: updated to upstream version 8.0.6<br />
;havp: updated to upstream version 0.93<br />
;iptables: updated to upstream version to 1.8.3<br />
;krb5: updated to upstream version 1.17<br />
;libaio: updated to upstream version 0.3.111<br />
;libedit: updated to upstream version 20191025-3.1<br />
;liggpgerror: updated to upstream version 1.36<br />
;libgssglue: updated to upstream version 0.4<br />
;libxslt: updated to upstream version 1.1.34<br />
;lua: updated to upstream version 5.3.4<br />
;mgetty: updated to upstream version 1.1.37<br />
;rng-tools: updated to upstream version 6.8<br />
;rpi-firmware: update firmware for kernel 4.19 and add firmware files for rpi4<br />
;usbmodeswitch: updated to upstream version 2.6.0<br />
;usbmodeswitchdata: updated to upstream version 20191128<br />
;xtables-addon: updated to upstream version 3.5<br />
<br />
;New Packages: <br />
;jimctl: Jim is an opensource small-footprint implementation of the Tcl<br />
;libfastjson: a fast json library for C<br />
;libnftnl: a userspace library providing a low-level netlink programming interface (API) to the in-kernel nf_tables subsystem<br />
;rsyslog: a powerful and flexible syslog implementation <br />
---- <br />
{| summary="Navigation footer" width="100%"<br />
| width="40%" align="left" |<br />
| width="20%" align="center" | [[Bering-uClibc 7.x|Up]]<br />
| width="40%" align="right" |<br />
|}<br />
[[Category:Bering-uClibc_7.x]]</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.0.x_-_Changelog&diff=4595Bering-uClibc 7.0.x - Changelog2020-12-30T21:20:37Z<p>Etitl: some more 7.0.1 -> comments</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.0.x - Changelog|Changelog]]<br />
|-<br />
| width="20%" align="left" |<br />
! width="60%" align="center" | [[Bering-uClibc 7.x|Bering-uClibc 7.x - Overview]]<br />
| width="20%" align="right" |<br />
|}<br />
----<br />
<br />
==Changes between 7.0.2-rc1 and 7.0.1==<br />
(unreleased)<br />
<br />
;webconf: moved the content from the various .lwp files to the corresponding packages making the .lwp file building and loading redundant.<br />
;leafinstall: added code to support the single partition setup for ARM architecture.<br />
;wpasupplicant: added code to allow the use of a pasupplicant.conf file from the PKGPATH to mimic behaviour of raspbian.<br />
;upgrade: adapted the code to handle ARM architecture.<br />
<br />
==Changes between 7.0.1 and 7.0.1-rc1==<br />
(released 29 Dec 2020)<br />
<br />
;kernel: updated to upstream version 5.4.84<br />
;dnsmasq: move /etc/trust-anchors.conf to a more appropriate location in /etc/dnsmasq.d and change dnsmasq.conf accordingly<br />
<br />
==Changes between 7.0.1-rc1 and 7.0.0==<br />
(released 11 Dec 2020)<br />
<br />
;kernel: updated to upstream version 5.4.81<br />
:fix kernel config for rpi 3 and rpi 4 to boot from mmc<br />
:disable Intel NIC modules that are present with more recent/enhanced sources<br />
;accel-ppp: updated to latest trunk<br />
;e1000e: updated to upstream version 3.8.7<br />
;eoip: fix init script and permissions<br />
;igb: updated to upstream version 5.4.6<br />
;ixgbe: updated to upstream version 5.9.4<br />
;strongswan: updated to upstream version 5.9.1<br />
;tor: updated to upstream version 0.4.4.6<br />
;wireguard-linux-compat: updated to upstream version 1.0.20201112<br />
;wpa_supplicant: add libnl3 as dependency<br />
;xtables-addons: updated to upstream version 3.13<br />
<br />
==Changes between 7.0.0 and 7.0.0-rc2==<br />
(released 09 Nov 2020)<br />
<br />
;kernel: updated to upstream version 5.4.72<br />
:add APU LED driver in x86_64<br />
;general: add fetch_pkg to load/install packages from the package repository<br />
:improve installation LEAF Bering-uClibc from an USB stick<br />
;dropbear: updated to upstream version 2020.81<br />
;expat: updated to upstream version 2.2.10<br />
;freetype: updated to upstream version 2.10.4<br />
;nsd: updated to upstream version 4.3.3<br />
;webconf: Added build of hdsupp.lwp to the lwp buildtool target<br />
: add loading/installing packages through webconf from the web interface<br />
;strace: updated to upstream version 5.9<br />
<br />
==Changes between 7.0.0-rc2 and 7.0.0-rc1==<br />
(released 4 Oct 2020)<br />
<br />
;general: install.sh - changed block device selection algorithm to also show mmcblk devices<br />
:uclibc-ng: updated to upstream version 1.0.35<br />
;kernel: updated to upstream version 5.4.68<br />
;bash: updated to patchlevel 5.0p18<br />
;bind: add libatomic as requirement/depends on for named.lrp<br />
:fix error in /etc/init.d/named <br />
:fix permissions for /var/named <br />
:add localhost.ip6.zone <br />
;clamav: updated to upstream version 0.103.0<br />
;curl: updated to upstream version 7.72.0<br />
;dbus: updated to upstream version 1.12.20<br />
;ddclient: updated to upstream version 3.9.1<br />
;ethtool: updated to upstream version 5.8<br />
;dnsmasq: updated to upstream version 2.82<br />
;freetype: updated to upstream version 2.10.2<br />
;hdsupp: add libreadline (librl.lrp) as requirement <br />
;iperf3: updated to upstream version 3.9<br />
;keepalived: updated to upstream version 2.1.5<br />
:fix dependencies<br />
:fix location of pidfile<br />
;iptables: updated to upstream version 1.8.5<br />
;libcares: updated to upstream version 1.16.1<br />
;libconfuse: updated to upstream version 3.3<br />
;libell: updated to upstream version 0.32 <br />
;libevent: updated to upstream version 2.1.12<br />
;libffi: updated to upstream version 3.3<br />
;libgcrypt: updated to upstream version 1.8.6<br />
;libnetfilter_queue: updated to upstream version 1.0.5<br />
;libnftnl: updated to upstream version 1.1.7<br />
;libyaml: updated to upstream version 0.2.5<br />
;mini_httpd[s]: fix logrotation script for mini_hhtpd<br />
;nsd: updated to upstream version 4.3.2<br />
;openldap: updated to upstream version 2.4.53<br />
;openssh: updated to upstream version 8.4p1<br />
;oprofile: updated to upstream version 1.4.0 <br />
;pmacctd: updated to upstream version 1.7.5<br />
;python: updated to upstream version 3.8.5<br />
;rpi-firmware: update to latest upstream version (incl. support for kernel 5.4.65)<br />
;rsync: updated to upstream version 3.2.2<br />
;rsyslog: updated to upstream version 8.2008.0<br />
;sqlite: updated to upstream version 3.33.0<br />
;squid: updated to upstream version 4.13<br />
;strace: updated to upstream version 5.8<br />
;strongswan: updated to upstream version 5.9.0<br />
;sysstat: updated to upstream version 12.2.3<br />
;tor: updated to upstream version 0.4.4.5<br />
;unbound: updated to upstream release version 1.11.0<br />
;util-linux: updated to upstream version 2.36<br />
;wireguard: updated to upstream version wireguard-linux-compat-1.0.20200908 <br />
;wireguard-tools: updated to upstream version 1.0.20200827<br />
;xtables-addons: updated to upstream version 3.9<br />
<br />
;New Packages:<br />
;keyutils: Tools used to control the key management system built into the Linux kernel<br />
;libdata-validate-ip-perl: collecting ip validation routines to make input validation, and untainting easier and more readable<br />
;libnet-netmask-perl: Net::Netmask parses and understands IPv4 and IPv6 CIDR blocks<br />
<br />
==Changes between 7.0.0-rc1 and 7.0.0-beta2==<br />
(released 27 Jun 2020)<br />
<br />
;kernel: updated to upstream version 5.4.47<br />
:wireless-regdb updated to upstream version 2020.04.29<br />
;axel: updated to upstream version 2.17.9<br />
;busybox: updated to upstream version 1.32.0 <br />
;curl: updated to upstream version 7.70.0<br />
;dbus: updated to upstream version 1.12.18<br />
;igb: updated to upstream version 5.3.5.61<br />
;keepalived: updated to upstream version 2.1.2<br />
;libarchive: updated to upstream version 3.4.3<br />
;nano: updated to upstream version 4.9.3 <br />
;ncurses: updated to upstream version 6.2<br />
;nettle: updated to upstream version 3.6 <br />
;openssh: updated to upstream version 8.3p1<br />
;openvpn: updated to upstream version 2.4.9<br />
;pciutils: updated to upstream version 3.7.0<br />
; perl: updated to upstream version 5.32.0<br />
;rng-tools: updated to upstream version 6.10<br />
:add depedencies for installation<br />
;tor: updated to upstream version 0.4.3.5<br />
;sqlite: updated to upstream version 3.32.1<br />
;squid: updated to upstream version 4.12<br />
;sysfsutils: package libsysfs and sysfsutil<br />
<br />
==Changes between 7.0.0-beta2 and 7.0.0-beta1==<br />
(released 26 May 2020)<br />
<br />
;general: uclibc-ng: updated to upstream version 1.0.34<br />
:binutils updated to upstream version 2.34<br />
;kernel: updated to upstream version 5.4.42<br />
;avahi: updated to upstream version 0.8<br />
;axel: updated to upstream version 2.17.8<br />
;bash: updated to patchlevel 5.0p17<br />
;clamav: updated to upstream version 0.102.3<br />
;conntrack-tools: updated to upstream version 1.4.6<br />
;etc: fix /etc/logrotate.d/syslog to work with rsyslogd<br />
:add logrotate for ppp.log<br />
;e2fsprogs: updated to upstream version 1.45.6<br />
;e3: updated to upstream version 2.82<br />
;ethtool: update to upstream verson 5.6<br />
;igmpproxy: add latest fixes from github<br />
;ipset: updated to upstream version 7.6<br />
:fix rules restore<br />
;iptables: updated to upstream version 1.8.4<br />
;krb5: updated to upstream version 1.18.1<br />
;libnetfilter_conntrack: updated to upstream version 1.0.8<br />
;libnftnl: updated to upstream version 1.1.6<br />
;libtirpc: updated to upstream version 1.2.6<br />
;libusb-compat: updated to upstream version 0.1.7<br />
;monit: fix syslog monitoring<br />
;nano: updated to upstream version 4.9.2<br />
;nsd: updated to upstream version 4.3.1<br />
;ntp: fix logrotation script for rsyslogd<br />
;openldap: updated to upstream version 2.4.50<br />
;oprofile: updated to upstream verson 1.3.0<br />
;perl: updated to upstream version 5.30.2<br />
;pmacctd: updated to upstream version 1.7.4p1<br />
;ppp: fix logrotation script for rsyslogd<br />
;python: updated to upstream version 3.8.2<br />
;tor: updated to upstream version 0.4.2.7<br />
;rsyslog: updated to upstream version 8.2002.0<br />
:log all ppp daemons (ppp/pptp/l2tp/etc) to ppp.log<br />
;ser2net: updated to upstream version 4.1.8<br />
;strongswan: updated to upstream version 5.8.4<br />
;squid: updated to upstream version 4.11<br />
;unbound: updated to upstream version 1.10.1<br />
;util-linux: updated to upstream version 2.35.2<br />
;webconf: change syslog-ng to rsyslog<br />
;wireguard: updated to upstream version wireguard-linux- compat 1.0.20200506<br />
:updated wireguard-tools to upstream version 1.0.20200513<br />
<br />
;New Package:<br />
;libmspack: A portable library for some loosely related Microsoft compression formats<br />
<br />
==Changes between 7.0.0-beta1 and 7.0.0-alpha1==<br />
(released 18 Mar 2020)<br />
<br />
;general: gcc: updated to 8.4.0<br />
;kernel: updated to upstream version 4.19.109<br />
;arptables: updated to upstream version 0.0.5<br />
;axel: updated to upstream version 2.17.7<br />
;bash: updated to patchlevel 5.0p16<br />
;bind: updated to upstream version 9.14.10 <br />
;dhcpcd: updated to upstream version 8.1.5<br />
;e2fsprogs: updated to upstream version 1.45.5<br />
;ethtool: updated to upstream version 5.4<br />
;fail2ban: updated to upstream version 0.11.1<br />
;freeradius: updated to upstream version 3.0.20<br />
;ipset: updated to upstream version 7.5<br />
;libell: updated to upstream version 0.27<br />
;libgmp: updated to upstream version 6.2.0<br />
;libgpgerror: updated to upstream version 1.37<br />
;libmicrohttpd: updated to upstream version 0.9.70<br />
;openssh: updated to upstream version 8.2p1<br />
;pciutils: updated to upstream version 3.6.3 <br />
;pmacctd: updated to upstream version 1.7.4<br />
;ppp: updated to upstream version 2.4.8<br />
;rng-tools: updated to upstream version 6.9<br />
;rsyslog: updated to upstream version 8.1910.0<br />
;ser2net: updated to upstream version 4.1.6<br />
;sqlite: updated to upstream version 3.31.0<br />
;strongswan: load modules when starting ipsec<br />
;tor: updated to upstream version 0.4.2.6<br />
;unbound: updated to upstream version 1.10.0<br />
;util-linux: updated to upstream version 2.35.1<br />
;vim: updated to upstream version 8.2<br />
;xtables-addons: updated to upstream version 3.7<br />
;zabbix: updated to upstream version 4.0.16<br />
<br />
;New Packages: <br />
;gensio: General Stream I/O<br />
;libpcre2: PCRE2 package contains a new generation of the Perl Compatible Regular Expression libraries<br />
;libnet-cidr-lite-perl: Perl extension for merging IPv4 or IPv6 CIDR addresses<br />
;libtext-csv-xs-perl: Perl extension with comma-separated values manipulation routines<br />
<br />
==Changes between 7.0.0-alpha1 and 6.2.x==<br />
(released 4 Jan 2020)<br />
<br />
;general: uClibc-ng: updated to upstream version 1.0.32<br />
:gcc: updated to 8.3.0<br />
:binutils: updated to upstream version 2.32<br />
:replace syslog-ng with rsyslog<br />
;kernel: updated to LTS version 4.19.88<br />
:add support for Raspberry Pi 4<br />
:remove support for Raspberry Pi 1 (python packages fails to compile with gcc 8.3.0)<br />
;bird: updated to upstream version 2.0.7<br />
;dhcpcd: updated to upstream version 8.0.6<br />
;havp: updated to upstream version 0.93<br />
;iptables: updated to upstream version to 1.8.3<br />
;krb5: updated to upstream version 1.17<br />
;libaio: updated to upstream version 0.3.111<br />
;libedit: updated to upstream version 20191025-3.1<br />
;liggpgerror: updated to upstream version 1.36<br />
;libgssglue: updated to upstream version 0.4<br />
;libxslt: updated to upstream version 1.1.34<br />
;lua: updated to upstream version 5.3.4<br />
;mgetty: updated to upstream version 1.1.37<br />
;rng-tools: updated to upstream version 6.8<br />
;rpi-firmware: update firmware for kernel 4.19 and add firmware files for rpi4<br />
;usbmodeswitch: updated to upstream version 2.6.0<br />
;usbmodeswitchdata: updated to upstream version 20191128<br />
;xtables-addon: updated to upstream version 3.5<br />
<br />
;New Packages: <br />
;jimctl: Jim is an opensource small-footprint implementation of the Tcl<br />
;libfastjson: a fast json library for C<br />
;libnftnl: a userspace library providing a low-level netlink programming interface (API) to the in-kernel nf_tables subsystem<br />
;rsyslog: a powerful and flexible syslog implementation <br />
---- <br />
{| summary="Navigation footer" width="100%"<br />
| width="40%" align="left" |<br />
| width="20%" align="center" | [[Bering-uClibc 7.x|Up]]<br />
| width="40%" align="right" |<br />
|}<br />
[[Category:Bering-uClibc_7.x]]</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.0.x_-_Changelog&diff=4594Bering-uClibc 7.0.x - Changelog2020-12-30T21:15:37Z<p>Etitl: adding info for 7.0.1-> 7.0.2</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.0.x - Changelog|Changelog]]<br />
|-<br />
| width="20%" align="left" |<br />
! width="60%" align="center" | [[Bering-uClibc 7.x|Bering-uClibc 7.x - Overview]]<br />
| width="20%" align="right" |<br />
|}<br />
----<br />
<br />
==Changes between 7.0.2-rc1 and 7.0.1==<br />
(unreleased)<br />
<br />
;webconf: moved the content from the various .lwp files to the corresponding packages making the .lwp file building and loading redundant.<br />
<br />
==Changes between 7.0.1 and 7.0.1-rc1==<br />
(released 29 Dec 2020)<br />
<br />
;kernel: updated to upstream version 5.4.84<br />
;dnsmasq: move /etc/trust-anchors.conf to a more appropriate location in /etc/dnsmasq.d and change dnsmasq.conf accordingly<br />
<br />
==Changes between 7.0.1-rc1 and 7.0.0==<br />
(released 11 Dec 2020)<br />
<br />
;kernel: updated to upstream version 5.4.81<br />
:fix kernel config for rpi 3 and rpi 4 to boot from mmc<br />
:disable Intel NIC modules that are present with more recent/enhanced sources<br />
;accel-ppp: updated to latest trunk<br />
;e1000e: updated to upstream version 3.8.7<br />
;eoip: fix init script and permissions<br />
;igb: updated to upstream version 5.4.6<br />
;ixgbe: updated to upstream version 5.9.4<br />
;strongswan: updated to upstream version 5.9.1<br />
;tor: updated to upstream version 0.4.4.6<br />
;wireguard-linux-compat: updated to upstream version 1.0.20201112<br />
;wpa_supplicant: add libnl3 as dependency<br />
;xtables-addons: updated to upstream version 3.13<br />
<br />
==Changes between 7.0.0 and 7.0.0-rc2==<br />
(released 09 Nov 2020)<br />
<br />
;kernel: updated to upstream version 5.4.72<br />
:add APU LED driver in x86_64<br />
;general: add fetch_pkg to load/install packages from the package repository<br />
:improve installation LEAF Bering-uClibc from an USB stick<br />
;dropbear: updated to upstream version 2020.81<br />
;expat: updated to upstream version 2.2.10<br />
;freetype: updated to upstream version 2.10.4<br />
;nsd: updated to upstream version 4.3.3<br />
;webconf: Added build of hdsupp.lwp to the lwp buildtool target<br />
: add loading/installing packages through webconf from the web interface<br />
;strace: updated to upstream version 5.9<br />
<br />
==Changes between 7.0.0-rc2 and 7.0.0-rc1==<br />
(released 4 Oct 2020)<br />
<br />
;general: install.sh - changed block device selection algorithm to also show mmcblk devices<br />
:uclibc-ng: updated to upstream version 1.0.35<br />
;kernel: updated to upstream version 5.4.68<br />
;bash: updated to patchlevel 5.0p18<br />
;bind: add libatomic as requirement/depends on for named.lrp<br />
:fix error in /etc/init.d/named <br />
:fix permissions for /var/named <br />
:add localhost.ip6.zone <br />
;clamav: updated to upstream version 0.103.0<br />
;curl: updated to upstream version 7.72.0<br />
;dbus: updated to upstream version 1.12.20<br />
;ddclient: updated to upstream version 3.9.1<br />
;ethtool: updated to upstream version 5.8<br />
;dnsmasq: updated to upstream version 2.82<br />
;freetype: updated to upstream version 2.10.2<br />
;hdsupp: add libreadline (librl.lrp) as requirement <br />
;iperf3: updated to upstream version 3.9<br />
;keepalived: updated to upstream version 2.1.5<br />
:fix dependencies<br />
:fix location of pidfile<br />
;iptables: updated to upstream version 1.8.5<br />
;libcares: updated to upstream version 1.16.1<br />
;libconfuse: updated to upstream version 3.3<br />
;libell: updated to upstream version 0.32 <br />
;libevent: updated to upstream version 2.1.12<br />
;libffi: updated to upstream version 3.3<br />
;libgcrypt: updated to upstream version 1.8.6<br />
;libnetfilter_queue: updated to upstream version 1.0.5<br />
;libnftnl: updated to upstream version 1.1.7<br />
;libyaml: updated to upstream version 0.2.5<br />
;mini_httpd[s]: fix logrotation script for mini_hhtpd<br />
;nsd: updated to upstream version 4.3.2<br />
;openldap: updated to upstream version 2.4.53<br />
;openssh: updated to upstream version 8.4p1<br />
;oprofile: updated to upstream version 1.4.0 <br />
;pmacctd: updated to upstream version 1.7.5<br />
;python: updated to upstream version 3.8.5<br />
;rpi-firmware: update to latest upstream version (incl. support for kernel 5.4.65)<br />
;rsync: updated to upstream version 3.2.2<br />
;rsyslog: updated to upstream version 8.2008.0<br />
;sqlite: updated to upstream version 3.33.0<br />
;squid: updated to upstream version 4.13<br />
;strace: updated to upstream version 5.8<br />
;strongswan: updated to upstream version 5.9.0<br />
;sysstat: updated to upstream version 12.2.3<br />
;tor: updated to upstream version 0.4.4.5<br />
;unbound: updated to upstream release version 1.11.0<br />
;util-linux: updated to upstream version 2.36<br />
;wireguard: updated to upstream version wireguard-linux-compat-1.0.20200908 <br />
;wireguard-tools: updated to upstream version 1.0.20200827<br />
;xtables-addons: updated to upstream version 3.9<br />
<br />
;New Packages:<br />
;keyutils: Tools used to control the key management system built into the Linux kernel<br />
;libdata-validate-ip-perl: collecting ip validation routines to make input validation, and untainting easier and more readable<br />
;libnet-netmask-perl: Net::Netmask parses and understands IPv4 and IPv6 CIDR blocks<br />
<br />
==Changes between 7.0.0-rc1 and 7.0.0-beta2==<br />
(released 27 Jun 2020)<br />
<br />
;kernel: updated to upstream version 5.4.47<br />
:wireless-regdb updated to upstream version 2020.04.29<br />
;axel: updated to upstream version 2.17.9<br />
;busybox: updated to upstream version 1.32.0 <br />
;curl: updated to upstream version 7.70.0<br />
;dbus: updated to upstream version 1.12.18<br />
;igb: updated to upstream version 5.3.5.61<br />
;keepalived: updated to upstream version 2.1.2<br />
;libarchive: updated to upstream version 3.4.3<br />
;nano: updated to upstream version 4.9.3 <br />
;ncurses: updated to upstream version 6.2<br />
;nettle: updated to upstream version 3.6 <br />
;openssh: updated to upstream version 8.3p1<br />
;openvpn: updated to upstream version 2.4.9<br />
;pciutils: updated to upstream version 3.7.0<br />
; perl: updated to upstream version 5.32.0<br />
;rng-tools: updated to upstream version 6.10<br />
:add depedencies for installation<br />
;tor: updated to upstream version 0.4.3.5<br />
;sqlite: updated to upstream version 3.32.1<br />
;squid: updated to upstream version 4.12<br />
;sysfsutils: package libsysfs and sysfsutil<br />
<br />
==Changes between 7.0.0-beta2 and 7.0.0-beta1==<br />
(released 26 May 2020)<br />
<br />
;general: uclibc-ng: updated to upstream version 1.0.34<br />
:binutils updated to upstream version 2.34<br />
;kernel: updated to upstream version 5.4.42<br />
;avahi: updated to upstream version 0.8<br />
;axel: updated to upstream version 2.17.8<br />
;bash: updated to patchlevel 5.0p17<br />
;clamav: updated to upstream version 0.102.3<br />
;conntrack-tools: updated to upstream version 1.4.6<br />
;etc: fix /etc/logrotate.d/syslog to work with rsyslogd<br />
:add logrotate for ppp.log<br />
;e2fsprogs: updated to upstream version 1.45.6<br />
;e3: updated to upstream version 2.82<br />
;ethtool: update to upstream verson 5.6<br />
;igmpproxy: add latest fixes from github<br />
;ipset: updated to upstream version 7.6<br />
:fix rules restore<br />
;iptables: updated to upstream version 1.8.4<br />
;krb5: updated to upstream version 1.18.1<br />
;libnetfilter_conntrack: updated to upstream version 1.0.8<br />
;libnftnl: updated to upstream version 1.1.6<br />
;libtirpc: updated to upstream version 1.2.6<br />
;libusb-compat: updated to upstream version 0.1.7<br />
;monit: fix syslog monitoring<br />
;nano: updated to upstream version 4.9.2<br />
;nsd: updated to upstream version 4.3.1<br />
;ntp: fix logrotation script for rsyslogd<br />
;openldap: updated to upstream version 2.4.50<br />
;oprofile: updated to upstream verson 1.3.0<br />
;perl: updated to upstream version 5.30.2<br />
;pmacctd: updated to upstream version 1.7.4p1<br />
;ppp: fix logrotation script for rsyslogd<br />
;python: updated to upstream version 3.8.2<br />
;tor: updated to upstream version 0.4.2.7<br />
;rsyslog: updated to upstream version 8.2002.0<br />
:log all ppp daemons (ppp/pptp/l2tp/etc) to ppp.log<br />
;ser2net: updated to upstream version 4.1.8<br />
;strongswan: updated to upstream version 5.8.4<br />
;squid: updated to upstream version 4.11<br />
;unbound: updated to upstream version 1.10.1<br />
;util-linux: updated to upstream version 2.35.2<br />
;webconf: change syslog-ng to rsyslog<br />
;wireguard: updated to upstream version wireguard-linux- compat 1.0.20200506<br />
:updated wireguard-tools to upstream version 1.0.20200513<br />
<br />
;New Package:<br />
;libmspack: A portable library for some loosely related Microsoft compression formats<br />
<br />
==Changes between 7.0.0-beta1 and 7.0.0-alpha1==<br />
(released 18 Mar 2020)<br />
<br />
;general: gcc: updated to 8.4.0<br />
;kernel: updated to upstream version 4.19.109<br />
;arptables: updated to upstream version 0.0.5<br />
;axel: updated to upstream version 2.17.7<br />
;bash: updated to patchlevel 5.0p16<br />
;bind: updated to upstream version 9.14.10 <br />
;dhcpcd: updated to upstream version 8.1.5<br />
;e2fsprogs: updated to upstream version 1.45.5<br />
;ethtool: updated to upstream version 5.4<br />
;fail2ban: updated to upstream version 0.11.1<br />
;freeradius: updated to upstream version 3.0.20<br />
;ipset: updated to upstream version 7.5<br />
;libell: updated to upstream version 0.27<br />
;libgmp: updated to upstream version 6.2.0<br />
;libgpgerror: updated to upstream version 1.37<br />
;libmicrohttpd: updated to upstream version 0.9.70<br />
;openssh: updated to upstream version 8.2p1<br />
;pciutils: updated to upstream version 3.6.3 <br />
;pmacctd: updated to upstream version 1.7.4<br />
;ppp: updated to upstream version 2.4.8<br />
;rng-tools: updated to upstream version 6.9<br />
;rsyslog: updated to upstream version 8.1910.0<br />
;ser2net: updated to upstream version 4.1.6<br />
;sqlite: updated to upstream version 3.31.0<br />
;strongswan: load modules when starting ipsec<br />
;tor: updated to upstream version 0.4.2.6<br />
;unbound: updated to upstream version 1.10.0<br />
;util-linux: updated to upstream version 2.35.1<br />
;vim: updated to upstream version 8.2<br />
;xtables-addons: updated to upstream version 3.7<br />
;zabbix: updated to upstream version 4.0.16<br />
<br />
;New Packages: <br />
;gensio: General Stream I/O<br />
;libpcre2: PCRE2 package contains a new generation of the Perl Compatible Regular Expression libraries<br />
;libnet-cidr-lite-perl: Perl extension for merging IPv4 or IPv6 CIDR addresses<br />
;libtext-csv-xs-perl: Perl extension with comma-separated values manipulation routines<br />
<br />
==Changes between 7.0.0-alpha1 and 6.2.x==<br />
(released 4 Jan 2020)<br />
<br />
;general: uClibc-ng: updated to upstream version 1.0.32<br />
:gcc: updated to 8.3.0<br />
:binutils: updated to upstream version 2.32<br />
:replace syslog-ng with rsyslog<br />
;kernel: updated to LTS version 4.19.88<br />
:add support for Raspberry Pi 4<br />
:remove support for Raspberry Pi 1 (python packages fails to compile with gcc 8.3.0)<br />
;bird: updated to upstream version 2.0.7<br />
;dhcpcd: updated to upstream version 8.0.6<br />
;havp: updated to upstream version 0.93<br />
;iptables: updated to upstream version to 1.8.3<br />
;krb5: updated to upstream version 1.17<br />
;libaio: updated to upstream version 0.3.111<br />
;libedit: updated to upstream version 20191025-3.1<br />
;liggpgerror: updated to upstream version 1.36<br />
;libgssglue: updated to upstream version 0.4<br />
;libxslt: updated to upstream version 1.1.34<br />
;lua: updated to upstream version 5.3.4<br />
;mgetty: updated to upstream version 1.1.37<br />
;rng-tools: updated to upstream version 6.8<br />
;rpi-firmware: update firmware for kernel 4.19 and add firmware files for rpi4<br />
;usbmodeswitch: updated to upstream version 2.6.0<br />
;usbmodeswitchdata: updated to upstream version 20191128<br />
;xtables-addon: updated to upstream version 3.5<br />
<br />
;New Packages: <br />
;jimctl: Jim is an opensource small-footprint implementation of the Tcl<br />
;libfastjson: a fast json library for C<br />
;libnftnl: a userspace library providing a low-level netlink programming interface (API) to the in-kernel nf_tables subsystem<br />
;rsyslog: a powerful and flexible syslog implementation <br />
---- <br />
{| summary="Navigation footer" width="100%"<br />
| width="40%" align="left" |<br />
| width="20%" align="center" | [[Bering-uClibc 7.x|Up]]<br />
| width="40%" align="right" |<br />
|}<br />
[[Category:Bering-uClibc_7.x]]</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_Developer_Guide_-_Adding_a_Kernel_Architecture_Variant&diff=4053Bering-uClibc 7.x - Developer Guide - Adding a Kernel Architecture Variant2019-10-06T12:05:24Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - Developer Guide - Adding a Kernel Architecture Variant|Adding a Kernel Architecture Variant]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - Developer Guide - Building an Image|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - Developer Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - Developer Guide - Adding a Hardware Architecture Variant|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Introduction==<br />
[[Bering-uClibc 3.x]] was built for a single "lowest common denominator" platform - a generic i486 CPU.<br />
This offered maximum flexibility but meant that it was not possible to include optimisations for more recent CPU models, which is becoming more of a problem as the i486 gets older and less common.<br />
<br />
For [[Bering-uClibc 4.x]] and later this approach has changed and a small number of different CPU platform variants are supported as standard. Specific kernels and kernel Modules are built for all of the supported variants and distributed via disk Image variants for each platform.<br />
<br />
This page outlines the procedure for adding a new CPU variant to the standard list.<br />
<br />
<br />
==Add the Kernel Architecture Name==<br />
Most of the build tools automatically process each of the entries in the kernel architecture list which is defined in one place.<br />
<br />
In file <code class="filename">make/toolchain/i486-unknown-linux-uclibc.mk</code> edit the definition of variable "<tt>KARCHS</tt>" to add a new name to the space-separated list.<br />
Search for lines like:<br />
# available kernel archs<br />
export KARCHS:=i686 i486 geode<br />
<br />
The new name should be short (ideally 4 characters) and should clearly refer to the new CPU architecture.<br />
<br />
The new name will be referred to as "<tt>''karch''</tt>" in the remainder of this page.<br />
<br />
<br />
===Version 7.x and later===<br />
The previous approach using config diff files and release tagged config files has shown to be tedious and not well corresponding to modern release management tools. Therefore we have reintroduced the old naming convention for the config files which used to be created from the ''basic'' configuration files plus a ''.diff'' file. To easier maintain these Files in ''git'' the kernel release numbers are now omitted from the file names. Thus the config files now follow the convention ''Bering.config-<karch>''.<br />
<br />
'''ToDo: define the process maintaining these files in detail'''<br />
<br />
==Add the <tt>kmodules</tt> Configuration==<br />
Since the kernel Modules vary from one kernel architecture variant to another each variant needs its own <code class="filename">moddb-''karch''.lrp</code> which is generated from the <tt>kmodules</tt> source.<br />
<br />
Edit <code class="filename">repo/kmodules/buildtool.cfg</code> and add a new block of lines for "<tt><moddb-''karch''></tt>".<br />
<br />
<br />
==Add the Image Configuration==<br />
Each kernel architecture variant needs its own disk Image variant(s).<br />
<br />
Create a new directory under <code class="filename">image/</code> and create file <code class="filename">buildimage.cfg</code> within that (best to copy and edit an existing file).<br />
Refer to the [[Bering-uClibc 5.x - Developer Guide - Building an Image|Building an Image]] page for details of the directory naming convention.<br />
<br />
Repeat if multiple types (e.g. ISOLINUX versus SYSLINUX) of image are relevant for this kernel variant, but only create the minimum set likely to be required.<br />
<br />
<br />
==Add the Documentation==<br />
Usually, a new kernel architecture variant will be added because it is required for a specific hardware device which is particularly suitable for running [[Bering-uClibc 5.x]].<br />
<br />
Please therefore add some content to the [[Bering-uClibc 5.x - User Guide - Appendices - Hardware-Specific Guides|Hardware-Specific Guides]] page of this Wiki to detail the hardware device and to specify which Image should be used for it.<br />
<br />
<br />
----<br />
{| summary="Navigation footer" width="100%"<br />
| width="40%" align="left" | [[Bering-uClibc 7.x - Developer Guide - Building an Image|Prev]]<br />
| width="20%" align="center" | [[Bering-uClibc 7.x - Developer Guide|Up]]<br />
| width="40%" align="right" | [[Bering-uClibc 7.x - Developer Guide - Adding a Hardware Architecture Variant|Next]]<br />
|}<br />
<br />
[[Category:Bering-uClibc 7.x]]<br />
[[Category:Developer Guide]]</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_Developer_Guide_-_Adding_a_Kernel_Architecture_Variant&diff=4052Bering-uClibc 7.x - Developer Guide - Adding a Kernel Architecture Variant2019-10-06T12:04:02Z<p>Etitl: /* Add the initrd Configuration */</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 5.x - Developer Guide - Adding a Kernel Architecture Variant|Adding a Kernel Architecture Variant]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 5.x - Developer Guide - Building an Image|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 5.x - Developer Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 5.x - Developer Guide - Adding a Hardware Architecture Variant|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Introduction==<br />
[[Bering-uClibc 3.x]] was built for a single "lowest common denominator" platform - a generic i486 CPU.<br />
This offered maximum flexibility but meant that it was not possible to include optimisations for more recent CPU models, which is becoming more of a problem as the i486 gets older and less common.<br />
<br />
For [[Bering-uClibc 4.x]] and later this approach has changed and a small number of different CPU platform variants are supported as standard. Specific kernels and kernel Modules are built for all of the supported variants and distributed via disk Image variants for each platform.<br />
<br />
This page outlines the procedure for adding a new CPU variant to the standard list.<br />
<br />
<br />
==Add the Kernel Architecture Name==<br />
Most of the build tools automatically process each of the entries in the kernel architecture list which is defined in one place.<br />
<br />
In file <code class="filename">make/toolchain/i486-unknown-linux-uclibc.mk</code> edit the definition of variable "<tt>KARCHS</tt>" to add a new name to the space-separated list.<br />
Search for lines like:<br />
# available kernel archs<br />
export KARCHS:=i686 i486 geode<br />
<br />
The new name should be short (ideally 4 characters) and should clearly refer to the new CPU architecture.<br />
<br />
The new name will be referred to as "<tt>''karch''</tt>" in the remainder of this page.<br />
<br />
<br />
===Version 7.x and later===<br />
The previous approach using config diff files and release tagged config files has shown to be tedious and not well corresponding to modern release management tools. Therefore we have reintroduced the old naming convention for the config files which used to be created from the ''basic'' configuration files plus a ''.diff'' file. To easier maintain these Files in ''git'' the kernel release numbers are now omitted from the file names. Thus the config files now follow the convention ''Bering.config-<karch>''.<br />
<br />
'''ToDo: define the process maintaining these files in detail'''<br />
<br />
==Add the <tt>kmodules</tt> Configuration==<br />
Since the kernel Modules vary from one kernel architecture variant to another each variant needs its own <code class="filename">moddb-''karch''.lrp</code> which is generated from the <tt>kmodules</tt> source.<br />
<br />
Edit <code class="filename">repo/kmodules/buildtool.cfg</code> and add a new block of lines for "<tt><moddb-''karch''></tt>".<br />
<br />
<br />
==Add the Image Configuration==<br />
Each kernel architecture variant needs its own disk Image variant(s).<br />
<br />
Create a new directory under <code class="filename">image/</code> and create file <code class="filename">buildimage.cfg</code> within that (best to copy and edit an existing file).<br />
Refer to the [[Bering-uClibc 5.x - Developer Guide - Building an Image|Building an Image]] page for details of the directory naming convention.<br />
<br />
Repeat if multiple types (e.g. ISOLINUX versus SYSLINUX) of image are relevant for this kernel variant, but only create the minimum set likely to be required.<br />
<br />
<br />
==Add the Documentation==<br />
Usually, a new kernel architecture variant will be added because it is required for a specific hardware device which is particularly suitable for running [[Bering-uClibc 5.x]].<br />
<br />
Please therefore add some content to the [[Bering-uClibc 5.x - User Guide - Appendices - Hardware-Specific Guides|Hardware-Specific Guides]] page of this Wiki to detail the hardware device and to specify which Image should be used for it.<br />
<br />
<br />
----<br />
{| summary="Navigation footer" width="100%"<br />
| width="40%" align="left" | [[Bering-uClibc 5.x - Developer Guide - Building an Image|Prev]]<br />
| width="20%" align="center" | [[Bering-uClibc 5.x - Developer Guide|Up]]<br />
| width="40%" align="right" | [[Bering-uClibc 5.x - Developer Guide - Adding a Hardware Architecture Variant|Next]]<br />
|}<br />
<br />
[[Category:Bering-uClibc 5.x]]<br />
[[Category:Developer Guide]]</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_Developer_Guide_-_Adding_a_Kernel_Architecture_Variant&diff=4051Bering-uClibc 7.x - Developer Guide - Adding a Kernel Architecture Variant2019-10-06T11:57:16Z<p>Etitl: /* Version 7.x and later */</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 5.x - Developer Guide - Adding a Kernel Architecture Variant|Adding a Kernel Architecture Variant]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 5.x - Developer Guide - Building an Image|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 5.x - Developer Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 5.x - Developer Guide - Adding a Hardware Architecture Variant|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Introduction==<br />
[[Bering-uClibc 3.x]] was built for a single "lowest common denominator" platform - a generic i486 CPU.<br />
This offered maximum flexibility but meant that it was not possible to include optimisations for more recent CPU models, which is becoming more of a problem as the i486 gets older and less common.<br />
<br />
For [[Bering-uClibc 4.x]] and later this approach has changed and a small number of different CPU platform variants are supported as standard. Specific kernels and kernel Modules are built for all of the supported variants and distributed via disk Image variants for each platform.<br />
<br />
This page outlines the procedure for adding a new CPU variant to the standard list.<br />
<br />
<br />
==Add the Kernel Architecture Name==<br />
Most of the build tools automatically process each of the entries in the kernel architecture list which is defined in one place.<br />
<br />
In file <code class="filename">make/toolchain/i486-unknown-linux-uclibc.mk</code> edit the definition of variable "<tt>KARCHS</tt>" to add a new name to the space-separated list.<br />
Search for lines like:<br />
# available kernel archs<br />
export KARCHS:=i686 i486 geode<br />
<br />
The new name should be short (ideally 4 characters) and should clearly refer to the new CPU architecture.<br />
<br />
The new name will be referred to as "<tt>''karch''</tt>" in the remainder of this page.<br />
<br />
<br />
===Version 7.x and later===<br />
The previous approach using config diff files and release tagged config files has shown to be tedious and not well corresponding to modern release management tools. Therefore we have reintroduced the old naming convention for the config files which used to be created from the ''basic'' configuration files plus a ''.diff'' file. To easier maintain these Files in ''git'' the kernel release numbers are now omitted from the file names. Thus the config files now follow the convention ''Bering.config-<karch>''.<br />
<br />
'''ToDo: define the process maintaining these files in detail'''<br />
<br />
==Add the <tt>kmodules</tt> Configuration==<br />
Since the kernel Modules vary from one kernel architecture variant to another each variant needs its own <code class="filename">moddb-''karch''.lrp</code> which is generated from the <tt>kmodules</tt> source.<br />
<br />
Edit <code class="filename">repo/kmodules/buildtool.cfg</code> and add a new block of lines for "<tt><moddb-''karch''></tt>".<br />
<br />
<br />
==Add the <tt>initrd</tt> Configuration==<br />
Since the kernel Modules vary from one kernel architecture variant to another each variant needs its own <code class="filename">initrd-''karch''.lrp</code> which is generated from the <tt>initrd</tt> source.<br />
<br />
Edit <code class="filename">repo/initrd/buildtool.cfg</code> and add a new block of lines for "<tt><initrd-''karch''></tt>".<br />
<br />
<br />
==Add the Image Configuration==<br />
Each kernel architecture variant needs its own disk Image variant(s).<br />
<br />
Create a new directory under <code class="filename">image/</code> and create file <code class="filename">buildimage.cfg</code> within that (best to copy and edit an existing file).<br />
Refer to the [[Bering-uClibc 5.x - Developer Guide - Building an Image|Building an Image]] page for details of the directory naming convention.<br />
<br />
Repeat if multiple types (e.g. ISOLINUX versus SYSLINUX) of image are relevant for this kernel variant, but only create the minimum set likely to be required.<br />
<br />
<br />
==Add the Documentation==<br />
Usually, a new kernel architecture variant will be added because it is required for a specific hardware device which is particularly suitable for running [[Bering-uClibc 5.x]].<br />
<br />
Please therefore add some content to the [[Bering-uClibc 5.x - User Guide - Appendices - Hardware-Specific Guides|Hardware-Specific Guides]] page of this Wiki to detail the hardware device and to specify which Image should be used for it.<br />
<br />
<br />
----<br />
{| summary="Navigation footer" width="100%"<br />
| width="40%" align="left" | [[Bering-uClibc 5.x - Developer Guide - Building an Image|Prev]]<br />
| width="20%" align="center" | [[Bering-uClibc 5.x - Developer Guide|Up]]<br />
| width="40%" align="right" | [[Bering-uClibc 5.x - Developer Guide - Adding a Hardware Architecture Variant|Next]]<br />
|}<br />
<br />
[[Category:Bering-uClibc 5.x]]<br />
[[Category:Developer Guide]]</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_Developer_Guide_-_Adding_a_Kernel_Architecture_Variant&diff=4050Bering-uClibc 7.x - Developer Guide - Adding a Kernel Architecture Variant2019-10-06T11:53:12Z<p>Etitl: /* Version 7.x and later */</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 5.x - Developer Guide - Adding a Kernel Architecture Variant|Adding a Kernel Architecture Variant]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 5.x - Developer Guide - Building an Image|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 5.x - Developer Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 5.x - Developer Guide - Adding a Hardware Architecture Variant|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Introduction==<br />
[[Bering-uClibc 3.x]] was built for a single "lowest common denominator" platform - a generic i486 CPU.<br />
This offered maximum flexibility but meant that it was not possible to include optimisations for more recent CPU models, which is becoming more of a problem as the i486 gets older and less common.<br />
<br />
For [[Bering-uClibc 4.x]] and later this approach has changed and a small number of different CPU platform variants are supported as standard. Specific kernels and kernel Modules are built for all of the supported variants and distributed via disk Image variants for each platform.<br />
<br />
This page outlines the procedure for adding a new CPU variant to the standard list.<br />
<br />
<br />
==Add the Kernel Architecture Name==<br />
Most of the build tools automatically process each of the entries in the kernel architecture list which is defined in one place.<br />
<br />
In file <code class="filename">make/toolchain/i486-unknown-linux-uclibc.mk</code> edit the definition of variable "<tt>KARCHS</tt>" to add a new name to the space-separated list.<br />
Search for lines like:<br />
# available kernel archs<br />
export KARCHS:=i686 i486 geode<br />
<br />
The new name should be short (ideally 4 characters) and should clearly refer to the new CPU architecture.<br />
<br />
The new name will be referred to as "<tt>''karch''</tt>" in the remainder of this page.<br />
<br />
<br />
===Version 7.x and later===<br />
The previous approach using config diff files and release tagged config files has shown to be tedious and not well corresponding to modern release management tools. Therefore we have reintroduced the old naming convention for the config files which used to be created from the ''basic'' configuration files plus a ''.diff'' file. To easier maintain these Files in ''git'' the kernel release numbers are now omitted from the file names. Thus the config files now follow the convention ''Bering.config-<karch>''.<br />
<br />
==Add the <tt>kmodules</tt> Configuration==<br />
Since the kernel Modules vary from one kernel architecture variant to another each variant needs its own <code class="filename">moddb-''karch''.lrp</code> which is generated from the <tt>kmodules</tt> source.<br />
<br />
Edit <code class="filename">repo/kmodules/buildtool.cfg</code> and add a new block of lines for "<tt><moddb-''karch''></tt>".<br />
<br />
<br />
==Add the <tt>initrd</tt> Configuration==<br />
Since the kernel Modules vary from one kernel architecture variant to another each variant needs its own <code class="filename">initrd-''karch''.lrp</code> which is generated from the <tt>initrd</tt> source.<br />
<br />
Edit <code class="filename">repo/initrd/buildtool.cfg</code> and add a new block of lines for "<tt><initrd-''karch''></tt>".<br />
<br />
<br />
==Add the Image Configuration==<br />
Each kernel architecture variant needs its own disk Image variant(s).<br />
<br />
Create a new directory under <code class="filename">image/</code> and create file <code class="filename">buildimage.cfg</code> within that (best to copy and edit an existing file).<br />
Refer to the [[Bering-uClibc 5.x - Developer Guide - Building an Image|Building an Image]] page for details of the directory naming convention.<br />
<br />
Repeat if multiple types (e.g. ISOLINUX versus SYSLINUX) of image are relevant for this kernel variant, but only create the minimum set likely to be required.<br />
<br />
<br />
==Add the Documentation==<br />
Usually, a new kernel architecture variant will be added because it is required for a specific hardware device which is particularly suitable for running [[Bering-uClibc 5.x]].<br />
<br />
Please therefore add some content to the [[Bering-uClibc 5.x - User Guide - Appendices - Hardware-Specific Guides|Hardware-Specific Guides]] page of this Wiki to detail the hardware device and to specify which Image should be used for it.<br />
<br />
<br />
----<br />
{| summary="Navigation footer" width="100%"<br />
| width="40%" align="left" | [[Bering-uClibc 5.x - Developer Guide - Building an Image|Prev]]<br />
| width="20%" align="center" | [[Bering-uClibc 5.x - Developer Guide|Up]]<br />
| width="40%" align="right" | [[Bering-uClibc 5.x - Developer Guide - Adding a Hardware Architecture Variant|Next]]<br />
|}<br />
<br />
[[Category:Bering-uClibc 5.x]]<br />
[[Category:Developer Guide]]</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_Developer_Guide_-_Adding_a_Kernel_Architecture_Variant&diff=4049Bering-uClibc 7.x - Developer Guide - Adding a Kernel Architecture Variant2019-10-06T11:51:43Z<p>Etitl: /* Add the Kernel .config Patch File */</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 5.x - Developer Guide - Adding a Kernel Architecture Variant|Adding a Kernel Architecture Variant]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 5.x - Developer Guide - Building an Image|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 5.x - Developer Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 5.x - Developer Guide - Adding a Hardware Architecture Variant|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Introduction==<br />
[[Bering-uClibc 3.x]] was built for a single "lowest common denominator" platform - a generic i486 CPU.<br />
This offered maximum flexibility but meant that it was not possible to include optimisations for more recent CPU models, which is becoming more of a problem as the i486 gets older and less common.<br />
<br />
For [[Bering-uClibc 4.x]] and later this approach has changed and a small number of different CPU platform variants are supported as standard. Specific kernels and kernel Modules are built for all of the supported variants and distributed via disk Image variants for each platform.<br />
<br />
This page outlines the procedure for adding a new CPU variant to the standard list.<br />
<br />
<br />
==Add the Kernel Architecture Name==<br />
Most of the build tools automatically process each of the entries in the kernel architecture list which is defined in one place.<br />
<br />
In file <code class="filename">make/toolchain/i486-unknown-linux-uclibc.mk</code> edit the definition of variable "<tt>KARCHS</tt>" to add a new name to the space-separated list.<br />
Search for lines like:<br />
# available kernel archs<br />
export KARCHS:=i686 i486 geode<br />
<br />
The new name should be short (ideally 4 characters) and should clearly refer to the new CPU architecture.<br />
<br />
The new name will be referred to as "<tt>''karch''</tt>" in the remainder of this page.<br />
<br />
<br />
===Version 7.x and later===<br />
The previous approach using config diff files and release tagged config files has shown to be tedious and not well corresponding to modern release management tools. Therefore we have reintroduced the old naming convention for the config files which used to be created from the ''basic'' configuration files plus a ''.diff'' file. To easier maintain these Files in ''git'' the kernel release numbers are now omitted from the file names. Thus the config files follow the convention ''Bering.config-<KVAR>''.<br />
<br />
==Add the <tt>kmodules</tt> Configuration==<br />
Since the kernel Modules vary from one kernel architecture variant to another each variant needs its own <code class="filename">moddb-''karch''.lrp</code> which is generated from the <tt>kmodules</tt> source.<br />
<br />
Edit <code class="filename">repo/kmodules/buildtool.cfg</code> and add a new block of lines for "<tt><moddb-''karch''></tt>".<br />
<br />
<br />
==Add the <tt>initrd</tt> Configuration==<br />
Since the kernel Modules vary from one kernel architecture variant to another each variant needs its own <code class="filename">initrd-''karch''.lrp</code> which is generated from the <tt>initrd</tt> source.<br />
<br />
Edit <code class="filename">repo/initrd/buildtool.cfg</code> and add a new block of lines for "<tt><initrd-''karch''></tt>".<br />
<br />
<br />
==Add the Image Configuration==<br />
Each kernel architecture variant needs its own disk Image variant(s).<br />
<br />
Create a new directory under <code class="filename">image/</code> and create file <code class="filename">buildimage.cfg</code> within that (best to copy and edit an existing file).<br />
Refer to the [[Bering-uClibc 5.x - Developer Guide - Building an Image|Building an Image]] page for details of the directory naming convention.<br />
<br />
Repeat if multiple types (e.g. ISOLINUX versus SYSLINUX) of image are relevant for this kernel variant, but only create the minimum set likely to be required.<br />
<br />
<br />
==Add the Documentation==<br />
Usually, a new kernel architecture variant will be added because it is required for a specific hardware device which is particularly suitable for running [[Bering-uClibc 5.x]].<br />
<br />
Please therefore add some content to the [[Bering-uClibc 5.x - User Guide - Appendices - Hardware-Specific Guides|Hardware-Specific Guides]] page of this Wiki to detail the hardware device and to specify which Image should be used for it.<br />
<br />
<br />
----<br />
{| summary="Navigation footer" width="100%"<br />
| width="40%" align="left" | [[Bering-uClibc 5.x - Developer Guide - Building an Image|Prev]]<br />
| width="20%" align="center" | [[Bering-uClibc 5.x - Developer Guide|Up]]<br />
| width="40%" align="right" | [[Bering-uClibc 5.x - Developer Guide - Adding a Hardware Architecture Variant|Next]]<br />
|}<br />
<br />
[[Category:Bering-uClibc 5.x]]<br />
[[Category:Developer Guide]]</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_Developer_Guide_-_Adding_a_Kernel_Architecture_Variant&diff=4048Bering-uClibc 7.x - Developer Guide - Adding a Kernel Architecture Variant2019-10-06T11:47:30Z<p>Etitl: /* Version 7.x and later */</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 5.x - Developer Guide - Adding a Kernel Architecture Variant|Adding a Kernel Architecture Variant]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 5.x - Developer Guide - Building an Image|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 5.x - Developer Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 5.x - Developer Guide - Adding a Hardware Architecture Variant|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Introduction==<br />
[[Bering-uClibc 3.x]] was built for a single "lowest common denominator" platform - a generic i486 CPU.<br />
This offered maximum flexibility but meant that it was not possible to include optimisations for more recent CPU models, which is becoming more of a problem as the i486 gets older and less common.<br />
<br />
For [[Bering-uClibc 4.x]] and later this approach has changed and a small number of different CPU platform variants are supported as standard. Specific kernels and kernel Modules are built for all of the supported variants and distributed via disk Image variants for each platform.<br />
<br />
This page outlines the procedure for adding a new CPU variant to the standard list.<br />
<br />
<br />
==Add the Kernel Architecture Name==<br />
Most of the build tools automatically process each of the entries in the kernel architecture list which is defined in one place.<br />
<br />
In file <code class="filename">make/toolchain/i486-unknown-linux-uclibc.mk</code> edit the definition of variable "<tt>KARCHS</tt>" to add a new name to the space-separated list.<br />
Search for lines like:<br />
# available kernel archs<br />
export KARCHS:=i686 i486 geode<br />
<br />
The new name should be short (ideally 4 characters) and should clearly refer to the new CPU architecture.<br />
<br />
The new name will be referred to as "<tt>''karch''</tt>" in the remainder of this page.<br />
<br />
<br />
==Add the Kernel .config Patch File==<br />
Rather than separately maintaining a complete <code class="filename">.config</code> file each kernel variant a "baseline" plus "delta" approach has been adopted.<br />
All of the standard, common settings for [[Bering-uClibc 5.x]] are in the "baseline" file and just the bare minimum of variant-specific changes are in a per-variant "delta" file implemented in the form of a patch.<br />
<br />
===Versions 5.0 and 5.1===<br />
All of these files are stored in directory <code class="filename">repo/linux/</code>:<br />
* The "baseline" file is called <code class="filename">Bering-''kver''.config</code> where "<tt>''kver''</tt>"" is something like "<tt>3.4.50</tt>". For example <code class="filename">Bering-3.4.50.config</code>. The baseline kernel is based on the i686 variant.<br />
* The "delta" file is called <code class="filename">Bering-''kver''.config-''karch''.patch</code>. For example <code class="filename">Bering-3.4.50.config-i486.patch</code>.<br />
As part of the build process, each "delta" patch is applied to the "baseline" file to create file <code class="filename">source/linux/Bering-''kver''.config-''karch''</code> which is then copied to <code class="filename">source/linux/linux-''karch''/.config</code> and used to configure the kernel.<br />
<br />
You need to create the new <code class="filename">Bering-''kver''.config-''karch''</code> file by some means and then create the patch as follows:<br />
diff -c Bering-''kver''.config Bering-''kver''.config-''karch'' > Bering-''kver''.config-''karch''.patch<br />
<br />
The new <code class="filename">.patch</code> file name needs to be added to <code class="filename">repo/linux/buildtool.cfg</code>.<br />
<br />
===Version 5.2 and 6.x===<br />
With Bering-uClibc 5.2 <code class="filename">tools/confdiff.py</code> and <code class="filename">tools/confpatch.py</code> replaced the diff/patch utilities used earlier.<br />
<br />
As before, all of these files are stored in directory <code class="filename">repo/linux/</code>:<br />
* The "baseline" file is called <code class="filename">Bering-''kver''.config</code> where "<tt>''kver''</tt>"" is something like "<tt>4.1.4</tt>". For example <code class="filename">Bering-4.1.4.config</code>. The baseline kernel is based on the i486 variant.<br />
* The "delta" file is called <code class="filename">Bering-''kver''.config-''karch''.patch</code>. For example <code class="filename">Bering-4.1.4.config-i486.patch</code>.<br />
As part of the build process, each "delta" patch is applied to the "baseline" file to create file <code class="filename">source/linux/Bering-''kver''.config-''karch''</code> which is then copied to <code class="filename">source/linux/linux-''karch''/.config</code> and used to configure the kernel.<br />
<br />
You need to create the new <code class="filename">Bering-''kver''.config-''karch''</code> file by some means and then create the patch as follows:<br />
tools/confdiff.py repo/linux/Bering-''kver''.config repo/linux/Bering-''kver''.config-''karch'' > repo/linux/Bering-''kver''.config-''karch''.cdiff<br />
<br />
The new <code class="filename">.cdiff</code> file name needs to be added to <code class="filename">repo/linux/buildtool.cfg</code>.<br />
<br />
===Version 7.x and later===<br />
The previous approach using config diff files and release tagged config files has shown to be tedious and not well corresponding to modern release management systems. Therefore we have reintroduced the old naming convention for the config files which used to be created from the ''basic'' configuration files plus a ''.diff'' file. To easier maintain these Files in ''git'' we the kernel release numbers are now omitted from the file names.<br />
<br />
==Add the <tt>kmodules</tt> Configuration==<br />
Since the kernel Modules vary from one kernel architecture variant to another each variant needs its own <code class="filename">moddb-''karch''.lrp</code> which is generated from the <tt>kmodules</tt> source.<br />
<br />
Edit <code class="filename">repo/kmodules/buildtool.cfg</code> and add a new block of lines for "<tt><moddb-''karch''></tt>".<br />
<br />
<br />
==Add the <tt>initrd</tt> Configuration==<br />
Since the kernel Modules vary from one kernel architecture variant to another each variant needs its own <code class="filename">initrd-''karch''.lrp</code> which is generated from the <tt>initrd</tt> source.<br />
<br />
Edit <code class="filename">repo/initrd/buildtool.cfg</code> and add a new block of lines for "<tt><initrd-''karch''></tt>".<br />
<br />
<br />
==Add the Image Configuration==<br />
Each kernel architecture variant needs its own disk Image variant(s).<br />
<br />
Create a new directory under <code class="filename">image/</code> and create file <code class="filename">buildimage.cfg</code> within that (best to copy and edit an existing file).<br />
Refer to the [[Bering-uClibc 5.x - Developer Guide - Building an Image|Building an Image]] page for details of the directory naming convention.<br />
<br />
Repeat if multiple types (e.g. ISOLINUX versus SYSLINUX) of image are relevant for this kernel variant, but only create the minimum set likely to be required.<br />
<br />
<br />
==Add the Documentation==<br />
Usually, a new kernel architecture variant will be added because it is required for a specific hardware device which is particularly suitable for running [[Bering-uClibc 5.x]].<br />
<br />
Please therefore add some content to the [[Bering-uClibc 5.x - User Guide - Appendices - Hardware-Specific Guides|Hardware-Specific Guides]] page of this Wiki to detail the hardware device and to specify which Image should be used for it.<br />
<br />
<br />
----<br />
{| summary="Navigation footer" width="100%"<br />
| width="40%" align="left" | [[Bering-uClibc 5.x - Developer Guide - Building an Image|Prev]]<br />
| width="20%" align="center" | [[Bering-uClibc 5.x - Developer Guide|Up]]<br />
| width="40%" align="right" | [[Bering-uClibc 5.x - Developer Guide - Adding a Hardware Architecture Variant|Next]]<br />
|}<br />
<br />
[[Category:Bering-uClibc 5.x]]<br />
[[Category:Developer Guide]]</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_Developer_Guide_-_Adding_a_Kernel_Architecture_Variant&diff=4047Bering-uClibc 7.x - Developer Guide - Adding a Kernel Architecture Variant2019-10-06T11:46:00Z<p>Etitl: /* Add the Kernel .config Patch File */</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 5.x - Developer Guide - Adding a Kernel Architecture Variant|Adding a Kernel Architecture Variant]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 5.x - Developer Guide - Building an Image|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 5.x - Developer Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 5.x - Developer Guide - Adding a Hardware Architecture Variant|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Introduction==<br />
[[Bering-uClibc 3.x]] was built for a single "lowest common denominator" platform - a generic i486 CPU.<br />
This offered maximum flexibility but meant that it was not possible to include optimisations for more recent CPU models, which is becoming more of a problem as the i486 gets older and less common.<br />
<br />
For [[Bering-uClibc 4.x]] and later this approach has changed and a small number of different CPU platform variants are supported as standard. Specific kernels and kernel Modules are built for all of the supported variants and distributed via disk Image variants for each platform.<br />
<br />
This page outlines the procedure for adding a new CPU variant to the standard list.<br />
<br />
<br />
==Add the Kernel Architecture Name==<br />
Most of the build tools automatically process each of the entries in the kernel architecture list which is defined in one place.<br />
<br />
In file <code class="filename">make/toolchain/i486-unknown-linux-uclibc.mk</code> edit the definition of variable "<tt>KARCHS</tt>" to add a new name to the space-separated list.<br />
Search for lines like:<br />
# available kernel archs<br />
export KARCHS:=i686 i486 geode<br />
<br />
The new name should be short (ideally 4 characters) and should clearly refer to the new CPU architecture.<br />
<br />
The new name will be referred to as "<tt>''karch''</tt>" in the remainder of this page.<br />
<br />
<br />
==Add the Kernel .config Patch File==<br />
Rather than separately maintaining a complete <code class="filename">.config</code> file each kernel variant a "baseline" plus "delta" approach has been adopted.<br />
All of the standard, common settings for [[Bering-uClibc 5.x]] are in the "baseline" file and just the bare minimum of variant-specific changes are in a per-variant "delta" file implemented in the form of a patch.<br />
<br />
===Versions 5.0 and 5.1===<br />
All of these files are stored in directory <code class="filename">repo/linux/</code>:<br />
* The "baseline" file is called <code class="filename">Bering-''kver''.config</code> where "<tt>''kver''</tt>"" is something like "<tt>3.4.50</tt>". For example <code class="filename">Bering-3.4.50.config</code>. The baseline kernel is based on the i686 variant.<br />
* The "delta" file is called <code class="filename">Bering-''kver''.config-''karch''.patch</code>. For example <code class="filename">Bering-3.4.50.config-i486.patch</code>.<br />
As part of the build process, each "delta" patch is applied to the "baseline" file to create file <code class="filename">source/linux/Bering-''kver''.config-''karch''</code> which is then copied to <code class="filename">source/linux/linux-''karch''/.config</code> and used to configure the kernel.<br />
<br />
You need to create the new <code class="filename">Bering-''kver''.config-''karch''</code> file by some means and then create the patch as follows:<br />
diff -c Bering-''kver''.config Bering-''kver''.config-''karch'' > Bering-''kver''.config-''karch''.patch<br />
<br />
The new <code class="filename">.patch</code> file name needs to be added to <code class="filename">repo/linux/buildtool.cfg</code>.<br />
<br />
===Version 5.2 and 6.x===<br />
With Bering-uClibc 5.2 <code class="filename">tools/confdiff.py</code> and <code class="filename">tools/confpatch.py</code> replaced the diff/patch utilities used earlier.<br />
<br />
As before, all of these files are stored in directory <code class="filename">repo/linux/</code>:<br />
* The "baseline" file is called <code class="filename">Bering-''kver''.config</code> where "<tt>''kver''</tt>"" is something like "<tt>4.1.4</tt>". For example <code class="filename">Bering-4.1.4.config</code>. The baseline kernel is based on the i486 variant.<br />
* The "delta" file is called <code class="filename">Bering-''kver''.config-''karch''.patch</code>. For example <code class="filename">Bering-4.1.4.config-i486.patch</code>.<br />
As part of the build process, each "delta" patch is applied to the "baseline" file to create file <code class="filename">source/linux/Bering-''kver''.config-''karch''</code> which is then copied to <code class="filename">source/linux/linux-''karch''/.config</code> and used to configure the kernel.<br />
<br />
You need to create the new <code class="filename">Bering-''kver''.config-''karch''</code> file by some means and then create the patch as follows:<br />
tools/confdiff.py repo/linux/Bering-''kver''.config repo/linux/Bering-''kver''.config-''karch'' > repo/linux/Bering-''kver''.config-''karch''.cdiff<br />
<br />
The new <code class="filename">.cdiff</code> file name needs to be added to <code class="filename">repo/linux/buildtool.cfg</code>.<br />
<br />
===Version 7.x and later===<br />
The previous aproach using config diff files and release tagged config files has shown to be tedious and not well corresponding to modern release management systems. Therefore we have reintroduced the old naming convention for the config files which used to be created from the ''basic'' configuration files plus a ''.diff'' file. To easier maintain these Files in ''git'' we the kernel release numbers are now omitted from the file names.<br />
<br />
==Add the <tt>kmodules</tt> Configuration==<br />
Since the kernel Modules vary from one kernel architecture variant to another each variant needs its own <code class="filename">moddb-''karch''.lrp</code> which is generated from the <tt>kmodules</tt> source.<br />
<br />
Edit <code class="filename">repo/kmodules/buildtool.cfg</code> and add a new block of lines for "<tt><moddb-''karch''></tt>".<br />
<br />
<br />
==Add the <tt>initrd</tt> Configuration==<br />
Since the kernel Modules vary from one kernel architecture variant to another each variant needs its own <code class="filename">initrd-''karch''.lrp</code> which is generated from the <tt>initrd</tt> source.<br />
<br />
Edit <code class="filename">repo/initrd/buildtool.cfg</code> and add a new block of lines for "<tt><initrd-''karch''></tt>".<br />
<br />
<br />
==Add the Image Configuration==<br />
Each kernel architecture variant needs its own disk Image variant(s).<br />
<br />
Create a new directory under <code class="filename">image/</code> and create file <code class="filename">buildimage.cfg</code> within that (best to copy and edit an existing file).<br />
Refer to the [[Bering-uClibc 5.x - Developer Guide - Building an Image|Building an Image]] page for details of the directory naming convention.<br />
<br />
Repeat if multiple types (e.g. ISOLINUX versus SYSLINUX) of image are relevant for this kernel variant, but only create the minimum set likely to be required.<br />
<br />
<br />
==Add the Documentation==<br />
Usually, a new kernel architecture variant will be added because it is required for a specific hardware device which is particularly suitable for running [[Bering-uClibc 5.x]].<br />
<br />
Please therefore add some content to the [[Bering-uClibc 5.x - User Guide - Appendices - Hardware-Specific Guides|Hardware-Specific Guides]] page of this Wiki to detail the hardware device and to specify which Image should be used for it.<br />
<br />
<br />
----<br />
{| summary="Navigation footer" width="100%"<br />
| width="40%" align="left" | [[Bering-uClibc 5.x - Developer Guide - Building an Image|Prev]]<br />
| width="20%" align="center" | [[Bering-uClibc 5.x - Developer Guide|Up]]<br />
| width="40%" align="right" | [[Bering-uClibc 5.x - Developer Guide - Adding a Hardware Architecture Variant|Next]]<br />
|}<br />
<br />
[[Category:Bering-uClibc 5.x]]<br />
[[Category:Developer Guide]]</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_Developer_Guide_-_Adding_a_Kernel_Architecture_Variant&diff=4046Bering-uClibc 7.x - Developer Guide - Adding a Kernel Architecture Variant2019-10-06T11:35:56Z<p>Etitl: Created page with "{| summary="Navigation header" width="100%" ! colspan="3" align="center" | Bering-uClibc 5.x - Developer Guide - Adding a Kernel Architecture Variant|Adding a Kernel Archite..."</p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 5.x - Developer Guide - Adding a Kernel Architecture Variant|Adding a Kernel Architecture Variant]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 5.x - Developer Guide - Building an Image|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 5.x - Developer Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 5.x - Developer Guide - Adding a Hardware Architecture Variant|Next]]<br />
|}<br />
----<br />
<br />
<br />
==Introduction==<br />
[[Bering-uClibc 3.x]] was built for a single "lowest common denominator" platform - a generic i486 CPU.<br />
This offered maximum flexibility but meant that it was not possible to include optimisations for more recent CPU models, which is becoming more of a problem as the i486 gets older and less common.<br />
<br />
For [[Bering-uClibc 4.x]] and later this approach has changed and a small number of different CPU platform variants are supported as standard. Specific kernels and kernel Modules are built for all of the supported variants and distributed via disk Image variants for each platform.<br />
<br />
This page outlines the procedure for adding a new CPU variant to the standard list.<br />
<br />
<br />
==Add the Kernel Architecture Name==<br />
Most of the build tools automatically process each of the entries in the kernel architecture list which is defined in one place.<br />
<br />
In file <code class="filename">make/toolchain/i486-unknown-linux-uclibc.mk</code> edit the definition of variable "<tt>KARCHS</tt>" to add a new name to the space-separated list.<br />
Search for lines like:<br />
# available kernel archs<br />
export KARCHS:=i686 i486 geode<br />
<br />
The new name should be short (ideally 4 characters) and should clearly refer to the new CPU architecture.<br />
<br />
The new name will be referred to as "<tt>''karch''</tt>" in the remainder of this page.<br />
<br />
<br />
==Add the Kernel .config Patch File==<br />
Rather than separately maintaining a complete <code class="filename">.config</code> file each kernel variant a "baseline" plus "delta" approach has been adopted.<br />
All of the standard, common settings for [[Bering-uClibc 5.x]] are in the "baseline" file and just the bare minimum of variant-specific changes are in a per-variant "delta" file implemented in the form of a patch.<br />
<br />
===Versions 5.0 and 5.1===<br />
All of these files are stored in directory <code class="filename">repo/linux/</code>:<br />
* The "baseline" file is called <code class="filename">Bering-''kver''.config</code> where "<tt>''kver''</tt>"" is something like "<tt>3.4.50</tt>". For example <code class="filename">Bering-3.4.50.config</code>. The baseline kernel is based on the i686 variant.<br />
* The "delta" file is called <code class="filename">Bering-''kver''.config-''karch''.patch</code>. For example <code class="filename">Bering-3.4.50.config-i486.patch</code>.<br />
As part of the build process, each "delta" patch is applied to the "baseline" file to create file <code class="filename">source/linux/Bering-''kver''.config-''karch''</code> which is then copied to <code class="filename">source/linux/linux-''karch''/.config</code> and used to configure the kernel.<br />
<br />
You need to create the new <code class="filename">Bering-''kver''.config-''karch''</code> file by some means and then create the patch as follows:<br />
diff -c Bering-''kver''.config Bering-''kver''.config-''karch'' > Bering-''kver''.config-''karch''.patch<br />
<br />
The new <code class="filename">.patch</code> file name needs to be added to <code class="filename">repo/linux/buildtool.cfg</code>.<br />
<br />
===Version 5.2 and later===<br />
With Bering-uClibc 5.2 <code class="filename">tools/confdiff.py</code> and <code class="filename">tools/confpatch.py</code> replaced the <br />
diff/patch utilities used earlier.<br />
<br />
As before, all of these files are stored in directory <code class="filename">repo/linux/</code>:<br />
* The "baseline" file is called <code class="filename">Bering-''kver''.config</code> where "<tt>''kver''</tt>"" is something like "<tt>4.1.4</tt>". For example <code class="filename">Bering-4.1.4.config</code>. The baseline kernel is based on the i486 variant.<br />
* The "delta" file is called <code class="filename">Bering-''kver''.config-''karch''.patch</code>. For example <code class="filename">Bering-4.1.4.config-i486.patch</code>.<br />
As part of the build process, each "delta" patch is applied to the "baseline" file to create file <code class="filename">source/linux/Bering-''kver''.config-''karch''</code> which is then copied to <code class="filename">source/linux/linux-''karch''/.config</code> and used to configure the kernel.<br />
<br />
You need to create the new <code class="filename">Bering-''kver''.config-''karch''</code> file by some means and then create the patch as follows:<br />
tools/confdiff.py repo/linux/Bering-''kver''.config repo/linux/Bering-''kver''.config-''karch'' > repo/linux/Bering-''kver''.config-''karch''.cdiff<br />
<br />
The new <code class="filename">.cdiff</code> file name needs to be added to <code class="filename">repo/linux/buildtool.cfg</code>.<br />
<br />
==Add the <tt>kmodules</tt> Configuration==<br />
Since the kernel Modules vary from one kernel architecture variant to another each variant needs its own <code class="filename">moddb-''karch''.lrp</code> which is generated from the <tt>kmodules</tt> source.<br />
<br />
Edit <code class="filename">repo/kmodules/buildtool.cfg</code> and add a new block of lines for "<tt><moddb-''karch''></tt>".<br />
<br />
<br />
==Add the <tt>initrd</tt> Configuration==<br />
Since the kernel Modules vary from one kernel architecture variant to another each variant needs its own <code class="filename">initrd-''karch''.lrp</code> which is generated from the <tt>initrd</tt> source.<br />
<br />
Edit <code class="filename">repo/initrd/buildtool.cfg</code> and add a new block of lines for "<tt><initrd-''karch''></tt>".<br />
<br />
<br />
==Add the Image Configuration==<br />
Each kernel architecture variant needs its own disk Image variant(s).<br />
<br />
Create a new directory under <code class="filename">image/</code> and create file <code class="filename">buildimage.cfg</code> within that (best to copy and edit an existing file).<br />
Refer to the [[Bering-uClibc 5.x - Developer Guide - Building an Image|Building an Image]] page for details of the directory naming convention.<br />
<br />
Repeat if multiple types (e.g. ISOLINUX versus SYSLINUX) of image are relevant for this kernel variant, but only create the minimum set likely to be required.<br />
<br />
<br />
==Add the Documentation==<br />
Usually, a new kernel architecture variant will be added because it is required for a specific hardware device which is particularly suitable for running [[Bering-uClibc 5.x]].<br />
<br />
Please therefore add some content to the [[Bering-uClibc 5.x - User Guide - Appendices - Hardware-Specific Guides|Hardware-Specific Guides]] page of this Wiki to detail the hardware device and to specify which Image should be used for it.<br />
<br />
<br />
----<br />
{| summary="Navigation footer" width="100%"<br />
| width="40%" align="left" | [[Bering-uClibc 5.x - Developer Guide - Building an Image|Prev]]<br />
| width="20%" align="center" | [[Bering-uClibc 5.x - Developer Guide|Up]]<br />
| width="40%" align="right" | [[Bering-uClibc 5.x - Developer Guide - Adding a Hardware Architecture Variant|Next]]<br />
|}<br />
<br />
[[Category:Bering-uClibc 5.x]]<br />
[[Category:Developer Guide]]</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_Developer_Guide_-_Providing_kernel_headers&diff=4034Bering-uClibc 7.x - Developer Guide - Providing kernel headers2019-10-02T18:59:42Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - Developer Guide - Providing kernel headers|Providing kernel headers]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - Developer Guide - Adding a Hardware Architecture Variant|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - Developer Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - Developer Guide - Policies and Guidelines|Next]]<br />
|}<br />
----<br />
Building the kernel headers tarball is different from building all other Packages.<br />
<br />
The kernel headers are a requirement to build the toolchain. <br />
The command<br />
<br />
<code class="filename">./buildtool.pl headers linux</code><br />
<br />
builds those headers in the directory <code class="filename">headers</code> in the buildtool root directory and creates a link in <code class="filename">repo/toolchain/linux-headers</code>.<br />
<br />
As we are moving away from the tarball code containers to a true git environment creating these tarballs has become obsolete. <br />
<br />
'''Please note, that toolchains can support different kernel versions, which may be useful especially in transitions to newer versions, where not all toolchains will be supported immediately. It is advised to keep the kernel headers for the oldest kernel a toolchain uses.'''<br />
----<br />
{| summary="Navigation footer" width="100%"<br />
| width="40%" align="left" | [[Bering-uClibc 7.x - Developer Guide - Adding a Kernel Architecture Variant|Prev]]<br />
| width="20%" align="center" | [[Bering-uClibc 7.x - Developer Guide|Up]]<br />
| width="40%" align="right" | [[Bering-uClibc 7.x - Developer Guide - Policies and Guidelines|Next]]<br />
|}<br />
<br />
[[Category:Bering-uClibc 7.x]]<br />
[[Category:Developer Guide]]</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_Developer_Guide_-_Providing_kernel_headers&diff=4033Bering-uClibc 7.x - Developer Guide - Providing kernel headers2019-10-02T18:51:00Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - Developer Guide - Providing kernel headers|Providing kernel headers]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - Developer Guide - Adding a Hardware Architecture Variant|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - Developer Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - Developer Guide - Policies and Guidelines|Next]]<br />
|}<br />
----<br />
Building the kernel headers tarball is different from building all other Packages.<br />
<br />
The kernel headers are a requirement to build the toolchain. <br />
The command<br />
<br />
<code class="filename">./buildtool.pl headers linux</code><br />
<br />
builds those headers in the directory <code class="filename">headers</code> in the buildtool root directory and creates a link in <code class="filename">repo/toolchain/linux-headers</code>.<br />
<br />
As we are moving away from the tarball code containers to a true git environment creating these tarballs has become obsolete. <br />
<br />
Please note, that toolchains can support different kernel versions, which may be useful especially in transitions to a newer versions, where not all toolchains will be supported immediately. It is advised to keep the kernel headers for the oldest kernel a toolchain uses. <br />
----<br />
{| summary="Navigation footer" width="100%"<br />
| width="40%" align="left" | [[Bering-uClibc 7.x - Developer Guide - Adding a Kernel Architecture Variant|Prev]]<br />
| width="20%" align="center" | [[Bering-uClibc 7.x - Developer Guide|Up]]<br />
| width="40%" align="right" | [[Bering-uClibc 7.x - Developer Guide - Policies and Guidelines|Next]]<br />
|}<br />
<br />
[[Category:Bering-uClibc 7.x]]<br />
[[Category:Developer Guide]]</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_Developer_Guide_-_Providing_kernel_headers&diff=4032Bering-uClibc 7.x - Developer Guide - Providing kernel headers2019-10-02T18:49:10Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - Developer Guide - Providing kernel headers|Providing kernel headers]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - Developer Guide - Adding a Hardware Architecture Variant|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - Developer Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - Developer Guide - Policies and Guidelines|Next]]<br />
|}<br />
----<br />
Building the kernel headers tarball is different from building all other Packages.<br />
<br />
The kernel headers are a requirement to build the toolchain. <br />
The command<br />
<code class="filename">./buildtool.pl headers linux</code><br />
builds those headers in the directory <code class="filename">headers</code> in the buildtool root directory and creates a link in <code class="filename">repo/tolchain/linux-headers</code>.<br />
<br />
As we are moving away from the tarball code containers to a true git environment creating these tarballs has become obsolete. <br />
<br />
Please note, that toolchains can support different kernel versions, which may be useful especially in transitions to a newer versions, where not all toolchains will be supported immediately. It is advised to keep the kernel headers for the oldest kernel a toolchain uses. <br />
----<br />
{| summary="Navigation footer" width="100%"<br />
| width="40%" align="left" | [[Bering-uClibc 7.x - Developer Guide - Adding a Kernel Architecture Variant|Prev]]<br />
| width="20%" align="center" | [[Bering-uClibc 7.x - Developer Guide|Up]]<br />
| width="40%" align="right" | [[Bering-uClibc 7.x - Developer Guide - Policies and Guidelines|Next]]<br />
|}<br />
<br />
[[Category:Bering-uClibc 7.x]]<br />
[[Category:Developer Guide]]</div>Etitlhttp://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_7.x_-_Developer_Guide_-_Providing_kernel_headers&diff=4029Bering-uClibc 7.x - Developer Guide - Providing kernel headers2019-10-02T16:59:39Z<p>Etitl: </p>
<hr />
<div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 7.x - Developer Guide - Providing kernel headers|Providing kernel headers]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 7.x - Developer Guide - Adding a Hardware Architecture Variant|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 7.x - Developer Guide]]<br />
| width="20%" align="right" | [[Bering-uClibc 7.x - Developer Guide - Policies and Guidelines|Next]]<br />
|}<br />
----<br />
Building the kernel headers tarball is different from building all other Packages.<br />
<br />
The kernel headers are needed to build the toolchain and can be found in <code class="filename">repo/toolchain</code>.<br />
To create the tarball run in your buidtool root:<br />
<br />
./buildtool.pl headers linux <br />
cd headers/include<br />
tar cvfJ ../../repo/toolchain/linux-headers.tar.xz *<br />
<br />
Please note, that toolchains can support different kernel versions, which may be useful especially in transitions to a newer versions, where not all toolchains will be supported immediately. It is advised to keep the kernel headers for the oldest kernel a toolchain uses. <br />
----<br />
{| summary="Navigation footer" width="100%"<br />
| width="40%" align="left" | [[Bering-uClibc 7.x - Developer Guide - Adding a Kernel Architecture Variant|Prev]]<br />
| width="20%" align="center" | [[Bering-uClibc 7.x - Developer Guide|Up]]<br />
| width="40%" align="right" | [[Bering-uClibc 7.x - Developer Guide - Policies and Guidelines|Next]]<br />
|}<br />
<br />
[[Category:Bering-uClibc 7.x]]<br />
[[Category:Developer Guide]]</div>Etitl