Re: Multiple Loopback Interfaces

2013-08-29 Thread Dan Williams
On Thu, 2013-08-29 at 15:46 +0200, Reindl Harald wrote: > > Am 29.08.2013 15:38, schrieb John Chludzinski: > > 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

Re: Multiple Loopback Interfaces

2013-08-29 Thread Reindl Harald
Am 29.08.2013 15:38, schrieb John Chludzinski: > 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)

Re: Multiple Loopback Interfaces

2013-08-29 Thread Reindl Harald
BTW: try to ping 127.0.0.1, 127.0.0.2, 127.0.0.3 here they are pingable as default the instruction below if only needed if the application checks that a configured IP exists via ifconfig or lookalike Am 29.08.2013 15:46, schrieb Reindl Harald: > Am 29.08.2013 15:38, schrieb John Chl

Re: Multiple Loopback Interfaces

2013-08-29 Thread Reindl Harald
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

Re: Multiple Loopback Interfaces

2013-08-29 Thread Neil Horman
On Thu, Aug 29, 2013 at 08:32:56AM -0700, John Chludzinski wrote: > Both 127.0.0.7 and 127.0.0.10 exist in /etc/hosts for the client apps to > use when connecting to the server.The clients use both > gethostbyname() and getservbyname() for connecting. Currently, there > are *no* multiple loopb

Re: Multiple Loopback Interfaces

2013-08-29 Thread John Chludzinski
Both 127.0.0.7 and 127.0.0.10 exist in /etc/hosts for the client apps to use when connecting to the server.The clients use both gethostbyname() and getservbyname() for connecting. Currently, there are *no* multiple loopback interfaces defined. I wrote my own example TCP socket code to test

Re: Multiple Loopback Interfaces

2013-08-29 Thread Martin Langhoff
On Thu, Aug 29, 2013 at 9:47 AM, Juan Orti Alcaine wrote: > In IPv4 you can get any IP in the 127.0.0.0/8 subnet for the lo interface. And in current fedora, they are already assigned to localhost. You can ping 127.0.0.22 if you want. AIUI, you can bind to it freely, too. m -- martin.langh

Re: Multiple Loopback Interfaces

2013-08-29 Thread Neil Horman
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 si

Re: Multiple Loopback Interfaces

2013-08-29 Thread Neil Horman
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

Re: Multiple Loopback Interfaces

2013-08-29 Thread Juan Orti Alcaine
El Jueves, 29 de agosto de 2013 06:38:00 John Chludzinski escribió: > 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 ba