The addtron access point's serial port is actually _unused_ as of right now.
they're still developing the firmware to allow the use of the serial port.

As far as getting it configged properly, just use the WLAN AP utility for
windows. that will work regardless of whether the AP has an IP address or
not. it will let you assign a temporary IP, and then you can use the web
interface on the AP to finish configuring it.
BTW this AP is based on a x86 (AMD Elan family). Maybe someone could port an
embedded loonix distro/wlan-ng to it ;)

regards,

Vlad

-----Original Message-----
From: owner-linux-wlan-develnightsky.com
[mailto:owner-linux-wlan-develnightsky.com]On Behalf Of Terry Griffin
Sent: Tuesday, January 09, 2001 10:24 PM
To: linux-wlan-develabsoval.com
Subject: Re: [lwlan-devel]: Addtron Access Point serial port

Just to follow up on my own post, I checked the DHCP log files and the
Addtron AWS-100 access point reports its own host name as "DHCPCLIENT"
in its DHCP request. This is the name that would show up in your DNS tables
if you had dynamic DNS.

I can think of better names that they could have used. AWS100 would have
been
nice. Being able to configure it would have been even better, but the name
DHCPCLIENT is probably hardcoded in some piece of off-the-shelf firmware
that
has no idea what sort of box it might end up in.

On Tuesday 09 January 2001 17:40, you wrote:
> The Addtron Access Point's serial port connection uses some proprietary
> protocol. You have to use the Windows utility if you want to talk to it
> over a null modem cable.
>
> On the DHCP problem, I configured the DHCP server to always give the same
> IP address out to the Access Point's ethernet address. That effectively
> gives the Access Point a fixed IP address without having to configure it
> with the proprietary Windows utility.
>
> Also, if your DHCP server supports dynamic DNS, you should be able to
> connect to your access point by name. Unfortunately I can't recall the
> host name reported by the Access Point in its DHCP request. I can check
> the logs next time I get near them. If you have more than one Access Point
> though then you've got problems. I think they all report the same name and
> so which ever one gets to the DHCP/DNS server last wins the right to the
> name in the DNS table.
>
> Terry
>
> > The addtron Access point has a serial port on it.
> >
> > I tried connecting to it vial null and passthrough, but got nothing.
> > Does anyone know what it does?
> >
> > I can not seem to find the access point on my local LAN. I am afraid
> > DHCP gave its IP out again. nmap does not show it, yet the wireless
> > works fine....
> >
> > --
> > Zot O'Connor
> > --------------------------------------------------
> > Linux WLAN Developer's List
> > For more information about this list see:
> > http://www.absoval.com/linux-wlan/lists.html
--------------------------------------------------
Linux WLAN Developer's List
For more information about this list see:
http://www.absoval.com/linux-wlan/lists.html

--------------------------------------------------
Linux WLAN Developer's List
For more information about this list see:
http://www.absoval.com/linux-wlan/lists.html

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]