@oric1:
I just re-tested here, and I have no problem changing my output power. I suspect it might be a browser issue - try with a different browser, or try flushing your browser cache.
@Maghook:
I also occasionally notice the issue where the workgroup is displayed instead of the hostname. Unfortunately this is highly random, so I can't reproduce it easily enough to be able to troubleshoot it. Usually the problem disappears within a day, when all devices have renewed their DHCP leases.
USB apps: try with a disk plugged in. Download Master for instance will require a USB disk to be able to install itself.
Your issues with the timezone and the radio schedule sound like browser-based issues, as I can't reproduce any of these. Try flushing your browser cache, or using a different browser. Asuswrt relies heavily on Javascript, so things can easily break if, for instance, you run addins in your browser that interfere with them (AdBlock with incorrect filters, for example).
Fab30:
I'm not sure, but I assume it will create the .swap file on the same disk where you have Optware initialized. Check using "ls /tmp/sda1/.swap -al" to see if it's on sda1, try again with sdb1 and sdc1. I never actually tested the swap support, only saw the related nvram entries and some code in the optware support tools.
Andu:
I have to agree there, using a router with a non-bridged modem will always be quite tricky (if not flat out quirky). If you establish the PPPoE connection inside the router, then make sure the modem is not configured to also establish the connection itself (i.e. enter blank usernames/passwords in the router). What is even weirder to me is the fact that a reboot does not work, while a power cycle works. The only way this could actually make a difference is if the modem itself is the one doing something special whenever it sees the router disappear from its LAN interface (when you power cycle it).
I don't know how much ADSL2 modems cost in your area, but see if you could get an inexpensive one for like 30$-40$. If you can, I think it would be money well spent if you don't see VDSL available for a few months.
You could also see if anyone you know has one they could let you use so you could at least test it during a weekend.
Otherwise, it could be easy to setup a cron job on the router that would force it to reboot every 24 hours. You could set it to reboot itself in the middle of the night for instance - see if that helps.
cc666:
You could also have checked the Sysinfo page, under Tools I report the used/total nvram there.
nackerton:
Turning some of the LEDs off isn't really the problem. The problem is ensuring they don't turn themselves back on - that's the tricky part. Making a global "LED killswitch" would be a bit tricky, and I'm not even sure I can easily control ALL of the LEDs. Some of them (like power or the LAN LEds) might be hardwired.
I just re-tested here, and I have no problem changing my output power. I suspect it might be a browser issue - try with a different browser, or try flushing your browser cache.
@Maghook:
I also occasionally notice the issue where the workgroup is displayed instead of the hostname. Unfortunately this is highly random, so I can't reproduce it easily enough to be able to troubleshoot it. Usually the problem disappears within a day, when all devices have renewed their DHCP leases.
USB apps: try with a disk plugged in. Download Master for instance will require a USB disk to be able to install itself.
Your issues with the timezone and the radio schedule sound like browser-based issues, as I can't reproduce any of these. Try flushing your browser cache, or using a different browser. Asuswrt relies heavily on Javascript, so things can easily break if, for instance, you run addins in your browser that interfere with them (AdBlock with incorrect filters, for example).
Fab30:
I'm not sure, but I assume it will create the .swap file on the same disk where you have Optware initialized. Check using "ls /tmp/sda1/.swap -al" to see if it's on sda1, try again with sdb1 and sdc1. I never actually tested the swap support, only saw the related nvram entries and some code in the optware support tools.
Andu:
I have to agree there, using a router with a non-bridged modem will always be quite tricky (if not flat out quirky). If you establish the PPPoE connection inside the router, then make sure the modem is not configured to also establish the connection itself (i.e. enter blank usernames/passwords in the router). What is even weirder to me is the fact that a reboot does not work, while a power cycle works. The only way this could actually make a difference is if the modem itself is the one doing something special whenever it sees the router disappear from its LAN interface (when you power cycle it).
I don't know how much ADSL2 modems cost in your area, but see if you could get an inexpensive one for like 30$-40$. If you can, I think it would be money well spent if you don't see VDSL available for a few months.
You could also see if anyone you know has one they could let you use so you could at least test it during a weekend.
Otherwise, it could be easy to setup a cron job on the router that would force it to reboot every 24 hours. You could set it to reboot itself in the middle of the night for instance - see if that helps.
cc666:
You could also have checked the Sysinfo page, under Tools I report the used/total nvram there.
nackerton:
Turning some of the LEDs off isn't really the problem. The problem is ensuring they don't turn themselves back on - that's the tricky part. Making a global "LED killswitch" would be a bit tricky, and I'm not even sure I can easily control ALL of the LEDs. Some of them (like power or the LAN LEds) might be hardwired.