I setup the DHCP server on RE.
It gives IP to my sprinkler.

Communication is not working ...
The DHCP server IP range can't be changed. I changed from .90 to .99 and it change back always .100 - .199. (IP of sprinkler: 101).

Hmmm...

TIA,

WDS mode doesn't work at all.
On the status page everything seems good and wireless or wired connection don't work (maybe the wrong DHCP address range what I'm not able to change from the .100-.199 range).
Terrible. :-(

TIA,

aruzsi wrote

WDS mode doesn't work at all.
On the status page everything seems good and wireless or wired connection don't work (maybe the wrong DHCP address range what I'm not able to change from the .100-.199 range).
Terrible. :-(

TIA,

It means your main router doesn't support WDS Mode..
Are you using TL-WA750RE_V1? If yes, you can try the beta firmware: http://tp-link.com/resources/software/wa750rev1_en_3_15_8_up_boot(150503_proxySTA-beta.zip
Follow the Quick Setup Wizard to finish all the settings and I believe the problem will be resolved.

You're right! My AP isn't int AP with WDS mode. :-(
I'll test it soon.

Yes, my extender is _V1.
I'll test that beta firmware. Do I need the AP with WDS mode, too?

TIA,

aruzsi wrote

You're right! My AP isn't int AP with WDS mode. :-(
I'll test it soon.

Yes, my extender is _V1.
I'll test that beta firmware. Do I need the AP with WDS mode, too?

TIA,

No need for any changes in your AP now, just try the beta firmware then configure via the Quick Setup Wizard, check whether it works or not.

OK, I upgraded the firmware to the beta version. I haven't changed anything on the root AP.
It wasn't too easy because of the http://tplinkrepeater.net problem (I wasn't able to reach the extender with this URL) [I hate this "easy" solution instead of a default IP address ...] and something was changed with the MAC addresses all of the hosts which are connected through extender. The 1st. byte of the MAC was changed so my DHCP fix associations was wrong. OWRT's admin WEB page helped me a lot!
I think it is very confused now but I hope it will work and I can change the MAC->IP associations (when the recent lease times will be timed out).

Why had to change the MAC addresses? So now there is a MAC address printed on the back of the extender. I can see it on the Status page, too. The root AP said almost the same MAC address except the 1st byte which was changed from 30: to 36: ...

Checking the good working we have to wait 2-4 days.

The connection time to the root AP is longer than before upgrade.

TIA,

This is the 9th day as I upgraded to new firmware.
I haven't restarted the RE, yet! But ...

There are 2 MACs for my mobil tel in the system. One of them is the original and the other which was modified by RE (32:B5:C2:).
The problem is: if I'm moving out from the field of RE and connected to rootAP, I can't communicate to the hosts which are connected to RE's
ethernet port or the RE itself.

In the DHCP lease list there are 2 IPs for the mobil tel because of the 2 different MACs!!! So the roaming between the APs doesn't work seamless.

I don't understand this behaviour with the modified MAC-s.

TIA,

aruzsi wrote

This is the 9th day as I upgraded to new firmware.
I haven't restarted the RE, yet! But ...

There are 2 MACs for my mobil tel in the system. One of them is the original and the other which was modified by RE (32:B5:C2:).
The problem is: if I'm moving out from the field of RE and connected to rootAP, I can't communicate to the hosts which are connected to RE's
ethernet port or the RE itself.

In the DHCP lease list there are 2 IPs for the mobil tel because of the 2 different MACs!!! So the roaming between the APs doesn't work seamless.

I don't understand this behaviour with the modified MAC-s.

TIA,

The mode you're using in the beta firmware is called "Proxy Mode", it's an advanced mode which are used by most vendors now and also in the future.
You have found a feature that Proxy Mode has: RE will generate a virtual MAC address for its clients and communicate with router.
As the problem you mentioned: if I'm moving out from the field of RE and connected to rootAP, I can't communicate to the hosts which are connected to RE's ethernet port or the RE itself.
Usually it won't have this problem, do you have special settings in your router or RE.

At last, since it works ok than before, it's a good news indeed : )

Yes, it is working.

Now I switched on the MAC filter and the only one enabled device is the rootAP. I think it is just a workaround.
There isn't any special config in 2543ND root AP and RE.
AP is the DHCP server.
DHCP server is disabled on RE. Its IP address is dynamic from the root AP (MAC -> IP assoc.) and I think
that's all.

One thing: The problem is in RE somewhere because the firmware change was better.

TIA,