samba2 for optware is not working with XP "out of the box" (neither samba 3)
its a shame because the package is working its just the configuration that doesnt connect
BUT i cannot add user nobody (i use root for samba whick is not very secure)
because i can add nobody with "adduser nobody" but i cannot set his password
(there is no passwd command...is it enough to have nobody without password and
give him a smbpassword ?)
By the way how much is your WL-500gP transfer speed from the HD ?
is it 3 MBytes/sec (only) like mine ?
why the command hdparm gives out 97 MByte/sec cached and 9 MB/sec non-cached
disk reads but ftp only gives 3 Mbyte/sec ?
also hdparm -d <device> fails (the command that replies the DMA status of the disk interface)
USB2 means that it performs faster than USB1. And it does. USB2 does not mean that you would get 400MBit. Look arround for NAS disk transfer rate specs/lineup with USB attached disk. You would see that 4MB/s is max what you could get. That's why many NAS boxes use SATA for disk attachment.
This router was ment for some USB camera, USB key or USB printer attachment and in rare cases for DISK. But again I am happy if I get 2MB/s with my "Deluxe" as long it is low power and stable. My upgrade to 64MB did not produce notable improvement except some some disk caching.
See my pos about disk performance testing with iozone at http://wl500g.info/showthread.php?t=5788
Code:
Iozone: Performance Test of File I/O
Version $Revision: 3.259 $
Compiled for 32 bit mode.
Build: Generic
Contributors:William Norcott, Don Capps, Isom Crawford, Kirby Collins
Al Slater, Scott Rhine, Mike Wisner, Ken Goss
Steve Landherr, Brad Smith, Mark Kelly, Dr. Alain CYR,
Randy Dunlap, Mark Montague, Dan Million,
Jean-Marc Zucconi, Jeff Blomberg,
Erik Habbinga, Kris Strecker, Walter Wong.
very interesting...i will buy a SD ram chip for PC and do it myself...
i bet i can use the leftover chips from WL-500gP to upgrade WRT54GL(16MB Ram) to 32 MB
can you please tell me now why samba works only if i set encrypt passwords = yes and guest account = root
without adding smbpasswd for 'nobody' or any other user (i added smbpasswd for root and nobody but deleted them after - i deleted completely /opt/etc/smbpasswd)
and it works...but it doesnt work in any other way...also i am not sure what password it uses for root...maybe its the login password i dont know
also samba folder browsing is very sloooooooooooowww....
FTP may go up to 3+ MB/sec but samba doesnt go more than 1 MB/sec...thats USB1 not USB2
when i try to browse a folder with samba from 2% CPU load that was before it flies to 90-100% instantly
I would bet that without professional hot air desoldering station this safe removal is not an easy job. Some guys tried with cheap gas soldering station. Remember that with one 128MB four chips PC133 SDRAM module you could upgrade two routers.
Samba sped can be tailored to some extent with socket options and oplocks.
If browsing gives trouble, try to force router to become master browser with raisng OS level.
guest account = nobody works if there is nobody in /etc/passwd.
for login without encrypt passwords=yes Registry of each windows client should be changes. read samba FAQ for this.
the more trouble is that CPU flies to 100% when i try to browse samba shares
give some options examples cause im lost in Samba FAQ
give your smbmount options
when you browse samba shares how much CPU utilization do you have ?
i found out why its working with root and not with 'nobody'...because in /tmp/etc/passwd every reboot there is only root...if i add nobody with adduser next reboot its gone...i tried adding adduser -h /tmp/nobody nobody in a script but it didnt work, so if i want to have nobody for samba logins i have to add it manually every reboot
i dont have professional tools...but i believe with a hot air station or a fine tip soldering iron and a razor i could raise the pins without damage (one by one)
i dont know what gas soldering station is
What smbmount ? Are you using remote smbmounted share as samba share?
I have three different routers with samba and the following firmwares: Xwrt, Oleg, dd-wrt. But I have disk only on Oleg fw.I am using the following config on xwrt with USB key:
Code:
[global]
# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = Samba Optware Server
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.
# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
printcap name = /etc/printcap
load printers = no
# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx
; printing = bsd
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
log file = /opt/var/log/samba/log.%m
# Put a capping on the size of the log files (in Kb).
max log size = 50
# Security mode. Most people will want user level security. See
# security_level.txt for details.
security = share
# Use password server option only with security = server
; password server = <NT-Server-Name>
# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
; password level = 8
; username level = 8
# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
encrypt passwords = no
; smb passwd file = /etc/samba/smbpasswd
# The following are needed to allow password changing from Windows to
# update the Linux sytsem password also.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
# the encrypted SMB passwords. They allow the Unix password
# to be kept in sync with the SMB password.
; unix password sync = Yes
; passwd program = /usr/bin/passwd %u
; passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
# Unix users can map to different SMB User names
; username map = /opt/etc/samba/smbusers
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /etc/samba/smb.conf.%m
# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
; socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
; interfaces = br0
# Configure remote browse list synchronisation here
# request announcement to, or browse list sync from:
# a specific host or from / to a whole subnet (see below)
; remote browse sync = 192.168.3.25 192.168.5.255
# Cause this host to announce itself to local subnets here
; remote announce = 192.168.1.255 192.168.2.44
# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes
# Use only if you have an NT server on your network that has been
# configured at install time to be a primary domain controller.
; domain controller = <NT-Domain-Controller-SMBName>
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes
# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U
# All NetBIOS names must be resolved to IP Addresses
# 'Name Resolve Order' allows the named resolution mechanism to be specified
# the default order is "host lmhosts wins bcast". "host" means use the unix
# system gethostbyname() function call that will use either /etc/hosts OR
# DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf
# and the /etc/resolv.conf file. "host" therefore is system configuration
# dependant. This parameter is most often of use to prevent DNS lookups
# in order to resolve NetBIOS names to IP Addresses. Use with care!
# The example below excludes use of name resolution for machines that are NOT
# on the local network segment
# - OR - are not deliberately to be known via lmhosts or via WINS.
; name resolve order = wins lmhosts bcast
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
dns proxy = no
# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
preserve case = yes
; short preserve case = no
# Default case is normally upper case for all DOS files
; default case = lower
# Be very careful with case sensitivity - it can break things!
; case sensitive = no
# This parameter specifies the DOS code page that the clients accessing
# Samba are using. To determine what code page a Windows or DOS client
# is using, open a DOS command prompt and type the command chcp.
; client code page = 852
# This allows smbd to map incoming filenames from a DOS Code page
# (see the client code page parameter) to several built in UNIX character sets.
; character set = ISO8859-2
#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = no
writable = yes
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /opt/home/netlogon
; guest ok = yes
; writable = no
; share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /opt/home/profiles
; browseable = no
; guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /opt/var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
guest ok = no
writable = no
printable = yes
# This one is useful for people to share files
[tmp]
comment = Temporary file space
path = /tmp
read only = no
public = yes
[www]
comment = HTTP server files
path = /opt/share/www
read only = no
public = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; read only = yes
; write list = @staff
# Other examples.
#
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
:;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %u option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes
# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
