net/ipv4 for Source VIPA support, kernel BK Head
Quoted 2 lines · ?Alan Cox
Is there anything here that cannot already be done by the ip route command and iptables nat ?
Our experiences with customers operating high-available enterprise installations indicate that ip route and iptables nat do not fullfill all the relevant requirements:
The high-availability requirements drive those customers to ensure that all routes are dynamic which is not possible with the proposed ip route approach.
The complexity of the relevant setups necessitates an easy and requirements-driven configuration and solution approach. The overall concept of setting up a virtual device with a virtual IP adress and assigning this virtual IP adress as a Source VIPA to the devices which should allow for a failover is well known from other operating system and expected by relevant enterprise customers. IP routes and NAT allow to achieve the same effect with the exception mentioned above, but the corresponding configuration overhead is in the opinion of customers having enterprise setups too complex and complicated. Our overall approach introduces this concept as a facility to address these requirements very clearly.
Einar
Quoted 3 lines · Einar Lueck
The high-availability requirements drive those customers to ensure that all routes are dynamic which is not possible with the proposed ip route approach.
Why. You are simply doing NAT for that port from all locally sourced packets to your "virtual" address ?
Alan
Quoted 7 lines · On Donnerstag, 2. September 2004 13:05 Alan Cox wrote:
Quoted 3 lines · Einar Lueck
The high-availability requirements drive those customers to ensure that all routes are dynamic which is not possible with the proposed ip route approach.
Why. You are simply doing NAT for that port from all locally sourced packets to your "virtual" address ?
I thought You proposed to utilize ip route in the following way:
"ip route xxx.xxx.xxx.xxx/xx via xxx dev xxx src MY_VIRTUAL_IP_ADDRESS" This approach does not work with the setups we have in mind. So I misunderstood You. As we pointed out in the other part of the mail iptables NAT is not an option for the relevant customers.
Einar
Quoted 2 lines · Einar Lueck
You. As we pointed out in the other part of the mail iptables NAT is not an option for the relevant customers.
You've failed as far as I can see to explain why NAT doesn't do the right thing in this case. I don't care whether the customers like it, I care whether it works. If it works then we don't need to add junk to the kernel. If it works but is hard to configure then its an opportunity to write a nice tool to manage it.
Quoted 5 lines · On Donnerstag, 2. September 2004 13:24 Alan Cox wrote:
You've failed as far as I can see to explain why NAT doesn't do the right thing in this case. I don't care whether the customers like it, I care whether it works. If it works then we don't need to add junk to the kernel. If it works but is hard to configure then its an opportunity to write a nice tool to manage it.
I am sorry: I failed to point out that NAT does the job!
We think that the the proposed patch, that is a really small one, introduces a facility that works well for existing operating systems and is desired by customers. Consequently, it enriches the kernel with a concept that has already proven its value. That's the reason why we think the kernel could profit from the application of the corresponding patch, especially as it makes more customers happy. As the whole feature may be configured out we don't see what's wrong with making more and especially large customers happy with an enriched kernel.
Einar
Quoted 6 lines · On Thu, 2 Sep 2004 14:51:55 +0200 Einar Lueck <[email protected]> wrote:
Quoted 5 lines · On Donnerstag, 2. September 2004 13:24 Alan Cox wrote:
You've failed as far as I can see to explain why NAT doesn't do the right thing in this case. I don't care whether the customers like it, I care whether it works. If it works then we don't need to add junk to the kernel. If it works but is hard to configure then its an opportunity to write a nice tool to manage it.
Quoted 6 lines
I am sorry: I failed to point out that NAT does the job!
We think that the the proposed patch, that is a really small one, introduces a facility that works well for existing operating systems and is desired by customers. Consequently, it enriches the kernel with a concept that has already proven its value.
We never add patches that duplicate existing functionality just to make it somehow "easier" for the user. That's a job for scripts and good tools, that make use of existing kernel facilities.
Alan is saying you can hide whatever complexity you claim exists via tools, without any kernel modifications. If you continue to ignore that part of the discussion, it seems likely we will just the same ignore your patch.
I, frankly, see no reason at all to even remotely consider your patch. Furthermore, you'll get more discussion by bringing this up in the proper place to propose such networking changes ([email protected]).
Quoted 10 lines · Einar Lueck
The complexity of the relevant setups necessitates an easy and requirements-driven configuration and solution approach. The overall concept of setting up a virtual device with a virtual IP adress and assigning this virtual IP adress as a Source VIPA to the devices which should allow for a failover is well known from other operating system and expected by relevant enterprise customers. IP routes and NAT allow to achieve the same effect with the exception mentioned above, but the corresponding configuration overhead is in the opinion of customers having enterprise setups too complex and complicated. Our overall approach introduces this concept as a facility to address these requirements very clearly.
The problem here is not the kernel, it's the awful state of network management in the common initscripts and routing daemons, which have not evolved far beyond the traditional (static) BSD model of interfaces, despite the qualitative leap in functionality brought on by Alexey's contributions to Linux 2.2, netfilter and vlans in 2.4, and now IPsec in 2.6.
While policy routing, traffic control, netfilter, etc., are extremely powerful separately and in combination, there is no unified mechanism for managing different aspects of network configuration (addressing, redundancy, security, QoS, etc.) that cut across each of these kernel mechanisms.
Several of the routing daemons (Quagga, Bird, etc.) have gotten partway there, but none is (AFAIK, correct me if I'm wrong) in a state where one can eliminate all of the other networking-related scripts from initscripts and just expect the daemon(s) to manage networking.
It seems that effort would be better spent cleaning up userspace, by looking at use cases, identifying the right abstractions, and reifying them. Choose a routing daemon, and turn it into a "Network Mgmt daemon".
Should this be built on top of HAL/D-BUS? I don't know, will HAL/D-BUS remain lightweight enough to be used in an embedded router? I sure hope so.
Regards,
Bill Rugolsky