thr3ads.net - openssh unix dev - ssh ethernet tunnel jumbo frame udp is not work [May 2017]

If this information is useful, please help other people find it:
Share via:

Алексей Болдырев

2017-May-14 21:24 UTC

ssh ethernet tunnel jumbo frame udp is not work

root at ne-vlezay80:~# tcpdump -i tap0 -n
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on tap0, link-type EN10MB (Ethernet), capture size 262144 bytes
00:23:53.206672 ARP, Request who-has 10.194.0.2 tell 10.194.0.200, length 28
00:23:53.206691 ARP, Reply 10.194.0.2 is-at 52:54:00:38:b9:0b, length 28
00:23:53.710691 STP 802.1d, Config, Flags [none], bridge-id
8000.52:54:00:48:98:88.8000, length 35
00:23:55.559070 IP 10.194.0.200.50356 > 10.194.0.2.5201: Flags [S], seq
2722613399, win 29200, options [mss 1460,sackOK,TS val 2910016 ecr 0,nop,wscale
6], length 0
00:23:55.559212 IP 10.194.0.2.5201 > 10.194.0.200.50356: Flags [S.], seq
4252447420, ack 2722613400, win 26928, options [mss 2460,sackOK,TS val
3706806890 ecr 2910016,nop,wscale 5], length 0
00:23:55.559571 IP 10.194.0.200.50356 > 10.194.0.2.5201: Flags [.], ack 1,
win 457, options [nop,nop,TS val 2910016 ecr 3706806890], length 0
00:23:55.559589 IP 10.194.0.200.50356 > 10.194.0.2.5201: Flags [P.], seq
1:38, ack 1, win 457, options [nop,nop,TS val 2910016 ecr 3706806890], length 37
00:23:55.559879 IP 10.194.0.2.5201 > 10.194.0.200.50356: Flags [.], ack 38,
win 842, options [nop,nop,TS val 3706806891 ecr 2910016], length 0
00:23:55.559913 IP 10.194.0.2.5201 > 10.194.0.200.50356: Flags [P.], seq 1:2,
ack 38, win 842, options [nop,nop,TS val 3706806891 ecr 2910016], length 1
00:23:55.560094 IP 10.194.0.200.50356 > 10.194.0.2.5201: Flags [.], ack 2,
win 457, options [nop,nop,TS val 2910016 ecr 3706806891], length 0
00:23:55.560153 IP 10.194.0.200.50356 > 10.194.0.2.5201: Flags [P.], seq
38:42, ack 2, win 457, options [nop,nop,TS val 2910016 ecr 3706806891], length 4
00:23:55.600656 IP 10.194.0.2.5201 > 10.194.0.200.50356: Flags [.], ack 42,
win 842, options [nop,nop,TS val 3706806932 ecr 2910016], length 0
00:23:55.601099 IP 10.194.0.200.50356 > 10.194.0.2.5201: Flags [P.], seq
42:117, ack 2, win 457, options [nop,nop,TS val 2910026 ecr 3706806932], length
75
00:23:55.601593 IP 10.194.0.2.5201 > 10.194.0.200.50356: Flags [.], ack 117,
win 842, options [nop,nop,TS val 3706806932 ecr 2910026], length 0
00:23:55.601639 IP 10.194.0.2.5201 > 10.194.0.200.50356: Flags [P.], seq 2:3,
ack 117, win 842, options [nop,nop,TS val 3706806932 ecr 2910026], length 1
00:23:55.602041 IP 10.194.0.200.43100 > 10.194.0.2.5201: UDP, length 4
00:23:55.602627 IP 10.194.0.2.5201 > 10.194.0.200.43100: UDP, length 4
00:23:55.642352 IP 10.194.0.200.50356 > 10.194.0.2.5201: Flags [.], ack 3,
win 457, options [nop,nop,TS val 2910036 ecr 3706806932], length 0
00:23:55.642564 IP 10.194.0.2.5201 > 10.194.0.200.50356: Flags [P.], seq 3:5,
ack 117, win 842, options [nop,nop,TS val 3706806974 ecr 2910036], length 2
00:23:55.642763 IP 10.194.0.200.50356 > 10.194.0.2.5201: Flags [.], ack 5,
win 457, options [nop,nop,TS val 2910037 ecr 3706806974], length 0
00:23:55.642876 IP 10.194.0.200.43100 > 10.194.0.2.5201: UDP, length 8192
00:23:55.642925 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.642966 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.643025 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.643058 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.643115 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.723126 STP 802.1d, Config, Flags [none], bridge-id
8000.52:54:00:48:98:88.8000, length 35
00:23:55.743187 IP 10.194.0.200.43100 > 10.194.0.2.5201: UDP, length 8192
00:23:55.743240 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.743283 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.743327 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.743353 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.743357 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.843261 IP 10.194.0.200.43100 > 10.194.0.2.5201: UDP, length 8192
00:23:55.843344 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.843456 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.843501 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.843508 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.843527 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.843558 IP 10.194.0.200.43100 > 10.194.0.2.5201: UDP, length 8192
00:23:55.843563 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.843566 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.843570 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.843573 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.843577 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.943215 IP 10.194.0.200.43100 > 10.194.0.2.5201: UDP, length 8192
00:23:55.943267 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.943272 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.943275 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.943279 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:55.943282 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.043339 IP 10.194.0.200.43100 > 10.194.0.2.5201: UDP, length 8192
00:23:56.043489 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.043535 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.043544 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.043548 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.043552 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.043589 IP 10.194.0.200.43100 > 10.194.0.2.5201: UDP, length 8192
00:23:56.043594 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.043597 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.043601 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.043604 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.043608 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.143438 IP 10.194.0.200.43100 > 10.194.0.2.5201: UDP, length 8192
00:23:56.143568 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.143573 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.143576 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.143581 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.143585 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.143625 IP 10.194.0.200.43100 > 10.194.0.2.5201: UDP, length 8192
00:23:56.143632 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.143635 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.143639 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.143642 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
00:23:56.143646 IP 10.194.0.200 > 10.194.0.2: ip-proto-17
^C
75 packets captured
141 packets received by filter
0 packets dropped by kernel

