RE: End System PMTUD behavior question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: End System PMTUD behavior question
- To: "Mark_Andrews at isc.org" <Mark_Andrews at isc.org>
- Subject: RE: End System PMTUD behavior question
- From: "Dunn, Jeffrey H." <jdunn at mitre.org>
- Date: Fri, 23 Jan 2009 07:06:03 -0500
- Accept-language: en-US
- Acceptlanguage: en-US
- Cc: "Peter.Hunt at nokia.com" <Peter.Hunt at nokia.com>, "ipv6-bounces at ietf.org" <ipv6-bounces at ietf.org>, "Sherman, Kurt T." <ksherman at mitre.org>, "ipv6 at ietf.org" <ipv6 at ietf.org>, "Liou, Chern" <csliou at mitre.org>, "steve_eiserman at uscourts.gov" <steve_eiserman at uscourts.gov>, "Huang, Frank" <fhuang at mitre.org>, "v6ops at ops.ietf.org" <v6ops at ops.ietf.org>, "Grayeli, Parisa" <pgrayeli at mitre.org>
- Delivered-to: ietfarch-ipv6-archive at core3.amsl.com
- Delivered-to: ipv6 at core3.amsl.com
- In-reply-to: <200901230436.n0N4akbE042009 at drugs.dv.isc.org>
- List-archive: <http://www.ietf.org/pipermail/ipv6>
- List-help: <mailto:ipv6-request@ietf.org?subject=help>
- List-id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
- List-post: <mailto:ipv6@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
- References: Your message of "Thu, 22 Jan 2009 23:27:45 CDT." <3C6F21684E7C954193E6C7C4573B762701D3DD7186 at IMCMBX1.MITRE.ORG> <200901230436.n0N4akbE042009 at drugs.dv.isc.org>
- Sender: ipv6-bounces at ietf.org
- Thread-index: Acl9FDkLNonOErpYTFKHM4HeUN959AAPPtMg
- Thread-topic: End System PMTUD behavior question
Fair enough, it appears the short answer to which implementation you know of is BIND (I assume 9.x). With respect to IPV6_USE_MIN_MTU, I thought the value for this was 1280. If so, this simply circumvents PMTUD and uses the IPv6 minimum MTU.
Best Regards,
Jeffrey Dunn
Info Systems Eng., Lead
MITRE Corporation.
(301) 448-6965 (mobile)
-----Original Message-----
From: Mark_Andrews at isc.org [mailto:Mark_Andrews at isc.org]
Sent: Thursday, January 22, 2009 11:37 PM
To: Dunn, Jeffrey H.
Cc: Peter.Hunt at nokia.com; shemant at cisco.com; Huang, Frank; Sherman, Kurt T.; ipv6 at ietf.org; Liou, Chern; steve_eiserman at uscourts.gov; ipv6-bounces at ietf.org; v6ops at ops.ietf.org; Grayeli, Parisa
Subject: Re: End System PMTUD behavior question
In message <3C6F21684E7C954193E6C7C4573B762701D3DD7186 at IMCMBX1.MITRE.ORG>, "Dun
n, Jeffrey H." writes:
> Mark,
>
> Could you elaborate on what you mean by "DNS servers just tell the kernel t=
> o fragment at network mtu for UDP/IPv6 and ensure that DF is off for UDP/IP=
> v4." What is the "network MTU?" Also, to which implementations of DNS serv=
> er are you referring?
Cut-and-pasted from BIND's bsd socket implementation.
Mark
#ifdef IPV6_USE_MIN_MTU /* RFC 3542, not too common yet*/
/* use minimum MTU */
if (sock->pf == AF_INET6) {
(void)setsockopt(sock->fd, IPPROTO_IPV6,
IPV6_USE_MIN_MTU,
(void *)&on, sizeof(on));
}
#endif
#if defined(IP_MTU_DISCOVER) && defined(IP_PMTUDISC_DONT)
/*
* Turn off Path MTU discovery on IPv4/UDP sockets.
*/
if (sock->pf == AF_INET) {
int action = IP_PMTUDISC_DONT;
(void)setsockopt(sock->fd, IPPROTO_IP, IP_MTU_DISCOVER,
&action, sizeof(action));
}
#endif
#if defined(IP_DONTFRAG)
/*
* Turn off Path MTU discovery on IPv4/UDP sockets.
*/
if (sock->pf == AF_INET) {
int off = 0;
(void)setsockopt(sock->fd, IPPROTO_IP, IP_DONTFRAG,
&off, sizeof(off));
}
#endif
> Best Regards,=20
> =A0=20
> Jeffrey Dunn=20
> Info Systems Eng., Lead=20
> MITRE Corporation.
> (301) 448-6965 (mobile)
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews at isc.org
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 at ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.