[cisco-nas] Windows 10 with AS5400

[Aaron Leonard]

Thanks for the input Juergen ... it's good to get feedback from the 
"real world".

I will note that, in Cisco Unified Wireless, our access points can 
perform MSS adust ... and, starting in the 8.5 release later this year, 
we will set it to 1250 by default.  (On the theory that that should work 
well in virtually all topologies, with minimal performance degradation 
vs. an MSS of say 1400.)

Cheers,

Aaron

------------------------------------------------------------------------

On 6/9/2017 12:02 AM, cnsp at marenda.net (Juergen Marenda) wrote:
>
> Hi,
>
> Remember to set it on both/all interfaces, WANs and LANs
>
> (don't know weather it’s a bug or feature, but it helped).
>
> I tend to use (very conservative) 2**10+2**8 = 1280 since that fits 
> most environments
>
> (L2TP relayed PPPoE Broadband access with IPsec Tunnel for example)
>
> and is a “well known” value cause of display resolutions ;-)
>
> I don’t set it in the core, only  on edge and CPEs since the core
>
> should not be loaded with traffic inspection or tcp-handshake-interaction
>
> but forward packets fast.
>
> My 0.01 $,
>
> Juergen.
>
> *Von:*cisco-nas [mailto:cisco-nas-bounces at puck.nether.net] *Im Auftrag 
> von *Aaron Leonard
> *Gesendet:* Freitag, 9. Juni 2017 00:16
> *An:* Joseph Mays; cisco-nas at puck.nether.net
> *Betreff:* Re: [cisco-nas] Windows 10 with AS5400
>
> Joseph,
>
> As a matter of course, I always just set adjust-mss to 1300 (or 
> whatever my fancy is that day) on all edge routers, i.e. the routers 
> that are clients' first-hop gateways.
>
> You might not want to set it on your more core routers, because this 
> could impact performance.  (On the other hand, it might benefit 
> performance, if it allows you to avoid doing fragmentation [and even 
> worse, reassembly, if your routers are tunnel endpoints that do that 
> sort of thing.])
>
> Now, if you *only* see this problem on your dialup clients, then I 
> suppose you could be conservative and set it only on your 5400s.  But 
> I can tell you that I absolutely see this problem affecting Windows 10 
> Creators Update clients in other topologies (e.g. Wi-Fi, which is my 
> bailiwick nowadays.)
>
> Best regards,
>
> Aaron
>
> ------------------------------------------------------------------------
>
> On 6/8/2017 2:46 PM, mays at win.net <mailto:mays at win.net> (Joseph Mays) 
> wrote:
>
>     I meant to say they are all cisco routers.
>
>     *From:*Joseph Mays
>
>     *Sent:*Thursday, June 08, 2017 3:46 PM
>
>     *To:*cisco-nas at puck.nether.net <mailto:cisco-nas at puck.nether.net>
>
>     *Subject:*Re: [cisco-nas] Windows 10 with AS5400
>
>     Thanks for the response! Trying all the client-side suggestions.
>     WRT this, though...
>
>       * on the infrastructure side, if a router in the affected
>         network path is a Cisco IOS router, then turn on TCP MSS
>         Adjust (set it to 1250 or 1360 or so.)
>
>     All the routers in the network path on our system are network
>     routers. Are you suggesting I turn this on for all of them, or
>     just on the AS5400 that answers the dialup connection?
>
>     ------------------------------------------------------------------------
>
>     _______________________________________________
>     cisco-nas mailing list
>     cisco-nas at puck.nether.net <mailto:cisco-nas at puck.nether.net>
>     https://puck.nether.net/mailman/listinfo/cisco-nas
>
>
>
>
>     _______________________________________________
>
>     cisco-nas mailing list
>
>     cisco-nas at puck.nether.net <mailto:cisco-nas at puck.nether.net>
>
>     https://puck.nether.net/mailman/listinfo/cisco-nas
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-nas/attachments/20170609/cbf3015a/attachment.html>