Business Community > Routers > ER605 Reporting BUG - doesn't report wired VLAN clients egressing via L2TP
< Routers

ER605 Reporting BUG - doesn't report wired VLAN clients egressing via L2TP

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

ER605 Reporting BUG - doesn't report wired VLAN clients egressing via L2TP

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
ER605 Reporting BUG - doesn't report wired VLAN clients egressing via L2TP
ER605 Reporting BUG - doesn't report wired VLAN clients egressing via L2TP
2022-07-12 13:41:55 - last edited 2022-08-31 03:39:44
Model: ER605 (TL-R605)  
Hardware Version: V1
Firmware Version: 1.2.0

My setup is

 

FTTH ONT->ER605->SG2008P->OC200 (etc.)

 

I have configured a VLAN which is attached to a guest SSID and has a WAN policy route via an L2TP VPN.  Wireless clients connected to the guest SSID are recognized and reported correctly.  However, I have two LAN ports on the ER605 (WAN3 + LAN) which are configured to belong the same VLAN and wired clients connected to these ports are NOT recognized nor reported on as clients, nor is the traffic they generate reported via the OC200 in Dashboard->Summary graphs (ie ISP Load etc.).

<< Paying it forward, one juicy problem at a time... >>
  0      
 
  0      
 
#1
Options
3 Reply
Re:ER605 Reporting BUG - doesn't report wired VLAN clients egressing via L2TP
2022-07-13 08:07:57 - last edited 2022-08-31 03:39:44

  @d0ugmac1 

 

If you reboot the controller does that fix the problem?
Does this problem occur after you set up a guest network or VLAN?
Was it displayed normally before?
Are you connecting to two clients that are powered on and transmitting data?

Just striving to develop myself while helping others.
  0  
  0  
#2
Options
Re:ER605 Reporting BUG - doesn't report wired VLAN clients egressing via L2TP
2022-07-13 15:33:27 - last edited 2022-08-31 03:39:44
My ER605 went la-la and had to be rebooted. This caused another bug whereby the VLAN'd device hardwired to the switch jumps onto the wrong VLAN when rebooted (LAN port cannot be removed from VLAN1). So it will be a while before I can recreate the conditions and provide more detail on this one. The problem occurs on a device hardwired to the ER605 which is assigned an IP belonging to a non-default VLAN which is also considered a Guest network, and whose uplink is via an L2TP tunnel.
<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#3
Options
Re:ER605 Reporting BUG - doesn't report wired VLAN clients egressing via L2TP
2022-08-03 13:02:43 - last edited 2022-08-31 03:39:44

  @d0ugmac1 

 

With the device hardwired to an SG2008P port instead of the ER605 port, the usage reporting is correct (OC200 v 5.3.2, ER605 1.2.1)

 

Until we have more flexibility with the 4 LAN-capable ports on the ER605 (ie remove VLAN1), I cannot revert my setup to test further.

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#4
Options

Information

Helpful: 0

Views: 323

Replies: 3

Related Articles
Bug report: ACL rules cannot be created or edited in ER605's latest firmware, in standalone mode.
1292 0
WAN doesn't connect to ER605
8348 0
ER605 disconnect issue when moving ER605 to MGMT VLAN
890 0
SSID with VLAN doesn't work
381 0
ER605 DHCP doesn't work out of the box
1103 2
ER605 does not assign IP to VLAN clinets
1073 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.