mtu 9000 issues only on tcp and not icmp possible?
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I have a connection between two datacenters and rsync between them stalls often. I think it is related to the mtu 9000 (I actualy set it to 8900 because of some possible vlan use)
I have the impression that the icmp mtu 8900 is working, but that tcp traffic is having sometimes problems with big frames.
Has any one experienced something similar? And how do you test MTU 8900 with just a tcp test?
PS. I don't have control over this connection
networking tcp ethernet icmp
asked Apr 28 at 17:53
f1 outsourcing
11
 |Â
show 3 more comments
up vote
0
down vote
favorite
I have a connection between two datacenters and rsync between them stalls often. I think it is related to the mtu 9000 (I actualy set it to 8900 because of some possible vlan use)
I have the impression that the icmp mtu 8900 is working, but that tcp traffic is having sometimes problems with big frames.
Has any one experienced something similar? And how do you test MTU 8900 with just a tcp test?
PS. I don't have control over this connection
networking tcp ethernet icmp
asked Apr 28 at 17:53
f1 outsourcing
11
Jumbo frames are only supposed to be used in a network where all the NICs are operating at jumbo frames, and mostly for a LAN network.
– Rui F Ribeiro
Apr 28 at 18:54
Have you tried reducing the MTU to see if the issue goes away? And/or have you tried doing a tcpdump on both sides when the issue is occurring to see if packets are making it through?
– Patrick
Apr 28 at 19:39
1
On a few *NIXes (Linux, some *BSD) it should even be possible to lower the MSS (which usually derives from MTU) for TCP without changing the jumbo frame settings: with iptables + TCPMSS on Linux, and pf + scrub max-mss on *BSD.
– A.B
Apr 28 at 20:13
1
@RuiFRibeiro, it is configured like this
– f1 outsourcing
May 2 at 8:01
1
@f1outsourcing If dropping the MTU fixed it, then yes, you should definitely do a packet capture. This smells like you have something in the mix which is dropping ICMP packets, which are critical to the operation of networks, especially when you have oversized frames.
– Patrick
May 2 at 11:11
 |Â
show 3 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a connection between two datacenters and rsync between them stalls often. I think it is related to the mtu 9000 (I actualy set it to 8900 because of some possible vlan use)
I have the impression that the icmp mtu 8900 is working, but that tcp traffic is having sometimes problems with big frames.
Has any one experienced something similar? And how do you test MTU 8900 with just a tcp test?
PS. I don't have control over this connection
networking tcp ethernet icmp
asked Apr 28 at 17:53
f1 outsourcing
11
I have a connection between two datacenters and rsync between them stalls often. I think it is related to the mtu 9000 (I actualy set it to 8900 because of some possible vlan use)
I have the impression that the icmp mtu 8900 is working, but that tcp traffic is having sometimes problems with big frames.
Has any one experienced something similar? And how do you test MTU 8900 with just a tcp test?
PS. I don't have control over this connection
networking tcp ethernet icmp
asked Apr 28 at 17:53
f1 outsourcing
11
asked Apr 28 at 17:53
f1 outsourcing
11
asked Apr 28 at 17:53
f1 outsourcing
11
asked Apr 28 at 17:53
f1 outsourcing
11
11
Jumbo frames are only supposed to be used in a network where all the NICs are operating at jumbo frames, and mostly for a LAN network.
– Rui F Ribeiro
Apr 28 at 18:54
Have you tried reducing the MTU to see if the issue goes away? And/or have you tried doing a tcpdump on both sides when the issue is occurring to see if packets are making it through?
– Patrick
Apr 28 at 19:39
1
On a few *NIXes (Linux, some *BSD) it should even be possible to lower the MSS (which usually derives from MTU) for TCP without changing the jumbo frame settings: with iptables + TCPMSS on Linux, and pf + scrub max-mss on *BSD.
– A.B
Apr 28 at 20:13
1
@RuiFRibeiro, it is configured like this
– f1 outsourcing
May 2 at 8:01
1
@f1outsourcing If dropping the MTU fixed it, then yes, you should definitely do a packet capture. This smells like you have something in the mix which is dropping ICMP packets, which are critical to the operation of networks, especially when you have oversized frames.
– Patrick
May 2 at 11:11
 |Â
