Date: Sat, 15 Jul 2000 20:37:08 +0200 From: Andre Albsmeier <andre.albsmeier@mchp.siemens.de> To: Nick Rogness <nick@rapidnet.com> Cc: Andre Albsmeier <andre.albsmeier@mchp.siemens.de>, Robert Watson <rwatson@freebsd.org>, freebsd-net@freebsd.org Subject: Re: routed: possible netmask problem ... Message-ID: <20000715203708.A11638@curry.mchp.siemens.de> In-Reply-To: <Pine.BSF.4.21.0007141215560.8367-100000@rapidnet.com>; from nick@rapidnet.com on Fri, Jul 14, 2000 at 12:29:39PM -0600 References: <Pine.NEB.3.96L.1000714140842.86137C-100000@fledge.watson.org> <Pine.BSF.4.21.0007141215560.8367-100000@rapidnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 14-Jul-2000 at 12:29:39 -0600, Nick Rogness wrote:
> On Fri, 14 Jul 2000, Robert Watson wrote:
>
> > On Fri, 14 Jul 2000, Nick Rogness wrote:
> >
> > > > root@webfix:~>ifconfig fxp0
> > > > 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
> > >
> > > you have a /32 netmask on 1.4, change it to a /24 address
> > > (255.255.255.0) and see if that helps.
> >
> > I don't have much experience with routed, but I can tell you that the /32
> > here is correct in my experience -- the two addresses are in the same /24
> > subnet. Putting both in with a netmask of /24 will cause problems due to
> > muliple routing entries with the same prefix/netmask.
> >
>
> I don't have much experience with routed either. I do agree in
> "specific" situations, setting both netmasks to /24 could be a
> problem.
>
> I have used /32 within the same network, but I binded it to the
> loopback interface and used arp (pub). That might solve your
Tried that (it is a different machine now for experimenting...)
root@messfix2:~>ifconfig -a
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.17.21 netmask 0xffffff00 broadcast 192.168.17.255
ether 00:a0:c9:ca:b0:8d
media: autoselect (100baseTX) status: active
supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
root@messfix2:~>ifconfig lo0 192.168.17.254 netmask 0xffffff00 alias
But at this moment the same error appears in the syslog:
Jul 15 20:28:45 <daemon.err> messfix2 routed[110]: possible netmask problem between lo0:192.168.17.254/32 and fxp0:192.168.17.0/24
Interestingly, it says lo0:192.168.17.254/32 but I
intentionally specified 0xffffff00 ...
> problems. I've also run gated without problems with this type of
> setup.
Well, it works here as well (both, your and my version). I think the problem
lies within routed since it appeared exactly when Peter Wemm commited the
changes...
-Andre
>
>
> Nick Rogness
> - Speak softly and carry a Gigabit switch.
>
>
--
Your mouse has moved.
Windows NT must be restarted for the change to take effect!
Reboot now? [OK]
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000715203708.A11638>