111 replies to this topic

[theparasol]

I think this all is related. In dutch section a similar/same issue is going on.
I did some research and found a solution for my network:

http://openpli.org/f...post__p__321768

[theparasol]

There is no "broadcast" adress within the network configuration. Is it normal?

Here also, my box has been configured with static IP on the box itself.
If its a problem with DHCP leases from a dhcp server, the exact same issues rises if the user did a manual configuration and assigned a static ip in the box netwerk interface menu.

root@xp1000:~# ifconfig
eth0	  Link encap:Ethernet  HWaddr B4:9D:B4:00:02:30
		  inet addr:192.168.1.32  Bcast:0.0.0.0  Mask:255.255.255.0
		  inet6 addr: 2a02:58:e5:c601:b69d:b4ff:fe00:230/64 Scope:Global
		  inet6 addr: fe80::b69d:b4ff:fe00:230/64 Scope:Link
		  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
		  RX packets:16930 errors:0 dropped:2 overruns:0 frame:0
		  TX packets:7202 errors:0 dropped:0 overruns:0 carrier:0
		  collisions:0 txqueuelen:1000
		  RX bytes:17448746 (16.6 MiB)  TX bytes:801837 (783.0 KiB)

[superleok]

I have reflash the box today and a new configuration of network parameter BCast Address now is fine.

eth0	  Link encap:Ethernet  HWaddr 00:16:B4:03:A9:38
		  inet addr:192.168.10.254  Bcast:192.168.10.255  Mask:255.255.255.0
		  inet6 addr: fe80::216:b4ff:fe03:a938/64 Scope:Link
		  UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
		  RX packets:17754 errors:0 dropped:4 overruns:0 frame:0
		  TX packets:7906 errors:0 dropped:0 overruns:0 carrier:0
		  collisions:0 txqueuelen:50000

At the moment i play around with samba and i saw some strange errors.

Samba can't bind to port 139 and 445. I think it's a Problem with IPv6 because Samba bind the ports on IPv6 address.

1970/01/01 01:00:21.709218,  2] lib/interface.c:340(add_interface)
  added interface eth0 ip=fe80::216:b4ff:fe03:a938%eth0 bcast=fe80::ffff:ffff:ffff:ffff%eth0 netmask=ffff:ffff:ffff:ffff:: >>> IPv6 is the first interface!!!
[1970/01/01 01:00:21.713724,  2] lib/interface.c:340(add_interface)
  added interface eth0 ip=192.168.10.254 bcast=192.168.10.255 netmask=255.255.255.0

Error Message:
IPv4 doesen't work because the IPv6 binding:

1970/01/01 01:00:22.141118,  2] lib/util_sock.c:875(open_socket_in)
  bind failed on port 445 socket_addr = 0.0.0.0.
  Error = Address already in use
