ok,i ran tcpdump. nothing happened util I tried to ping from another
machine in the internal net. then I got a ton of traffic, alot of it from
another server on the at&t network. I will attach the file I generated as
a result,okay see the file below(still learning pine!!)
20:38:26.402134 ha1.svc1.il.home.com.bootps > 255.255.255.255.bootpc: xid:0x6270 
Y:10.93.209.148 [|bootp]
20:38:26.492134 ha1.svc1.il.home.com.bootps > 255.255.255.255.bootpc: xid:0x6270 
Y:10.93.209.148 [|bootp]
20:38:27.582134 C454783-C.laporte1.in.home.com.1026 > 
proxy1.grffth1.in.home.com.domain: 44624+ (40)
20:38:27.592134 proxy1.grffth1.in.home.com.domain > 
C454783-C.laporte1.in.home.com.1026: 44624 1/2/2 (150)
20:38:27.682134 C454783-C.laporte1.in.home.com.1026 > 
proxy1.grffth1.in.home.com.domain: 44625+ (44)
20:38:27.692134 proxy1.grffth1.in.home.com.domain > 
C454783-C.laporte1.in.home.com.1026: 44625 NXDomain 0/1/0 (106)
20:38:27.702134 C454783-C.laporte1.in.home.com.1026 > 
proxy1.grffth1.in.home.com.domain: 44626+ (43)
20:38:27.722134 proxy1.grffth1.in.home.com.domain > 
C454783-C.laporte1.in.home.com.1026: 44626 1/2/2 (159)
20:38:29.802134 arp who-has c1638680-a.laporte1.in.home.com tell 24.182.167.129
20:38:29.812134 C454783-C.laporte1.in.home.com.1026 > 
proxy1.grffth1.in.home.com.domain: 44627+ (45)
20:38:29.822134 proxy1.grffth1.in.home.com.domain > 
C454783-C.laporte1.in.home.com.1026: 44627 1/2/2 (166)
20:38:29.832134 C454783-C.laporte1.in.home.com.1026 > 
proxy1.grffth1.in.home.com.domain: 44628+ (45)
20:38:29.842134 proxy1.grffth1.in.home.com.domain > 
C454783-C.laporte1.in.home.com.1026: 44628 NXDomain 0/1/0 (106)
20:38:32.582134 arp who-has 24.179.224.1 tell C454783-C.laporte1.in.home.com
20:38:32.582134 C454783-C.laporte1.in.home.com.1026 > 
proxy1.grffth1.in.home.com.domain: 44629+ (43)
20:38:32.582134 arp reply 24.179.224.1 is-at 0:d0:ba:a8:56:70
20:38:32.602134 proxy1.grffth1.in.home.com.domain > 
C454783-C.laporte1.in.home.com.1026: 44629 NXDomain 0/1/0 (104)
20:38:32.772134 arp who-has c1638680-a.laporte1.in.home.com tell 24.182.167.129
20:38:38.692134 ha1.svc1.il.home.com.bootps > 255.255.255.255.bootpc: xid:0xffffc9ce

I haven't a clue as to what this means as it goes way beyond my networking
abilities. I did notice the arp stuff, but could that be thier dhcp server
looking to fill requests?
Also, I still need to find out why I get those error messages from the net
interface(they are very annoying) this is what they look like:

eth1: tx interrupt but no status

I get this over and over again when someone is surfing on the other
computers. tried reconfiguring the net cards for different io and irqs, no
change. Tried changing eth1 for eth0 and no change, so its not in the
cards, has to be in the driver or the kernel.

I really am lost on this one and need allthe help I can get! :-)

thanks again Dennis


 On Sat, 26 May 2001, Pierre Fortin wrote:

> [EMAIL PROTECTED] wrote:
> > 
> > I have an older 486 w/6megs(max for this machine) running mandrake 6.0.
> > This machine is my gateway/firewall to the internet. It always is able to
> > access the net for its own,but, If I want the other machines to be able to
> > see the internet I have to ping one of them from the 486. After this all
> > the machines on the in house net have normal access. So basically I have
> > to log in and ping the internal net on the 486 every time I lose power or
> > reboot. Also I get error messages on eth1, it says that eth1 generated a
> > tx interupt with no status. I have intel etherexpress 16 net cards
> > installed. Doesn't make any difference which one is used as eth1, still get
> > that error message repeatedly when someone is on the internet on the other
> > machines,this also screws up my screen on the 486 forcing me to hit return
> > or have the app I'm running rescroll its screen so I can get rid of those
> > error messages. At the least I would like to send those error messages to
> > /dev/null and also not have to ping to activate the interal net.
> > Any ideas?
> > 
> >         thanks Dennis
> 
> More info required...   From your comments so far, it sounds like attempts to
> get through your gateway fail...  assuming the gateway is specified in all
> hosts, you are unable to ping the gateway after it reboots...  but pinging from
> the 486 lets the other hosts figure out where the gateway is.
> 
> Can you run tcpdump, ethereal or other sniffer on the 486..?  If so, does the
> 486 see a broadcast ARP request packet** when you try to ping the 486 from
> another host?  If so, does the 486 send an ARP reply packet?  If so, does the
> pinging host get the reply?
> 
> If all the above works, does the pinging host's ping packet now appear at the
> 486?  Note that after all this, if every answer is 'yes', then we'll have to dig
> deeper.  
>  
> **Are you using a hub or switch?  If a switch, the broadcast ARP request might
> not be flooded to all ports.
> 
> Pierre
> 


Reply via email to