1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice

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!

AC86U - Doesn't like wired devices

Discussion in 'Asuswrt-Merlin' started by Draken, Feb 22, 2020.

  1. Draken

    Draken Occasional Visitor

    Joined:
    Feb 8, 2020
    Messages:
    21
    After been a bit unsuccessful/unlucky with the 88U I returned it for a 86U. The installation went smoother but I have a pretty annoying issue with the wired devices.

    I have a 86U acting as the main router and a 68U connected as an AiMesh Node (no hard wire).

    The 68U node serves two desktop PC (connected via powerline) and a few other wired devices.

    The main router itself serves a couple of RaspberryPis, an android box and a TV (all connected through LAN).

    The two desktop PCs connected on the 68U seem to be OK but none of the other devices connected via LAN seem to see the outside world. Some of the devices are actually connected directly to the LAN ports of the 86U and still they cannot see any WAN and are only accessible through my internal network.

    Any ideas on what I can try.
     
  2. OzarkEdge

    OzarkEdge Part of the Furniture

    Joined:
    Feb 14, 2018
    Messages:
    2,195
    Location:
    USA
    Why did you add the 68U node if clients wired to the router are not working correctly? I would step through the install again and only proceed when successful. Maybe the 88U install did not fail on bad luck.

    My 86U install notes (using stock firmware) might help.

    OE
     
    QuikSilver likes this.
  3. Draken

    Draken Occasional Visitor

    Joined:
    Feb 8, 2020
    Messages:
    21
    Thanks for the reply. All has been resolved. It had to do with the local DNS I am using. The process was not as straight forward as I would have thought.