UPDATE: [lug] problems manually configuring IP...

[D. Stimits]

"celttechie (Brian Jarrett)" wrote:
> 
> After doing some packet captures from the debian box I have determined that
> the arp cache is not getting updated even though the machine sends out an
> arp request and receives an arp reply.  As a matter of fact, it seems to be
> continually asking for 10.0.0.250 which is my gateway (and receives a reply
> each time).  Since the arp cache is not getting updated, I decided to add a
> static entry to 10.0.0.162.  Packet captures now show that the machine sends
> out an ICMP echo (ping) and 10.0.0.162 sends out the echo reply.  The
> machine STILL does not register any packets coming back in on the interface!
> 
> The machine obviously isn't processing any packets coming back in the
> interface.  Running ifconfig reveals that interface eth0 has received no
> packets, yet all of the communication is present on the wire.
> 
> Any ideas?  The only other thing I could think of was IPCHAINS but I have to
> update that because it won't run with my present kernel (2.2.17) and I
> hadn't configured it anyway.  What else could be blocking incoming packets?
> 
> Brian
> 
> ----- Original Message -----
> From: "celttechie (Brian Jarrett)" <celttechie at yahoo.com>
> To: <lug at lug.boulder.co.us>
> Sent: Thursday, April 12, 2001 1:16 PM
> Subject: Re: [lug] problems manually configuring IP...
> 
> >
> > > This probably won't fix the problem, but you might want to change your
> > > mask to 255.0.0.0 for that network range.
> > >
> > I am actually subnetting on purpose but I suppose I could give it a try.
> I
> > didn't think to ping localhost, but since you mentioned it I did give it a
> > try and it works fine.
> >
> > > Check /var/log/messages, as well as dmesg. It isn't unusual for someone
> > > to compile a kernel and not use all the modules they used before, and
> > > leave the old modules still there, which would make trying to load them
> > > fail. Then there is /etc/conf.modules (sometimes named modules.conf),
> > > which if it describes loading of modules that are no longer used, can
> > > still try to load them. It would all depend, but if ping works to
> > > localhost, unlikely it is a cause of failure elsewhere.
> > >
> > I had already looked at /var/log/messages and I couldn't find anything
> about
> > the depmod errors, so I thought it would be somewhere else.  dmesg doesn't
> > show anything on it either.  The only messages I see regarding eth0 at all
> > have to do with it going in and out of promiscuous mode probably because
> of
> > arpwatch.
> >
> > I also noticed on my ifconfig listing that it is incrementing packets
> > transmitted, but doesn't have any packets received.  So now I've done a
> > packet capture and all I see are ARP requests coming from the machine.
> I'm
> > going to try removing arpwatch from the startup to see if that makes a
> > difference.
> >
> > Brian

Does your 10.0.0.250 default route/gateway have enabled what it needs to
reply? Or pass through? Is the combination of netmask and gateway
enabling on there? Does it go through a hub or a switch or direct?

D. Stimits, stimits at idcomm.com