Jump to content
Как правильно добавить self-test и прочую отладку в тему
Где взять тестовые сборки
  • 0

Видимость samba сервера для телефона xiaomi

Александр Сухоруков

Asked by Александр Сухоруков,

 Share

Question

Александр Сухоруков Advanced Member

Александр Сухоруков

Posted
Posted

Всем привет!

Заметил что на встроенном smb сервере мой телефон не видит smb сервера.

А если поставить samba36_server и opkg то телефон начинает видеть smb сервер, прям во встроенном проводнике!

Есть мысли что в них за отличия?

Скриншоты прилагаю.

Screenshot_2017-11-08-14-50-39-213_com.android.fileexplorer.png

Screenshot_2017-11-08-14-50-56-406_com.android.fileexplorer.png

Link to comment
Share on other sites

5 answers to this question

Recommended Posts

  • 0
Александр Сухоруков Advanced Member

Александр Сухоруков

Posted
  • Author
Posted (edited)

Я не сильно силен в сборе сетевых дампом, и работе сетевых протоколов на таком уровне, но вот логи NG и SAMBA во время запуска проводника на телефоне.

Собирал на giga через tcpdump

команда целиком выглядит

Цитата

 tcpdump -n not src 192.168.0.2 and not arp and not ip6

где 0.17 айпи телефона, а 0.1 айпи гиги

 

 

NG 

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ra0, link-type EN10MB (Ethernet), capture size 262144 bytes
15:28:03.860178 IP 192.168.0.17.46021 > 255.255.255.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
15:28:04.377576 IP 192.168.0.1.138 > 192.168.0.255.138: NBT UDP PACKET(138)
15:28:05.847357 IP 192.168.0.17.46021 > 255.255.255.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
15:28:07.865162 IP 192.168.0.17.46021 > 255.255.255.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
15:28:09.867348 IP 192.168.0.17.60843 > 255.255.255.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
15:28:13.674917 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 410
15:28:13.675165 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 482
15:28:13.675342 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 419
15:28:13.675519 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 478
15:28:13.675668 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 419
15:28:13.675858 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 458
15:28:13.676035 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 419
15:28:13.676220 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 472
15:28:13.676399 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 490
15:28:13.676615 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 474
15:28:13.676800 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 474
15:28:13.927626 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 474
15:28:13.927780 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 474
15:28:13.927882 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 490
15:28:13.927985 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 472
15:28:13.928100 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 419
15:28:13.928189 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 458
15:28:13.928285 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 419
15:28:13.928384 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 478
15:28:13.928486 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 419
15:28:13.928587 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 482
15:28:13.928687 IP 192.168.0.1.42981 > 239.255.255.250.1900: UDP, length 410
15:28:14.387463 IP 192.168.0.1.138 > 192.168.0.255.138: NBT UDP PACKET(138)

Samba 

15:26:20.950722 IP 192.168.0.17.50655 > 255.255.255.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
15:26:20.951239 IP 192.168.0.1.137 > 192.168.0.17.50655: NBT UDP PACKET(137): QUERY; POSITIVE; RESPONSE; UNICAST
15:26:20.987184 IP 192.168.0.17 > 192.168.0.1: ICMP echo request, id 26, seq 1, length 64
15:26:20.987420 IP 192.168.0.1 > 192.168.0.17: ICMP echo reply, id 26, seq 1, length 64
15:26:21.000493 IP 192.168.0.17.37856 > 192.168.0.1.445: Flags [S], seq 2863824489, win 65535, options [mss 1460,sackOK,TS val 783176 ecr 0,nop,wscale 8], length 0
15:26:21.000678 IP 192.168.0.1.445 > 192.168.0.17.37856: Flags [S.], seq 870004909, ack 2863824490, win 14480, options [mss 1460,sackOK,TS val 221117 ecr 783176,nop,wscale 6], length 0
15:26:21.001862 IP 192.168.0.17.37856 > 192.168.0.1.445: Flags [.], ack 1, win 343, options [nop,nop,TS val 783176 ecr 221117], length 0
15:26:21.002613 IP 192.168.0.17.37856 > 192.168.0.1.445: Flags [P.], seq 1:52, ack 1, win 343, options [nop,nop,TS val 783176 ecr 221117], length 51 SMB PACKET: SMBnegprot (REQUEST)

