From andre.albsmeier@mchp.siemens.de  Wed Feb 23 11:04:08 2000
Return-Path: <andre.albsmeier@mchp.siemens.de>
Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131])
	by hub.freebsd.org (Postfix) with ESMTP id A00C337B908
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 23 Feb 2000 11:04:06 -0800 (PST)
	(envelope-from andre.albsmeier@mchp.siemens.de)
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by goliath.siemens.de (8.9.3/8.9.3) with ESMTP id UAA09065
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 23 Feb 2000 20:04:03 +0100 (MET)
Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7])
	by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id UAA15058
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 23 Feb 2000 20:04:03 +0100 (MET)
Received: (from daemon@localhost)
	by curry.mchp.siemens.de (8.9.3/8.9.3) id UAA44947
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 23 Feb 2000 20:04:03 +0100 (CET)
Message-Id: <200002231904.UAA83978@internal>
Date: Wed, 23 Feb 2000 20:04:02 +0100 (CET)
From: Andre Albsmeier <andre.albsmeier@mchp.siemens.de>
To: FreeBSD-gnats-submit@freebsd.org
Subject: routed: possible netmask problem between fxp0:192.168.1.4/32 and fxp0:192.168.1.0/24
X-Send-Pr-Version: 3.2

>Number:         16941
>Category:       bin
>Synopsis:       routed: possible netmask problem between fxp0:192.168.1.4/32 and fxp0:192.168.1.0/24
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    sheldonh
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Feb 23 11:10:00 PST 2000
>Closed-Date:    Mon Aug 14 09:59:47 PDT 2000
>Last-Modified:  Mon Aug 14 10:00:50 PDT 2000
>Originator:     Andre Albsmeier
>Release:        FreeBSD 3.4-STABLE i386
>Organization:
<
>Environment:

FreeBSD 3.4-STABLE with the routed changes of Feb 17.

>Description:

There have been various changes to routed on Feb 17. I am now
experiencing a strange message when routed is started:

routed: possible netmask problem between fxp0:192.168.1.4/32 and fxp0:192.168.1.0/24
routed: Send mcast sendto(fxp0, 224.0.0.9.520): No route to host

If have the following ifconfig lines on the machine in question:

ifconfig_fxp0="inet 192.168.1.3 media 100BaseTX mediaopt full-duplex"
ifconfig_fxp0_alias0="inet 192.168.1.4 netmask 0xFFFFFFFF"

As we can see, 192.168.1.4 is an alias for the machine.
ifconfig -a tells me:

fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255
        inet 192.168.1.4 netmask 0xffffffff broadcast 192.168.1.4
        ether 00:a0:c9:ca:18:64 
        media: 100baseTX <full-duplex> status: active
        supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP


I have never had problems with this setup. OK, I still don't
have problems (everything is working) but the message is confusing.
I assume it would go away with a different netmask for the alias
but this would be wrong, I think.

>How-To-Repeat:

Configure a machine similar as above. Start routed.

>Fix:
	
unknown

>Release-Note:
>Audit-Trail:

From: Andre Albsmeier <andre.albsmeier@mchp.siemens.de>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: bin/16941: routed: possible netmask problem between fxp0:192.168.1.4/32 and fxp0:192.168.1.0/24
Date: Fri, 14 Apr 2000 20:58:11 +0200

 Today I compiled an older routed without the changes of Feb 17th
 and the problem persists. I assume that something somwhere else
 has changed and makes routed emit the error message.
 
State-Changed-From-To: open->feedback 
State-Changed-By: sheldonh 
State-Changed-When: Wed Aug 2 06:10:24 PDT 2000 
State-Changed-Why:  
Andre, if you have access to a -CURRENT box, could you try 
this with the new routed-2.21 which I just committed? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=16941 

From: Sheldon Hearn <sheldonh@uunet.co.za>
To: Andre Albsmeier <andre.albsmeier@mchp.siemens.de>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: bin/16941: routed: possible netmask problem between fxp0:192.168.1.4/32 and fxp0:192.168.1.0/24 
Date: Wed, 02 Aug 2000 15:18:34 +0200

 On Wed, 02 Aug 2000 15:15:34 +0200, Andre Albsmeier wrote:
 
 > I am just setting up a 4.1-STABLE machine. I have got the
 > -current routed sources as well. Should it be possible to
 > run your -current routed under 4.1-STABLE ?
 
 Yes.  The necessary newcomers RTM_NEWMADDR and RTM_DELMADDR exist in
 RELENG_4, so you should have no problems.
 
 Ciao,
 Sheldon.
 

