Delay before routing to LAN addresses

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

Delay before routing to LAN addresses

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Delay before routing to LAN addresses
Delay before routing to LAN addresses
2021-07-10 17:19:53
Model: Archer VR400  
Hardware Version: V3
Firmware Version: 1.3.0 0.9.1 v00a1.0 Build 201109 Rel.54507n

I use this router to connect to by ISP (Vodafone UK) and for wireless connections.

On my network I have a dedicated linux server which provides DHCP to the network and DNS. There are two other wireless access points configured on my network

 

The VR400 is configured with an address of 192.168.2.1, the linux server is 192.168.2.4.

 

When devices connect wirelessly to the VR400 there is a long delay (typically 10 minutes) between connecting and being able to connect to the server. this can be demonstrated by connecting a device and ping 192.168.2.1 responds immediately but ping 192.168.2.4 gets 100% packet loss for a few minutes. When I connect i can immediacy access "external" addresses (for example ping 8.8.8.8 responds), but because I cant access the server on 192.168.2.4 for a few minutes I have no DNS resolution so commands like ping bbc.co.uk fail.

 

The other wireless points on my network (both TP-Link Archer C7) allow full network access on connection (no delay).

 

Configuration wise I have turned DHCP off on all the routes.

 

Am I doing anything wrong or is there an issue with the VR400?

 

 

  0      
  0      
#1
Options
3 Reply
Re:Delay before routing to LAN addresses
2021-07-13 12:07:29 - last edited 2021-07-13 12:11:20

@Nick_19 

Hi, thank you very much for your feedback.

To be more specific, were you trying to say, when trying to connect the Wi-Fi of VR400, it took almost 10mins to get an IP address from Linux server?

Or it could connect to the Wi-Fi immediately, but within the next 10mins, it could not get internet service and ping 192.168.2.4, 100% lost?

And Could you please tell me how you connect the Linux and VR400+2*Archer C7 together?

By the way, how often did this issue repeat?

During the 10 minutes delay, could reboot the VR400 fix this issue?

  0  
  0  
#2
Options
Re:Delay before routing to LAN addresses
2021-07-15 17:46:39

@TP-Link 

So I've just tried connecting with my MacBook (running Mac OS 11.4).

It connected to the WiFi almost immediatly (it appeared to connect, disconecct and reconnect) and immediately obtained an IP adress of 192.168.2.48 (this is the same IP address it had when connected via an AP). It then showed the poor connectivity icon (an ! over the wifi symbol). I could ping 192.168.2.1 (the router) fine, but 192.168.2.4 (the linux server) got request timeout. After about 3 minutes (this time -- this period seems quite variable) pings to 192.168.2.4 started working fine, as did all other internet access.

 

Access point connection: I have a cable connection from one of the routers LAN ports to a switch. each of the access points is cable connected via cable to the switch.

 

I also have an RE300 range extender connected to the router (via WiFi)

 

The issue repeats every time I try to connect to this route. 

 

I will test if resetting the route solves the problem later.

  0  
  0  
#3
Options
Re:Delay before routing to LAN addresses
2021-07-17 11:07:44

@TP-Link I've just tried rebooting the VR400 at the start of the 10 minute deley while my MacBook was trying to connect to it. It connected as soon as the VR400 rebooted.

  0  
  0  
#4
Options