TL-SG105E v2 - Web interface unresponsive - Config utility works

Re:TL-SG105E v2 - Web interface unresponsive - Config utility works
2018-01-29 11:10:09
I have a Canadian version C7(CA) and experiencing the same issues connnection a laptop with Qualcomm Atheros QCA61x4A adapter. Is there a Canadian version of the beta firmware that is supposed to fix the issue? Can a flash a US or EU version? Will it brick my router? What's the best course of actions for me?



โหลดจีคลับ
0
0
#12
Options
Re:TL-SG105E v2 - Web interface unresponsive - Config utility works
2018-01-30 00:12:35

Damoms wrote

I have a Canadian version C7(CA) and experiencing the same issues connnection a laptop with Qualcomm Atheros QCA61x4A adapter. Is there a Canadian version of the beta firmware that is supposed to fix the issue? Can a flash a US or EU version? Will it brick my router? What's the best course of actions for me?


There is nothing to fix on TP-Link's side, since this is a Windows-related bug. As for firmware for wireless equipment such as Archer C7 you should only use firmware appropriate for your region due to different regulatory conditions.
༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
0
0
#13
Options
Re:TL-SG105E v2 - Web interface unresponsive - Config utility works
2019-10-14 02:28:48

@80211WiGuy 

 

let me help all to understand why this happens. Magic word MTU.

 

The mandatory TCP packet length of hardware interfaces is 1500 bytes. IEEE802.1q VLAN  tagging adds 4 bytes. ANY browser will follow your NIC setting of 1500 bytes. So, the switch sends 1504 bytes while the NIC in the computer wants/understands 1500 bytes. The overhead of 4 bytes is seen as content of the next packet. But the header of 32 bytes is missing, so your browser waits for another 1496 bytes. Waiting forever...

 

There is a solution called TCP ADJUST-MSS (bytes). if this value is set for 1496 bytes + 4 bytes for VLAN tagging it works. it forces the switch to send the payload in 1496 bytes

 

The software does this and so does ANY hypervisor. Some flat OSses do this 'trick' with specific NIC drivers. Advanced drivers with VLAN Tagging like in hypervisors.

 

Fred

0
0
#14
Options