Hi all,

I've found that at some point, ifconfig has not been listing my aliases
correctly either.  I haven't changed /etc/conf.d/net for a long time,
and yet I only see eth0 when I run ifconfig, and not eth0:1 (which is
also created from /etc/conf.d/net)

However, if I run ifconfig eth0:1 from the command line, then ifconfig
displays it, so I don't know what's going on and why it's changed...

On Mon, 2006-12-11 at 23:35 +0100, Pawel Kraszewski wrote:
> Dnia poniedziaƂek, 11 grudnia 2006 18:34, Leandro Melo de Sales napisaƂ:
> 
> > config_eth0=( "192.168.1.2 netmask 255.255.255.0"
> >               "192.168.1.3 netmask 255.255.255.0"
> >               "192.168.1.6 netmask 255.255.255.0"
> > )
> 
> Well, it is a design flaw to have 3 addresses in overaping networks. From 
> what 
> I recall you may use only one non /32 address in a network. If the 
> requirement is not met, problems arise:

Not necessarily.  It may be necessary to have multiple addresses on the
same subnet.

> Problem: You want to broadcast to 192.168.1.255.
> Question: From which of these addresses should it origin?

The first one it finds?  A random one? don't know.

you could also say `ping I 192.168.1.2 b 192.168.1.255`

> Problem: Someone else broadcasts to 192.168.1.255.
> Question: Which of these addresses should catch it? One? All?

All of course, it is a broadcast after all :)

> I was taught that configurations of multiple-ip-per-net should look like:
> 
>  config_eth0=( "192.168.1.2 netmask 255.255.255.0"
>                "192.168.1.3 netmask 255.255.255.255"
>                "192.168.1.6 netmask 255.255.255.255"
>  )
> 
> Only the first has a regular mask (and therefore is source and target for 
> broadcasts) - the rest has /32 mask and is only valid for unicast 
> communication.

good idea.

> AFAIK this is true for both multiple cards on single network and multiple 
> aliases on single card.

cya,
-- 
Iain Buchanan <iaindb at netspace dot net dot au>

The other day I... uh, no, that wasn't me.
                -- Steven Wright

-- 
gentoo-user@gentoo.org mailing list

Reply via email to