Microchip-Ethernet / EVB-KSZ9477

Repository for using Microchip EVB-KSZ9477 board. Product Supported: KSZ9477, KSZ9567, KSZ9897, KSZ9896, KSZ8567, KSZ8565, KSZ9893, KSZ9563, KSZ8563, LAN9646, Phys(KSZ9031/9131, LAN8770
76 stars 79 forks source link

Ping is success but cant browse #73

Open ashikP6 opened 3 years ago

ashikP6 commented 3 years ago

Hi I am not sure this has to do something with the driver. I am using ksz9896 on my board and I used 4.9 kernel ksz9477 dsa driver. I was able to load the driver successfully and i can ping to any network. But when i browse from browsers such as chrome or falkon I am getting the error "This site cant be reached". I tried ping google.com and is successful.

If i use this driver https://github.com/Microchip-Ethernet/EVB-KSZ9477/tree/0802dd40dc391aa580d15c59cbc0203eb8c699bc/KSZ/linux-drivers/ksz9897/linux-4.9/drivers/net/ethernet/micrel there is no issue. The issue is seen only while using the ksz9477 dsa driver.

Does it have to do something with driver?

ashikP6 commented 2 years ago

Hi All, I debugged further. When I change MTU to 1428 the above issue is solved but when the mtu is 1500 connection timed out error is coming.

triha2work commented 2 years ago

What is the MAC driver you are using? Most modern MAC can handle 1580 bytes so I think the problem is not caused by the switch. For testing you can use ping with the parameters "-s " to send large packets. If ping does not have issue then the problem is probably caused by the router that connects to Internet. The maximum ping size is about 65500. You can use that and the actual frame size may be 1498.

ewhac commented 2 years ago

Hi All, I debugged further. When I change MTU to 1428 the above issue is solved but when the mtu is 1500 connection timed out error is coming.

You noticed this, too...

Some Wireshark dumps suggested that 1500-byte packets were being dropped at the driver level -- Wireshark never saw them. However, 1428-byte packets (LTE frame size) are captured and passed correctly.

I seriously doubt it's a router issue, as nothing else we've plugged in to it -- all of which advertising 1500-byte MTUs -- has had this problem.

I don't know offhand what MAC driver we're using; will look in to that.