From: Andre Albsmeier <andre.albsmeier@mchp.siemens.de>
To: Sheldon Hearn <sheldonh@uunet.co.za>
Cc: Andre Albsmeier <andre.albsmeier@mchp.siemens.de>,
	freebsd-gnats-submit@FreeBSD.org
Subject: Re: bin/16941: routed: possible netmask problem between fxp0:192.168.1.4/32 and fxp0:192.168.1.0/24
Date: Wed, 2 Aug 2000 15:19:57 +0200

 On Wed, 02-Aug-2000 at 15:18:34 +0200, Sheldon Hearn wrote:
 > 
 > 
 > On Wed, 02 Aug 2000 15:15:34 +0200, Andre Albsmeier wrote:
 > 
 > > I am just setting up a 4.1-STABLE machine. I have got the
 > > -current routed sources as well. Should it be possible to
 > > run your -current routed under 4.1-STABLE ?
 > 
 > Yes.  The necessary newcomers RTM_NEWMADDR and RTM_DELMADDR exist in
 > RELENG_4, so you should have no problems.
 
 Great. I will try as soon I have the machine ready and 
 time permits (I am a bit overloaded at the moment :-)).
 
 Thanks,
 
 	-Andre
 

From: Andre Albsmeier <andre.albsmeier@mchp.siemens.de>
To: sheldonh@FreeBSD.org
Cc: andre.albsmeier@mchp.siemens.de, freebsd-bugs@FreeBSD.org
Subject: Re: bin/16941: routed: possible netmask problem between fxp0:192.168.1.4/32 and fxp0:192.168.1.0/24
Date: Wed, 2 Aug 2000 17:53:37 +0200

 On Wed, 02-Aug-2000 at 06:11:25 -0700, sheldonh@FreeBSD.org wrote:
 > Synopsis: routed: possible netmask problem between fxp0:192.168.1.4/32 and fxp0:192.168.1.0/24
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: sheldonh
 > State-Changed-When: Wed Aug 2 06:10:24 PDT 2000
 > State-Changed-Why: 
 > Andre, if you have access to a -CURRENT box, could you try
 > this with the new routed-2.21 which I just committed?
 > 
 > http://www.freebsd.org/cgi/query-pr.cgi?pr=16941
 
 I tried the -current routed on 4.1-STABLE, it compiled cleanly.
 Unfortunately, the error message is still there. I am sure
 the ip alias is set up properly. The message started to appear
 when peter made his commit to routed in february, e.g.:
 
 ---------------- snip ----------------------
 
 Thu Feb 17 05:26:36 2000 CET (5 months, 2 weeks ago) by peter 
 
 MFC: all fixes and cleanups - this is the last straw, it has broken one
 time too many.  The 3.4 version has been doing bizzare things while the
 4.0 version compiled on 3.4 has worked fine.
 
 ---------------- snap ----------------------
 
 
 Before these commits, routed never complained about the ip alias.
 
 
State-Changed-From-To: feedback->analyzed 
State-Changed-By: sheldonh 
State-Changed-When: Thu Aug 10 03:44:01 PDT 2000 
State-Changed-Why:  
Andre believes that Vernon's routed-2.22 addresses his problem. 
I've merged this distribution into HEAD on FreeBSD.  We'll 
wait a while before merging it onto RELENG_4. 


Responsible-Changed-From-To: freebsd-bugs->sheldonh 
Responsible-Changed-By: sheldonh 
Responsible-Changed-When: Thu Aug 10 03:44:01 PDT 2000 
Responsible-Changed-Why:  
My reminder. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=16941 
State-Changed-From-To: analyzed->closed 
State-Changed-By: sheldonh 
State-Changed-When: Mon Aug 14 09:59:47 PDT 2000 
State-Changed-Why:  
Turns out we didn't wait as long as anticipated.  Acting on 
feedback from Andre, I merged this onto RELENG_4 today. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=16941 
>Unformatted:
