after falling asleep reading, the system locked-up. Re-started winbox and the terminal indicated some sort of fault and wanted a reboot. After reboot Dude happened!!! OK, all this time and I guess I needed winbox to screw-up to get dude to start. OK, false alarm, go back to whatever it was you were doing while I was napping. Thank you.
I am glad that you were able to succeed. I knew that it could not be such big problem for anyone.
Go through the following basic recipe which exactly follows the manual:
- Take one r3 hEX and reset it to the default factory configuration.
- Connect to the hEX from a Windows machine via ethernet port 2 using DHCP.
- Update the hEX to v6.40.rc5 of ROS to get the most recent version. Reboot.
- Download the Dude version v6.40.rc5. Reboot.
- In Dude > Settings enable The Dude. Reboot and check that The Dude is running and that it has created all of its files.
- Install The Dude client on the Windows machine.
- Start The Dude client and try to connect using IP address 192.168.88.1, user admin and no password - remember this is the default configuration.
- The client reports that it is connecting but nothing happens. End of demonstration.
- For variants add a microSD card with extra storage and format it as Ext3, etc, …
No doubt there is some magic missing ingredient - the point is that it is missing, i.e. undocumented. Actually, I assume that Mt has got the firewall settings wrong on either or both the client machine and the server machine, but I am not interested in debugging their mistakes.
First. Use stable version 6.39 or 6.39.1,not the RC. Paste the /dude export and /dude print commands result here.
The client has to be the same version like server.
I should say I had it working. No matter what I try, I could not get it to take the backup data from the previous router. Restore of the un-encrypted file even after removal of the ethernet port data fails. Restore of the other file causes a lockup. Cannot even login via winbox or webfig. I get the login feature turns grey and stays that way. Login username and password, hit enter… stays greyed-out. Have to interrupt using the power-plug. Then reset and start over.
I need the file restoration to work because there is data in the old one I do not know how to get entered into the new one. There are remote routers this one links to, they login, the data for this is buried somewhere in the old router and I cannot find it.
What backup do you mean exactly? TheDude does not have option to encrypt it’s backups.
From what device amd TheDude version are you trying to export your data?
the router with the dude on it is the problem. I can’t get the config from the old router into the new router such that the Dude can function properly. Not happening
Do not try to restore a backup file from another router or from different Ros version. Never.
This is very bad. I have a complex number of stuff to transfer from one router into another. The new one needs to work and you’re saying this should never be done? This is so impractical, it is insane! It would take hours to retype all this stuff and the passwords of numerous users would be lost. I’ve had other IT people do this in less than 5 minutes, I know they didn’t type a hundred lines of code by hand, nor did they log into a dozen other routers and check the passwords (because they can’t, they’re all mikrotik where passwords are hidden).
Use export - import instead. Read the manual.
been there, done that, doesn’t work, which is why I’m here. I really love it when I get or see the RTFM reply. Just really means you don’t know or won’t share the answer. I need to put the configuration of an rb2011 onto an rb750gr3. Only 2 of the ethernet ports are being used, the configuration is complex. It’s sole purpose in life was for monitoring other routers via eth1 (WAN) and the monitor connects to eth2 (a windows machine running dude and/or eth1 machines running the client remotely. The manual explains it as being simple to do, following those instructions, it faults everytime, even when the ethernet configuration is removed, router still becomes a brick and the manual doesn’t cover that. Insanity is doing the same thing over and over again expecting different results. Tired of this, RTFM yourself!
Maybe a different moderator will pickup with some real answers or be brave enough to share info.
The config import causes the hEX to become a brick? Most likely you simply lose connectivity because it disables or somehow alters the port you use to configure it. It would be great if you would show us the config that you are trying to import, that causes the problem.
You know, you can edit that file and remove anything that you don’t need to be imported in the other device.
Neighbor tab in winbox shows an address and a mac but can’t login. Attempts at login leave the winbox screen as greyed-out for a very long time (15 or more minutes) and then give a failed message.
did you try to connect with mac telnet?
actually to other model config. export works well just only by .rsc export - import
I understand that my hints may not help you directly. My approach is to reset wrongly working device with no defaults and set it from scratch. If easy, fully manually, if complex, by previously prepaired config script block by block. I cannot foresee mistakes you do during that… Just pay attention and do not do wrong things many times mentioned on this forum and follow the manual. If you have problems with reading it, do not expect that anyone will be rewriting it for you here.
I don’t suspect a router not responding to ping is going to telnet. No I haven’t tried telnet. Having never used telnet in the last 30 years, didn’t seem worth re-learning nor did it even come to mind. Is this spaghetti cooking class, see what sticks to the wall? I get a MAC and an IP showing in the neighbor tab on winbox. If I try to use either, the login screen goes grey and stays that way.
There are no MAC addresses appearing in *.rsc file, they have been removed. The config has been removed, router is a blank slate and it still screws up. I can reset it and log into it with default settings, so I don’t believe it’s broken. I no-longer have time to deal with this anymore as it requires me to be geographically somewhere else at a time when I need to be far away elsewhere. Problem with mortality.
If you see a Mac of fully reset device in neighbors of winbox, double click on that mac and connect with default admin user and no password.
did not work.
Here’s what I noticed. Reset 750gr3. login to it, remove config. Copy text of exported file from rb2011 into terminal, reboot, can’t login. Repeat previous except don’t reboot. Found stuff about rb2011 installed, however, none of that stuff was in the text (at least the part printed out on printer), hidden text in the export file(?). So now, trying to install the settings manually. Stuck at the firewall stuff. Cannot control the order, and some options don’t seem to be there like: dst-address-list=accept, and src-address-list=accept. Spent a few hours looking for this, what did Mikrotik change the name to?
Your difficulties look like learning process. Almost everything except setting the other mac to interface and few things with dude server can be done via winbox the same like in console. Maybe after the config removal you loose a bridge and connected interface has different mac so you need to follow. Leave the interface you use to config device alone and untouched until the rest works as expected and then put it in bridge /switch as intended and reconnect via ip… Maybe you have some other problem… Reordering the rules works when rules are aligned by their numbers. Then you can just drag and drop.
Address lists needs to be created before they can be used.