Try this:
#!/bin/sh
echo "server=/bbc.co.uk/149.154.158.186" > /tmp/etc/dnsmasq.conf
Thanks, but it did not help.
My guess is the startup script does not start correctly or the dnsmasq.conf will be rewritten after this script.
Updated OP with 3.0.0.3.157.12 Beta 3. This will hopefully be the last beta before the final release.
This update mostly consists of fixes related to the new NAT loopback code.
Hello.
I just flashed this firmware being attracted by dual wan functionality mainly. Here is some feedback from me.
Failover is all i need and it seems to be working somewhat, but not completely. My primary connection is set to automatic ip and secondary to static ip (i plugged it into lan 4). If I unplug cable from wan port the switch over happens as it should and everything works just fine. But when I reconnect the cable back reverse switch doesn't happen, the secondary connection stays active forever and I can't find any way to switch back manually except rebooting router.
Also it's quite convenient to have some way to enable/disable primary and secondary connections separately through web interface (like it's done in chinese tomato dualwan firmware, for example). I hope it will be implented some day.
Good day!!!
Is it possible to expect adjustment on the following items?
1) Adjusting the reserve LAN\WAN channel we can't specify for it wan connection type. ..if provider distribute ip-adr not in «automatic IP» we will have disabled reserve LAN\WAN channel!!!(it is necessary to specify wan connection type for reserve LAN\WAN)
2) If the reserve channel is put via the USB modem, there is no transition to the main at its restoration(when the main channel becomes efficient);
3) whether it is possible to realize two reserve channels? Both through LAN\WAN and through USB? And as to point a priority to connection (first of all) when falling the main WAN?...
4) The most important for the reserve channel... method of determination of its not working capacity:
When on the account of provider money come to an end, service to us isn't available. And we have the disabled channel. In this regard one of methods of check of operability of the channel would be ping to the specified knot (which is set by the user). When the main channel can ping knot, we pass to the main channel…(it is good to unite a method which is also and method on an available resource)
Excuse for my English, we very much watch closely your updatings. Is Internet resource lostrealm.ca your (donate)?
The Dual WAN code is actually developed by Asus, and I'd rather not do any change to it since I have no way of actually testing those changes. Also, each new firmware release they make sees a lot of changes around that code, so I think it's still under active development by Asus. A lot can change with each new version related to Dual WAN, so any work I would do on that code might be wasted once the next version comes out.
Link recovery is probably the biggest missing feature at the moment to make Dual WAN really useful as a failover mechanism. I expect Asus to eventually implement it, since it's a pretty important part of any failover mechanism. If not, I recommend emailing them once they start releasing official firmware releases with Dual WAN enabled in them.
Yes, http://www.lostrealm.ca/ is my personal website, and the Paypal donate button there links to my account.
Link recovery is something that Asus hasn't implemented yet AFAIK. The issue also occurs when using the regular 3G failover mode, so it's not specific to the Dual Wan code.
One way to manually recover could be to disable, then re-enable the WAN interface. This should hopefully trigger a restart of all WAN interfaces, without rebooting the entire router. Give it a try.
You can test the dual wan link by using your N66U behind a "internet" connected router.
init-start is run before all services. Your config is probably overwritten when the dnsmasq service starts.
Try using services-start instead of init-start, and make sure to also restart dnsmasq in that script after you modify the config file.
Sorry for asking but what's the command to restart dnsmasq?.
killall dnsmasq
dnsmasq -c 1500 --log-async -n
Traffic Monitor seems to be broken when viewing Internet in beta 2+3?
http://s10.postimage.org/b6cwttrqx/Capture.png
As you can see after I flashed the beta the usage is bugged.
I guess its related
Thanks, but it did not help.
My guess is the startup script does not start correctly or the dnsmasq.conf will be rewritten after this script.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!