Which master, can you tell me why Samba doesn't show up in the online neighborhood? But it can be accessed with an IP

lyx4040

A DD-WRT secondary router is connected to a hard drive and is going to share files with Samba.

The route management address LAN is set to 192.168.17.1, and the wireless address is statically fixed at 192.168.1.232 via a wireless connection to the primary route.

On other computers, you can't see Samba's name in your neighborhood, but you can access it through \\192.168.1.232, and you can manipulate the folder normally.

Q: How do you set up your online neighbor's name display? (There are other routes that can be displayed in the online neighborhood, and there should be no problem with the computer settings)

/etc/samba/smb.conf reads as follows

[global]
        netbios name = file_server
        display charset = UTF-8
        interfaces = 127.0.0.1/8 lo 192.168.17.1/24 br-lan
        server string = file_server
        unix charset = UTF-8
        workgroup = WORKGROUP
        browseable = yes
        deadtime = 30
        domain master = yes
        encrypt passwords = true
        enable core files = no
        guest account = nobody
        guest ok = yes
        invalid users = root
        local master = yes
        load printers = no
        map to guest = Bad User
        max protocol = SMB2
        min receivefile size = 16384
        null passwords = yes
        obey pam restrictions = yes
        os level = 65
        passdb backend = smbpasswd
        preferred master = yes
        printable = no
        security = share
        smb encrypt = disabled
        smb passwd file = /etc/samba/smbpasswd
        socket options = TCP_NODELAY IPTOS_LOWDELAY
        syslog = 2
        use sendfile = yes
        writeable = yes
        wins support = yes

[homes]
        comment     = Home Directories
        browsable   = no
        read only   = no
        create mode = 0750

[disk1]
        path = /mnt/sda1
        read only = no
        guest ok = yes
        create mask = 0750
        directory mask = 0750

jzhou404

Samba's old problem, try a few more firmware

locomotive

Are the groups the same?

loog2009

Different network segments are not broadcast
=============
How to use UDP to broadcast across network segments
Broadcast domains
First, let's understand the concept of the broadcast domain.
A broadcast domain is a collection of all hosts on a network that can receive broadcast frames from any host. That is, if one of the hosts in the broadcast domain emits a broadcast frame, all other hosts in the same broadcast domain can receive the broadcast frame.
Calculation of the broadcast domain
How do you know which broadcast domain a host belongs to? In fact, the calculation is very simple, as long as the IP address and subnet mask of the host are used to perform the calculation, you can know which broadcast domain the host belongs to. For example, if the IP address of a host is 192.168.23.150 and the subnet mask is 255.255.255.0, the broadcast domain to which it belongs is 192.168.23.150 & 255.255.255.0 = 192.168.23.0. Then all other hosts in the broadcast domain 192.168.23.0 can access the broadcast packets sent by the device. If you change the subnet mask to 255.255.0.0, then the broadcast domain to which it belongs is 192.168.23.150&255.255.0.0=192.168.0.0. All other hosts in the broadcast domain 192.168.0.0 can receive the broadcast packets sent by the device.
Calculation of broadcast addresses
In order to receive broadcast frames from other hosts in the same broadcast domain, you also need to specify the broadcast address in the current broadcast domain when sending the broadcast packet. The calculation method of the broadcast address is to negate the subnet mask and then perform or calculate with the broadcast domain.
For example, if the host belongs to a broadcast domain of 192.168.0.0 and the subnet mask is 255.255.0.0, the broadcast address is 192.168.255.255.
Use UDP for cross-network segment broadcasting
To enable the broadcast packet sent by host A to be received by host B on another network segment, it is only necessary to change the subnet mask of host A so that it is in the same broadcast domain as host B, and then use the broadcast address of the new broadcast domain to send the broadcast packet.

For example, if you want to use 192.168.23.150 to send a broadcast packet for 192.168.27.135 to receive, you only need to set the subnet mask of 192.168.23.150 to 255.255.0.0, and then use the broadcast address 192.168.255.255.
In particular, 255.255.255.255 is a restricted broadcast address and cannot be used to send broadcast packets.
https://www.cnblogs.com/caicaizi/p/7371937.html

lyx4040

I tried it, and it was indeed a problem with different network segments. Connect the computer to the secondary route and automatically assign it to the address: 192.168.17.X. Online neighbors can discover Samba.

I'm not connected to the computer at the secondary route, just to a hard drive. The computers are connected to the main route, and the address assigned is 192.168.1.X. Online neighbors can't spot Samba.

Samba should be broadcasting to the 192.168.17.X segment, but not to the 192.168.1.X segment.

1. How do I set up Samba for my online neighbors to discover?

2. There is another problem, both the primary route and the secondary route have DHCP enabled. If the secondary route is also broadcast to the 192.168.1.X segment, are the two DHCPs interfering with each other?

duxingniao

I've been working on this issue recently, but what you said is not broadcast to the main route, I think it's inappropriate, because you use your mobile phone to connect to the main route, and then use the ES file manager to search the Samba shared folder, but the computer under the main route just can't be searched, and can only be accessed with IP.

duxingniao

In addition, I opened the 137,138,139,445 ports related to NetBios and Samba on the WAN port, but I still can't find it under the main route

duxingniao

The problem is solved, if you want to access the SAMBA port of the WAN port, you must open several ports 137, 138, 139, and 445 if you are a neighbor on the Internet
If you still can't see it, go to Figure 1 to reset it, and you can see the sharing through the WAN port.

xuese333

Thank you so much