Ethernet slow

Discussion in 'Troubleshooting' started by Keridos, Jun 21, 2014.

  1. Keridos

    Keridos New Member

    Joined:
    Nov 19, 2013
    Messages:
    22
    Likes Received:
    0
    Hello,
    i have the udoo-quad here and I noticed that my ethernet is really slow though I have a full Gigabit connection. My Performance in Ethernet is only about 5 Mbit/s which is really really low for gigabit. I tried some linux tuning tips for sysctl, but they do not seem to have any influence.
    What can cause the ethernet to be so slow and how can I fix it?
     
  2. peter247

    peter247 New Member

    Joined:
    Mar 10, 2014
    Messages:
    263
    Likes Received:
    2
    Are you using a sd card and what class ? and using a Gigbbit switch.

    on a sata ssd drive I`m getting 35 meg / sec using samba .
     
  3. Keridos

    Keridos New Member

    Joined:
    Nov 19, 2013
    Messages:
    22
    Likes Received:
    0
    It is a sata ssd, the perfomance with dd is about 80 MBytes/s, so there is plenta headroom. samba uses less than 10% CPU.
    When I shutdown Xbmc it gets a bit faster, i think about 15-20 Mbit/s, but that is also very slow. Can you post your smb.conf (at least the perfomance section) please for me to compare it to mine?
     
  4. peter247

    peter247 New Member

    Joined:
    Mar 10, 2014
    Messages:
    263
    Likes Received:
    2
    Code:
    #
    # Sample configuration file for the Samba suite for Debian GNU/Linux.
    #
    #
    # This is the main Samba configuration file. You should read the
    # smb.conf(5) manual page in order to understand the options listed
    # here. Samba has a huge number of configurable options most of which 
    # are not shown in this example
    #
    # Some options that are often worth tuning have been included as
    # commented-out examples in this file.
    #  - When such options are commented with ";", the proposed setting
    #    differs from the default Samba behaviour
    #  - When commented with "#", the proposed setting is the default
    #    behaviour of Samba but the option is considered important
    #    enough to be mentioned here
    #
    # NOTE: Whenever you modify this file you should run the command
    # "testparm" to check that you have not made any basic syntactic 
    # errors. 
    # A well-established practice is to name the original file
    # "smb.conf.master" and create the "real" config file with
    # testparm -s smb.conf.master >smb.conf
    # This minimizes the size of the really used smb.conf file
    # which, according to the Samba Team, impacts performance
    # However, use this with caution if your smb.conf file contains nested
    # "include" statements. See Debian bug #483187 for a case
    # where using a master file is not a good idea.
    #
    
    #======================= Global Settings =======================
    
    [global]
    	log file = /var/log/samba/log.%m
    	load printers = no
    	passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
    	obey pam restrictions = yes
    	map to guest = bad user
    	encrypt passwords = true
    	public = yes
    	passwd program = /usr/bin/passwd %u
    	passdb backend = tdbsam
    	dns proxy = no
    	writeable = yes
    	printing = bsd
    	server string = %h server
    	unix password sync = yes
    	workgroup = WORKGROUP
    	revalidate = yes
    	os level = 20
    	force user = root
    	auto services = global
    	printcap name = /dev/null
    	syslog = 0
    	panic action = /usr/share/samba/panic-action %d
    	usershare allow guests = yes
    	max log size = 1000
    	pam password change = yes
    
    ## Browsing/Identification ###
    
    # Change this to the workgroup/NT-domain name your Samba server will part of
    
    # server string is the equivalent of the NT Description field
    
    # Windows Internet Name Serving Support Section:
    # WINS Support - Tells the NMBD component of Samba to enable its WINS Server
    #   wins support = no
    
    # 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
    
    # This will prevent nmbd to search for NetBIOS names through DNS.
    
    # What naming service and in what order should we use to resolve host names
    # to IP addresses
    ;   name resolve order = lmhosts host wins bcast
    
    #### Networking ####
    
    # The specific set of interfaces / networks to bind to
    # This can be either the interface name or an IP address/netmask;
    # interface names are normally preferred
    ;   interfaces = 127.0.0.0/8 eth0
    
    # Only bind to the named interfaces and/or networks; you must use the
    # 'interfaces' option above to use this.
    # It is recommended that you enable this feature if your Samba machine is
    # not protected by a firewall or is a firewall itself.  However, this
    # option cannot handle dynamic or non-broadcast interfaces correctly.
    ;   bind interfaces only = yes
    
    
    
    #### Debugging/Accounting ####
    
    # This tells Samba to use a separate log file for each machine
    # that connects
    
    # Cap the size of the individual log files (in KiB).
    
    # If you want Samba to only log through syslog then set the following
    # parameter to 'yes'.
    #   syslog only = no
    
    # We want Samba to log a minimum amount of information to syslog. Everything
    # should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
    # through syslog you should set the following parameter to something higher.
    
    # Do something sensible when Samba crashes: mail the admin a backtrace
    
    
    ####### Authentication #######
    
    # "security = user" is always a good idea. This will require a Unix account
    # in this server for every user accessing the server. See
    # /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
    # in the samba-doc package for details.
    #   security = user
    
    # You may wish to use password encryption.  See the section on
    # 'encrypt passwords' in the smb.conf(5) manpage before enabling.
    
    # If you are using encrypted passwords, Samba will need to know what
    # password database type you are using.  
    
    
    # This boolean parameter controls whether Samba attempts to sync the Unix
    # password with the SMB password when the encrypted SMB password in the
    # passdb is changed.
    
    # For Unix password sync to work on a Debian GNU/Linux system, the following
    # parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
    # sending the correct chat script for the passwd program in Debian Sarge).
    
    # This boolean controls whether PAM will be used for password changes
    # when requested by an SMB client instead of the program listed in
    # 'passwd program'. The default is 'no'.
    
    # This option controls how unsuccessful authentication attempts are mapped
    # to anonymous connections
    
    ########## Domains ###########
    
    # Is this machine able to authenticate users. Both PDC and BDC
    # must have this setting enabled. If you are the BDC you must
    # change the 'domain master' setting to no
    #
    ;   domain logons = yes
    #
    # The following setting only takes effect if 'domain logons' is set
    # It specifies the location of the user's profile directory
    # from the client point of view)
    # The following required a [profiles] share to be setup on the
    # samba server (see below)
    ;   logon path = \\%N\profiles\%U
    # Another common choice is storing the profile in the user's home directory
    # (this is Samba's default)
    #   logon path = \\%N\%U\profile
    
    # The following setting only takes effect if 'domain logons' is set
    # It specifies the location of a user's home directory (from the client
    # point of view)
    ;   logon drive = H:
    #   logon home = \\%N\%U
    
    # The following setting only takes effect if 'domain logons' is set
    # It specifies the script to run during logon. The script must be stored
    # in the [netlogon] share
    # NOTE: Must be store in 'DOS' file format convention
    ;   logon script = logon.cmd
    
    # This allows Unix users to be created on the domain controller via the SAMR
    # RPC pipe.  The example command creates a user account with a disabled Unix
    # password; please adapt to your needs
    ; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
    
    # This allows machine accounts to be created on the domain controller via the 
    # SAMR RPC pipe.  
    # The following assumes a "machines" group exists on the system
    ; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u
    
    # This allows Unix groups to be created on the domain controller via the SAMR
    # RPC pipe.  
    ; add group script = /usr/sbin/addgroup --force-badname %g
    
    ########## Printing ##########
    
    # If you want to automatically load your printer list rather
    # than setting them up individually then you'll need this
    #   load printers = yes
    
    # lpr(ng) printing. You may wish to override the location of the
    # printcap file
    #;   printing = bsd
    #;   printcap name = /etc/printcap
    
    
    
    
    # CUPS printing.  See also the cupsaddsmb(8) manpage in the
    # cupsys-client package.
    #;   printing = cups
    #;   printcap name = cups
    
    ############ Misc ############
    
    # 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 = /home/samba/etc/smb.conf.%m
    
    # Most people will find that this option gives better performance.
    # See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
    # for details
    # You may want to add the following on a Linux system:
    #         SO_RCVBUF=8192 SO_SNDBUF=8192
    #   socket options = TCP_NODELAY
    
    # The following parameter is useful only if you have the linpopup package
    # installed. The samba maintainer and the linpopup maintainer are
    # working to ease installation and configuration of linpopup and samba.
    ;   message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &
    
    # Domain Master specifies Samba to be the Domain Master Browser. If this
    # machine will be configured as a BDC (a secondary logon server), you
    # must set this to 'no'; otherwise, the defyault behavior is recommended.
    #   domain master = auto
    
    # Some defaults for winbind (make sure you're not using the ranges
    # for something else.)
    ;   idmap uid = 10000-20000
    ;   idmap gid = 10000-20000
    ;   template shell = /bin/bash
    
    # The following was the default behaviour in sarge,
    # but samba upstream reverted the default because it might induce
    # performance issues in large organizations.
    # See Debian bug #368251 for some of the consequences of *not*
    # having this setting and smb.conf(5) for details.
    ;   winbind enum groups = yes
    ;   winbind enum users = yes
    
    # Setup usershare options to enable non-root users to share folders
    # with the net usershare command.
    
    # Maximum number of usershare. 0 (default) means that usershare is disabled.
    ;   usershare max shares = 100
    
    # Allow users who've been granted usershare privileges to create
    # public shares, not just authenticated ones
    
    #======================= Share Definitions =======================
    
    #[homes]
    #   comment = Home Directories
    #   browseable = no
    
    # By default, the home directories are exported read-only. Change the
    # next parameter to 'no' if you want to be able to write to them.
    #   read only = yes
    
    # File creation mask is set to 0700 for security reasons. If you want to
    # create files with group=rw permissions, set next parameter to 0775.
    #  create mask = 0700
    
    # Directory creation mask is set to 0700 for security reasons. If you want to
    # create dirs. with group=rw permissions, set next parameter to 0775.
    #  directory mask = 0700
    
    # By default, \\server\username shares can be connected to by anyone
    # with access to the samba server.
    # The following parameter makes sure that only "username" can connect
    # to \\server\username
    # This might need tweaking when using external authentication schemes
    #   valid users = %S
    
    # Un-comment the following and create the netlogon directory for Domain Logons
    # (you need to configure Samba to act as a domain controller too.)
    ;[netlogon]
    ;   comment = Network Logon Service
    ;   path = /home/samba/netlogon
    ;   guest ok = yes
    ;   read only = yes
    
    # Un-comment the following and create the profiles directory to store
    # users profiles (see the "logon path" option above)
    # (you need to configure Samba to act as a domain controller too.)
    # The path below should be writable by all users so that their
    # profile directory may be created the first time they log on
    ;[profiles]
    ;   comment = Users profiles
    ;   path = /home/samba/profiles
    ;   guest ok = no
    ;   browseable = no
    ;   create mask = 0600
    ;   directory mask = 0700
    
    #[printers]
    #   comment = All Printers
    #   browseable = no
    #   path = /var/spool/samba
    #   printable = yes
    #   guest ok = no
    #   read only = yes
    #   create mask = 0700
    
    # Windows clients look for this share name as a source of downloadable
    # printer drivers
    
    #[print$]
    #   comment = Printer Drivers
    #   path = /var/lib/samba/printers
    #   browseable = yes
    #   read only = yes
    #   guest ok = no
    # Uncomment to allow remote administration of Windows print drivers.
    # You may need to replace 'lpadmin' with the name of the group your
    # admin users are members of.
    # Please note that you also need to set appropriate Unix permissions
    # to the drivers directory for these users to have write rights in it
    ;   write list = root, @lpadmin
    
    # A sample share for sharing your CD-ROM with others.
    ;[cdrom]
    ;   comment = Samba server's CD-ROM
    ;   read only = yes
    ;   locking = no
    ;   path = /cdrom
    ;   guest ok = yes
    
    # The next two parameters show how to auto-mount a CD-ROM when the
    #	cdrom share is accesed. For this to work /etc/fstab must contain
    #	an entry like this:
    #
    #       /dev/scd0   /cdrom  iso9660 defaults,noauto,ro,user   0 0
    #
    # The CD-ROM gets unmounted automatically after the connection to the
    #
    # If you don't want to use auto-mounting/unmounting make sure the CD
    #	is mounted on /cdrom
    #
    ;   preexec = /bin/mount /cdrom
    ;   postexec = /bin/umount /cdrom
    
    
    [master_share]
    	path = /mnt/sata_share
    
    [watch]
    	comment = torrent watch dir
    	path = /mnt/sata_share/watch
    
    [completed]
    	path = /mnt/sata_share/completed
    
    [store]
    	path = /mnt/sata_share/store
    
    [tv]
    	path = /mnt/sata_share/tv
    
    [usb]
    	force user = root
    	path = /media/usb_mnt
     
  5. Keridos

    Keridos New Member

    Joined:
    Nov 19, 2013
    Messages:
    22
    Likes Received:
    0
    I noticed the issue is very strange: When I use Gigabit ethernet i have huge packetloss on the udoo. Seems as if it is not able to keep up with the amount of packets sent. What could cause that? Only workaround I found so far is changing the networking speed to 100Mbits/s, that seems to run fine.
     
  6. Andrea Rovai

    Andrea Rovai Well-Known Member

    Joined:
    Oct 27, 2014
    Messages:
    1,703
    Likes Received:
    240
    Hi there Keridos,
    What do you mean by "huge packetloss"? Can you post where did you reach this information? I think I need more clue, can you post something?
    Andrea
     
  7. robertkjonesjr

    robertkjonesjr New Member

    Joined:
    Jan 3, 2015
    Messages:
    5
    Likes Received:
    0
    I have run into this slow Ethernet issue. With iperf, I could detect it. I found in one of these threads someone pointed to a link that discussed pause frames - and sure enough, when I enable pause frame support on my managed switch, I get max throughput. I would see - from memory - somewhere around 450Mbps with iperf tcp, maximum. When plugged into a gig port without pause frame support, it's much less. I still have not figured out how to capture a pause frame in Wireshark, but I have counters in my switch that show them, and I recall some drivers in Linux will show them as well - check ethtool. I forget if udoo let me see them with the fec driver, but I know one of my other laptops did with ethtool.

    Anyway, something to check.
     
  8. fetcher

    fetcher Member

    Joined:
    Mar 9, 2014
    Messages:
    166
    Likes Received:
    20
    The i.MX6 chip's Ethernet controller is not capable of keeping up with full Gigabit transfer rates. Freescale notes this in their reference manual (p. 1073 of IMX6DQRM.pdf)--

    "Important Note:The theoretical maximum performance of 1 Gbps ENET is limited to 470 Mbps (total for Tx and Rx) due to Chip internal bus throughput limitation. The actual measured performance in an optimized environment is up to 400 Mbps. See erratum ERR004512 in the device silicon errata document."

    If incoming data rates exceed the bus capacity, packets will get dropped, and due to TCP's congestion-avoidance backoff behavior this can have a severe impact on performance, way beyond what you might expect from the proportion of drops. It sounds like the pause-frame flow control mechanism is an effective way to avoid overrunning the i.MX6's receive buffers.

    I've avoided this issue by just keeping my Udoo's locked at 100M, since that's sufficient for my needs and allows using cheap 8309sc-based switches for VLAN tagging and fanout to multiple routed interfaces. Dropping from 1000baseT to 100baseTX line rate also saves about a watt of power total across both ends of the link.
     
  9. Keridos

    Keridos New Member

    Joined:
    Nov 19, 2013
    Messages:
    22
    Likes Received:
    0
    I had the issue that until now I could not get Pause Frame Support working on my distribution. Updated the pretty old 3.0 Kernel to a 3.18.8 now which should also improve Networking a bit since some changes were made to it in 3.10. Gonna recheck if I can get pause frame use working.

    /edit: ethtool lists pause frame use as Symmetric so i guess I got that working now. Now to check why the heck my sata hd is not showing any partitions...

    /edit2: still have packet loss, but far less than on the old kernel. Pause Frame Use is on now. Any additional Hints how I could fix that?
     

Share This Page