midd:traffic_scheduling:project_log
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
midd:traffic_scheduling:project_log [2009/04/12 17:11] perryk |
midd:traffic_scheduling:project_log [2009/04/12 17:19] perryk |
||
|---|---|---|---|
| Line 123: | Line 123: | ||
| Learned some fascinating things about Windows networking. The metric you specify in the network settings doesn't do diddly. If you really want to change network metrics you have explicitly set metrics in the routing tables. I wrote a large TCP block sender plug-in. This caused a lot of opportunity to reassess the capture code. And, finally, caused a lot of pouring over wireshark captures comparing them to mine. This caused some learning about D-Link NIC options. Get this, in order to get fast performance with my NAS I enabled Jumbo packets (9KB). This is OK - as the NAS and my machine (and my switches) all understand Jumbo packets. The router doesn't so the negotiation between my machine and the router drops packet sizes back to normal for that path.. Turned out I had some other option on - Large Packet Offload. This is REALLY how large packets happen (32KB). But THIS OPTION doesn't get negotiated. So, when I blast something out to the Internet, I get huge numbers of retries because I'm sending 32KB segments with the Don't Fragment flag set. So now I understand and can reconcile wireshark to my server and client logs. But I can't get optimum performance to my NAS and the Internet at the same time. Spent 7 hours on this today. | Learned some fascinating things about Windows networking. The metric you specify in the network settings doesn't do diddly. If you really want to change network metrics you have explicitly set metrics in the routing tables. I wrote a large TCP block sender plug-in. This caused a lot of opportunity to reassess the capture code. And, finally, caused a lot of pouring over wireshark captures comparing them to mine. This caused some learning about D-Link NIC options. Get this, in order to get fast performance with my NAS I enabled Jumbo packets (9KB). This is OK - as the NAS and my machine (and my switches) all understand Jumbo packets. The router doesn't so the negotiation between my machine and the router drops packet sizes back to normal for that path.. Turned out I had some other option on - Large Packet Offload. This is REALLY how large packets happen (32KB). But THIS OPTION doesn't get negotiated. So, when I blast something out to the Internet, I get huge numbers of retries because I'm sending 32KB segments with the Don't Fragment flag set. So now I understand and can reconcile wireshark to my server and client logs. But I can't get optimum performance to my NAS and the Internet at the same time. Spent 7 hours on this today. | ||
| + | At this point I think the software is done to the point where meaningful capture is all there. Crud. I still have to send capture data from the server to the client when asked. I'll do this next. | ||
midd/traffic_scheduling/project_log.txt ยท Last modified: 2009/05/15 14:55 by afbarnard
Page Tools
