Devices Slow to Access Internet

Devices Slow to Access Internet

Devices Slow to Access Internet
Devices Slow to Access Internet
2024-07-29 00:42:26 - last edited 2024-07-30 01:07:45
Model: ER7212PC  
Hardware Version: V1
Firmware Version: 5.8.38

Good Morning All, 

 

A bit of a strange issue I'm hoping to get some assistance with. 

 

I have an ER7212PC with 3 access Points, EAP650, EAP650-OUTDOOR, EAP615-WALL. 

 

Internet is Dynamic IP and at that level I have 1.1.1.1 and 8.8.8.8 set as the DNS Servers. 

 

I have two networks (interfaces) configured

LAN is the default, Vlan ID 1. 192.168.0.x

IoT is the second, Vlan ID 9. 192.168.1.x

Both use a self hosted DNS server at 192.168.x.254.

Dhcp enabled on both. 

Ipv6 disabled on both. 

 

Ports to the APs are configured to carry both VLANs

 

I have two WLANs, "Home" and "IoT". 

Home has no VLAN configured.

IoT is configured to Vlan 9.

 

 

There is one ACL in place, blocking traffic from Vlan 9 to Vlan 1.

 

For the most part, everything is working as intended. Both networks have internet access. Both distribute ips, my self hosted dns is working. Devices on Vlan 9 cannot see anything on Vlan 1.

 

 

Now the issues:

 

Some devices, wireless or wired (via the 615-wall) will take ~2 minutes to establish an internet connection on the LAN/Home network/Wireless. 

During this time, I can ping the gateway (192.168.0.1), but pinging 1.1.1.1 will fail. The device gets a valid ip via dhcp and correct gateway/dns information. 

Eventually 1.1.1.1 will start responding. 

Ive only tested this part with wifi as I don't have many IoT ports available, but if I  disconnect a wireless device from Home while it is in this weird state, and connect to IoT, it gets internet connectivity immediately. 

Swapping back to home, same issue. 

 

 

Another, less pressing issue, is that 802.11r was causing a Samsung device to have a ~5s delay in loading webpages. Disabling 802.11r has resolved that, but I would like to keep it enabled. 

 

Final, also minor issue, devices (I.e. my phone), seem to be getting ipv6 addresses even though it is disabled at the interface (ipv6 interface = none). 

 

 

Anyway, for the more pressing issue. Things i have tried:

Setting the Vlan ID of "Home" wifi to 1. This caused internet to drop out. 

Setting dns to 1.1.1.1 and 8.8.8.8 at all locations. No change. 

Disabling acls. No change. 

 

Things that may be relevant:

The IoT vlan/wifi was only added recently. Prior to this, both the 802.11r issue and the delay connecting to internet issue were not seen. 

The issues have only started since adding the IoT vlan/wifi. 

 

I'm hesitant to reconfigure my whole network. I have a feeling though that if I created a new network interface i.e. "Home" on a new vlan, and put the Home wifi onto that new vlan, I'd be ok. 

 

 

I'm holding off on that until I get some feedback here though. 99% sure I've just made a mistake in the config and someone here can help me fix it. 

 

Thanks in advance. 

 

  0      
  0      
#1
Options
1 Accepted Solution
Re:Devices Slow to Access Internet-Solution
2024-07-29 07:31:05 - last edited 2024-07-30 01:07:45

  @Clive_A 

 

Hi Clive,

 

Thanks for your assistance.

I've decided to just separate the default "LAN" network (VLAN ID 1) into a management network for Omada devices on a new subnet, and created a new interface "Home" on VLAN ID 2 (similar to the working IoT network). This was probably the 'correct' thing to do in the first place but I was being lazy.

 

This seems to be working so far, none of the devices on the new interface have had any delays pinging the internet. 

 

If the issue returns I will draw a network diagram and seek your assistance.

 

Appreciate if you can leave the case open for a couple of weeks in case the issue returns.

 

Thanks

Recommended Solution
  1  
  1  
#5
Options
4 Reply
Re:Devices Slow to Access Internet
2024-07-29 01:51:48

Hi @Mmee 

Thanks for posting in our business forum.

Huh.. Self-hosted DNS server 192.168.x.254? What do you mean? Is it a typo?

 

If the ping to the 1.1.1.1 fails, you should check the Internet connection. This is not a problem with the LAN.

As long as the LAN ping to 192.168.0.1 is good and with low latency, then this is not a problem residing in the LAN.

At most, you swap with the cables.

 

As for the fast roaming issue, please create a separate discussion on the EAP page about this. I don't have a comment on this as I am not the specialist for the EAP.

A generic knowledge, if the Fast Roaming is enabled, and your EAPs are placed in the proper position/place, they will perform pretty well. You have to know the RSSI threshold and make sure the signal can be disconnected. The positioning and picking up the places of the EAP installation are pretty important. The rest of the software-level stuff is just enable/disable.

 

I am now not suspecting there is an issue with the DNS as the ping does not well with the a plain IP address, which indicates it is a problem with the Internet/WAN. Possibly a problem with the cables.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
  2  
  2  
#2
Options
Re:Devices Slow to Access Internet
2024-07-29 02:58:30

  @Clive_A 

 

Hi Clive, 

 

It is not an issue with the internet. 

As mentioned, disconnecting from the Home network and connecting to the IoT network results in an immediate connection (ping to 1.1.1.1 responds immediately). 

Swapping back to Home will again take a couple of minutes before 1.1.1.1 responds. 

 

 

Self-hosted dns at 192.168.x.254 - I mean there is a dns server for each vlan (192.168.0.254 and 192.168.1.254, as the ER7212PC does not allow an acl rule for a single destination/port between VLANs). 

 

I agree that DNS shouldn't be an issue as I am attempting to ping the IP directly. 

  0  
  0  
#3
Options
Re:Devices Slow to Access Internet
2024-07-29 05:42:58

Hi @Mmee 

Thanks for posting in our business forum.

Mmee wrote

  @Clive_A 

 

Hi Clive, 

 

It is not an issue with the internet. 

As mentioned, disconnecting from the Home network and connecting to the IoT network results in an immediate connection (ping to 1.1.1.1 responds immediately). 

Swapping back to Home will again take a couple of minutes before 1.1.1.1 responds. 

 

 

Self-hosted dns at 192.168.x.254 - I mean there is a dns server for each vlan (192.168.0.254 and 192.168.1.254, as the ER7212PC does not allow an acl rule for a single destination/port between VLANs). 

 

I agree that DNS shouldn't be an issue as I am attempting to ping the IP directly. 

Is it up-to-date? The firmware of the ER7212PC. What's the current firmware?

Try to keep it in the latest firmware and see if it can work properly or not.

 

Can you draw a diagram for me to understand your network? The VLAN and the configs matter a lot.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
  1  
  1  
#4
Options
Re:Devices Slow to Access Internet-Solution
2024-07-29 07:31:05 - last edited 2024-07-30 01:07:45

  @Clive_A 

 

Hi Clive,

 

Thanks for your assistance.

I've decided to just separate the default "LAN" network (VLAN ID 1) into a management network for Omada devices on a new subnet, and created a new interface "Home" on VLAN ID 2 (similar to the working IoT network). This was probably the 'correct' thing to do in the first place but I was being lazy.

 

This seems to be working so far, none of the devices on the new interface have had any delays pinging the internet. 

 

If the issue returns I will draw a network diagram and seek your assistance.

 

Appreciate if you can leave the case open for a couple of weeks in case the issue returns.

 

Thanks

Recommended Solution
  1  
  1  
#5
Options

Information

Helpful: 0

Views: 299

Replies: 4

Related Articles