Unwanted AP activity from client bridge?

[Mike S.]

After 10 years I'm still a novice at this, but I've managed to keep a home
network running for internet access. Lately we have an ASUS router
connected to a cable modem, with one wired and several wireless clients.
One of the wireless clients is at the fringe of of the router's coverage,
using an old Linksys ethernet bridge plugged into a desktop PC.

Last week that ethernet bridge died. Even with a directional antenna,
reception had been spotty, so I replaced the bridge with an Engenius ECB-150
multifunction device (which has a more powerful transmitter) running in
client bridge mode. It worked very well for that PC, giving much more
solid wireless connectivity to the router. Then the problems started.

Other PC's within the house started having intermittent loss of
connectivity. It seemed like wireless inferference until tonight, when I
discovered that the computer that is hardwired to the router could not
connect either. Trying to sort things out using the wired PC, I tried
to access the router's configuration page at 192.168.1.1, and instead
got the login page for the ECB150! (Yes they're at the same address).
When I powered down the client bridge, everything went back to normal.

So it seems that the client bridge is also acting as an access point, and
devices in the house are connecting to it (even through the wired router)
instead of the ASUS. How can that be ... isn't that the opposite of what a
bridge is supposed to do?

More important - how can I fix this so that the ECB150 only works to
bridge the PC it's connected, as the old Linksys did? Would appreciate any
suggestions - thanks!

[Char Jackson]

On Thu, 18 Apr 2013 23:02:18 +0000 (UTC), rets...@xinap.moc (Mike S.)
wrote:

I would assign it a unique IP address as a first step, using an address in
your current LAN but outside of your router's DHCP scope.

Next, I would put the new device into Client Bridge mode. It sounds like
you've selected one of the other modes, a couple of which enable a DHCP
server, which is not what you want.

[Mike S.]

In article <v1k1n85tnqu1vh792...@4ax.com>,

Yes, that makes sense and should avoid them steeping on each other.

>Next, I would put the new device into Client Bridge mode. It sounds like
>you've selected one of the other modes, a couple of which enable a DHCP
>server, which is not what you want.

It absolutely is in client bridge mode; in fact, that is the default
out-of-box operation mode and it says so clearly on the status screen.

[Char Jackson]

On Fri, 19 Apr 2013 11:34:57 +0000 (UTC), rets...@xinap.moc (Mike S.)

In that case, with the AP and the router both using the same IP address,
what looks like a loss of connectivity is probably just the new AP
responding to ARP traffic faster than the router for certain PC's on the
network, making those PC's think that the AP is the Internet gateway when
it's not. Changing the AP's IP address should fix things.

[Mike S.]

In article <k4k6n853qm983ie9l...@4ax.com>,

Looks like you nailed it.

I set the base address of the bridge outside the DHCP range of the router,
and the problem disappeared.

Many thanks for steering my in the right direction.

[Char Jackson]

On Mon, 22 Apr 2013 17:43:45 +0000 (UTC), rets...@xinap.moc (Mike S.)
wrote:

>

Excellent. Glad you got it working.