Re: Troubleshooting connection loss (novice question)
- From: Bit Twister <BitTwister@xxxxxxxxxxxxxxxx>
- Date: Wed, 31 Oct 2007 03:45:31 GMT
On Wed, 31 Oct 2007 01:01:10 GMT, Allen Weiner wrote:
I posted to this thread my output yesterday in a rush.
Dang, I'll have to google for it. I missed it.
Bit Twister: Your script dump_net.txt Ver 3.4 appears to have some
problems with respect to Fedora. I'd like to repair my copy of it. I
have zero experience with bash scripting.
http://tldp.org/LDP/abs/html/index.html
1. The script is intended to post
/etc/sysconfig/networks-scripts/ifdown.d and ifup.d.
Had you read the top of the script, you may have noticed it was to run
on several different Linux OSs.
Those directories exists on Mandriva.
Are you looking for /etc/sysconfig/network-scripts/ifdown-eth and ifup-eth?
Nope. Some users put their own code/script there and I wanted contents
of directories if existed. See
# ls -al /etc/sysconfig/network-scripts/ifdown.d
total 12
drwxr-xr-x 2 root root 4096 2007-10-09 11:59 .
drwxr-xr-x 8 root root 4096 2007-10-09 12:26 ..
-rwxr-xr-x 1 root root 224 2007-10-03 16:49 vpn
Here is new/improved/untested code.
if [ -d /etc/sysconfig/network-scripts ] ; then
for _d in "ifdown.d" "ifup.d" ; do
if [ -e /etc/sysconfig/network-scripts/${_d} ] ; then
_cmd="cd /etc/sysconfig/network-scripts/${_d} ; ls -al "
echo "===== $_cmd ====" >> $_out_fn
cd /etc/sysconfig/network-scripts/${_d}
ls -al >> $_out_fn
fi
done
fi
2. The output of mii-tool was truncated.
Hmmm, must work different on Fedora. On Mandriva
# mii-tool -v eth0
eth0: no autonegotiation, 100baseTx-FD, link ok
product info: vendor 00:c0:b4, model 0 rev 8
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
Then the script dumped dmesg without printing the comment line.
Might try changing it to
echo "======== dmesg | grep eth$nic ==========" >> $_out_fn
It also appears that possibly the dmesg contents were dumped more
than once. (There was an enormous amount of output)
It would look repeating because it was to get
eth0, eth1, eth2 and look something like
========== dmesg | grep eth0 =================
eth0: Lite-On 82c168 PNIC rev 32 at Port 0xdf00, 00:A0:CC:21:B8:91, IRQ 19.
eth0: Setting full-duplex based on MII#1 link partner capability of 05e1.
eth0: no IPv6 routers present
========== dmesg | grep eth1 =================
eth1: RealTek RTL8139 at 0xf8826000, 00:16:17:57:66:54, IRQ 19
eth1: Identified 8139 chip type 'RTL-8100B/8139D'
Guess I'll have to get back into the script and try to figure out how to exit
loop if there is not an eth1 or eth2.
3. Ethtool is installed on my system. The script source invokes ethtool.
There was no ethtool output in the results.
Maybe an argument problem. I know ethtool does not work on my linksys nic
.
- References:
- Troubleshooting connection loss (novice question)
- From: Allen Weiner
- Re: Troubleshooting connection loss (novice question)
- From: Bit Twister
- Re: Troubleshooting connection loss (novice question)
- From: Allen Weiner
- Re: Troubleshooting connection loss (novice question)
- From: Allen Weiner
- Troubleshooting connection loss (novice question)
- Prev by Date: Re: verisign certificate
- Next by Date: accessing subversion repository server through local vpn server
- Previous by thread: Re: Troubleshooting connection loss (novice question)
- Next by thread: Re: Troubleshooting connection loss (novice question)
- Index(es):
Relevant Pages
|
