fedora core 2 client behind sonicwall

Hi:
I have a client running fedora core 2 sitting behind a sonicwall TZ-170
firewall which periodically loses all network connectivity, can't even
ping itself or other computers on lan. Doing an ifdown/up solves the
problem, but this does not happen on other lans that do not have a
sonicwall. It also does not happen at some of our sites with other
sonicwall firewalls. Is there some setting that needs to be modified in
the kernel?
Thanks for any and all replies
Happy holidays

On Fri, 24 Dec 2004 16:52:11 GMT, Ward Taylor <(E-Mail Removed)> wrote:
> Hi:
> I have a client running fedora core 2 sitting behind a sonicwall TZ-170
> firewall which periodically loses all network connectivity, can't even
> ping itself or other computers on lan. Doing an ifdown/up solves the
> problem, but this does not happen on other lans that do not have a
> sonicwall. It also does not happen at some of our sites with other
> sonicwall firewalls. Is there some setting that needs to be modified in
> the kernel?
> Thanks for any and all replies

What nic and what module? I had one nic that worked fine with earlier
kernel 2.2 tulip module, but networking would stop at times with kernel
2.4, or did not work until pinged from network in newer 2.2 tulip (worked
fine with old_tulip).

I have also had Dlink DFE-530TX+ nics that usually worked fine with
8139too, but would sometimes go into a frenzy (flickering link LED) with
heavy packet loss unless kicked back with mii-tool -A
10baseT-FD,10baseT-HD.

David Efflandt wrote:
> On Fri, 24 Dec 2004 16:52:11 GMT, Ward Taylor <(E-Mail Removed)> wrote:
>
>>Hi:
>>I have a client running fedora core 2 sitting behind a sonicwall TZ-170
>>firewall which periodically loses all network connectivity, can't even
>>ping itself or other computers on lan. Doing an ifdown/up solves the
>>problem, but this does not happen on other lans that do not have a
>>sonicwall. It also does not happen at some of our sites with other
>>sonicwall firewalls. Is there some setting that needs to be modified in
>>the kernel?
>>Thanks for any and all replies
>
>
> What nic and what module? I had one nic that worked fine with earlier
> kernel 2.2 tulip module, but networking would stop at times with kernel
> 2.4, or did not work until pinged from network in newer 2.2 tulip (worked
> fine with old_tulip).
>
> I have also had Dlink DFE-530TX+ nics that usually worked fine with
> 8139too, but would sometimes go into a frenzy (flickering link LED) with
> heavy packet loss unless kicked back with mii-tool -A
> 10baseT-FD,10baseT-HD.
Thanks for your reply. It is a built-in intel 10/100 device in an hp
laptop.