[MLB-WIRELESS] Linksys Alchemy-pre5.1 v2.07.1.8sv firmware question.

[Johnno]

OK, I seem to be getting somewhere now
for some strange reason it just connected ....hmmm

John

----- Original Message ----- 
From: "Andrew Leech" <a_leech at swin.edu.au>
To: "Johnno" <fromjohnno at hotmail.com>
Sent: Sunday, August 08, 2004 7:53 PM
Subject: Re: [MLB-WIRELESS] Linksys Alchemy-pre5.1 v2.07.1.8sv firmware
question.


> I'm currently using pre5.1 as well. so you're not getting the association
on the status page?
> The ap's I'm associating with are my uni's cisco ones, I don't have any
control over them, but yeah, as soon as I'm in range, it just picks it up.
> It might have something to do with the other settings on the
administration management page. I've got AP watchdog disabled, dhcpd
disabled, dns masq & local dns disabled, loopback enabled, 802.1x routing
enabled, upnp disabled. These are the only ones I think may make a
difference, but yeah not completely sure.
>
> Are you sitting right next to the associating ap? such that you can
absolutly rule out range issues. I've turned up my wireless power, but
haven't touched any other wireless advanced settings.
>
> Andrew
>
>
> On Sun, 8 Aug 2004 19:43:29 +1000, Johnno <fromjohnno at hotmail.com> wrote:
>
> > thx Andrew but still no go :(
> > I tried all combos, mixed, 54, 11....just wont connect
> > what ver firmware are you using there?
> >
> >
> > ----------------------------------
> > Regards
> > John
> > ----------------------------------
> >
> >
> > ----- Original Message -----
> > From: "Andrew Leech" <a_leech at swin.edu.au>
> > To: "Johnno" <fromjohnno at hotmail.com>
> > Cc: <melbwireless at wireless.org.au>
> > Sent: Sunday, August 08, 2004 6:53 PM
> > Subject: Re: [MLB-WIRELESS] Linksys Alchemy-pre5.1 v2.07.1.8sv firmware
> > question.
> >
> >
> >> I had difficulty getting it to work initially in client mode myself. It
> > was basically a trial and error method of getting this set up, as I
assume
> > you found out there is next to no info about it on the sveasoft pages.
> >>
> >> The ap I'm associating with has dhcp running, and I had to turn off the
> > dhcp server on the client mode wrt first, then enable client mode. Once
> > client mode is enabled, I made sure I had the exact ssid in the box, and
I
> > set the ip address in the box below to the ip of the ap associating
with.
> > When associating with an ap in B mode, not G, I had to explicitly set it
to
> > B mode rather than mixed.
> >>
> >> Then go to the status page, then on the wireless sub-page, it will
report
> > when it's associated and gives the signal strength and noise levels as a
> > bottom line called 'AP Signal'. THis line isn't there at all when not
> > associated.
> >>
> >> In client mode, the ap acts as a wireless bridge, so a computer plugged
> > into the switch on the back of the client mode ap can get dhcp from the
> > associated ap. Or if you're using static ip's, the computer set to the
same
> > subnet as the associated ap should be able to ping it.
> >>
> >> Hope this helps...I'm thinking your trouble might most likely be the B
> > mode rather than mixed setting, it caught me for some time.
> >>
> >> Andrew
> >>
> >>
> >> On Sun, 8 Aug 2004 17:31:05 +1000, Johnno <fromjohnno at hotmail.com>
wrote:
> >>
> >> > I'm using the above firmware on a Linksys wrt54g ver2
> >> > I am having trouble running it in client mode.....
> >> > just wont connect with the AP.
> >> >
> >> > anyone used it in client mode ?
> >> >
> >> >
> >> > John
> >> >
> >> > To unsubscribe: send mail to majordomo at wireless.org.au
> >> > with "unsubscribe melbwireless" in the body of the message
> >> >
> >> >
> >>
> >>
> >>
> >> To unsubscribe: send mail to majordomo at wireless.org.au
> >> with "unsubscribe melbwireless" in the body of the message
> >>
> >>
> >
>
>
>

To unsubscribe: send mail to majordomo at wireless.org.au
with "unsubscribe melbwireless" in the body of the message