Blah, Cloud.

Adventures in architectures

  • Twitter
  • GitHub
  • Home
  • Blog
  • Kubernetes on vSphere
  • Multi-tenant IaaS Networking
  • Me
    • About
    • CV
    • Contact
Home » Blog » Networks » Enabling Mini Jumbo Frames (RFC4638) on OpenReach FTTC

Enabling Mini Jumbo Frames (RFC4638) on OpenReach FTTC

28/08/2016 by Myles Gray Leave a Comment

I swapped out my single Fortigate 100D at home a while back for a cluster of two in active/passive, as part of this migration, that I have written about before I needed to terminate any DHCP or PPPoE interfaces on a different piece of kit than the clustered firewalls.

I have had this in the lab for a while on a Cisco 2811 router set up pretty much exactly like I had in the previous article.

However, it came to my attention that OpenReach support RFC4638 (Mini Jumbo Frames) on their WAN, so I felt compelled to remove a few lines of config from my router to clean it up and gain whatever marginal benefit an extra 8 bytes of frame size will get me.

The current config looked like this (the parts that matter anyway):

interface FastEthernet0/0
 description FG_side
 ip address my.public.ip.address 255.255.255.248
 duplex auto
 speed 100
!
interface FastEthernet0/1
 description WAN_side
 no ip address
 duplex auto
 speed auto
 pppoe enable group global
 pppoe-client dial-pool-number 1
!
interface Dialer1
 ip unnumbered FastEthernet0/0
 ip mtu 1492
 encapsulation ppp
 ip tcp adjust-mss 1452
 dialer pool 1
 dialer idle-timeout 0
 dialer-group 1
 ppp authentication chap pap callin
 ppp chap hostname USERNAME HERE
 ppp chap password 7 PASSWORD
 ppp pap sent-username USERNAMEHERE password 7 PASSWORD
 no cdp enable
!

The RFC allows for you to send a standard 1500 byte ethernet frame over the WAN – so we need to increase the MTU on the WAN side interface and tell ppp to negotiate a MRU size of 1500 as it is larger than the 1492 standard:

interface fa 0/1
 mtu 1508
 pppoe-client ppp-max-payload 1500

And we can also now remove ip tcp adjust-mss and ip mtu from the dialler as no frames will need their size change when going over wan:

interface Dial 1
 no ip mtu 1492
 no ip tcp adjust-mss 1452

You can see from the ping below running during my change that we are now able to ping google.com at a 1472 (accoung for 28 byte overhead) MTU.

Mini Jumbo Frames Ping

Props to this thread, without it I wouldn’t have known OpenReach implemented this feature.

Why not follow @mylesagray on Twitter for more like this!

Show some love:

  • Reddit
  • Twitter
  • Pocket
  • LinkedIn
  • Email
  • Telegram

Similar things I've written

Filed Under: Networks Tagged With: bt, cisco, mtu, networking, wan

About Myles Gray

Hi! I'm Myles, and I'm a Dev Advocate at VMware. Focused primarily on content generation, product enablement and feedback from customers and field to engineering.

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Myles Gray

Hi! I'm Myles, and I'm a Dev Advocate at VMware. Focused primarily on content generation, product enablement and feedback from customers and field to engineering. Read More…

Categories

Tags

active directory authentication CBT cisco datastore dell design esxi fortigate iscsi jumbo frame kubernetes lab linux load-balancing lun md3000i mtu networking NginX nic nsx openSUSE osx pxe readynas san sdelete serial teaming ubuntu vcenter vcloud director vcsa vexpert video VIRL vmdk vmfs vmware vsan vsphere vsphere 6 vsphere beta windows

Subscribe to Blog via Email

Copyright © 2021 · News Pro Theme on Genesis Framework · WordPress · Log in

loading Cancel
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.