[MLB-WIRELESS] replacement for a dlink900+

Robert Tchia robert.tchia at palantir.com.au
Fri Jul 18 02:31:48 EST 2003


I have my 900+ set to client mode and I seem to get requested timed out
as well. But when I changed the basic rates to a higher setting, all
packets are delivered.


Cheers
Rob

> -----Original Message-----
> From: owner-melbwireless at wireless.org.au [mailto:owner-
> melbwireless at wireless.org.au] On Behalf Of David Ng
> Sent: Thursday, 17 July 2003 12:14 AM
> To: Melb Wireless
> Subject: Re: [MLB-WIRELESS] replacement for a dlink900+
> 
> I assume 10.10.144.130 is the eth address of the AP?
> 
> Yeah I get that problem sometimes.  Are you running in bridge mode or
> AP/client mode?
> I find that when the AP is busy processing or forwarding something, it
> hangs
> momentiarly (ie stops responding), so the eth pings dont get replied
by
> the
> AP.  It also happens when the tx rates are set too high (maybe the AP
is
> trying to step down to a lower speed), try lowering them.
> 
> I've had lots of little problems with the 900AP+, running two units in
> AP/client mode causes all sorts of headaches like dropouts, etc, but
> running
> them back to back in brg mode seems ok.
> 
> Regards,
> David
> 
> ----- Original Message -----
> From: "rick" <mibz at optushome.com.au>
> To: "Melb Wireless" <melbwireless at wireless.org.au>
> Sent: Wednesday, July 16, 2003 11:54 PM
> Subject: [MLB-WIRELESS] replacement for a dlink900+
> 
> 
> > i seam to be having alot of problems with my dlink900+ im after
> something
> i
> > can have full control thru a web interface like the dlink900+ it
doesnt
> have
> > to be 22mb
> >
> > there is NOTHING wrong with the wireless side only with the eth side
> where
> > im getting alot of loss
> >
> > any ideas (see below for pings)
> >
> > Pinging 10.10.144.130 with 32 bytes of data:
> >
> > Reply from 10.10.144.130: bytes=32 time<1ms TTL=127
> > Request timed out.
> > Request timed out.
> > Reply from 10.10.144.130: bytes=32 time<1ms TTL=127
> > Request timed out.
> > Reply from 10.10.144.130: bytes=32 time<1ms TTL=127
> > Reply from 10.10.144.130: bytes=32 time<1ms TTL=127
> > Reply from 10.10.144.130: bytes=32 time<1ms TTL=127
> > Reply from 10.10.144.130: bytes=32 time<1ms TTL=127
> > Request timed out.
> > Reply from 10.10.144.130: bytes=32 time<1ms TTL=127
> > Reply from 10.10.144.130: bytes=32 time<1ms TTL=127
> > Reply from 10.10.144.130: bytes=32 time<1ms TTL=127
> > Reply from 10.10.144.130: bytes=32 time<1ms TTL=127
> >
> > Ping statistics for 10.10.144.130:
> >     Packets: Sent = 14, Received = 10, Lost = 4 (28% loss),
> > Approximate round trip times in milli-seconds:
> >     Minimum = 0ms, Maximum = 0ms, Average = 0ms
> > Control-C
> > ^C
> > C:\Documents and Settings\rik>
> >
> >
> >
> > 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



More information about the Melbwireless mailing list