i have a laptop and a alpha multia system. its all i can do to make the
two cisco cards connect to one another. cisco implemented their own
/proc/drivers/aironet/ethX/ directory with a bunch of config files you
can write to or read from. but if you write the SSID file, it messes up
the iwconfig essid. iwconfig ethX essid 01:02:03:04:05:06 leaves you
with a complteely random essid no matter whats in the SSID file and no
matter what you hardcode your essid.
my current practice has been iwconfig ethX ap off; iwconfig ethX ap any
until both cards randomly decide to choose the same one. how am i
supposed to set up essid's?
sometimes i'll have the essid's matching, both cards will be on the same
subnet and they still fail to ping each other. snooping the connection,
assuming i can even get rf-mon snooping to actually snoop anything,
shows that often one system will actually be responding to pings, but
the first system marks the reply as having the wrong nwid, or so i'd
wager since ping is marking everything as packets lost. besides subnets
and essids, what do i need to match? for the life of me, i cant figure
out why they're not talking.
i bought this card because it was universally recommended as one of the
better supported cards in linux. unfortunately, it seems these
proprietary extensions break just about everything for ad-hoc mode. i'm
sure there's some way to use it, if someone could fill me in, i'd be
much obldged.
every once and again i can actually get bridging working to the extent
that i can connect to both sides of the bridge from the one ip address.
traffic doesnt flow across the bridge though. and, also problematic,
the wireless side of the bridge stops responding completely within ten
minutes. what a slap in the face. i'll be doing nothing except having
each system ping the other, and the connection will just drop.
what are the proper methods to get a cisco 350 connecting to another in
linux via ad-hoc?
Myren
|
Similar Threads
Linear Mode
