[PLUG] PowerPC

robinsoq robinsoq at mail.opusnet.com
Fri Jul 11 00:15:02 UTC 2003


>1) remapping the keyboard to do dvorak 
>
>2) eth0 stops working periodically /etc/init.d/networking restart
>fixes it, so I have a cron job check every 2 min, however this would
>not be tollerable on anything other than a convience machine (if any
>one has reccomendations I'd love to hear them!).
>
>-Rogan
>

This may not be it, however in the past working with Redhat on a 
Pentium III I've noticed that changing the network settings in the 
sysconfig files and then doing a network restart won't change the 
active system settings from those the config files had in them at 
boot.  However, if you manually use ifconfig, route, etc. you can 
enter the new settings manually.  Of course if you reset your files 
those settings will be affective when you reboot also.  BTW, many 
times I've caused a router to stop working by turning off forwarding 
or downing a masquerading firewall.  Usually sysctl, look at 
/etc/stysctl.conf, is configured to turn forwarding off.  The init 
scripts are also good culprits for this where for firewalling, 
especially when taking one down, turning off forwarding and downing 
interfaces is a very good idea.

As always, assume any network conectivity problem is a bad cable or 
other media problem before thinking it's your Linux box.  It may be 
that you have high packet loss somewhere and that resetting your 
networking is cancelling a long retransmit loop.  One thing to look 
out for is an intersection of unshielded network cable and a large 
transformer.  If you have this situation, try wrapping the patch 
cable in aluminum foil to shield it.  With ping there is a flood
option, look at your packet loss when your interface works.  If
you make your own patch cables go buy one instead, they're not 
expensive and stranded wire is less likely to break than the 
solid core stuff that's bought in bulk.

Oh, watch out for 100 megabit/second nics that for some reason
won't run at 10mbits/s under Linux even on low speed hubs.  
I ran into this problem with Intel Etherexpress pro 10/100
builtin cards.  The only solution I've ever found was to 
connect to a 100 mbit/s switch instead of a low speed hub
from these machines.


     --  Michael C. Robinson 




More information about the PLUG mailing list