hi everyone
two days ago, i have bought an rb192 as an upgrade for my home network, and i wanted to have dude server on it, so i wanted it to have ROS3. just before installing i checked the resources and it said that i have about 800 sector writes and 3 bad sectors, which i thought is not good but when i checked other people with routerboards they reported similar numbers. at this point i downloaded the latest rc of ROS3 from this site and loaded it via FTP to the routerboard (the number of written sectors went rapidly up, that was not unexpected) and rebooted it. this is where the problems appeared, the routerboard stareted checking my DHCP server with BOOTP requests, once every ten minutes. as i recall (i don’t have access to serial cable to change something in the BIOS), routerboard has default setting of boot from NAND and network if fail, using BOOTP for network. that means it has some problems with the internal memory…
and now the question
how can i revive my routerboard? it is only two days old and it doesn’t deserve to die like this…
yeah, i tried that, but it didn’t work (maybe because i have other DHCP servers in the network, although i turned them off for that moment), i couldn’t see any connecting routerboards. i think it it because netinstall is PXE/etherboot server but routerboard defaults to BOOTP. as i said, i don’t have the serial cable at me now (i can get one from a friend in like a week or so) so changing the communication protocol in BIOS is not possible at the moment.
anyway, how come that the routerboard could’t boot from NAND? maybe corrupted upload? or should i format the NAND before upgrading? or will the netinstall utility do this for me? and isn’t there a problem with netinstall under vmware? i use linux but have virtual windows for future experiments…
EDIT: I can set up a tftp server and boot the routerboard from it (theoretically), but what files should i put there and what settings should i use in the DHCP config file (ISC dhcpd)?
Netinstall runs its own bootp server so the best thing to do would be plug the routerboard directly into your computer. Set an IP (ex: 192.168.1.10/255.255.255.0) on your pc, then under the netbooting option in netinstall make sure the boot server is enabled, and put in an ip (ex: 192.168.1.11) then power cycle the routerboard. Wait approx 1 minute and it should show up in the netinstall program.
I’m not sure why your upgrade failed. Possibly the file didn’t transfer in binary mode or was corrupted somehow during the download/upload. I’m not sure. I’ve only had it happen a handful of times out of the 1000’s of RB’s I’ve upgraded.
The netinstall program will format the nand memory and I’m not not sure if netinstall will work in vmware. My guess is that it won’t..
Mikrotik doesn’t provide the files for us to run our own bootp/tftp server for netinstall so that’s not really an option either.
Also having a serial cable won’t help you much either since afaik there isn’t a way to upload routeros via serial.
You could (which saved my butt once apon a time) was to do a software reset. worked for me im not sure if it will fix this though. If not netinstall… -Jordan
ok, i’ll have to find a friend willing to lend me a winXP laptop, which means results will be available in two days or so…thanks for your help, hopefully, no more will be needed
my network consists of less than 10 nodes, which shouldn’t be too much for the rb192, while doing a bridge on all of its interfaces and a wireless AP (i have a separate linux machine for filtering/routing, but there is no dude server for linux AFAIK)
thanks everyone, it looks like it works (uploading the firmware just now)…
one hint to anyone trying this, DON’T make the subnet same as any other active connection (WiFi on my laptop) as netinstall will get confused and will not see the routerboard…
thanks everyone, especially Gerard, again…
EDIT: is there a dude server package for mipsel (rb100 and rb500)? i can’t find it in the system, installed from the complete package, but it is in my virtual ROS on x86…
