Search results

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. T

    Asuswrt-Merlin 3.0.0.4.374.38 is out

    this is the same problem that Merlin already fixed in some not yet released code. Change "Connect to DNS server automatically" to Enable, click Apply, and reboot the router. Of course, this will make you use the ISPs ipv6 dns servers rather than your custom ones. Merlin's next release...
  2. T

    Asuswrt-Merlin 3.0.0.4.374.38 is out

    telnet to port 80 is fine if he's trying to check if the router's web UI is available (http is port 80). He shouldn't get a connection refused to port 80 on the router's IP address, the router's internal webserver has crashed or become unresponsive.
  3. T

    Asuswrt-Merlin 3.0.0.4.374.38 is out

    Thanks Merlin. I had just noticed the broken dhcp file myself :) the 374.38_1 code still produces a working IPv6 connection for me as long as I use Comcast DNS, so I don't need to downgrade necessarily. Thanks for the quick fix!
  4. T

    Asuswrt-Merlin 3.0.0.4.374.38 is out

    I had difficulty with this also. I suspect there may be a bug with the IPv6 DNS settings in the .38 build. In 3.0.0.4.374.37, I had set "Connect to DNS Server automatically" in the IPv6 settings to "Off" so I could use a different set of IPv6 DNS servers other than those automatically supplied...
  5. T

    unsupported NAT-PMP version

    No problem RMerlin. I don't have a burning use case for it, mostly wanted to point out the source of the log error message since it had puzzled people before.
  6. T

    unsupported NAT-PMP version

    RMerlin, you might try http://sourceforge.net/projects/pcptestingsuits/ appears to be a PCP testing tool from some engineers at France Telecom. It requires Apache + PHP, either on Windows or Linux.
  7. T

    unsupported NAT-PMP version

    This message also occurs if you have the "Back to My Mac" feature in Mac OS turned on (assuming you have a Mac on your network) "Back to My Mac" allows you to remotely login to your Mac, as such it needs to open ports on the router for the feature to work (TCP port 5354 and UDP ports 4500 and...
Top