Darren Tucker

2017-May-14 23:49 UTC

head link

ssh ethernet tunnel jumbo frame udp is not work

On Mon, May 15, 2017 at 7:24 AM, ??????? ???????? <
devel-net-ne-vlezay80 at yandex.ru> wrote:
> root at ne-vlezay80:~# tcpdump -i tap0 -n
>
You will likely need to supply some more information before anyone can even
offer any suggestions.  This includes:
 - what version of OpenSSH are the client and server?
 - what platforms are they running on?  which addresses in the dump
correspond to which?
 - how big the packet was before it was tunnelled?  was it fragmented?
 - what does the debug logging "ssh -vvv and sshd -ddd" say when this
occurs?

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860  37F4 9357 ECEF 11EA A6FA (new)
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

Алексей Болдырев

2017-May-15 13:38 UTC

head link

ssh ethernet tunnel jumbo frame udp is not work

Client:

   root at ne-vlezay80:~# ssh -V
   OpenSSH_6.7p1 Debian-5+deb8u3, OpenSSL 1.0.1t?  3 May 2016
   root at ne-vlezay80:~#
   Server:
   t58065487545 default # ssh -V
   OpenSSH_6.7p1 Debian-5+deb8u3, OpenSSL 1.0.1t?  3 May 2016
   t58065487545 default #
   Platforms client:
   58065487545 default # uname -r
   3.16.0-4-amd64
   t58065487545 default #
   t58065487545 default # arch
   x86_64
   Platforms server
   root at ne-vlezay80:~# uname -r
   4.10.9
   root at ne-vlezay80:~# arch
   x86_64
   root at ne-vlezay80:~#
   >? - how big the packet was before it was tunnelled? ? was it
   fragmented?
   SSH tunnel ethernet mtu is 2500 bytes. Network MTU 1500 bytes.

   15.05.2017, 02:49, "Darren Tucker" <dtucker at zip.com.au>:

   On Mon, May 15, 2017 at 7:24 AM, ???????????? ?????????????
   <[1]devel-net-ne-vlezay80 at yandex.ru> wrote:

     root at ne-vlezay80:~# tcpdump -i tap0 -n

   You will likely need to supply some more information before anyone can
   even offer any suggestions.?  This includes:
   ? - what version of OpenSSH are the client and server?
   ? - what platforms are they running on? ? which addresses in the dump
   correspond to which?
   ? - how big the packet was before it was tunnelled? ? was it
   fragmented?
   ? - what does the debug logging "ssh -vvv and sshd -ddd" say when
this
   occurs?
   --
   Darren Tucker (dtucker at [2]zip.com.au)
   GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860 ? 37F4 9357 ECEF 11EA A6FA
   (new)
   ?  ?  Good judgement comes with experience. Unfortunately, the
   experience
   usually comes from bad judgement.

References

   1. mailto:devel-net-ne-vlezay80 at yandex.ru
   2. http://zip.com.au/

openssh unix dev - May 2017 - ssh ethernet tunnel jumbo frame udp is not work

ssh ethernet tunnel jumbo frame udp is not work

ssh ethernet tunnel jumbo frame udp is not work

ssh ethernet tunnel jumbo frame udp is not work