Re: kernel pppoe performance problems

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Mitja Muženič
Date: Wednesday, July 14, 2010 - 1:53 pm

First of all, do not reply to mails sent in private on a public list, it's
impolite and will expose my email address to more spam.

Second, man 4 pppoe says:

MTU/MSS ISSUES
     Problems can arise on machines with private IPs connecting to the Inter-
     net via a machine running both Network Address Translation (NAT) and
     pppoe.  Standard Ethernet uses a Maximum Transmission Unit (MTU) of 1500
     bytes, whereas PPPoE mechanisms need a further 8 bytes of overhead.
This
     leaves a maximum MTU of 1492.  pppoe sets the MTU on its interface to
     1492 as a matter of course.  However, machines connecting on a private
     LAN will still have their MTUs set to 1500, causing conflict.

     While pppoe(8) has an internal option, ``mssfixup'', which is enabled by
     default and takes care of this, pppoe users have to rely on other meth-
     ods.  Using a packet filter, the Maximum Segment Size (MSS) can be set
     (clamped) to the required value.  The following rule in pf.conf(5) would
     set the MSS to 1440:

           match on pppoe0 scrub (max-mss 1440)

     Although in theory the maximum MSS over a PPPoE interface is 1452 bytes,
     1440 appears to be a safer bet.  Note that setting the MSS this way can
     have undesirable effects, such as interfering with the OS detection fea-
     tures of pf(4).

which is definitely not "the same as man 8 pppoe".


Matt
It's
Of
it
is
ping
I
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
kernel pppoe performance problems, Matt S, (Wed Jul 14, 1:15 pm)
Re: kernel pppoe performance problems, Matt Schwartz, (Wed Jul 14, 1:41 pm)
Re: kernel pppoe performance problems, Mitja Muženič, (Wed Jul 14, 1:53 pm)