Hey,

Using your units as client mode in a growing community wireless network. The IP allocation has been broken into fairly small subnets to allow as much expansion as possible in the near future. Due to their price and features your units are very popular however there is one thing which would be fantastic if it could be implemented.

Currently, each node requires 2 IP's from the Allocation effectively 1/2'ing the amount of client nodes each WPOP can sustain. One for the AP/client and one for the external interface in the firewall/nat'ing machine.

What would be fantastic is if these units could do what another manufacturers DSL modems do (DSL-300), or similar. These modems get a local IP address as does the wired machine for configuration, however as soon as the unit connects to the network it passes the address assigned back to the interface that the modem is plugged in to, thus only requiring one IP from the range to be utilised. This also brings into question wether there was any thoughts of supporting DHCP in client mode as I have been informed by others that there is no option for selecting a DHCP assigned address in client mode? (I would confirm this however my unit turned into an under-massed paper weight when upgrading firmware and I am in the RMA process at the moment).

One last question! What do the units do when faced with IPv6? Is there even any layer 3 interpretation?

Cheers, Craig

Hi there,

We have asked for firmware requests like this before from our OEM and the response hasn't been hopeful. I doubt there will be any major features upgrades as all the focus has moved onto 802.11g of late (at least for this OEM).

I doubt the unit has any support for ipv6.

As for the IP allocation for the client mode I feel that the unit will still bridge packets even if the IP address assigned to it isn't in the bridged range. I think I tested this ages ago, mayby someone can confirm for us (or I will if noone else can but it will have to be next week).

For example, you could assign 192.168.0.1 to the AP and then bridge some other network over it. Of course you will have todo some static magic if you want to be able to access the administration interface (and unless you static route a whole "admin" network then only the client will be able to admin it's own AP).

Was that all garble ?

S.