Difference between revisions of "Bering-uClibc 4.x - User Guide - IPv4 Networking"
From bering-uClibc
Davidmbrooke (Talk | contribs) (Created skeleton) |
Davidmbrooke (Talk | contribs) (Added link to new Traffic Management page) |
||
| (8 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
| − | ===Sub-Chapters=== | + | ===IPv4 Networking Overview=== |
| − | * [[Bering-uClibc 4.x - User Guide - | + | A default installation of [[Bering-uClibc 4.x]] has IPv4 networking enabled and configured as follows: |
| − | * [[Bering-uClibc 4.x - User Guide - | + | * External Ethernet interface <tt>eth0</tt> with an IPv4 address obtained using DHCP. |
| − | * [[Bering-uClibc 4.x - User Guide - | + | * Internal Ethernet interface <tt>eth1</tt> with static IPv4 address 192.168.1.254. |
| − | * [[Bering-uClibc 4.x - User Guide - | + | * Linux kernel <tt>iptables</tt> firewall code loaded. |
| + | * Shorewall utility installed, for managing the <tt>iptables</tt> configuration. | ||
| + | * Dnsmasq utility installed, providing DNS forwarding and a DHCP server. | ||
| + | * Dropbear utility installed, providing an SSH server. | ||
| + | * A small HTTP server installed, providing a web-based administration interface. | ||
| + | More information on configuring some of these features can be found in the Sub-Chapters. | ||
| + | |||
| + | Note that [[Bering-uClibc 4.x]] network configuration is almost identical to other Debian-based systems, so standard Debian documentation like http://wiki.debian.org/NetworkConfiguration might be useful. | ||
| + | |||
| + | |||
| + | ===IPv4 Networking Sub-Chapters=== | ||
| + | * [[Bering-uClibc 4.x - User Guide - IPv4 Networking - External Network Connections |External Network Connections]] | ||
| + | * [[Bering-uClibc 4.x - User Guide - IPv4 Networking - Internal Network Connections|Internal Network Connections]] | ||
| + | * [[Bering-uClibc 4.x - User Guide - IPv4 Networking - Configure Shorewall|Configure Shorewall]] | ||
| + | * [[Bering-uClibc 4.x - User Guide - IPv4 Networking - Configure Traffic Management|Configure Traffic Management]] | ||
| + | * [[Bering-uClibc 4.x - User Guide - IPv4 Networking - Configure Dnsmasq|Configure Dnsmasq]] | ||
| + | * [[Bering-uClibc 4.x - User Guide - IPv4 Networking - Configure 802.1Q VLANs|Configure 802.1Q VLANs]] | ||
| + | |||
| + | |||
| + | ===IPv6 Notes for IPv4 Users=== | ||
| + | By default, [[Bering-uClibc 4.x]] has some limited IPv6 features enabled. Specifically: | ||
| + | * The <code class="filename">ipv6.ko</code> kernel Module is loaded automatically. | ||
| + | ** This means that every network interface will be given a "link local" IPv6 address (except for the loopback interface, <tt>lo</tt>, which is given a "host local" IPv6 address). | ||
| + | ** In addition, if an IPv6 router is configured on an interface (such as <tt>eth0</tt>) then that will be used to assign a "global" IPv6 address to the interface. | ||
| + | * The <code class="filename">ip6tables.lrp</code> Package is installed, and Shorewall uses this to specify that IPv6 traffic should be DROPped. | ||
| + | ** This is because <tt>DISABLE_IPv6=Yes</tt> is specified in <code class="filename">/etc/shorewall/shorewall.conf</code> | ||
| + | |||
| + | In order to completely disable IPv6 it is necessary to prevent the <code class="filename">ipv6.ko</code> kernel Module from being loaded. | ||
| + | If required, the recommended way of doing that is to add the following line to <code class="filename">/etc/modules.conf</code>: | ||
| + | blacklist ipv6 | ||
| + | |||
| + | Further information on configuring IPv6 can be found in [[Bering-uClibc 4.x - User Guide - IPv6 Networking|the Next Chapter]]. | ||
Latest revision as of 15:26, 4 June 2011
| IPv4 Networking | ||
|---|---|---|
| Prev | Bering-uClibc 4.x - User Guide | Next |
IPv4 Networking Overview
A default installation of Bering-uClibc 4.x has IPv4 networking enabled and configured as follows:
- External Ethernet interface eth0 with an IPv4 address obtained using DHCP.
- Internal Ethernet interface eth1 with static IPv4 address 192.168.1.254.
- Linux kernel iptables firewall code loaded.
- Shorewall utility installed, for managing the iptables configuration.
- Dnsmasq utility installed, providing DNS forwarding and a DHCP server.
- Dropbear utility installed, providing an SSH server.
- A small HTTP server installed, providing a web-based administration interface.
More information on configuring some of these features can be found in the Sub-Chapters.
Note that Bering-uClibc 4.x network configuration is almost identical to other Debian-based systems, so standard Debian documentation like http://wiki.debian.org/NetworkConfiguration might be useful.
IPv4 Networking Sub-Chapters
- External Network Connections
- Internal Network Connections
- Configure Shorewall
- Configure Traffic Management
- Configure Dnsmasq
- Configure 802.1Q VLANs
IPv6 Notes for IPv4 Users
By default, Bering-uClibc 4.x has some limited IPv6 features enabled. Specifically:
- The
ipv6.kokernel Module is loaded automatically.- This means that every network interface will be given a "link local" IPv6 address (except for the loopback interface, lo, which is given a "host local" IPv6 address).
- In addition, if an IPv6 router is configured on an interface (such as eth0) then that will be used to assign a "global" IPv6 address to the interface.
- The
ip6tables.lrpPackage is installed, and Shorewall uses this to specify that IPv6 traffic should be DROPped.- This is because DISABLE_IPv6=Yes is specified in
/etc/shorewall/shorewall.conf
- This is because DISABLE_IPv6=Yes is specified in
In order to completely disable IPv6 it is necessary to prevent the ipv6.ko kernel Module from being loaded.
If required, the recommended way of doing that is to add the following line to /etc/modules.conf:
blacklist ipv6
Further information on configuring IPv6 can be found in the Next Chapter.
| Prev | Up | Next |
