Re: PMTU vs device MTU and Frag decisions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I think I want something like this. I would think that dev
should point to the output device by here.
Or should it be skb->dst->dev->mtu?


static inline int ip_send(struct sk_buff *skb)
{
-	if (skb->len > skb->dst->pmtu)
+	if ( FRAG_NEXT_HOP ? (skb->len > skb->dev->mtu) : (skb->len > skb->dst->pmtu) )
		return ip_fragment(skb, ip_finish_output);
	else
		return ip_finish_output(skb);
}

On Thu, Jun 07, 2001 at 04:28:52AM +0100, Glynn Clements wrote:
> 
> andrew may wrote:
> 
> > So even though the PMTU from end to end may be smaller than the MTU
> > for the next hop, I still don't want to fragment until after going
> > through the next hop. After that it will be fine to fragment the 
> > packet as needed.
> 
> 	sysctl -w net/ipv4/ip_no_pmtu_disc=1
> 
> -- 
> Glynn Clements <glynn.clements@virgin.net>
> -
> : send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.kernel.org
> 
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux