There are collisions in the eth0 interface while there are no collisions in
the eth1 wireless interface
I have tried the mii-tool as suggested by alexander.janssen@gmx.de it did
help to some extent but I was not successful in the overall situation
I would like to elaborate the setup in more detail
A(eth0) <----->distance 2mts <---> (intel Switch 550T) <---->distance30mts
(hub) distance 20mts <--->B(eth0) (eth1 wireless card wan) < ~ ~ ~ ~ ~ >
(eth1 wireless card wan) (eth0) <---->distance 2mts (hub) <------>distance
10mts (PC)
A(eth0) the value of this interface card as per the dmesg of the box is as
below
eth0: Intel Corporation 82557 [Ethernet Pro 100], 00:90:27:B2:04:82, IRQ 10.
Receiver lock-up bug exists -- enabling work-around.
Board assembly 677173-001, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x24c9f043).
Receiver lock-up workaround activated.
B(eth0) the value of this interface card as per the dmesg of the box is as
below
eth0: Intel Corporation 82557 [Ethernet Pro 100], 00:90:27:24:EC:8C, IRQ 15.
Receiver lock-up bug exists -- enabling work-around.
Board assembly 689661-004, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x24c9f043).
Receiver lock-up workaround activated.
B(eth1) this is a wireless aironet 4800 isa card mounted on a RH 7.3 box
who's bitrate is set to 11mbps and its status is as below
Every 2s: /bin/cat /proc/driver/aironet/eth1/Status
Fri Jan 3 16:20:26 2003
Mode: 1f
Signal Strength: 57
Signal Quality: 125
SSID: solgold
AP:
Freq: 0
BitRate: 11mbs
Driver Version: airo.c 1.5.2 2001/01/22 (Benjamin Reed ) + CISCO EXTENTIONS
Device: PC4800A
Manufacturer: Aironet Wireless Communications
Firmware Version: 3.82
Radio type: 2
Country: 1
Hardware Version: 52
Software Version: 382
Software Subversion: 0
Boot block version: 138
C(eth1) this is a wireless aironet 4800 isa card mounted on a MikroTik 2.4
ver router box who's bitrate is set to 11mbps and its status is as below
[GOLDEN] > interface pc monitor pc1
quality: 48
strength: 142
current-rate: 11Mbit/s
current-frequency: 2452MHz
synchronized: yes
associated: no
ssid: solgold
access-point: CA:03:35:02:16:02
access-point-name:
error-number: 0
Regards,
Vishal Gandhi
----- Original Message -----
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: "Vishal Gandhi Kommineni" <vishal@southernonline.net>
Cc: "LARTC" <lartc@mailman.ds9a.nl>
Sent: Thursday, January 02, 2003 9:49 PM
Subject: Re: [LARTC] speed problem
> Vishal,
>
> : > the first thing i'd like to check is if the ethernet cards are
running
> : > in full- or half-duplex mode. AFAIK running one card in half-duplex
mode
> : > and the other trying to force full-duplex mode can lead to lots of
> : > collisions, so this could be a reason for slow speed.
>
> I agree with Ulrich, and apparently that may have been your problem.
>
> : thanks for the reply, i found that there are collission when i use a
> : hub in between, How do i make sure that both the ethernet cards are
> : running in half or full duplex mode, how do i check if weathere an
> : ethernet is in half or full duplex mode
>
> You may find that one of the following tools helps you to determine what
> your ethernet card has negotiated with its peer:
>
> - ethtool ( the tool which will probably continue to be maintained and
> supported under linux )
> http://www.gnu.org/directory/sysadmin/Monitor/ethtool.html
>
> - mii-diag, aka mii-tool, ( one of these two is usually available on
> common distributions available today )
> http://freshmeat.net/projects/mii-diag/
>
> -Martin
>
> Here's some example output from mii-diag and mii-tool:
>
> # mii-tool --help
> usage: mii-tool [-VvRrwl] [-A media,... | -F media] [interface ...]
> -V, --version display version information
> -v, --verbose more verbose output
> -R, --reset reset MII to poweron state
> -r, --restart restart autonegotiation
> -w, --watch monitor for link status changes
> -l, --log with -w, write events to syslog
> -A, --advertise=media,... advertise only specified media
> -F, --force=media force specified media technology
> media: 100baseT4, 100baseTx-FD, 100baseTx-HD, 10baseT-FD, 10baseT-HD,
> (to advertise both HD and FD) 100baseTx, 10baseT
> # mii-tool eth0
> eth0: negotiated 100baseTx-FD flow-control, link ok
>
>
> # mii-diag --help
> Usage: mii-diag [-aDfrRvVw] [-AF <speed+duplex>] [--watch] <interface>.
>
> Show the link status of the specified network interface.
> The default interface is "eth0".
>
> The common usage is
> mii-diag eth0
> Frequently used options are
> -A --advertise <speed|setting>
> -F --fixed-speed <speed>
> Speed is one of: 100baseT4, 100baseTx, 100baseTx-FD, 100baseTx-HD,
> 10baseT, 10baseT-FD, 10baseT-HD
> -s --status Return exit status 2 if there is no link beat.
>
> Less frequently used options are
> -a --all-interfaces Show the status all interfaces
> (Not recommended with options that change settings.)
> -D --debug
> -g --read-parameters Get driver-specific parameters.
> -G --set-parameters PARMS Set driver-specific parameters.
> Parameters are comma separated, missing elements retain existing
> value.
> -M --msg-level LEVEL Set the driver message bit map.
> -p --phy ADDR Set the PHY (MII address) to report.
> -r --restart Restart the link autonegotiation.
> -R --reset Reset the transceiver.
> -v --verbose Report each action taken.
> -V --version Emit version information.
> -w --watch Continuously monitor the transceiver and report
> changes.
>
> This command returns success (zero) if the interface information can be
> read. If the --status option is passed, a zero return means that the
> interface has link beat.
> # mii-diag eth0
> Basic registers of MII PHY #1: 3000 7809 02a8 0154 05e1 0000 0000 0000.
> Basic mode control register 0x3000: Auto-negotiation enabled.
> Basic mode status register 0x7809 ... 7809.
> Link status: not established.
> End of basic transceiver information.
>
> --
> Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
>
>
