Been running a HEX S as a firewall / NAT along with DHCP in a small home (and a 2nd at a church) for several years and it’s worked fine. However after an upgrade here at home from 60/5 to 500/500 Mbps the HEX S has turned into a bottleneck with speeds topping out around 95 Mbps both ways. Still running 6.49.18 but willing to move to V7; no ipv6. Need minimum 4 (or more) ports, no WiFi.
Looking for suggestions / guidance - first off I’m a retired server sysadmin and at my final job there was a whole network group so there is a very good chance I’ve got something messed up with the configuration of the HEX S. Can upload a copy of my running config.
The HEX S has worked great but I’m open to upgrading to something more powerful from Mikrotik both for me and my church if they decide to get faster internet.
Did an export verbose from the terminal and all five ether1-5 show " speed=1Gbps". Check of my desktop computer shows link at 1 GBbs as well. A speed test before the hEX S does show 500 Gbps speeds so it is something with the Mikrotik. Oh, the spf port is not in use.
Hex S routing test results ( 512 bytes/25 firewall filter rules) say 265.
Usually that is a good indication of possible performance, i.e. you should be able to reach at least that speed.
Depending on setup/configuration (Fasttrack, Hardware Offload, etc.) usually much higher speed can be reached.
So there must be something “wrong” in your configuration, post It for review
Instructions here: http://forum.mikrotik.com/t/forum-rules/173010/1
I still think that you might have a problem. The “export” series of commands - whichever verbosity you select - only show the configuration of the device, not the actual status. My thought is that you configure - correctly - to advertise every speed up to 1Gbps, but then the auto-negotiation results in a lower speed actually selected. This does not show up in an export. The command for this is:
/interface ethernet monitor
This shows the actual rate the port is running at.
My suspicion is triggered not only because your throughput number is exactly where I would expect it on a 100 Mbps line, but the hEX S maxes out at somewhere in the 200-300 Mbps region. With fasttrack enabled, it can handle the 500/500 just fine - so probably once you find the problem, you won’t even need new hardware. Of course if you want new hardware, that’s another matter entirely
Ok first off I recognize you from the now gone dslreports.com based on your animated icon! We may have chatted at some point in the past years (decades?) but I can’t remember what it was about.
Doing some research the RB5009 did show up but I wanted to run it across folks who know networking and that could improve my home throughput and my old hEX S could be a spare for my church along with my DSL modem / router as backups once I get them programmed for their configuration until they decide to migrate to fiber with higher speeds.
1, It would seem the hex gets a private LANIP from an upstream device.
In any case, one should NOT duplicate having an IP address AND an enabled IP DHCP client setting for wan termination.
Thus pick one NOT both!!!
On this line, if you manually added the netmask then remove it ( if generated by router fine ) /ip dhcp-server network
add address=192.168.1.0/24 comment=defconf dns-server=
192.168.1.206,8.8.8.8,8.8.4.4 gateway=192.168.1.1 netmask=24
Yes. There’s a static route, manual dns config and everything. Delete or disable the dhcp client.
Having both a static config and a dhcp client on the same interfaces causes periodic brief (<1s) interruptions in service, but does not lead to the decreased bandwidth situation. Nonetheless, it should be corrected.
Resolved: lurker888 called it: short answer is the hEX S and the Quantum Q Fiber W1700K 1Gb ports will only connect at 100Mb speeds, something I haven’t seen in years (decades?) since the early days of 1Gb network cards. Plugging the hEX S into a spare 1Gb switch and from there into the W1700K links up at the correct speed and I’m getting around 500Mb speeds up and down through the hEX S.
Apologies for missing the obvious - the W1700K access point / router is only configurable via an app with no web interface. While I can find the IP address of a port it doesn’t show the speed. And the VOIP box plugged in was showing the same yellow port LED so I assumed it was linking up at 1Gb speeds but I was wrong. Not much info on the AP/router on the web but yes I misread the status LEDs on the ports.
And for the Mikrotik experts - is there a WebFig or terminal command to query the port speeds? I couldn’t find it and my (dim) light bulb ah-ha moment came when I started plugging 1Gb devices in the W1700K and seeing different port lights. (Head smack.)
Many thanks for all who responded - being retired it seems I’m loosing my troubleshooting skills.
I didn’t include my network topology so let me see if I can explain it since I’m coming from DSL with a configurable modem/router to now on fiber:
DSL → router (192.168.0.0/24) old WiFi AP → hEX S (192.168.1.1) running firewall and dhcp on a separate wired network. At 192.168.1.206 is an old Windows Server 2012 R2 and plugged in is a desktop and laptop that are member workstations in an active directory domain. Windows AD gets grumpy if it’s DNS isn’t exactly right; yes it’s a weird setup for home use but at my last (final) job my knowledge of AD came in handy dealing with customers and kept me up to speed on AD.
Besides I did have MCSE certifications from Microsoft - minesweeper consultant and solitare expert. (Stolen from the net.)
Again my background is more server than networking but hopefully this explains my oddball separate internal network. Thanks for bringing that up.
[admin@MikroTik] > /interface ethernet monitor 0
name: ether1
status: link-ok
auto-negotiation: done
rate: 1Gbps
full-duplex: yes
tx-flow-control: no
rx-flow-control: no
Thank you jaclaz & lurker888! Didn’t dig deep enough into the command line but I will file that away in case I encounter any other weirdness with the hEX S connected to other devices.
Just an FYI: I gave the CLI command out of habit, but the same info is clearly labelled and readily available in the GUI interfaces, including the web one.
(Stolen from the net.)