I can't get the extender's admin WEB page if I use reverse proxy or SSH port forwarding.

In this case you are trying to access the RE's web interface from a remote host of a remote IP.

1. Upgrade to the latest firmware from www.tp-link.com/en
2. The RE must have a correct IP address and gateway.

Test whether you can access it or not.
If unfortunately it says "you have no authority to access", no need to try anymore because most tplink firmware released later than March/2013 don't allow accessing web interface from another subnet in order to stop CSRF attack.

Recently some newer firmware have been using a new mechanism and again allow accessing web interface from another subnet. But I am not sure TL-WA750RE had got this update.

PS: tplinkrepeater.net has no difference with the IP address, if IP access fails, domain access fails too. If you don't want to use it just forget it, there is no way to disable.

Hi,

I think my extender is using the latest firmware. I can't check now because I can't connect to it but I will check it in some days.
RE gets its configuration by DHCP from the main router. I can ping it and I can see it in my wireless client list. Gateway is the main router (WDS peer?).

HTTPS would be the best not the restricted network reachning. Or SSH connection, or ...

I'm thinking OpenWRT firmware but a little bit afraid of it on RE. (I like OWRT on other TP-Link WiFi routers.)
I thought I couldn't disable it. :-( But how can I access the WEB management page? I use ssh -L ,,80 myrouter.foo.bar. If I type in my WEB browser http://localhost: I will redirect to tplinkrepeater.net...

I've got other problem with RE, too. For example something wrong DHCP REQUEST from a host which is connected to Ethernet port. The host disappears in 2 or 3 days after rebooting RE. If I reboot somehow the RE the host will be reachable again without any explicite operation with that host.

TIA,

I think my extender is using the latest firmware. I can't check now because I can't connect to it but I will check it in some days.
RE gets its configuration by DHCP from the main router. I can ping it and I can see it in my wireless client list. Gateway is the main router (WDS peer?).

That will be enough, you can just check whether you can access it or not someday.

I use ssh -L ,,80 myrouter.foo.bar. If I type in my WEB browser http://localhost: I will redirect to tplinkrepeater.net...

Now I am confused about your scenario. Does it look like this?
remote PC --------{ Internet }-----------router --------RE ----------LAN PC running SSH proxy service for the remote PC

I've got other problem with RE, too. For example something wrong DHCP REQUEST from a host which is connected to Ethernet port. The host disappears in 2 or 3 days after rebooting RE. If I reboot somehow the RE the host will be reachable again without any explicite operation with that host.

There are two modes on the RE. See http://forum.tp-link.com/showthread.php?78930-Pharos-MAXtream-introduction&p=156842&viewfull=1#post156842">this thread[URL="http://forum.tp-link.com/showthread.php?78930-Pharos-MAXtream-introduction&p=156842&viewfull=1#post156842 written by the forum admin.

By default it uses mode1 and behaves as a MAC layer proxy. The DHCP requests will be modified in mode 1, that is normal. What wrong DHCP REQUEST exactly you've seen?

Also, what do you mean by mentioned "the host disappeared", could you give some details about this issue?

coca koala wrote

Now I am confused about your scenario. Does it look like this?
remote PC --------{ Internet }-----------router --------RE ----------LAN PC running SSH proxy service for the remote PC

Almost perfect except:
Different direction.
I want to connect to RE from remote PC.

By default it uses mode1 and behaves as a MAC layer proxy. The DHCP requests will be modified in mode 1, that is normal. What wrong DHCP REQUEST exactly you've seen?
Also, what do you mean by mentioned "the host disappeared", could you give some details about this issue?

I don't know what is the problem.
I can see the DHCP REQUEST without answer. (by tcpdump on the main router which is the DHCP server, too)
When I reboot the RE the next REQUEST will be answered and everything will be good.
Disappear means: The leased time for LAN device expired. Wanted a new IP (or renew it because it is an assigned MAC-IP pairs) and the server didn't answer for its REQUEST packets until I restart (reboot) RE. Strange.
That LAN device is the only one which is connected to RE's Ethernet port but I can connect a new TP-Link WiFi router to test the situation (this router will be a simple test device which can communicate by IP and ask IP from DHCP server as the LAN device does).
Or I have to setup fix IP on LAN device or setup a separated DHCP pool in RE (DHCP server is disabled now!) give IP to LAN device instead of main router's DHCP server...

TIA,

There is problem with the WiFi connections when the DHCP problem appears (when I lost the connection to LAN device):

Mobil phones and my notebook is not able to connect to main router easily by WiFi! It seems to the WiFi devices try to connect to
RE not to main router. More strange.
If tRE was rebooted, everything is all right.
I think there is relation between the DHCP REQUEST and WiFi connection problem.

Before I reboot RE I can connect it. It means: I can reach it by WiFi because the Ethernet port was 'lost' that time and the LAN device had been lost. Reboot was given by from RE's WEB page.
(Between main router and RE there is just WiFi connection, of course.)

TIA,

So now we are discussing two different issues here

Issue 1: Trying to access RE from a remote PC on internet through a SSH proxy server in LAN.

Issue 2: Strange DHCP behavior and wireless issue.

I suggest you log into RE --> wireless menu and use mode 2

Yes, you're right, we've got 2 problems.

Yesterday evening I rebooted the RE. ASA the RE finished the reboot process the OpenSprinkler appered on the network (checking the ARP table of main router).

The firmware: 3.14.8 Build 140901 Rel60263n

What is the difference between mode 1 and 2?

I'm inside in my home network, now. I typed in my browser head line the host name of the extender and I arrived on the tplinkrepeater.net page again ... Terrible! Do I have to use the IP of the extender?

TIA,

OK, I switched to mode 2 (WDS mode?) from mode 1 (Universal mode?).

I'm not sure this was the problem.
In 2-3 days we will see the results.

TIA,

OK, in WDS mode after the reboot my sprinkler not answer to ping ...

TIA,

WDS mode is worse the Universal.
No IP address was given to sprinkler at all.
I disconnected RE from power connector, disconnected the LAN cable and nothing happened. Sprinkler tried to ask the IP and no answer. :-(

I've got some possibilities:

1. Fix IP to my sprinkler (I don't know how now.)
2. Setup DHCP server on RE
3. Test with an old TP-Link WiFi AP as DHCP client or with my notebook.