However, none of the computers in the house were able to print to it, using LPD/LPR - they would be able to send print jobs, and get acknowledgement, but there was no logging within the Admin UI, and nothing was received by the printer. Once I got back to the admin UI I was able to connect the printer, and the router showed that it had a connection.
#Dd wrt log in android#
One initial issue was that I wasn’t able to get back to the router’s admin UI, and neither Fing nor Nmap were able to find it on the subnet for whatever reasons, possibly pebkac Asus have a windows app called “Device Discovery”, which does the necessary magic to locate Asus devices and provide the IP, but since I don’t run Windows I was temporarily blocked, until I discovered that they also have an Android app - which worked, after I installed it. Third time was the charm, however, and I was able to get a good connection to the internet through the router.
#Dd wrt log in full#
Why did I want to use DD-WRT anyway? I had only moderately non-traditional requirements for it I wanted it to bridge a wireless connection from the main house router to my desktop computer, also act as server for a USB laserjet printer, and not broadcast as an access point itself (part of the goal here was to replace an aging Intel NUC which I have set up as a print server, running CUPS it frequently stalls in booting up when it gets inadvertently power cycled, leading to wife frustration at the printer not being available.) I did set it up in Media Bridge mode relatively easily, but on the first two attempts at doing so the router didn’t come up with an active connection (despite showing full bars on the access point that I wanted to connect it to, in the setup wizard).
Twice I got the thin webapp to come up and uploaded the DD-WRT image, but in both cases the router decided to reboot 2 or 3 minutes in, and left itself on the stock Asus firmware. It was only after I’d set the router to a static IP in Media Bridge mode, and rebooted into rescue mode, that I was able to get to it by IP, and then only sometimes. On several of the times that it did, I wasn’t able to navigate to it by IP. I attempted this routine somewhere around a dozen times often, my computer wasn’t even able to negotiate a wired connection with the router. This is then supposed to surface an alternate thin web application which permits uploading replacement firmware, a failsafe that allows bricked routers to be recovered. There’s a workaround mentioned in the DD-WRT wiki: power cycle the router with one of the two reset buttons held down (the inset one), and keep the reset button held down after it comes up until the power light starts blinking you’re also supposed to make sure you’re on the same subnet as the IP it comes up on, and need to be connected via ethernet cable. That’s not entirely true though, as they do permit the third party Asus Merlin firmware to be installed when I asked their tech support if they endorsed or recommended it, they said no, and told me to revert to stock firmware if I’d installed it (which I had, as an experiment.) When you try to upload firmware using the admin UI, you get a message that says roughly “for compliance reasons, we do not permit third party firmware”. This is quite frustrating, because for the past few years Asus have blocked (most) third party firmware from being installed.
When you search online for lists of recommended routers to run DD-WRT on, Asus comes up frequently, even in non-SEO-driven listicles.
0 kommentar(er)
