[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
