Changes

Jump to: navigation, search

Multiple network interfaces and ARP flux

340 bytes added, 22:19, 16 February 2007
no edit summary
== Overview ==This page discusses how to setup a HN with multiple network interfaces on the same physical network and on the same IP network. Then how to setup multiple VE's to use only one of these interfaces.
For example:, you want some of your VE's to always use eth3, and some to use eth4. But none of the VE traffic should use eth0, which is reserved for use by the HN only. This makes sense if you have VE's that may generate or receive a lot of traffic and you don't want your remote administration of the server over eth0 to degrade or get blocked because of this. To make this clear we'll use the following HN configuration. {| align="center" border="1" cellpadding=5! Interface !! MAC Address !! IP Address<pre>|-| eth0 = || 00:0c:29:b3:a2:54 with ip address || 192.168.18.10|-| eth3 = || 00:0c:29:b3:a2:68 with ip address || 192.168.18.11|-| eth4 = || 00:0c:29:b3:a2:fe with ip address || 192.168.18.12</pre>|} === HN ARP Flux ===The first issue is ARP flux. Any client on the network who broadcasts broadcasting an ARP "who has" message for any of these addresses will receive replies from all three interfaces. This results in IP addresses that float between three MAC addresses, depending on which response a client accepts first.
If all three network interfaces are on different IP networks (such as 10.x.x.x, 172.16.x.x, 192.168.x.x) then executing the following will work:
</pre>
Each of these should only generate responses from the network interface associated with that IP address on the HN.
----Now, let's say you want some of your VE's to always use eth3, and === Adding some to use eth4. None of the VE traffic should use eth0, which is reserved for use by the HN only. This makes sense if you have VE's that may generate or receive a lot of traffic and you don't want your remote administration of the server over eth0 to degrade or get blocked because of this.===
Setup two VE's as follows:
TODO: Discuss approach of <code>ip rule ...</code> and <code>ip route ...</code>.
 
TODO: Add examples of ARP flux before fix is applied, and after.
 
[[Category:HOWTO]]
[[Category:Networking]]
9
edits

Navigation menu