ER707-M2 v1.0 - Bugs/Winge

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

ER707-M2 v1.0 - Bugs/Winge

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
ER707-M2 v1.0 - Bugs/Winge
ER707-M2 v1.0 - Bugs/Winge
2024-05-01 11:10:25
Model: ER707-M2  
Hardware Version: V1
Firmware Version: 1.2.2

There is a bug.......  and a semi annoyance.

 

So....  ER707-M2 running 1.2.2 firmware.  Now I know IDS kills your speed, thats fine.....  so I had mine scheduled to only run between 1am-8am (when I am asleep) mostly......  as most attacks on our connection occur overnight.

 

That was fine, worked fine.  I presume it's just this latest firmware that has a bug.  Despite it ONLY being scheduled to run at that time it would seem it's on.  

 

I have gigabit net........ typically will speedtest around 930mbps down and 48ish up........  but this IDS thing.......  it'll run 160-300mbps.......  down and 48ísh up.  Despite it being on a schedule if I just TURN IT OFF........  speeds go back to 930/48.

 

And the second part........  my router has 2x 2.5G ports.........  but WAN1 is on a 2.5G port.......  why can't I move that WAN1 to a different port so I can free up another 2.5G port???

 

I only have gigabit net so I don't need it on a 2.5G port.....  

 

Thats my two cents.  

  0      
  0      
#1
Options
2 Reply
Re:ER707-M2 v1.0 - Bugs/Winge
2024-05-01 13:40:07 - last edited 2024-05-01 13:42:09

  @MrHC1983 

2.5G WAN1 is WAN only and cannot be changed. this is the default WAN for this device. that's probably why the port is called 2.5G WAN1 and not 2.5G WAN/LAN1

Why?? I do not know..

 

But that is perhaps because all routers must have at least 1 WAN port

 

  0  
  0  
#2
Options
Re:ER707-M2 v1.0 - Bugs/Winge
2024-05-02 13:56:07

  @MrHC1983 

 

Far more likely this is just a limitation of using commodity off-the-shelf SOC parts in the fabrication of TPlink gateways.  The (system on chip) SOC probably has a dedicated 2.5G port that the hardware engineers decided to wire directly to a port and the internal architecture of the SOC requires this port is always a WAN port.  Worst case, the standard 'router software' core being used for TPlink gateways, is dependent on assigning a single physical port as a dedicated WAN so that the underlying software modules used to build the 'router' like iptables, dnsmasq etc have an interface to bind to on startup.  Either way, never going to change.

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