show 3 more comments
Jumbo frames are only supposed to be used in a network where all the NICs are operating at jumbo frames, and mostly for a LAN network.
– Rui F Ribeiro
Apr 28 at 18:54
Have you tried reducing the MTU to see if the issue goes away? And/or have you tried doing a tcpdump on both sides when the issue is occurring to see if packets are making it through?
– Patrick
Apr 28 at 19:39
1
On a few *NIXes (Linux, some *BSD) it should even be possible to lower the MSS (which usually derives from MTU) for TCP without changing the jumbo frame settings: with iptables + TCPMSS on Linux, and pf + scrub max-mss on *BSD.
– A.B
Apr 28 at 20:13
1
@RuiFRibeiro, it is configured like this
– f1 outsourcing
May 2 at 8:01
1
@f1outsourcing If dropping the MTU fixed it, then yes, you should definitely do a packet capture. This smells like you have something in the mix which is dropping ICMP packets, which are critical to the operation of networks, especially when you have oversized frames.
– Patrick
May 2 at 11:11
Jumbo frames are only supposed to be used in a network where all the NICs are operating at jumbo frames, and mostly for a LAN network.
– Rui F Ribeiro
Apr 28 at 18:54
Jumbo frames are only supposed to be used in a network where all the NICs are operating at jumbo frames, and mostly for a LAN network.
– Rui F Ribeiro
Apr 28 at 18:54
Have you tried reducing the MTU to see if the issue goes away? And/or have you tried doing a tcpdump on both sides when the issue is occurring to see if packets are making it through?
– Patrick
Apr 28 at 19:39
Have you tried reducing the MTU to see if the issue goes away? And/or have you tried doing a tcpdump on both sides when the issue is occurring to see if packets are making it through?
– Patrick
Apr 28 at 19:39
1
1
On a few *NIXes (Linux, some *BSD) it should even be possible to lower the MSS (which usually derives from MTU) for TCP without changing the jumbo frame settings: with iptables + TCPMSS on Linux, and pf + scrub max-mss on *BSD.
– A.B
Apr 28 at 20:13
On a few *NIXes (Linux, some *BSD) it should even be possible to lower the MSS (which usually derives from MTU) for TCP without changing the jumbo frame settings: with iptables + TCPMSS on Linux, and pf + scrub max-mss on *BSD.
– A.B
Apr 28 at 20:13
1
1
@RuiFRibeiro, it is configured like this
– f1 outsourcing
May 2 at 8:01
@RuiFRibeiro, it is configured like this
– f1 outsourcing
May 2 at 8:01
1
1
@f1outsourcing If dropping the MTU fixed it, then yes, you should definitely do a packet capture. This smells like you have something in the mix which is dropping ICMP packets, which are critical to the operation of networks, especially when you have oversized frames.
– Patrick
May 2 at 11:11
@f1outsourcing If dropping the MTU fixed it, then yes, you should definitely do a packet capture. This smells like you have something in the mix which is dropping ICMP packets, which are critical to the operation of networks, especially when you have oversized frames.
– Patrick
May 2 at 11:11
 |Â
show 3 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f440614%2fmtu-9000-issues-only-on-tcp-and-not-icmp-possible%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Jumbo frames are only supposed to be used in a network where all the NICs are operating at jumbo frames, and mostly for a LAN network.
– Rui F Ribeiro
Apr 28 at 18:54
Have you tried reducing the MTU to see if the issue goes away? And/or have you tried doing a tcpdump on both sides when the issue is occurring to see if packets are making it through?
– Patrick
Apr 28 at 19:39
1
On a few *NIXes (Linux, some *BSD) it should even be possible to lower the MSS (which usually derives from MTU) for TCP without changing the jumbo frame settings: with iptables + TCPMSS on Linux, and pf + scrub max-mss on *BSD.
– A.B
Apr 28 at 20:13
1
@RuiFRibeiro, it is configured like this
– f1 outsourcing
May 2 at 8:01
1
@f1outsourcing If dropping the MTU fixed it, then yes, you should definitely do a packet capture. This smells like you have something in the mix which is dropping ICMP packets, which are critical to the operation of networks, especially when you have oversized frames.
– Patrick
May 2 at 11:11