Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!solace!nntp.uio.no!news.cais.net!news.mathworks.com!newsfeed.internetmci.com!vixen.cso.uiuc.edu!usenet From: Vlad <roubtsov@uiuc.edu> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: /kernel: "rtinit: wrong ifa ...." ???? Date: Fri, 07 Jun 1996 15:03:41 -0500 Organization: University of Illinois at Urbana Lines: 43 Message-ID: <31B88B1D.41C67EA6@uiuc.edu> References: <4okupn$k38@vixen.cso.uiuc.edu> <4p92u4$bkj@panix.com> NNTP-Posting-Host: mossberg-93.slip.uiuc.edu Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mozilla 3.0b4 (X11; I; FreeBSD 2.1.0-RELEASE i386) Barry Masterson wrote: > > Vladimir Roubtsov (roubtsov) wrote: > : Hi: > : A question to knowledgeable folks: what can a message > > : /kernel: rtinit: wrong (or bad) ifa: <some hex #> was <different hex #> > : ( or close to this ) > [...] > : It is possible that both times I was running X312_SVGA server > :and running > : user-land ppp on COM2. The X server might've been in 16bpp mode in > :which case > [...] > : Vlad. > > The 'rtinit' & 'ifa' messages are most likely from the ppp program. > I had these messages, and the fix was in the /etc/sysconfig & /etc/hosts > files. Basically, you have to check the 'hostname' value, and your > ip address, and make sure it is entered correctly. > > Is your ip address static or dynamic? If dynamic, then there may not > be much you can do about it. If its a static address you have, then > the fix is a simple one. > > Barry Masterson > jbarrm@panix.com -- Thanx to both people who responded. At least those bright letters on my console didn't indicate a hardware problem as I feared initially :) It does look like this comes from the ppp program. Not only I get dynamic ip addresses -- I even dial different numbers during the same day! The problem to me was what to put in sysconfig and ppp.conf so that everybody was happy. My guess: that particular message was due to my assigned ip # (or provider's) changing during a ppp session in on-demand regime. At the moment ppp negotiates provider's address and I always get the # I want -- good for ppp's -auto mode -- but I can't control ip #'s assigned to me. Well, I've tweaked and tweaked sysconfig, hosts, and ppp.conf -- and maybe it's fine now, because I haven't seen the "wrong ifa..." message in a while. But I really don't know if it's gone for good„ and if so, what was the crucial step there... Dazed, Vlad.