Weird Bandwith Behaviour (download Throughput) On CentOS Based Gateway

Home » CentOS » Weird Bandwith Behaviour (download Throughput) On CentOS Based Gateway
CentOS 3 Comments

I have a company gateway that is connected to a 30/30 Fiber connection, network termination point is a MRV OS-904. It acts as a firewall/router for the DMZ/hosts/lans behind.

Software: CentOS 6.9, bare minimum install, all latest patches. Hardware: Xeon CPU, Intel server MB with two Intel PRO 1000 (e1000, e1000e) network cards, adaptec RAID, 8GB RAM

On the hosts/lan behind I can happily achieve 28.8 mbs – it seems it’s being capped at that speed by the provider.

However, on the host itself I cannot get passed 820k/s max, even if I switch off Iptables and anything else that could interfere with the download/upload bandwidth.

I have no idea why this is the case – It only matters when I need to “yum update” as the updates take 4 times longer than on the CentOS DMZ hosts behind it – but yes, its rather annoying!

Where do I need to look?
What am I missing?

3 thoughts on - Weird Bandwith Behaviour (download Throughput) On CentOS Based Gateway

  • Hi,

    Are you sure that your issue isn’t related to the mirror that your systems are selecting ? If they are using different mirrors I would try using the fastestmirror plugin to make the gateway select the same mirror as you other host.

  • Darn!!!!

    I should have included in the initial email that I actually ran EXTRA tests from a {local} CentOS mirror using wget after I figured there was some differences in the “yum update” times …

    The Gateway:

    [root@GATEWAY /tmp] #>wget http://mirror.internode.on.net/pub/CentOS/6.9/isos/x86_64/CentOS-6.9-x86_64-bin-DVD1.iso
    –2017-10-05 14:59:55– http://mirror.internode.on.net/pub/CentOS/6.9/isos/x86_64/CentOS-6.9-x86_64-bin-DVD1.iso
    Resolving mirror.internode.on.net… 150.101.135.3
    Connecting to mirror.internode.on.net|150.101.135.3|:80… connected.
    HTTP request sent, awaiting response… 200 OK
    Length: 3972005888 (3.7G) [application/octet-stream]
    Saving to: “CentOS-6.9-x86_64-bin-DVD1.iso”
    0% [ ] 4,454,198 680K/s

    One of the hosts behind it:

    [root@piquet /tmp] #>wget http://mirror.internode.on.net/pub/CentOS/6.9/isos/x86_64/CentOS-6.9-x86_64-bin-DVD1.iso
    –2017-10-05 15:01:32– http://mirror.internode.on.net/pub/CentOS/6.9/isos/x86_64/CentOS-6.9-x86_64-bin-DVD1.iso
    Resolving mirror.internode.on.net… 150.101.135.3
    Connecting to mirror.internode.on.net|150.101.135.3|:80… connected.
    HTTP request sent, awaiting response… 200 OK
    Length: 3972005888 (3.7G) [application/octet-stream]
    Saving to: `CentOS-6.9-x86_64-bin-DVD1.iso’
    0% [ ] 13,616,730 2.4M/s

    Jobst

  • Very good question, answer is no for the following reasons:

    – it happens for all downloads – yum, wget etc
    – I have looked at the interfaces using ngrep, all traffic goes straight out through the closest (as in hops) interface
    – As you raised this I have disabled caching on the command line using wget, still happens
    – As you raised this I have checked whether there are any (environment) options set, none
    I, too, use the same bash scripts on all machines I have

    I though about the interfaces, but can’t be. The last two interfaces are on the problem machine, but when downloading on the LAN I get a throughput of ~28mbs, only when downloading on the gateway I only get <10mbs.

    So still baffled.

    Jobst

LEAVE A COMMENT