Business Community > WiFi > No internet access for client after upgrade EAP225 from 2.3.0 to 2.6.1
< WiFi

No internet access for client after upgrade EAP225 from 2.3.0 to 2.6.1

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

No internet access for client after upgrade EAP225 from 2.3.0 to 2.6.1

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
No internet access for client after upgrade EAP225 from 2.3.0 to 2.6.1
No internet access for client after upgrade EAP225 from 2.3.0 to 2.6.1
2019-12-30 18:39:21 - last edited 2019-12-31 01:02:33
Model: AP200  
Hardware Version: V3
Firmware Version: 2.6.1

Hello Team,

 

We have 25 EAP225, everything was working fine wiht no issues.

 

We treid to setup portal and to do that, the sMB recomended us to upgraede our EAP225 to 2.6.1, the problem now our clients can't access internet no ip for them.

 

DHCP is good we already tested its setup in tplink switch T1600G-52PS

 

I connected new AP version 2.3.0 just to test and sucessfully conencted to internet.

 

What is the problem? is there a bug?

 

I also using tplink controller mode OC200 1.0 Firemware version 1.2.0 controller version 3.2.3

 

 

FOR Tshoot, i did all below:

 

1. Are the EAPs getting valid IP addresses from DHCP Server and showing as Connected on the Controller? YES
2. If you configure the valid static IP on your wireless clients after connecting to EAP's SSID, would it be able to ping the Controller and access internet? No, its also shown no internet access
3. Have you configured any advanced or other settings via Controller, like VLAN, Multi SSIDs, Band Steering or Airtime Fairness? We just have vlan 2 which is never changed
 

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:No internet access for client after upgrade EAP225 from 2.3.0 to 2.6.1-Solution
2019-12-30 21:37:26 - last edited 2019-12-31 01:02:33
Issue fixed after changing the switch ports to tagging instead of untagging, however i kept the upstream Firewall as untagged, thanks for your reply.
Recommended Solution
  0  
  0  
#3
Options
3 Reply
Re:No internet access for client after upgrade EAP225 from 2.3.0 to 2.6.1
2019-12-30 21:08:07

 

GCisco wrote 

1. Are the EAPs getting valid IP addresses from DHCP Server and showing as Connected on the Controller? YES
2. If you configure the valid static IP on your wireless clients after connecting to EAP's SSID, would it be able to ping the Controller and access internet? No, its also shown no internet access
3. Have you configured any advanced or other settings via Controller, like VLAN, Multi SSIDs, Band Steering or Airtime Fairness? We just have vlan 2 which is never changed

 

It's a bit too vague to state just »clients get no Internet« for a description of a malfunction between clients and the router. Can you narrow down the problem a bit further?

  • Can clients with a static IP ping the EAP?
  • Can they ping the switch?
  • Can they ping the controller?
  • Can they ping the router?

 

If so, basic connectivity is given.


You say you use VLAN 2 and clients don't get an IP dynamically using DHCP. Please describe how you use the VLAN.

  • Is the switch's DHCP server assigned to VLAN 2?
  • Is the SSID – or if Multi-SSID: are the SSIDs – assigned to the VLAN 2?
  • Is the VLAN 2 just the management VLAN for the EAPs?
  • Is the switch port of the switch to which the EAP is connected a tagged or an untagged member of VLAN 2?

 

 

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  1  
  1  
#2
Options
Re:No internet access for client after upgrade EAP225 from 2.3.0 to 2.6.1-Solution
2019-12-30 21:37:26 - last edited 2019-12-31 01:02:33
Issue fixed after changing the switch ports to tagging instead of untagging, however i kept the upstream Firewall as untagged, thanks for your reply.
Recommended Solution
  0  
  0  
#3
Options
Re:No internet access for client after upgrade EAP225 from 2.3.0 to 2.6.1
2019-12-30 22:43:02 - last edited 2019-12-30 22:52:23

 

GCisco wrote

Issue fixed after changing the switch ports to tagging instead of untagging, however i kept the upstream Firewall as untagged, thanks for your reply.

 

Ok, then it probably was this bug fixed in EAP225 firmware 2.4.0 released 2018-11-21 which made the difference between old v2.3.0 behavior versus v2.6.1 behavior:

  • Fixed the bug that wireless clients connected with 2.4G SSID of EAP may receive broadcast packets from other VLAN.

 

 

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#4
Options

Information

Helpful: 0

Views: 1607

Replies: 3

Related Articles
Single client gets no DHCP lease
587 0
About Us
Press
Copyright © TP-Link Corporation Limited. All rights reserved.