DHCP does Not work

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

DHCP does Not work

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
25 Reply
Re:DHCP does Not work
2023-07-16 14:59:44

  @Fms_muc 

 

Hi,

 

Excuse me for jumping in, but after reading this whole thread I am getting the impression that you are trying to connect a repeater-type range extender directly to the wireless infrastructure of your Internet Service Provider. 

 

I would think that your ISP has put measures in place to prevent its customers from doing that.

 

Of course, using "WISP" mode, like @terziyski mentioned, is another matter, because from the ISP's side the WISP router would appear just as one single device.

 

  0  
  0  
#24
Options
Re:DHCP does Not work
2023-07-16 15:12:59

  @woozle 

i don't think so. 
 

As Bridge now it works, but DHCP request needs about 2 min to be answered. (Without c50 1 sec)

 

i assumed, that Smartip is working as Bridge (because dhcp off)  - and with Static IP with DHCP and NAT. That was wrong.

Would be a good Idea, if in TP-Link manuel there would be a hint, that it acts like a Bridge.

 

so i have to wait for a Firmware with WISP, because Devices like Google Nest requiries DHCP and NAT (Google Nest does Not Support captive Login)

  0  
  0  
#25
Options
Re:DHCP does Not work
2023-07-16 16:13:56

  @Fms_muc 

 

So, let's say you have client device A connected to the C50 (working in wireless range extender mode) and Internet is working fine.

 

Now you connect another client device, let's call it client device B, to the C50. After about two minutes client device B gets an IP address from the ISP's DHCP server and is then able to connect to the Internet. Right?

 

Question: Can both client devices A and B now concurrently browse the Internet or is client device A now without Internet access (for about two minutes, that is)?

 

  0  
  0  
#26
Options
Re:DHCP does Not work
2023-07-16 16:30:51

  @woozle

yes both can. For each is captive Login nessacery. DHCP answer through Range extender needs on Client a or Client b 2 Minutes. Sometimes even Time out.

without c50 dhcp request ist below 1sec

througput is about 50MBit (5GHz)

 

just now i am using two routers - the c50 for "normal Devices" where i Can do captive Login. The second router is an old 841n which do Not have Range extender or wisp und due of the old Hardware Revision.


But i installed dd wrt an now i can use Google Nest hub, because then  841n acts as "Wireless nat router". 

ok the Hardware of the old 841n is Slow and throughput is in due of 2.4 GHz only good for nesthub. (About 2MBit) For HD TV would This be to Slow.

 

Nevertheless,  i have a Solution for my Holidays in croatia, working but not optimal. Hope There will be a Firmware Update with wisp for the c50.

  0  
  0  
#27
Options
Re:DHCP does Not work
2023-07-16 19:01:09 - last edited 2023-07-16 19:03:43

  @Fms_muc 

 

Now that everything is clear regarding C50 'range-extender' mode bridge type connection, here are the routers that currently support WISP.

Only one of these supports 5GHz band - TL-WR902AC. As for the C50 new FW supporting WISP, only a TP-Link representative can elaborate on that.

If this was helpful click on the arrow pointing upward to make it blue. If this solves your issue, click the star to make it blue as a "Recommended Solution". Tips:149wubkkfoLmNDjDbiTxx4ZU8mpcMA5CJt
  1  
  1  
#28
Options