[1970/01/01 01:00:22.141750,  0] smbd/server.c:500(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[1970/01/01 01:00:22.143554,  2] lib/util_sock.c:875(open_socket_in)
  bind failed on port 139 socket_addr = 0.0.0.0.
  Error = Address already in use

You have to edit the smb.conf to bind the ports exclusive to the IPv4 Address:

interfaces = 192.168.10.254
   bind interfaces only = yes

I have also attached the name service resolve order:

name resolve order = bcast lmhosts host wins

After a reboot and some minutes i saw the box with explorer.

Edited by superleok, 18 January 2013 - 23:48.

[WanWizard]

I don't see that:

root@et9x00:~# netstat -lnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address		   Foreign Address		 State	   PID/Program name    
tcp	    0	  0 0.0.0.0:8001		    0.0.0.0:*			   LISTEN	  409/enigma2
tcp	    0	  0 0.0.0.0:139			 0.0.0.0:*			   LISTEN	  295/smbd
tcp	    0	  0 0.0.0.0:111			 0.0.0.0:*			   LISTEN	  331/portmap
tcp	    0	  0 0.0.0.0:80			  0.0.0.0:*			   LISTEN	  409/enigma2
tcp	    0	  0 0.0.0.0:21			  0.0.0.0:*			   LISTEN	  379/inetd
tcp	    0	  0 0.0.0.0:22			  0.0.0.0:*			   LISTEN	  368/dropbear
tcp	    0	  0 0.0.0.0:23			  0.0.0.0:*			   LISTEN	  379/inetd
tcp	    0	  0 0.0.0.0:443			 0.0.0.0:*			   LISTEN	  409/enigma2
tcp	    0	  0 0.0.0.0:445			 0.0.0.0:*			   LISTEN	  295/smbd
tcp	    0	  0 :::22				   :::*				    LISTEN	  368/dropbear
udp	    0	  0 0.0.0.0:111			 0.0.0.0:*						   331/portmap
udp	    0	  0 172.16.1.44:137		 0.0.0.0:*						   293/nmbd
udp	    0	  0 0.0.0.0:137			 0.0.0.0:*						   293/nmbd
udp	    0	  0 172.16.1.44:138		 0.0.0.0:*						   293/nmbd
udp	    0	  0 0.0.0.0:138			 0.0.0.0:*						   293/nmbd
udp	    0	  0 0.0.0.0:36764		   0.0.0.0:*						   391/avahi-daemon: r
udp	    0	  0 0.0.0.0:5353		    0.0.0.0:*						   391/avahi-daemon: r

I only have this in the logs:

[1970/01/01 01:00:13, 0] /dreambox/oe.openpli-3.0/build-et9x00/tmp/work/mips32el-oe-linux/samba-3.0.37-r8/samba-3.0.37/source/lib/pidfile.c:pidfile_create(112)
  ERROR: smbd is already running. File /var/run/smbd.pid exists and process id 295 is running.

[superleok]

You are right. There are no IPv6 Adresses. Mmmh. I have removed the IPv4 Binding from global section and after reboot it works again?!? Strange!

Maybe it will help some users to set the IPv4 Adress in global section and restart the service.

[superleok]

Hello WanWizard,

after reboot there are two IPv6 (Samba) Listening Ports. This could be a problem for Broadcast and Browser Announcments.

root@et9x00:~# netstat -lne
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address		   Foreign Address		 State
tcp	    0	  0 0.0.0.0:12000		   0.0.0.0:*			   LISTEN
tcp	    0	  0 0.0.0.0:8001		    0.0.0.0:*			   LISTEN
tcp	    0	  0 0.0.0.0:2049		    0.0.0.0:*			   LISTEN
tcp	    0	  0 0.0.0.0:16200		   0.0.0.0:*			   LISTEN
tcp	    0	  0 0.0.0.0:111			 0.0.0.0:*			   LISTEN
tcp	    0	  0 0.0.0.0:80			  0.0.0.0:*			   LISTEN
tcp	    0	  0 0.0.0.0:21			  0.0.0.0:*			   LISTEN
tcp	    0	  0 0.0.0.0:22			  0.0.0.0:*			   LISTEN
tcp	    0	  0 0.0.0.0:3031		    0.0.0.0:*			   LISTEN
tcp	    0	  0 0.0.0.0:23			  0.0.0.0:*			   LISTEN
tcp	    0	  0 0.0.0.0:8888		    0.0.0.0:*			   LISTEN
tcp	    0	  0 0.0.0.0:443			 0.0.0.0:*			   LISTEN
tcp	    0	  0 :::139				  :::*				    LISTEN <<<<< shorthanded IPv6
tcp	    0	  0 :::22				   :::*				    LISTEN
tcp	    0	  0 :::445				  :::*				    LISTEN <<<<<< shorthanded IPv6
udp	    0	  0 0.0.0.0:2049		    0.0.0.0:*
udp	    0	  0 0.0.0.0:20236		   0.0.0.0:*
udp	    0	  0 0.0.0.0:34875		   0.0.0.0:*
udp	    0	  0 0.0.0.0:26212		   0.0.0.0:*
udp	    0	  0 0.0.0.0:111			 0.0.0.0:*
udp	    0	  0 0.0.0.0:626			 0.0.0.0:*
udp	    0	  0 0.0.0.0:16500		   0.0.0.0:*
udp	    0	  0 192.168.10.255:137	  0.0.0.0:*
udp	    0	  0 192.168.10.254:137	  0.0.0.0:*
udp	    0	  0 0.0.0.0:137			 0.0.0.0:*
udp	    0	  0 192.168.10.255:138	  0.0.0.0:*
udp	    0	  0 192.168.10.254:138	  0.0.0.0:*
udp	    0	  0 0.0.0.0:138			 0.0.0.0:*
udp	    0	  0 0.0.0.0:25539		   0.0.0.0:*
udp	    0	  0 0.0.0.0:5353		    0.0.0.0:*

[WanWizard]

Nope, 139 and 445 are two different services, they should both be there. 139 is the old-style Netbios over TCP service, 445 is the "new" SMB over TCP service.

They should be there for IPv4 too (listening on 0.0.0.0 or on the eth0 IP if you have configured that). If not then IPv4 clients will be able to see the box (that is what 137/UDP and 138/UDP do), but they won't be able to connect.

root@et9x00:~# netstat -lnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address		   Foreign Address		 State	   PID/Program name	
tcp		0	  0 0.0.0.0:8001			0.0.0.0:*			   LISTEN	  409/enigma2
tcp		0	  0 0.0.0.0:139			 0.0.0.0:*			   LISTEN	  295/smbd		  <== this one should be there
tcp		0	  0 0.0.0.0:111			 0.0.0.0:*			   LISTEN	  331/portmap
tcp		0	  0 0.0.0.0:80			  0.0.0.0:*			   LISTEN	  409/enigma2
tcp		0	  0 0.0.0.0:21			  0.0.0.0:*			   LISTEN	  379/inetd
tcp		0	  0 0.0.0.0:22			  0.0.0.0:*			   LISTEN	  368/dropbear
tcp		0	  0 0.0.0.0:23			  0.0.0.0:*			   LISTEN	  379/inetd
tcp		0	  0 0.0.0.0:443			 0.0.0.0:*			   LISTEN	  409/enigma2
tcp		0	  0 0.0.0.0:445			 0.0.0.0:*			   LISTEN	  295/smbd		  <== this one should be there
tcp		0	  0 :::22				   :::*					LISTEN	  368/dropbear
udp		0	  0 0.0.0.0:111			 0.0.0.0:*						   331/portmap
udp		0	  0 172.16.1.44:137		 0.0.0.0:*						   293/nmbd
udp		0	  0 0.0.0.0:137			 0.0.0.0:*						   293/nmbd
udp		0	  0 172.16.1.44:138		 0.0.0.0:*						   293/nmbd
udp		0	  0 0.0.0.0:138			 0.0.0.0:*						   293/nmbd
udp		0	  0 0.0.0.0:36764		   0.0.0.0:*						   391/avahi-daemon: r
udp		0	  0 0.0.0.0:5353			0.0.0.0:*						   391/avahi-daemon: r

And I don't have the IPv6 entries here.

[superleok]

Hello WanWizard,

Browser and Host Announcents are UDP Based streams you can check this with Wireshark. And i have IPv6 entries! I see only those Announcements in the network (wireshark).

Be aware. Normaly the Browser Service on Windows 7 is deactivated and there is no Browser List. I activate the ComputerBrowser Service and saw Local Master Announcments.

Samba IPv4 / IPv6:

http://blog.flameeye...4-fails-to-work

Edited by superleok, 20 January 2013 - 16:44.

[superleok]

Nope, 139 and 445 are two different services, they should both be there. 139 is the old-style Netbios over TCP service, 445 is the "new" SMB over TCP service.

I know the difference but the box (samba) switch between IPv4 and IPv6 (see my post). I think it is not correct and many people don't have a pure IPv6 based network. For that reason i have set smb.conf to IPv4.
At the moment i can see (tried this with many reboots) the box but i have no connect to the shares. I think it's a SMB2 and a Authentication problem. Samba 3.0.xxx is not really Windows 7 compatible.

[WanWizard]

Correct, it's the ports 137 and 138 that do this.

I just find it odd that some people have only IPv6 entries, and not both. And I have only IPv4 entries...

In Windows 7 if you go to the network list and it's not enabled, Windows will prompt you to do so. And if you do you should see the list immediately (unless a firewall is blocking something, I think the built-in firewall opens automatically).

As for the connections, that's something odd too. My VU+ and ET run exactly the same OpenPLi version, and have the same config. I can see the VU+ shares and connect to them. I can't see the ET shares.

Some debugging with Wireshark reveals that the ET broadcasts himself with a space ( "ET9X00<20>" ) after the name, which is illegal. No clue where that comes from, and why the VU+ doesn't do that.

[superleok]

.

In Windows 7 if you go to the network list and it's not enabled, Windows will prompt you to do so. And if you do you should see the list immediately (unless a firewall is blocking something, I think the built-in firewall opens automatically).

I thought the service. Servics.msc >> Computerbrowser. This service is normaly disabled on Windows 7. After the service activated Windows sends a browser election request.

At the moment i can't see ET without this service enabled.

Edited by superleok, 20 January 2013 - 18:58.

[superleok]

.

In Windows 7 if you go to the network list and it's not enabled, Windows will prompt you to do so. And if you do you should see the list immediately (unless a firewall is blocking something, I think the built-in firewall opens automatically).

I thought the service. Servics.msc >> Computerbrowser. This service is normaly disabled on Windows 7. After the service activated Windows sends a browser election request.

At the moment i can't see ET without this service enabled.

That was rubbished. I played to much with Windows 7 network settings. ComputerBrowser Service is normaly enabled.

[superleok]

Hello WanWizard,

Without local master = no in smb.conf. Samba tries to be a local master after restart the box. After a while Samba sends a Local Master Announcement so Samba wins the election. Windows 7 Client sends also Election Requests and after a while a Local Master Announcement. I checked the Local Master Announcement smb block from Windows and Samba in Wireshark. I looks like both are local master. I think the Windows Client does not communicate correct with samba.

Edited by superleok, 20 January 2013 - 23:04.

[WanWizard]

Do you have an "os level = 8" is your config?

That is required, and makes sure that if you have another server in your network, the box will never win the election (and that other box will deal with browsing), but if you don't have another server, the box will become the master.

If you set it to 'no', and the box is all you have, then effectively there is NO master in your network, and you have disabled browsing.

Are you having an ET too? Can you check if your box also broadcasts it's name as "ET9X00<20>", so with an additional hex-20 (space) at the end? Which is an illegal name, so Windows will not connect to it.

I see that here, but the VU+ doesn't have this (and runs exactly the same OpenPLi version).

[pieterg]

to rule out the name(length), it'd be simple to change the hostname to something with the same length?

[WanWizard]

I'll try that when I have a chance to reboot the box.

[littlesat]

But XP1000 is OK and is equal long to ET9X00??? As DM800 is even shorter... and is fine too...

Edited by littlesat, 21 January 2013 - 07:43.

[superleok]

Do you have an "os level = 8" is your config?

That is required, and makes sure that if you have another server in your network, the box will never win the election (and that other box will deal with browsing), but if you don't have another server, the box will become the master.

If you set it to 'no', and the box is all you have, then effectively there is NO master in your network, and you have disabled browsing.

Are you having an ET too? Can you check if your box also broadcasts it's name as "ET9X00<20>", so with an additional hex-20 (space) at the end? Which is an illegal name, so Windows will not connect to it.

I see that here, but the VU+ doesn't have this (and runs exactly the same OpenPLi version).

I have a ET9000 and i don't have os level settings in my config. I set local master = 0. Windows 7 client wins the election and now everything works fine. I saw also the broadcasts from ET9000. They have ET9x00<20> inside. I don't think it's illegal. <20> means Server Service and is the 16 byte identifier.

http://www.microsoft...h.mspx?mfr=true

What do you mean exactly the hostname inside Microsoft Browser Protocol or Sourcname insede Netbios Datagram Service. Is it possible to post a picture from ET9000 broadcasts.

[WanWizard]

If your Windows 7 takes part in elections you have something installed/enabled that is normally not present. Windows clients never engage in elections, they are b-nodes and rely on WINS/DNS for resolving.
And that means your setup is not representative for the avarage home user.

The <20> doesn't appear as the 16th byte, it appears as the 7th byte, directly after the filename. smbtree gives me:

WORKGROUP
	\\VUDUO				  DreamBOX vuduo network services
		\\VUDUO\Configfiles		Configuration files - take care!
		\\VUDUO\Harddisk		   The harddisk
		\\VUDUO\IPC$			   IPC Service (vuduo STB network services)
	\\ET9X00				 Samba server et9x00
cli_start_connection: failed to connect to ET9X00<20> (0.0.0.0). Error NT_STATUS_BAD_NETWORK_NAME

The funny bit is, on the same machine:

[root@penguin ~]# smbclient -L 172.16.1.44 -U root
Password:
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.37]

	Sharename	   Type	  Comment
	---------	   ----	  -------
	IPC$			IPC	   IPC Service (et9x00 STB network services)
	Root			Disk	  Everything - take care!
	Harddisk		Disk	  The harddisk
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.37]

	Server			   Comment
	---------			-------
	ET9X00			   Samba server et9x00

	Workgroup			Master
	---------			-------
	WORKGROUP 			   CATWOMAN

which seems to list them without problems.

[superleok]

If your Windows 7 takes part in elections you have something installed/enabled that is normally not present. Windows clients never engage in elections, they are b-nodes and rely on WINS/DNS for resolving.
And that means your setup is not representative for the avarage home user.

This is not true every computer in a workgroup (without Domain Controller) can be a master browser. Normaly the clients doesen't win the election against servers in the network. I did not installed a software or enable something. If you have a Win 7 Machine you can reproduce this. Start and Stop the ComputerBrowser Service and take a look with Wireshark. You see that Win7 starts an election.

There a serveral circumstances to start a browser election:

1. There is no master browser on network
2. Preferred Master comes online
3. Domain Controller Starts


see also (since Win 98 / 95b / NT4)

http://technet.micro...y/cc959896.aspx

You can also disable Win 7 to be Master Browser with the following Registry Key or you can disable the complete Browser Service which is per default enabled.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters] "MaintainServerList"="No"

Edited by superleok, 21 January 2013 - 12:50.