DHCP reservations are stored in nvram, in the dhcp_staticlist variable.
thanks for this, If I set this from the command line will it show up in the web gui? I don't have any to set at the moment so I can't test.
DHCP reservations are stored in nvram, in the dhcp_staticlist variable.
thanks for this, If I set this from the command line will it show up in the web gui? I don't have any to set at the moment so I can't test.
nvram dhcp_staticlist="....."
nvram commit
i googled a lot already, but could not find a solution (yet).
i'll go for separate names, thanks.
keeping the same name is useful only for fallback connection, or is there some kind of channel bonding?
I'm trying to adapt a dnsmasq script for ad blocking which I found here
http://www.dd-wrt.com/wiki/index.php/Ad_blocking
before attempting, I wanted to know if anyone here has done this already ?
nvram wl0_country_code=US
nvram wl_country_code=US
nvram wl0_country=US
nvram wl1_country=US
nvram wl1_country_code=US
nvram regulation_domain=US
nvram regulation_domain_5G=US
nvram commit
@RMerlin lets wait for the next official firmware release then. Maybe Asus finishes developing it meantime. If not, did you consider implementing that yourself?Dual WAN is an experimental feature, so it's possible that some functions might not be fully working yet.
I haven't changed anything.
Just change your router's region if you really want to bypass restrictions, since it goes beyond just the webui:
This allows you to increase the output power of the signal amplifier beyond the European legal limit (100 mw) and give you better WiFi coverage.What does this allow you to do ? Pick a different frequency ?
@RMerlin lets wait for the next official firmware release then. Maybe Asus finishes developing it meantime. If not, did you consider implementing that yourself?
Dual WAN is an experimental feature, so it's possible that some functions might not be fully working yet.
to firewall-start script. Result was very stange. This command fully block NAS access from internal network after reboot.iptables -i ppp0 -I INPUT -p tcp --dport <UNSTANDARD SSH PORT> -j ACCEPT
Opening router ports should be done in the firewall-start script.
The nat table is only for port forwarding. For services directly running on the router, you need to adjust the INPUT chain in the default filter table.
Virtual Servers only relate to NAT, so it does not apply for the router's own ssh access.
I will assume this was the answer to both me and avp. Do I need to adjust the INPUT chain myself for services NOT running directly on the router?
Because at the moment this does not work as expected. I create simple "Virtual Server" entry for a service running on my PC and the INPUT chain is not being modified! Only the NAT table is.
And what If I wanted to do NAT the following way: access SSH internally on port 22 but externally on port 443, for instance. Then I would still need a NAT rule even for the router itself (which is what I did in the Virtual Server page but still there was no corresponding INPUT chain modification to accept connections on port 443).
In other words I am trying to say that the "Virtual Server" feature is broken, at least for me. The ports are forwarded OK but incoming connections are not allowed on those ports if you use standard web interface to configure it.
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!