15:26:21.002827 IP 192.168.0.1.445 > 192.168.0.17.37856: Flags [.], ack 52, win 227, options [nop,nop,TS val 221118 ecr 783176], length 0
15:26:21.006283 IP 192.168.0.1.445 > 192.168.0.17.37856: Flags [P.], seq 1:132, ack 52, win 227, options [nop,nop,TS val 221118 ecr 783176], length 131 SMB PACKET: SMBnegprot (REPLY)

15:26:21.007389 IP 192.168.0.17.37856 > 192.168.0.1.445: Flags [.], ack 132, win 343, options [nop,nop,TS val 783177 ecr 221118], length 0
15:26:21.009654 IP 192.168.0.17.37856 > 192.168.0.1.445: Flags [P.], seq 52:202, ack 132, win 343, options [nop,nop,TS val 783177 ecr 221118], length 150 SMB PACKET: SMBsesssetupX (REQUEST)

15:26:21.012910 IP 192.168.0.1.445 > 192.168.0.17.37856: Flags [P.], seq 132:252, ack 202, win 243, options [nop,nop,TS val 221120 ecr 783177], length 120 SMB PACKET: SMBsesssetupX (REPLY)

15:26:21.018192 IP 192.168.0.17.37856 > 192.168.0.1.445: Flags [P.], seq 202:323, ack 252, win 343, options [nop,nop,TS val 783178 ecr 221120], length 121 SMB PACKET: SMBtrans (REQUEST)

15:26:21.019334 IP 192.168.0.1.445 > 192.168.0.17.37856: Flags [P.], seq 252:351, ack 323, win 243, options [nop,nop,TS val 221122 ecr 783178], length 99 SMB PACKET: SMBtrans (REPLY)

15:26:21.021594 IP 192.168.0.17.50655 > 255.255.255.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
15:26:21.022027 IP 192.168.0.1.137 > 192.168.0.17.50655: NBT UDP PACKET(137): QUERY; POSITIVE; RESPONSE; UNICAST
15:26:21.054982 IP 192.168.0.17.37856 > 192.168.0.1.445: Flags [.], ack 351, win 343, options [nop,nop,TS val 783182 ecr 221122], length 0
15:26:21.055540 IP 192.168.0.17 > 192.168.0.1: ICMP echo request, id 27, seq 1, length 64
15:26:21.055687 IP 192.168.0.1 > 192.168.0.17: ICMP echo reply, id 27, seq 1, length 64
15:26:21.060202 IP 192.168.0.17.37856 > 192.168.0.1.445: Flags [P.], seq 323:455, ack 351, win 343, options [nop,nop,TS val 783182 ecr 221122], length 132 SMB PACKET: SMBtrans (REQUEST)

15:26:21.060897 IP 192.168.0.1.445 > 192.168.0.17.37856: Flags [P.], seq 351:477, ack 455, win 260, options [nop,nop,TS val 221132 ecr 783182], length 126 SMB PACKET: SMBtrans (REPLY)

15:26:21.061758 IP 192.168.0.17.37856 > 192.168.0.1.445: Flags [.], ack 477, win 343, options [nop,nop,TS val 783182 ecr 221132], length 0
15:26:21.062457 IP 192.168.0.17.50655 > 255.255.255.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
15:26:21.062929 IP 192.168.0.1.137 > 192.168.0.17.50655: NBT UDP PACKET(137): QUERY; POSITIVE; RESPONSE; UNICAST
15:26:21.095894 IP 192.168.0.17 > 192.168.0.1: ICMP echo request, id 28, seq 1, length 64
15:26:21.096075 IP 192.168.0.1 > 192.168.0.17: ICMP echo reply, id 28, seq 1, length 64
15:26:21.103329 IP 192.168.0.17.50655 > 255.255.255.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
15:26:21.140075 IP 192.168.0.17 > 192.168.0.2: ICMP echo request, id 29, seq 1, length 64

 

Edited by Александр Сухоруков
в прошлый раз дамп был собран с неверное командой, собрал с нужной!
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to question listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...