Trying to break the Evil Empire habit here. Next step in that
process is to get my RH 7.2 laptop up on wireless. Not working
so far. I must be overlooking something incredibly dumb & obvious.
Have two Orinoco Wavelan Silver 802.11b cards. First one is
in a W2K machine. Second is in a dualboot RH7.2/Win98 machine.
No other cards are inserted.
W2K to W98 works fine. W2K to RH7.2, well, they ain't talking
to one another. They *see* one another over the air, but no more.
Ping fails from either side. Both machines can ping themselves
but not the other. TX/RX appears to show packets are being *sent*,
but *not* received. This is true in either direction.
The Orinoco Client Manager for W2K has a "Link Test" option.
Invoking that indicates that the radio connection between the
two cards is "Excellent to good".
The link test from W2K also picks up the station name of the
RH7.2 machine, so packets are being sent and received.
The RH7.2 machine is also receiving the MAC address of the card
in the W2K box, according to iwconfig.
Both machines are set to channel 10, network name "JUPITER".
Client Manager confirms this on the W2K side, and iwconfig does
the same on RH7.2.
Both machines have been assigned IP addresses in a local 10-block.
Encryption is turned off on both sides until I get wireless up.
W2K machine is set for "Peer to peer" mode, RH7.2 is "Ad-hoc"
mode, which I assume is the same thing.
Here's the spec from both sides of the divide:
W2K machine --
station name "CALLISTO"
RH7.2 machine --
station name "GANYMEDE"
And relevant dumps from both machines, Windoze first:
Windows 2000 IP Configuration
Ethernet adapter Local Area Connection 7:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 10.255.255.8
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 02 2d 0d 88 c7 ...... ORINOCO PC Card
Network Destination Netmask Gateway Interface Metric
10.255.255.0 255.255.255.0 10.255.255.8 10.255.255.8 1
10.255.255.8 255.255.255.255 127.0.0.1 127.0.0.1 1
10.255.255.255 255.255.255.255 10.255.255.8 10.255.255.8 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
220.127.116.11 18.104.22.168 10.255.255.8 10.255.255.8 1
255.255.255.255 255.255.255.255 10.255.255.8 10.255.255.8 1
And here's how it looks from the Linux side:
eth0 Link encap:Ethernet HWaddr 00:02:2D:08:BE:2D
inet addr:10.255.255.3 Bcast:10.255.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:148 errors:0 dropped:0 overruns:0 frame:0
TX packets:148 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:9618 (9.3 Kb) TX bytes:9618 (9.3 Kb)
lo no wireless extensions.
eth0 IEEE 802.11-DS ESSID:"JUPITER" Nickname:"GANYMEDE"
Mode:Ad-Hoc Frequency:2.457GHz Cell: 02:02:2D:0D:88:C7
Bit Rate:2Mb/s Tx-Power=15 dBm Sensitivity:1/3
RTS thr:off Fragment thr:off
Link Quality:0/92 Signal level:-102 dBm Noise level:-102 dBm
Rx invalid nwid:0 invalid crypt:0 invalid misc:0
Inter-| sta-| Quality | Discarded packets
face | tus | link level noise | nwid crypt misc
eth0: 0000 0. 154. 154. 0 0 0
Those "link quality" readings under Linux are perturbing. I have
been combing the documentation trying to figure out if that means
there's no effective throughput. They haven't made that very clear.
Anyone's assistance would be quite gratefully welcomed.