Date: Wed, 17 Nov 1999 21:28:02 +0000 From: Brian Somers <brian@Awfulhak.org> To: Blaz Zupan <blaz@amis.net> Cc: brian@FreeBSD.org, freebsd-net@FreeBSD.org Subject: Re: rinit: wrong ifa (0xc09ba580) was (0xc0854880) - candidate for removal Message-ID: <199911172128.VAA02251@hak.lan.Awfulhak.org> In-Reply-To: Message from Blaz Zupan <blaz@amis.net> of "Wed, 17 Nov 1999 09:26:33 %2B0100." <Pine.BSF.4.20.9911170918560.67493-100000@titanic.medinet.si>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Nothing's changed of late here. Ppp will use whatever ``hostname'' resolves to as a default local address unless a ``set ifaddr'' is done. As you've got a ``set ifaddr'', I find it surprising that you see this message. Personally, my laptop is configured with a lo0 alias address of my hostname. When I plug the NIC in, I get the message because I'm assigning the same IP number to the ep0 device. Personally, I think the message should only be displayed if another interface is found configured with that address *AND* it's not a POINTOPOINT interface. In fact, I'll do this soon if nobody objects (freebsd-net cc'd). > The message in the subject is being printed on the console of a customers > machine. I looked through the mailing list archives and found a posting by > Garrett A. Wollman, who says: > > > What this means is that, in the process of trying to configure a network > > interface, the address which was specified for the new interface matched > > one that already belonged to another interface. The code is basically > > giving you a very cryptic warning to the effect that `what you asked me > > to do doesn't make any sense, but I'll force it through anyway'. > > I looked through the machine and noticed, that the tun0 interface contains > all IP numbers that were assigned to the machine (IP numbers are > dynamically assigned) as secondary addresses. > > This is a change in behaviour since FBSD 3.2, where the IP address has > been simply replaced on the interface and I believe the cryptic "wrong > ifa" message is being caused by this. > > Is this the intended behaviour? I was using a modified default > configuration from 3.3, but then changed to my "standard" config file that > I use on all dialup masquerading boxes, but the problem remains. > > Here is the ppp.conf file from the box: > > default: > set device /dev/cuaa0 > # set log Phase Chat LCP IPCP CCP tun command > set speed 115200 > set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT OK-AT-OK ATB40 OK \\dATDI\\T TIMEOUT 40 CONNECT" > disable lqr > deny lqr > papchap: > set phone 088932410 > set authname someuser > set authkey somepass > set timeout 110 > set openmode active > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 > delete ALL > add 0 0 HISADDR > alias enable yes > > I looked through the ppp commit logs if there was any mention of this > behaviour, but could not find anything - but I may have missed something. > > Any help will be appreciated. > > Regards, > > Blaz Zupan, blaz@amis.net, http://home.amis.net/blaz/ > Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia > > -- Brian <brian@Awfulhak.org> <brian@FreeBSD.org> <http://www.Awfulhak.org>; <brian@OpenBSD.org> Don't _EVER_ lose your sense of humour ! <brian@FreeBSD.org.uk> 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?199911172128.VAA02251>