Networking Forums

Networking Forums > Computer Networking > Linux Networking > loopback with netmask 255.255.255.255 visible for all network

Reply
Thread Tools Display Modes

loopback with netmask 255.255.255.255 visible for all network

 
 
Artur Kaminski
Guest
Posts: n/a

 
      06-03-2008, 04:29 PM
Hi all,

I have many virtual machines on a host and another server in the same
network 10.0.0.0/24.
One of the virtual machine has IP address/24 on eth0 and additional IP
in the same network, but with mask 32

ifconfig eth0 10.0.0.1 netmask 255.255.255.0 up
ifconfig lo:1 10.0.0.2 netmask 255.255.255.255 up

What can be the reason I can see 10.0.0.2 from external host?


___
Thanks in advance,
Artur
 
Reply With Quote
 
 
 
 
Pascal Hambourg
Guest
Posts: n/a

 
      06-03-2008, 10:06 PM
Hello,

Artur Kaminski a écrit :
>
> ifconfig eth0 10.0.0.1 netmask 255.255.255.0 up
> ifconfig lo:1 10.0.0.2 netmask 255.255.255.255 up
>
> What can be the reason I can see 10.0.0.2 from external host?


Linux enforces what is called the "weak model". this means that any
local address assigned to any interface is reachable on any interface.
In other words, addresses are globally assigned to the host rather than
specific interfaces. The only exception is the range 127.0.0.0/8, not
because it is assigned to the loopback interface but because it is
prohibited outside a host.
 
Reply With Quote
 
Artur Kaminski
Guest
Posts: n/a

 
      06-04-2008, 12:57 PM
On Jun 3, 11:06 pm, Pascal Hambourg <boite-a-s...@plouf.fr.eu.org>
wrote:
> Hello,
>
> Artur Kaminski a écrit :
>
>
>
> > ifconfig eth0 10.0.0.1 netmask 255.255.255.0 up
> > ifconfig lo:1 10.0.0.2 netmask 255.255.255.255 up

>
> > What can be the reason I can see 10.0.0.2 from external host?

>
> Linux enforces what is called the "weak model". this means that any
> local address assigned to any interface is reachable on any interface.
> In other words, addresses are globally assigned to the host rather than
> specific interfaces. The only exception is the range 127.0.0.0/8, not
> because it is assigned to the loopback interface but because it is
> prohibited outside a host.


Thanks Pascal,

I try to find why it stopped on one machine only while I have four
(two loadbalanced pairs of servers).



Regards
Artur
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Re: problem with ethernet loopback test using loopback plug/stub: receiving socket not seeing packet. Rick Jones Linux Networking 10 08-22-2010 07:17 PM
wireless network not visible =?Utf-8?B?Ymlyb2w=?= Broadband Hardware 1 10-29-2005 12:30 AM
Random workstations not visible on network =?Utf-8?B?YWxhZGViMTkyNQ==?= Broadband Hardware 1 02-24-2005 04:36 PM
Server not visible on network Gurmit Windows Networking 12 07-26-2004 12:28 AM
Printer not visible on Network Kevin J Windows Networking 3 07-15-2003 10:10 PM



1 2 3 4 5 6 7 8 9 10 11