Recent content by rhester72

  1. R

    Manually release WAN DHCP lease?

    I don't think that's accurate, because a) when you release a lease on Windows, for instance, tcpdump absolutely shows an explicit release being broadcast, and b) when swapping the Verizon-supplied Actiontec router for customer equipment (like, say, AsusWRT), explicitly releasing the lease...
  2. R

    Manually release WAN DHCP lease?

    How is it done on AsusWRT/Merlin? I have a lease locked on FiOS via my RT-N66U and can't seem to get it to release, even when I disable the WAN. Any way to do so via GUI or CLI? Rodney
  3. R

    DNS - is this "normal"?

    By the way, if you aren't sure how to generate these stats, you can do so without disruption (on a one-time basis) via ssh by issuing the following: killall -s USR1 dnsmasq and then looking at your system log (either via GUI or by issuing "tail /tmp/syslog.log" on the router via SSH)...
  4. R

    DNS - is this "normal"?

    Even more interesting data: If I enable strict-order, my failure rate drops from ~10% to about 0.25%. :/ Rodney
  5. R

    DNS - is this "normal"?

    Running a very standard setup on 75/75 FiOS, using Google Public DNS for my upstream resolvers (IPv4 via Verizon and IPv6 via Hurricane Electric). I've noticed the following stats: Nov 1 16:19:33 172.16.0.1 dnsmasq[6461]: server 2001:4860:4860::8844#53: queries sent 27327, retried or...
  6. R

    resolv.conf bug?

    Ahhhhhhh...now it makes perfect sense! Thank you! :) Rodney
  7. R

    resolv.conf bug?

    The fix he referenced was about 127.0.0.1 not appearing in /etc/resolv.conf, and from the diff, it is indeed fixed. That's why I asked the second question, because unless there was another fix, that means that /etc/resolv.conf now contains 127.0.0.1 *and* the IPv4 DNS servers, when it should...
  8. R

    resolv.conf bug?

    I suppose that's where my confusion is coming from. On current stable, this is what I'm seeing in AsusWRT Merlin having defined Google public DNS servers as the "WAN DNS" servers in the GUI: admin@cerberus:/tmp/home/root# cat /etc/resolv.conf nameserver 8.8.8.8 nameserver 8.8.4.4 derived...
  9. R

    resolv.conf bug?

    Thanks! Since upstream IPv4 servers appear to have previously been stored in resolv.conf (and thus picked up by dnsmasq), were those "relocated" as well? Rodney
  10. R

    resolv.conf bug?

    Firmware version 3.0.0.4.376.47_0 on a RT-N66U For local (i.e. on the router itself) name resolution in a standard dnsmasq setup, /etc/resolv.conf should _always_ be populated with 127.0.0.1. When setting "Connect to DNS Server automatically" to No (I'm using unbound locally), any entries in...
  11. R

    Unusual wireless request

    I went with your build for the performance above what Tomato can deliver on this specific hardware - doing it with Tomato is ugly for entirely different reasons. =) Thanks for the input re. wireless clients on AsusWRT. Rodney
  12. R

    Unusual wireless request

    That would no doubt, have the effect of restarting wireless - what I'm trying to understand is how I'd go about manually (i.e. in a script) setting up the wireless connection in the first place. Setting up the routing is no issue, I just don't know how to set up being a wireless WPA2 client *on...
  13. R

    Unusual wireless request

    Some things I'd like to quickly get out of the way: - I was one of the Tomato developers for many years - I know my way around a router ;) - I know what I'm trying to achieve can't be done via the GUI, and may not be possible at all, but ideally could be scripted My basic setup is that I...
Back
Top