I need to used multiple loopback addresses (interfaces) for an server application that communicates with multiple clients running on the same machine. Since a loopback interface short circuits the network stack (looping back in the IP layer) it is a more efficient means of communication, hence better for my purpose.
How do I define multiple loopback interfaces?
BTW, I'm a newbie to this mailing mailing list. Hopefully this is an appropriate question?
--- John Chludzinski john-chludzinski@myopera.com
On Thu, Aug 29, 2013 at 06:34:57AM -0700, John Chludzinski wrote:
I need to used multiple loopback addresses (interfaces) for an server application that communicates with multiple clients running on the same machine. Since a loopback interface short circuits the network stack (looping back in the IP layer) it is a more efficient means of communication, hence better for my purpose.
It doesn't short circuit the network stack, thats why we have the loopback driver in the first place.
How do I define multiple loopback interfaces?
you can use the ip utility to create dummy network devices on top of your loopback device, but the better question is - why? Having multiple clients and servers on a single system doesn't in any way require multiple loopback interfaces. just have the servers and clients all listen on, and connect to 127.0.0.1, and assign each server a separate port number.
Neil
BTW, I'm a newbie to this mailing mailing list. Hopefully this is an appropriate question?
John Chludzinski john-chludzinski@myopera.com
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Am 29.08.2013 15:53, schrieb Neil Horman:
you can use the ip utility to create dummy network devices on top of your loopback device, but the better question is - why? Having multiple clients and servers on a single system doesn't in any way require multiple loopback interfaces. just have the servers and clients all listen on, and connect to 127.0.0.1, and assign each server a separate port number.
that does not help you much in case as example a multi-postfix-installation when the software is not interested in using a different port and you want simulate real world by different IP's, binding services to specific ones and work with *hostnames* via /etc/hosts
On Thu, Aug 29, 2013 at 03:55:32PM +0200, Reindl Harald wrote:
Am 29.08.2013 15:53, schrieb Neil Horman:
you can use the ip utility to create dummy network devices on top of your loopback device, but the better question is - why? Having multiple clients and servers on a single system doesn't in any way require multiple loopback interfaces. just have the servers and clients all listen on, and connect to 127.0.0.1, and assign each server a separate port number.
that does not help you much in case as example a multi-postfix-installation when the software is not interested in using a different port and you want simulate real world by different IP's, binding services to specific ones and work with *hostnames* via /etc/hosts
Then add multiple address aliases to the existing loopback interface. Either way, theres really no reason at all to create multiple loopback interfaces Neil
devel@lists.stg.fedoraproject.org