Hi,
I’m just wondering if anyone else has experienced this - it’s hard to be sure of the exact reasons.
I’ve had the 433 for a couple of weeks, and it’s been running Beta 1 just fine on IPv4, over pure ethernet.
I reset the config and re-configured last night for PPPoE, firstly IPv4 (/28) and then IPv6. It worked fine for a couple of hours (very little traffic, home use) but as I started adding IPv6 firewall rules, it froze at the CLI.
I had to manually power-cycle it, and everything seemed okay again, but it kept freezing (my shell would get a read error eventually) and seemed to become more prominent - suffice to say, it wasn’t passing any data at the point of freeze (that I could see - my connections all died).
I tried disabling IPv6 in-between hangs, but it didn’t seem to stop the problem.
I’ve since gone back to my RB750 (on the 4.6 OS) with just IPv4 and I’m running again.
This could be a hardware fault or something else - I realise that - I’m just wondering if anyone has experienced something similar or if there’s a known problem.
(As an aside, why do RBs keep disconnecting after a short period via winbox if they have an invalid IP address ? I always seem to have to rush to get a valid IP assigned before it kicks me out - this is connecting via MAC using the wine version on OSX if it matters).
Thanks for any help,
Michael.
Not sure if I can help you, but if I can get Winbox working on my MacBook Pro, I can see if the Wine Mac OS X Winbox variable is the issue or not.
What version of Mac OS X are you running? I’ve gotten the pre-compiled Wine Winbox available on the MikroTik Wiki to run on an iMac running Mac OS X 10.5.8, but I only got it to come up with the “Connect To” box and never actually connected to a RouterBOARD to test it. I really need it to run on my MacBook Pro, so I can use it in the field. Are you running Winbox on Snow Leopard (I’m running OS X 10.6.3).
If so please share, so I can duplicate your setup here and see if I experience the same issue.
If you could, please share how you got Winbox running on Mac OS X on this thread discussion regarding Winbox on other OS’s: http://forum.mikrotik.com/viewtopic.php?f=1&t=23241&start=50&hilit=winbox+mac+os+x
I use the WineBottler version of winbox, as found http://wiki.mikrotik.com/wiki/MikroTik_WinBox_for_Mac_StandAlone, pre-compiled by SomniusX.
It runs both on OSX 10.5.8 and 10.6.2 for me, and generally functions fine, although as mentioned above it’s sometimes a bit ‘quirky’ if no address is defined. I generally use SSH into the RB anyway for most purposes as I’m happier that way and only use winbox for initial ‘addressing’ along with drag/drop re-ordering of firewall rules (If we could define each ‘chain’ in a separate area, it would make the CLI much easier to use).
I’m guessing it’s the UDP part that’s a bit ‘flaky’ in this regard, due to the connection method.
I don’t really have a problem with winbox, and if it bothered me much more I’d write a Java app to do it (though I’d like to know the UDP/MAC connection details).
I’m more concerned with whether my RB433UAH is suffering from a hardware fault (it’s new), or if it’a a bug in ROS 5.0 that needs to be fixed.
Michael.
Normis helped me get it working on my machine and I’ve used it quite a bit in the last 24 hours! lol. I haven’t come across any “quirks” that you are referring to. The only issue I’ve run into is not being able to drag and drop files into the files window to update the OS/Firmware. Everything else works like a charm. So I think it’s safe to say it is not a software issue (at least with WinBox running on a Mac).
I don’t have a RB433UAH so I can not load ROS 5 beta on one to see if I can duplicate the issue. However, I do have RB600a’s and RB800’s that I can (and was planning to) load ROS 5 beta for testing, and I will attempt to duplicate the issue and let you know what I find.
Did you ever determine whether the IPv6 Firewall Rules quirk was a config issue or hardware issue. And as far as using the MAC Address to connect to a RouterOS device using a Mac with the Wine version of Winbox, I use the crap out of Winbox on my MacBook Pro in both the lab and in the field and configure RouterBOARDs to deploy in the field completely from start to finish in my office using the MAC Address to access the device the whole time. I’ve been told you are not supposed to use the MAC Address to connect to a RouterBOARD by Normis, or rather to do it with caution and without warranty, but I have never experienced and issue with doing so thus far, even adding in the variable of using a program written for Windows on a Mac to access the BOARD via the MAC Address! lol.
I switched back to an Alix running m0n0wall until v5 is out of beta - I’ll maybe try again then, although I generally leave it alone whilst it’s working 
Amen. I’ve recently learned the hard way that the statement “if it ain’t broke don’t fix it” really holds value in networking. lol.