Hi all,
I'm posting this from a hotel which has a wireless AP (B+G) for guests.
It took me several hours to figure out how to get the connection working
with my 2.6.18 notebook -- works just fine with other guests' mswin machines.
WEP is used, and is set up and working just fine: I can access the AP's
built-in web interface without any troubles. But..
The AP has two MAC addresses:
# arping -c1 192.168.1.1 -I eth1
ARPING 192.168.1.1 from 192.168.1.53 eth1
Unicast reply from 192.168.1.1 [00:11:F5:BA:67:AA] 2.164ms
Unicast reply from 192.168.1.1 [00:11:F5:77:38:C2] 5.696ms
Sent 1 probes (1 broadcast(s))
Received 2 response(s)
#
The first MAC can connect locally to the AP, but not outside.
The second MAC can connect locally and/or outside.
Linux only seems to ever use the first (no good) MAC for the AP,
rather than the second. Whenever I try an outside access, the AP
sends a gratuitous ARP reply, telling my machine to use the other MAC.
This seems to be ignored by Linux, but heeded by Windows.
For now, I've just written a small script to detect such a situation,
and to set a static ARP mapping for the second MAC. This works, but is way
beyond "normal usage" for most people.
Surely there's a flag or something to have the kernel cope with this?
????
--
Mark Lord
Real-Time Remedies Inc.
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]