[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ifconfig: side effects of new lladdr feature
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: ifconfig: side effects of new lladdr feature
- From: Claudio Jeker <cjeker_(_at_)_diehard_(_dot_)_n-r-g_(_dot_)_com>
- Date: Tue, 5 Apr 2005 14:32:42 +0159
- Mail-followup-to: Claudio Jeker <cjeker_(_at_)_diehard_(_dot_)_n-r-g_(_dot_)_com>, misc_(_at_)_openbsd_(_dot_)_org
On Tue, Apr 05, 2005 at 03:43:28AM +0200, Andreas Bartelt wrote:
> Claudio Jeker wrote:
> >On Mon, Apr 04, 2005 at 01:40:06AM +0200, Andreas Bartelt wrote:
> >>(IP was not changed in the following example)
> >>example: #ifconfig fxp0 192.168.1.5 netmask 255.255.255.0 lladdr
> >This is a (broken) multicast ethernet address and so getting strange
> >results needs to be expected.
> Thanks, this explains the weird behaviour. Is it because the second
> number from the left isn't even? Or is there another reason why it's
> classified as multicast?
Yes multicast addresses are specified to have bit 0 of the first octet set
to 1. In your case 0x11 has bit 0 set and is therefor a link layer
multicast address. A check was added so that it is impossible to set a
multicast ll2 address.
Visit your host, monkey.org