Not a Winbox issue. I can connect a laptop with its NIC forced to 100FDX and see ping loss. I also see devices downstream of a 100M interface on this router that I monitor for packet loss and starting when this router was changed, the packet loss graphs went from essentially zero to around 0.5%.
From: Josh Luthman Sent: Sunday, January 03, 2016 5:03 PM To: [email protected] Subject: Re: [AFMUG] Mikrotik x86 and ROS 6.x problems on 100M Ethernet links FYI I use Winbox 2.2.18 100% of the time since 11/3/2011 - maybe try that? Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Sun, Jan 3, 2016 at 6:01 PM, Ken Hohhof <[email protected]> wrote: I get the same results with Winbox 3.0 or Winbox 2.2.13. Note this problem shows up as on other stuff not just Winbox, it's just easy to test with Winbox because it shows up easily as disconnects or failure to load plugins. Note that I can use Winbox fine through an interface running at gigabit, or I can Winbox through this router to another Mikrotik via a 100M interface, the stress on the interface seems to be when the packets are originating from this router itself and trying to go out a 100M interface. But I also see low level packet loss on normal traffic through the interface, although it doesn't show up as drops or errors in the stats. -----Original Message----- From: Faisal Imtiaz Sent: Sunday, January 03, 2016 4:35 PM To: [email protected] Subject: Re: [AFMUG] Mikrotik x86 and ROS 6.x problems on 100M Ethernet links Are u using the new version of winbox ? i.e. ver 3.0 ? there are issues with older version of the Winbox too. Faisal Imtiaz Snappy Internet & Telecom 7266 SW 48 Street Miami, FL 33155 Tel: 305 663 5518 x 232 Help-desk: (305)663-5518 Option 2 or Email: [email protected] ----- Original Message ----- From: "Ken Hohhof" <[email protected]> To: [email protected] Sent: Sunday, January 3, 2016 4:03:22 PM Subject: Re: [AFMUG] Mikrotik x86 and ROS 6.x problems on 100M Ethernet links I tried multi-queue Ethernet default and it didn't work, even with queue size increased to 500 packets. 5.26 still works fine. Best way to see problem is to clear Winbox cache so it has to download plugins. -----Original Message----- From: Faisal Imtiaz Sent: Sunday, January 03, 2016 11:02 AM To: [email protected] Subject: Re: [AFMUG] Mikrotik x86 and ROS 6.x problems on 100M Ethernet links Don't forget to reboot the unit after making the queue changes. Also I would suggest to reach out to Brian Vargas @ Balticnetworks and see if they have any suggestions and or if they can replicate what you are seeing. Regards. Faisal Imtiaz Snappy Internet & Telecom 7266 SW 48 Street Miami, FL 33155 Tel: 305 663 5518 x 232 Help-desk: (305)663-5518 Option 2 or Email: [email protected] ----- Original Message ----- From: "Ken Hohhof" <[email protected]> To: [email protected] Sent: Saturday, January 2, 2016 11:27:45 PM Subject: Re: [AFMUG] Mikrotik x86 and ROS 6.x problems on 100M Ethernet links I thought about the first part but didn't try it, I'll try it on the lab router tomorrow. No, I don't see anything reported in the stats, as far as they are concerned, everything is good. -----Original Message----- From: Faisal Imtiaz Sent: Saturday, January 02, 2016 10:17 PM To: [email protected] Subject: Re: [AFMUG] Mikrotik x86 and ROS 6.x problems on 100M Ethernet links Try something.... change the interface queue to multi-queue-Ethernet-default and increase the queue size packet buffer for it. (it should be mq pfifo) Do you see errors / packet loss being reported in the stats ? Regards. Faisal Imtiaz Snappy Internet & Telecom 7266 SW 48 Street Miami, FL 33155 Tel: 305 663 5518 x 232 Help-desk: (305)663-5518 Option 2 or Email: [email protected] ----- Original Message ----- From: "Ken Hohhof" <[email protected]> To: [email protected] Sent: Saturday, January 2, 2016 8:09:46 PM Subject: Re: [AFMUG] Mikrotik x86 and ROS 6.x problems on 100M Ethernet links I downgraded to 6.25 and still saw the problems. I don't really want to go back any farther, likely the issue started with the new kernel and drivers when 6.x first came out. I figure if I can't run any of the recent versions, I might as well go back to 5.26. Unless someone knows of a specific cause and how to fix it. -----Original Message----- From: Kevin Radunz Sent: Friday, January 01, 2016 1:32 PM To: [email protected] Subject: Re: [AFMUG] Mikrotik x86 and ROS 6.x problems on 100M Ethernet links I think some weard problems started around 6.33. There are posts of different topics about things like Winbox and VPN traffic not working but traffic through the device was fine. Some thought MTU changes but I'm not sure I saw concrete fixes. I know earlier versions don't do this. I recently upgraded one of those RouterMaxx 1106 routers from 5.2 to 6.33.1 (I actually configured a new router and swapped hardware). Ever since, I have had performance problems with a couple ports that are connected to radios with 100M Ethernet ports. The most obvious symptom is that Winbox won't stay connected or can't download plugins, but I also see pings dropped even to the directly connected equipment. I was a bad boy making multiple changes at once, so I've been gradually walking them back in the lab on the original router, I upgraded it to 6.33.1 and the problem appeared. I dropped back to 6.31 and it was still there, but when I dropped back to 5.26 everything was fine again. I haven't tried earlier 6.x versions yet, 6.31 is the oldest x86 version I have handy. This is not a radio problem, I can reproduce it with a directly connected laptop if I force the laptop NIC to 100M FDX. Is anyone familiar with this problem? I can't find anything on the Mikrotik forums. I guess I can live with 5.26 if I have to, but I'd like to know what is causing this. Do I just need to change some configuration parameter? I know 6.x brought out hardware only queues, but I think that's for Routerboards, not x86. Is there a problem with the Intel NIC drivers included with 6.x? Any chance that an earlier or later version of 6.x will >>> work for me? I see nothing in the change logs about it.
